Davis Apps DBA

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...

Recently I migrated a database(11gR1) from Windows Platform to 12C on Linux Platform. Migration was successful. During the sanity check, found lot of Invalid objects even after all the grants and privileges were provided. Ran utlrp.sql couple times, still the invalids count remains the same. So I choose an Invalid object, compiled it manually and faced the below issue. This was the issue for almost all the invalid objects. So I understood something is not right with the object DBMS_OUTPUT. So I checked this object and to my surprise it was valid. Since the status is Valid, before doing any change to the object 'DBMS_OUTPUT', I decided to check the coding of the invalid object, since the DBMS_OUTPUT is an oracle standard one. If I comment the line "dbms_output.put_line" from the invalid object, it is getting compiled and then it is a valid one but this is not the solution. This can be accepted as an workaround when a minimal no.of objects becomes invalid due to this is...

 In one of our environment, post migration we tested the SEND_MAIL procedure to initiate the mail via SMTP server from DB level and faced the below issue. ORA-01775: looping chain of synonyms Looping chain of synonyms means, the created synonyms points to another object in a circle. Here for better understanding, SEND_MAIL is the procedure used to trigger mails from DB Server UTL_SMTP and DBMS_OUTPUT are the dependent objects for SEND_MAIL procedure UTL_SMTP synonym is also dependent object for SEND_MAIL procedure So it is clearly evident that the dependent objects should be valid before fixing the issues with the SEND_MAIL procedure. So, I started the drilldown on the required dependent objects and found the procedure 'SEND_MAIL' and package body of the object 'UTL_SMTP' is invalid. So I made an attempt to compile the UTL_SMTP body to make it a valid object and faced the below issue. This issue indicates the format of the wrapped unit being compiled is not understood b...