Thursday, July 20, 2017

ORA-20001 FND_CANT_INSERT_USER_ROLE


Issue : ORA-20001 FND_CANT_INSERT_USER_ROLE














After searching, got a Document from Oracle Support which suits this exact issue.


Solution:

Run concurrent program "Workflow Directory Services User/Role Validation" 
    with parameters : 100000, Yes, Yes, No.



Once the program completed successfully, Functional Administrator Responsibility and other responsibility which is not visible in the Navigator will be available now.





Issue is solved.

Ref : ORA-20001 FND_CANT_INSERT_USER_ROLE After Upgrading To Release 12.0.2 (Doc ID 454988.1)

Sunday, July 9, 2017

Common R12.2 adcfgclone Issues

ERROR: Failed to configure the target system – Failed to enable EBS_LOGON trigger
The clone procedure for EBS R12.2 is quite different when compared with EBS R12.1. This post covers very generic  issues we may encounter while configuring the target server as a part of clone Process.


ERROR : 1
Checking the port pool 6
done: Port Pool 6 is free
Report file located at /u01/appl_PROD/PROD/fs2/inst/apps/PRODERP_erpnode3/admin/out/portpool.lst
The new APPL_TOP context file has been created :
/u01/appl_PROD/PROD/fs2/inst/apps/PRODERP_erpnode3/appl/admin/PRODERP_erpnode3.xml
Check Clone Context logfile /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/bin/CloneContextPatch_0811105848.log for details.

FMW Pre-requisite check log file location : /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/FMW/logs/prereqcheck.log
Running: FMW pre-req check...
ERROR: Run file system configuration has failed
Check the logfile /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/log/clone/run/RCloneApplyAppstier_08111059.log

ERROR: Failed to configure the target system,
please check the logfile in : /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/log/clone
Enter the APPS password : Enter the APPS password : Error while executing /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/bin/alter_ebs_logon_trigger.sql
Failed to enable EBS_LOGON trigger
When we check the logfile its mentioning FMW_Home already exists.
[root@erpnode3 run]# tail -100f /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/log/clone/run/RCloneApplyAppstier_08111059.log
#############################################################
Started RCloneApplyAppstier at Thu Aug 11 10:59:37 AST 2016
Version:
RCloneApplyAppstier.java : 120.0.12020000.4
#############################################################
Found the directory : /u01/appl_PROD/PROD/fs1/FMW_Home
Exiting cloning as FMW Home already exists..

Solution:
We must remove the directory FMW_Home. If the directory is empty also we should remove it, else rapidclone will exit out with status Error.



ERROR : 2
The error message is almost identical to the previous error in the clone configuration output.
Report file located at /u01/appl_PROD/PROD/fs2/inst/apps/PRODERP_erpnode3/admin/out/portpool.lst
The new APPL_TOP context file has been created :
/u01/appl_PROD/PROD/fs2/inst/apps/PRODERP_erpnode3/appl/admin/PRODERP_erpnode3.xml
Check Clone Context logfile /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/bin/CloneContextPatch_0811110821.log for details.

FMW Pre-requisite check log file location : /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/FMW/logs/prereqcheck.log
Running: FMW pre-req check...

Configuring: Run file system....
LogFile located at /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/log/clone/run/RCloneApplyAppstier_08111108.log

ERROR: Failed to configure the target system,
please check the logfile in : /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/log/clone
Error while executing /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/bin/alter_ebs_logon_trigger.sql
Failed to enable EBS_LOGON trigger
[applerp@erpnode3 bin]$
But this time the message in error log is different:
[root@erpnode3 inst]# more /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/log/clone/run/RCloneApplyAppstier_08111108.log
#############################################################
Started RCloneApplyAppstier at Thu Aug 11 11:08:36 AST 2016
Version:
RCloneApplyAppstier.java : 120.0.12020000.4
#############################################################

START: Calling ApplyAppsTier...

START: Creating the FMW Home from ApplyAppsTier
FMW JDK version in use: 1.7.0_85

START: Creating FMW Home.
Running /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/FMW/pasteBinary.sh -javaHome /u01/appl_PROD/PROD/fs1/EBSapps/comn/util/jdk64 -al /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/FMW/FMW_Home.jar -tl /
u01/appl_PROD/PROD/fs1/FMW_Home -invPtrLoc /etc/oraInst.loc -ldl /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/log/clone/run/fmwT2PApply -silent true -debug true -executeSysPrereqs false
Script Executed in 7558 milliseconds, returning status 255
ERROR: Script failed, exit code 255
[root@erpnode3 inst]#

Solution:
usually we will recieve this error when there are no proper privileges granted on oraInventory  (or) the oraInventory is not empty. To avoid this issue we should verify “oraInventory” directory has appropriate privileges and its empty.
[root@erpnode3 u01]# mkdir -p /u01/ora_prod/oraInventory
[root@erpnode3 u01]# chmod -R 755 /u01/ora_prod/oraInventory
[root@erpnode3 u01]# chown -R applerp:dbaerp /u01/ora_prod/oraInventory
[root@erpnode3 u01]# cat /etc/oraInst.loc
inventory_loc=/u01/ora_prod/oraInventory
inst_group=dba
[root@erpnode3 u01]#

During the R12.2 cloning process adcfgclone fails with below error message:



ERROR : 3
Below Oracle Homes are already registered in the global inventory:
/u01/oracle/R122/fs1/FMW_Home/oracle_common
/u01/oracle/R122/fs1/FMW_Home/webtier
/u01/oracle/R122/fs1/FMW_Home/Oracle_EBS-app1

Solution:
Make sure that the above Oracle Homes are unregistered from the global inventory. we should always clean the oraInventory directory by using the following commands.
cd $ORACLE_HOME/oui/bin  (/u01/oracle/R122/fs1/EBSapps/10.1.2/oui/bin)
./runInstaller -silent -deinstall REMOVE_HOMES={“/u01/oracle/R122/fs1/FMW_Home/Oracle_EBS-app1”}
./runInstaller -silent -deinstall REMOVE_HOMES={“/u01/oracle/R122/fs1/FMW_Home/oracle_common”}
./runInstaller -silent -deinstall REMOVE_HOMES={“/u01/oracle/R122/fs1/FMW_Home/webtier”}
Then restart the adcfgclone.pl appsTier

REP-0004: Warning: Unable to open user preference file.

Issue :
----------
Enter Password:
REP-0004: Warning: Unable to open user preference file.
REP-0069: Internal error
REP-57054: In-process job terminated:Finished successfully but output is voided

Report Builder: Release 10.1.2.2.0 - Production on Sat Jun 24 06:48:27 2017

Cause:

Your local (customized) Oracle Reports preference file could not be opened.
This is just a warning, so the product will continue to run even if this occurs.
The possible causes of this error include the following:

Case 1: The file was not found under the specified name in the specified location.

Case 2: You lacked the necessary privileges to open the file.

Case 3: A system error made it impossible to open the file.

Action:
-----------

You can take the following actions to rectify this error:

Case 1: Make sure the file prefs.ora is located in your "home" directory.

Case 2: Make sure that you have the privileges necessary to access the file. If you don't, change your privileges accordingly.

Case 3: Consult your operating system documentation or contact your system administrator.

======================================================================

The preferences file referred to above is:

Windows
ORACLE_HOME\CAUPREFS.ORA (user preferences)
ORACLE_HOME\CAGPREFS.ORA (global preferences)

UNIX
your_home_directory/prefs.ora (user preferences)
$ORACLE_HOME/tools/admin/prefs.ora (global preferences)

===================================================================== 
Simple Way:

Check whether u have prefs.ora file in your application user's home

eg: prefs file should be in /home/applmg/prefs.ora

if not please copy prefs.ora file from  $ORACLE_HOME/tools/admin/prefs.ora  to /home/applmg/prefs.ora location.

Run your concurrent request/program.



Common Cloning Issues


Issue : 1

-----------



After upgradation from DB 10.2.0.3 to 11.2.0.4 in OEL 4.6 of Release 12.2.5 application, did the autoconfig and preclone process successfully in both db and apps tier.

While cloning to the target instance getting error from DbTier.

$perl adcfgclone.pl dbTier

[AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution.  Errors are grouped by directory and phase.
The report format is:
[filename]  [phase]  [return code where appropriate]

[APPLY PHASE]
AutoConfig could not successfully execute the following scripts:
Directory: /u01/oracle/AJI/db/tech_st/11.2.0/perl/bin/perl -I /u01/oracle/AJI/db/tech_st/11.2.0/perl/lib/5.8.3 -I /u01/oracle/AJI/db/tech_st/11.2.0/perl/lib/site_perl/5.8.3 -I /u01/oracle/AJI/db/tech_st/11.2.0/appsutil/perl /u01/oracle/AJI/db/tech_st/11.2.0/appsutil/clone
ouicli.pl   INSTE8_APPLY 255

AutoConfig is exiting with status 1

RC-50013: Fatal: Instantiate driver did not complete successfully.
/u01/oracle/AJI/db/tech_st/11.2.0/appsutil/driver/regclone.drv

Solution :
--------------

I have resolved this issue by copying java folder to the appsutil folder. I have already installed the latest Java 6.0. The issue is caused by [DB oracle home]/appsutil not containing the jre directory

$cp -R /usr/java/jdk1.6.0_16/  $ORACLE_HOME/appsutil/jre

Again run the cloning process,
perl adcfgclone.pl dbTier

ApplyDatabase Completed Successfully.

Issue : 2


-----------


 perl adcfgclone.pl dbTier fails with below error

WARNING: [AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution.  Errors are grouped by directory and phase.
The report format is:
      <filename>  <phase>  <return code where appropriate>

  [APPLY PHASE]
  AutoConfig could not successfully execute the following scripts:
    Directory: /tlcc/db/tech_st/11.2.0.4/perl/bin/perl -I /tlcc/db/tech_st/11.2.0.4/perl/lib/5.10.0 -I /tlcc/db/tech_st/11.2.0.4/perl/lib/site_perl/5.10.0 -I /tlcc/db/tech_st/11.2.0.4/appsutil/perl /tlcc/db/tech_st/11.2.0.4/appsutil/clone
      ouicli.pl               INSTE8_APPLY       1



AutoConfig is exiting with status 1

Cause:

The script was trying to register the oracle home in inventory but its failing to update it.

Solution:


We need to ensure there are no files currently located in the Inventory directory, If there are any files in this directory then we should delete these files.


Issue : 3

--------------


perl adcfgclone.pl dbTier fails with RC-00110

Error:

APPS Password : Log file located at /d01/PREPROD/oradb/11.2.0.3/appsutil/log/PREPROD_rgovis/ApplyDBTechStack_12201105.log
  \      0% completed       RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack

ERROR while running Apply...
Sat Dec 20 11:06:07 2014

 ERROR: Failed to execute /d01/PREPROD/oradb/11.2.0.3/appsutil/clone/bin/adclone.pl

 Please check logfile.


 Detail log :/d01/PREPROD/oradb/11.2.0.3/appsutil/log/PREPROD_rgovis/ApplyDBTechStack_12201105.log
[AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution.  Errors are grouped by directory and phase.
The report format is:
      <filename>  <phase>  <return code where appropriate>

  [APPLY PHASE]
  AutoConfig could not successfully execute the following scripts:
    Directory: /d01/PREPROD/oradb/11.2.0.3/perl/bin/perl -I /d01/PREPROD/oradb/11.2.0.3/perl/lib/5.8.3 -I /d01/PREPROD/oradb/11.2.0.3/perl/lib/site_perl/5.8.3 -I /d01/PREPROD/oradb/11.2.0.3/appsutil/perl /d01/PREPROD/oradb/11.2.0.3/appsutil/clone
      ouicli.pl               INSTE8_APPLY       255


AutoConfig is exiting with status 1

RC-50013: Fatal: Instantiate driver did not complete successfully.
/d01/PREPROD/oradb/11.2.0.3/appsutil/driver/regclone.drv

Solution:

Set the perl to point to the <ORACLE_HOME>/perl/bin
Eg:
 export PATH=<ORACLE_HOME>/perl/bin:$PATH  


Issue : 4

-----------

 

ORACLE instance shut down.
Connected to an idle instance.
ORACLE instance started.

Total System Global Area 1071333376 bytes
Fixed Size                  1369420 bytes
Variable Size             436210356 bytes
Database Buffers          620756992 bytes
Redo Buffers               12996608 bytes

Control file created.


Database altered.


Tablespace altered.


Tablespace altered.


Database altered.

PL/SQL procedure successfully completed.


File created.

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
exit_code=0

Checking for errors ...


.end std out.

.end err out.


---------------------------------------------------------------
                   ADX Database Utility
---------------------------------------------------------------

getConnectionUsingAppsJDBCConnector() -->
    APPS_JDBC_URL='null'
    Trying to get connection using SID based connect descriptor
getConnection() -->
    sDbHost    : lcctest9
    sDbDomain  : lakshmicardclothing.com
    sDbPort    : 1523
    sDbSid     : dlcc
    sDbUser    : apps
    Trying to connect using SID...
getConnectionUsingSID() -->
    JDBC URL: jdbc:oracle:thin:@lcctest9.lakshmicardclothing.com:1523:dlcc
    Exception occurred: java.sql.SQLException: IO Error: The Network Adapter could not establish the connection
    Trying to connect using SID as ServiceName
getConnectionUsingServiceName() -->
    JDBC URL: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=lcctest9.lakshmicardclothing.com)(PORT=1523))(CONNECT_DATA=(SERVICE_NAME=dlcc)))
    Exception occurred: java.sql.SQLException: IO Error: The Network Adapter could not establish the connection
    Trying to connect using SID as ServiceName.DomainName
getConnectionUsingServiceName() -->
JDBC URL: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=lcctest9.lakshmicardclothing.com)(PORT=1523))(CONNECT_DATA=(SERVICE_NAME=dlcc.lakshmicardclothing.com)))
    Exception occurred: java.sql.SQLException: IO Error: The Network Adapter could not establish the connection
    Connection could not be obtained; returning null

-------------------ADX Database Utility Finished---------------

RC-00118: Error occurred during creation of database
Raised by oracle.apps.ad.clone.ApplyDatabase

Solution:
-------------
Workaround Done :-

1. Modify the Contextfile 'CTXORIG.xml', whcih is created by the pre-cloning script, which is found under the Database $ORACLE_HOME/appsutil/clone/context/db directory :

ORIGINAL :
<DB_LISTENER oa_var="s_db_listener" default=""><Name of the SOURCE DB listener></DB_LISTENER>

ACTION Taken:

UPDATE the file with the SID name of the TARGET Instance, e.g. TEST :

<DB_LISTENER oa_var="s_db_listener" default=""><Name of the TARGET DB listener></DB_LISTENER>

execute 'perl adcfgclone.pl dbTier <physical Path to the DB Tier Contextfile>

Or

You can restart the adcfgclone after making the required changes.

Issue : 5

-----------

Executing service control script:
/dlcc/apps/inst/apps/dlcc_lcctest9/admin/scripts/adformsctl.sh start
Timeout specified in context file: 100 second(s)

script returned:
****************************************************

You are running adformsctl.sh  version 120.12.12000000.6

Starting OPMN managed FORMS OC4J instance  ...
Calling txkChkFormsDeployment.pl to check whether latest FORMSAPP.EAR is deployed...
ERROR processing <arg> txkrgf : Argument value cannot be an empty string
Error while executing the perl script txkChkFormsDeployment.pl
/dlcc/apps/inst/apps/dlcc_lcctest9/logs/appl/admin/log/adformsctl.txt


adformsctl.sh: exiting with status 1

Tried adstpall and below is the status

Executing service control script:
/dlcc/apps/inst/apps/dlcc_lcctest9/admin/scripts/adformsctl.sh stop
script returned:
****************************************************

You are running adformsctl.sh  version 120.12.12000000.6

Stopping OPMN managed FORMS OC4J instance  ...

adformsctl.sh: exiting with status 150

-------------------------------------------------------------------------------------------

Workaround
-------------------
Simply again tried adstrtal.sh and this time all the services are started properly and
adstrtal.sh exited with status 0.





IAS Cache initialization failed

 Today I faced an Issue in R12.2 instance. The solution I followed to overcome the issue is very simple, but they are more than one solution...