EBS : How to continue the failed ADPATCH

1.  Backup the FND_INSTALL_PROCESSES table which is owned by the APPLSYS schema
sqlplus applsys/<password>

• create table fnd_Install_processes_back as select * from fnd_Install_processes;
• The 2 tables should have the same number of records.
• select count(*) from fnd_Install_processes_back;
• select count(*) from fnd_Install_processes;

2.  Backup the AD_DEFERRED_JOBS table.

• sqlplus applsys/<password>
• create table AD_DEFERRED_JOBS_back as select * from AD_DEFERRED_JOBS;
• The 2 tables should have the same number of records.
• select count(*) from AD_DEFERRED_JOBS_backup;
• select count(*) from AD_DEFERRED_JOBS;

3.  Backup the .rf9 files located in $APPL_TOP/admin/<SID>/restart directory.
At this point, the adpatch session should have ended and the cursor should be back at the Unix prompt.

• cd $APPL_TOP/admin/<SID>
• mv restart restart_backup
• mkdir restart

4.  Drop the FND_INSTALL_PROCESSES table and the AD_DEFFERED_JOBS table.

• sqlplus applsys/<password>
• drop table FND_INSTALL_PROCESSES;
• drop table AD_DEFERRED_JOBS;

5.  Apply the new patch.
6.  Restore the .rf9 files located in $APPL_TOP/admin/<SID>/restart_backup directory.

• cd $APPL_TOP/admin/<SID>
• mv restart restart_<patchnumber>
• mv restart_backup restart

7. Restore the FND_INSTALL_PROCESSES table which is owned by the APPLSYS schema.

• sqlplus applsys/<password>
• create table fnd_Install_processes as select * from fnd_Install_processes_backup;
• The 2 tables should have the same number of records.
• select count(*) from fnd_Install_processes;
• select count(*) from fnd_Install_processes_backup;

8. Restore the AD_DEFERRED_JOBS table.

• sqlplus applsys/<password>
• create table AD_DEFERRED_JOBS as select * from AD_DEFERRED_JOBS_backup;
• The 2 tables should have the same number of records.
• select count(*) from AD_DEFERRED_JOBS_backup;
• select count(*) from AD_DEFERRED_JOBS;

9. Re-create synonyms

• sqlplus apps/apps
• create synonym AD_DEFERRED_JOBS for APPLSYS.AD_DEFERRED_JOBS;
• create synonym FND_INSTALL_PROCESSES FOR APPLSYS.FND_INSTALL_PROCESSES;

10. Start adpatch, it will resume where it stopped previously.

LINUX : RPMS elfutils-libelf-devel failed due to dependency

Error:

[root@limsdb RPM_CD]# rpm -ivh elfutils-libelf-devel-0.137-3.el5.x86_64.rpm
warning: elfutils-libelf-devel-0.137-3.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
error: Failed dependencies:
       elfutils-libelf-devel-static-x86_64 = 0.137-3.el5 is needed by elfutils-libelf-devel-0.137-3.el5.x86_64
[root@limsdb RPM_CD]# rpm -ivh elfutils-libelf-devel-static-0.137-3.el5.x86_64.rpm
warning: elfutils-libelf-devel-static-0.137-3.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
error: Failed dependencies:
       elfutils-libelf-devel-x86_64 = 0.137-3.el5 is needed by elfutils-libelf-devel-static-0.137-3.el5.x86_64
[root@limsdb RPM_CD]# rpm -ivh elfutils-libelf-devel-0.137-3.el5.x86_64.rpm
warning: elfutils-libelf-devel-0.137-3.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
error: Failed dependencies:
       elfutils-libelf-devel-static-x86_64 = 0.137-3.el5 is needed by elfutils-libelf-devel-0.137-3.el5.x86_64
[root@limsdb RPM_CD]# rpm -ivh elfutils-libelf-devel-static-0.137-3.el5.x86_64.rpm
warning: elfutils-libelf-devel-static-0.137-3.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
error: Failed dependencies:
       elfutils-libelf-devel-x86_64 = 0.137-3.el5 is needed by elfutils-libelf-devel-static-0.137-3.el5.x86_64

Solution:
Both the RPMS elfutils-libelf-devel-0.137-3.el5.x86_64.rpm elfutils-libelf-devel-static-0.137-3.el5.x86_64.rpm are depenedent on each other so install both the RPMS in same line as below

rpm -ivh elfutils-libelf-devel-0.137-3.el5.x86_64.rpm elfutils-libelf-devel-static-0.137-3.el5.x86_64.rpm

EBS : autoconfig fails in dbTier (afdbprf.sh, adcrobj.sh)

Error:

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

  [PROFILE PHASE]
  AutoConfig could not successfully execute the following scripts:
    Directory: /oradb/oracle/11.2.0.3/appsutil/install/TEST_drebsdb01
      afdbprf.sh              INSTE8_PRF         1

  [APPLY PHASE]
  AutoConfig could not successfully execute the following scripts:
    Directory: /oradb/oracle/11.2.0.3/appsutil/install/TEST_drebsdb01
      adcrobj.sh              INSTE8_APPLY       1


AutoConfig is exiting with status 2

AutoConfig execution completed on Tue Jan 13 10:39:20 2015

Time taken for AutoConfig execution to complete : 0 mins  17 secs


Solution:

Step 1: Create the appsutil on the AP Tier again
perl $AD_TOP/bin/admkappsutil.pl

[applprod@driebsapp01 appl]$ perl $AD_TOP/bin/admkappsutil.pl
Starting the generation of appsutil.zip
Log file located at /appl/inst/apps/TEST_driebsapp01/admin/log/MakeAppsUtil_01131144.log
output located at /appl/inst/apps/TEST_driebsapp01/admin/out/appsutil.zip
MakeAppsUtil completed successfully.

Step 2: Copy the above created zip to the DB Tier Oracle Home
scp -pr appsutil.zip dbTier Oracle_Home

Step 3: On DB Tier
cd $ORACLE_HOME
unzip -o appsutil.zip

Step 4: Rerun autoconfig
$ORACLE_HOME/appsutil/bin/adconfig.sh contextfile={$CONFIG_FILE}

LINUX : start/stop/restart cron services

/etc/init.d/crond start/stop/restart

EBS : System Hold, Fix Manager before resetting counters - Concurrent Manager

Error:

"System Hold, Fix Manager before resetting counters" in two of the concurrent manageres "Receiving Transaction Manager" and "PO Document Approval Manager" after cloning


Solution:
1. Apply the patch 16735285

2.After the patch run adrelink:

cd $PO_TOP/bin
adrelink.sh force=y ranlib=y "PO RCVOLTM"
adrelink.sh force=y ranlib=y "PO POXCON"

3. Bounce the concurrent managers.

4. Retest the issue.

EBS : APP-FND-01510

Error:

APP-FND-01516L Invalid application username, password, or database

Username: APPLSYSPUB
Database: VIS

Solution:

Check the alter log file of the database for below error:

ORA-00020: maximum number of processes 0 exceeded
ORA-20 errors will not be written to the alert log for
 the next minute. Please look at trace files to see all
 the ORA-20 errors.

Shutdown the application and database

edit the init parameter file by increasing the parameter processes and sessions, then start the database with the edited init prameter file and start the application