Oracle Applications

adop give below error at prepare stage when trying to apply patch with phase=prepare optin *******FATAL ERROR******* PROGRAM : (/test/app01/appl/fs1/EBSapps/appl/ad/12.0.0/bin/adzdoptl.pl) TIME : Sat Apr 6 20:02:22 2013 FUNCTION: ADOP::Phase::executeSQL [ Level 1 ] ERRORMSG: Invalid Credentials adop patch log file has below error: AutoPatch error: The following ORACLE error: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor Procedure to Solve the Problem There may be multiple reasons for this error, Following are known causes: 1) ebs_patch service is not registered in listener due to local_listener parameter set . 2.local_listener is not define in init.ora. Solution: 1. Add following line to init.ora: local_listener = SID_LOCAL In this SID is database instance name. e.g local_listener = test_LOCAL SQL> alter system set service_names='test','ebs_patch','test_patch' scope=memory; System alter

1.       To run Autoconfig from the patch file system you must disable trigger ebs_login prior to running autoconfig. SQL> show user; USER is "SYSTEM" SQL> alter trigger ebs_logon disable; Trigger altered. 2.       Now run autoconfig with the patch env sourced [appltest@test001]$ echo $FILE_EDITION [appltest@test001]$patch [appltest@test001]$ adautocfg.sh Make sure Autoconfig completes ok      3. Enable the login trigger “alter trigger ebs_logon enable”                  SQL> conn system/Oracle4u                  Connected.                SQL> SQL> alter trigger ebs_logon enable;                 Trigger altered.

We had first cutover after 12.2 patching in production instance  , After the cutover, When instance is released to client, Client was getting the below error while accessing discoverer using the responsibility from EBS. We observed that the both the discoverer URL and EBS URL are in different domain which caused the issue 1. We changed the discoverer profile options in EBS and also updated the context file with the updated discoverer urls From - ICX: Discover Launcher – http://test001.test.com:8090/discoverer/plus?Connect=[APPS_SECURE] ICX :Discover Viewer Launcher http://test001.test.com:8090/discoverer/viewer?Connect=[APPS_SECURE] To – ICX:Discoverer Launcher - http://test001.testnet.com:8090/discoverer/plus?Connect=[APPS_SECURE] ICX :Discover Viewer Launcher http://test001.testnet.com:8090/discoverer/viewer?Connect=[APPS_SECURE] Update the below context file entry to new URL -bash-4.1$ grep  s_disco $CONTEXT_FILE          <disco_url oa_var="s_disco_url&qu

P While we were performing the clone from RMAN backup, Recovery was failing with the below error ORA-00279: change 5969245693131 generated at 06/10/2016 23:02:11 needed for thread 1 ORA-00289: suggestion : /test/arc01/test_1_32850_869208143.arc ORA-00280: change 5969245693131 for thread 1 is in sequence #32850 ORA-00278: log file '/test/arc01/test_1_32849_869208143.arc' no longer needed for this recovery ORA-00317: file type 0 in header is not log file ORA-00334: archived log: '/test/arc01/test_1_32850_869208143.arc' ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below ORA-01152: file 1 was not restored from a sufficiently old backup ORA-01110: data file 1: '/test/data01/system01.dbf' Below were the steps performed to resolve the issue 1 .We have checked the archive log size and did not find any issues with archive log size. 2. After checking the Metalink, We observed that the issue occurs when th

The customer is getting error   Frm-40735, ORA-04062: signature of package while trying to submit the concurrent request Below is the error customer is getting while submitting Create Auto Adjustments. 1. First we have compiled all the invalid objects as the invalid count was higher, Invalid count was decreased and we have retested the issue and the issue still exists. 2 .We have reviewed the note id 296700.1 which matches the error we are getting for our concurrent request 3. As per the Metalink id, We have compiled the ARXSUBAA.pld and ARXSUBAA.fmb using the adadmin First, compiled the library which is calling fnd_request - ARXSUBAA.pld Then Compile the form - ARXSUBAA.fmb 4.Below are the steps we followed a)Select Generate applications files menu b)Select Generate form files c)Provide the pld and fmb file to compile using below options d)make sure the forms are su

After Maintenance, The Report related Concurrent requests failing with SYSTEM-UNABLE TO SET NLS SORT,  Below is the error in concurrent request log file +----------------------------- | Starting concurrent program execution... +----------------------------- SYSTEM-UNABLE TO SET NLS SORT Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 48389631. Review your concurrent request log and/or report output file for more detailed information. 2.   We have ran "Generate concurrent processing environment information" and we see the below messages in the output of the request Value of NLS_SORT has changed since startup. Startup value: BINARY Current value:  3.We have reviewed the Metalink id 2150302.1 which matches the issue for R12 instances and performed the below steps 1. Navigate to the following screen to update the profile:     System Administrator==Profile==System 2. Search for Profile

1.Patch application was failing with the below error in Non production instance /usr/bin/ld: cannot find -lclntsh 2.We observed that the issue was due to libclntsh soft link which was incorrect, As you can see below the soft link was pointing to the PROD 3. Run the script  $ORACLE_HOME/bin/genclntsh which will fix the soft link issue [appstest@test001]$ sh genclntsh [appstest@test001]$ [appstest@test001]$ pwd /ebs/oracle/TEST/apps/tech_st/10.1.2/bin 4.Check the soft link  of libclntsh  again which will be corrected by the script we have run in 3 rd script as seen in below screenshot. 5.Run the relink again which will be successfully now

Please follow below steps 1.        Run adpreclone.pl on the target run file system to build the patch file system 2.        Copy over  the EBSapps from the run FS over to the patch FS 3.        Go to the patch file system and run adcfgclone.pl  from the <COMMON_TOP>/clone/bin of the patch file system. ·        When asked file system type, enter patch ·        When asked for the run file system  context file, please provide the complete path ·        When asked for the port pool, pass 0(based on the DB port) Make sure adcfgclone for patch FS completes successfully 

When we are performing a clone, We observed concurrent managers were not coming up due to node name issue, We tried to run autoconfig, But adgendbc of autoconifg was failing with below issue java.sql.SQLException: ORA-01403: no data found ORA-06512: at "APPS.FND_APP_SERVER_PKG", line 298 ORA-06512: at line 1   1.As per the error report we observed that the issue was due to lower case of concurrent manager node name SQL> select node_name from apps.fnd_nodes; NODE_NAME ------------------------------ AUTHENTICATION ebstestapp EBSTESTDB 2. The metalink id 1539713.1 matches the error we are facing and we performed the below steps which resolved the issue. A. Clean the FND_NODES Execute following commands in SQLPlus : SQL>EXEC FND_CONC_CLONE.SETUP_CLEAN; SQL>COMMIT; SQL>EXIT; B. Run autoconfig.sh C. Make a backup copy of the existing FND_NODES table then run the command in SQLPLUS to set the node_name to upper case: SQ

      We observed that the Concurrent Reports in Running Normal Forever status after 11.2.0.4 Database upgrade, Below were the steps done to fix the issue. 1.We have run the below command as per metalink document  R12 : Concurrent Reports in Running Normal Forever (Doc ID 1337005.1) and was able to fix the issue [appstest@test001]$ $INST_TOP/ora/10.1.2/bin/appsrwrun.sh userid=apps/xxx  mode=character report=$FND_TOP/reports/US/FNDSCURS.rdf batch=yes destype=file desname=./ddr2.out desformat=$FND_TOP/reports/HPL pagesize=132x66 traceopts=trace_all tracefile=ddr2.trc tracemode=trace_replace 2. The appsrwrun script was showing below error when we have checked the trace file ddr2.trc [2016/3/7 3:30:59:794] Exception 54005 (): Unable to create cache directory /ebs/oracle/TEST/inst/apps/appstest@test001/logs/ora/10.1.2/reports/cache oracle.reports.RWException: IDL:oracle/reports/RWException:1.0         at oracle.reports.utility.Utility.newRWException(Utility.java:758)         at or

1.In one of our 12.2.3 instance we observed that the mwa dispatcher was not coming up ,When we have checked the log file we found the below segmentation faults errors /TEST/app01/appl/fs2/inst/apps/TEST_test001/admin/scripts/mwactl.sh: line 237: 17932 Segmentation fault      ${MWA_TOP}/bin/MWADIS 2.We checked for the dispatcher port and it was available [appltest@test001]$ netstat -anp |grep 10616 (Not all processes could be identified, non-owned process info  will not be shown, you would have to be root to see it all.) 3. This issue is documented in Internal Bug 17459700  - MWACTL.SH START_DISPATCHER CAN NOT BE STARTED. smwaenv.h has been rebuilt and sets the relative path of mwa.cfg to  "/admin/install/mwa.cfg" 4. Observed that patch is not applied in our instance SQL> select bug_number,creation_date from apps.ad_bugs where bug_number='17459700'; no rows selected SQL> select name from v$database; NAME --------- TEST 5.After applying the pa

      1 .Below error was shown in the RMAN error log  while running the backup ORA-19554: error allocating device, device type: SBT_TAPE, device name: ORA-27211: Failed to load Media Management Library 2. The error was due to libobk.so soft link which was missing in new Oracle Home, Please create the soft link using specified steps below as per Metalink ID 1395024.1 [oratest@test]$ cd $ORACLE_HOME/lib  [oratest@test]$ ls -ltr /usr/openv/netbackup/bin/libobk.so64 -r-xr-xr-x 1 root daemon 1403655 Mar 17  2012 /usr/openv/netbackup/bin/libobk.so64 [oratest@test]$ ls -ltr libobk.so ls: libobk.so: No such file or directory [oratest@test]$ ln -s /usr/openv/netbackup/bin/libobk.so64 libobk.so [oratest@test]$ ls -ltr libobk.so lrwxrwxrwx 1 oratest dba 36 Aug 15 09:55 libobk.so -> /usr/openv/netbackup/bin/libobk.so64 3. Run the archive backup again which will complete successfully now.

After the database clone completion, instance was crashing frequently and we observed the below error in the alert log file ORA-07445: exception encountered: core dump [ksxp_rm_check()+26] [SIGSEGV] [ADDR:0x18C8] [PC:0x4BD174C] [Address not mapped to object] [] PMON (ospid: 20890): terminating the instance due to error 602 System state dump requested by (instance=1, osid=20890 (PMON)), summary=[abnormal instance termination]. System State dumped to trace file /schc/app01/app/diag/rdbms/schc/SCHC/trace/SCHC_diag_20901_20160423233812.trc Dumping diagnostic data in directory=[cdmp_20160423233812], requested by (instance=1, osid=20890 (PMON)), summary=[abnormal instance termination]. Instance terminated by PMON, pid = 20890 We have checked the ORA 07445 error lookup tool for this error and we observed that the document 2044334.1 matches the issue we are facing, As  per the document id we need to increase AQ_TM_PROCESSES to greater than or equal to 1. 1.       First