Davis Apps DBA

Overview of AutoConfig RC-50014 Error During Oracle E-Business Suite (EBS) cloning, environment patching, or system configuration updates, running adconfig.sh (AutoConfig) is mandatory to synchronize context files with system templates. A common failure during the ApplyApplTop execution phase triggers the error: ERROR: RC-50014: Fatal: Execution of AutoConfig failed This error indicates that the underlying deployment script was unable to execute terminal commands or write XML driver properties to the application file system, bringing the clone or patching process to a complete halt. Root Causes The RC-50014 exception usually points to one of three underlying system issues: Permission Mismatches: The Linux account running AutoConfig lacks read/write/execute permissions on APPL_TOP or sub-directories (e.g., inst/apps/$CONTEXT_NAME/admin/log ). Environment Variable Corruption: Missing or incorrectly set PATH , LD_LIBRARY_PATH , or ORACLE_HOME variables in the APPS tier environment f...

 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 to it based on the case. So I thought to make a post on this issue. Issue Faced After I entered creds to login to my R12.2, faced the below screen. On checking the log found the below issue. From the issue, I understood something is not correct with the port 12345. So I checked metalink and found two documents talks about the same issue. So I followed the test cases described there and the results from my environment are same as the results of oracle document.  In my case the instance where I'm facing the issue is not a recently cloned one. It was running fine for the past few months and no recent changes were done either at Instance or Network or Firewall level. So I came to a conclusion that this issue is not related to port.  So I decided to take a bounce of my managed servers (OA core) alone. After the bounce, behavior of my inst...

REP-3000 Issue is very common in Oracle Apps environments. If this issue persists, concurrent programs will complete with error code(Whose output is in PDF format). Generally this affects the OPP operations. I've faced this issue in both Linux and Unix platforms. The reason for this issue is common on both the platforms. Improper setting of the DISPLAY variable is the reason for this issue. In my environment, I recently faced this issue in EBS 11i Instance which runs on RHEL-5.11. Below are the detailed step by step process I followed to overcome this issue. When submitted 'Active Users' report it completed with error. When checked the log file found the below issue. Here it is understood, the issue is due to improper DISPLAY variable setting. So I start to work on setting the DISPLAY variable properly. In my server, display variable is set to value "localhost:10.0". Now I need to check whether this value is proper and can open xclock and windows using this Displa...

Sometimes we may forget the password we set for weblogic. At such times this method will be very much helpful.   Below is the step by step process to decrypt the password for weblogic. Take a backup of the boot.properties file Note the value of encrypted password Now invoke the WebLogic scripting tool                                                                                            sh wlst.sh Pass the values for Domain, service, encryption and password                                                  wls:/offline> domain = "<Domain Value>" wls:/offline> service = weblogic.security.internal.SerializedSystemIn...

After completed cloning of EBS-12.2.4, working on the post clone activities. When tried to change the APPS and SYSADMIN passwords using FNDCPASS utility faced the below issue. This is the first time I'm facing this issue. I can't understand why this issue has occurred as I didn't face any issues during cloning. Below is the step by step process to overcome this issue. Create two scripts 'rmcorejvm.sql' & 'corejvminst.sql' and execute them on the DB Tier. Content of rmcorejvm.sql connect / as sysdba set echo on set serveroutput on select * from v$instance; select owner, status, count(*) from all_objects where object_type like '%JAVA%' group by owner, status; execute rmjvm.run(false); shutdown immediate set echo off spool off exit Content of  corejvminst .sql set serveroutput on set echo on startup mount alter system set "_system_trig_enabled" = false scope=memory; alter database open; select owner, status, count(*) from all_objects where...

By default EM Express Console is not enabled in 18.1.0.0, 12.2.0.1 and 12.1.0.2 databases.  Below is the step by step process to enable EM Express Console in Oracle Database. In my environment, I had enabled the EM Console at PDB level. Before enabling the console listener status would be To enable the console and set its port Now confirm the listener is listening on the port '5500'. Now to open the port '5500' on DB system, follow the below steps Once the DB port is opened, update your security list in OCI console. To do this on an existing security list, follow the below steps. Open the  navigation menu . Under  Oracle Database , click ( Bare Metal / VM / Exadata)  ---> as per your environment Choose your  Compartment . A list of DB systems is displayed. Locate the DB system in the list. Note the DB system's  Subnet  name and click its  Virtual Cloud Network . Locate the subnet in the list, and then click its security list under...