DBA Arena

Symptoms:

ADOP Prepare phase fails while applying a patch.

Error:

[PROCEDURE] [END 2018/11/12 18:21:48] Acquiring lock on AD_ADOP_SESSION_PATCHES table
[PROCEDURE] [START 2018/11/12 18:21:48] Sync FS of RUN and PATCH
[PROCEDURE] Calling: /u02/oracle/ERPPROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl
[EVENT] Log: /u02/oracle/ERPPROD/fs_ne/EBSapps/log/adop/42/20181112_175050/prepare/erpisup
[UNEXPECTED]Error occurred running "perl /u02/oracle/ERPPROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/u01/oracle/ERPPROD/fs1/inst/apps/erpprod_erpisup/appl/admin/erpprod_erpisup.xml -patchcontextfile=/u01/oracle/ERPPROD/fs2/inst/apps/erpprod_erpisup/appl/admin/erpprod_erpisup.xml -promptmsg=hide -console=off -patchtop=/u02/oracle/ERPPROD/fs_ne/EBSapps/patch -mode=update -sync_mode=patch -sessionid=42 -timestamp=20181112_175050 -workercount=8 -outdir=/u02/oracle/ERPPROD/fs_ne/EBSapps/log/adop/42/20181112_175050/prepare/erpisup -autoskip=No"
[PROCEDURE] [START 2018/11/12 18:22:29] Unlocking AD_ADOP_SESSION_PATCHES table
[STATEMENT] Unlocking AD_ADOP_SESSION_PATCHES table for erpisup having lock name ADPATCH

[PROCEDURE] [END 2018/11/12 18:22:29] Unlocking AD_ADOP_SESSION_PATCHES table
[UNEXPECTED]Error calling runSyncFS subroutine.
[ERROR] Prepare phase has failed.

Read more...

Symptoms:

On Oracle Applications 12.2 version, online enablement patch 13543062 fails with:


begin
*
ERROR at line 1:
ORA-04063: package body "APPS.AD_ZD_PREP" has errors
ORA-06508: PL/SQL: could not find program unit being called: "APPS.AD_ZD_PREP"
ORA-06512: at line 4

 
Try to compile the package:

SQL> alter package apps.AD_ZD_PREP compile body;

1152/4 PL/SQL: Statement ignored
1152/17 PLS-00201: identifier 'SYS.DBMS_OBJECTS_APPS_UTILS' must be
declared

Read more...

Issue:

After applying Exadata or Super Cluster Bundle Patch on the RDBMS HOME of an EBS R12.2 database, the APPS.AD_ZD_ADOP Package becomes invalid and all ADOP sessions fail.

Error:

applprod@ebsapp01:~$ adop -status

Enter the APPS password:

==============================================================
ADOP (C.Delta.7)
Session Id: 55
Command: status
Output: /u01/PROD/fs_ne/EBSapps/log/status_20161115_112514/adzdshowstatus.out
===================================wo============================

File System Synchronization Type: Full
declare
*
ERROR at line 1:
ORA-04063: package body "APPS.AD_ZD_ADOP" has errors
ORA-06508: PL/SQL: could not find program unit being called: "APPS.AD_ZD_ADOP"
ORA-06512: at line 6

[STATEMENT] Please run adopscanlog utility, using the command

"adopscanlog -latest=yes"

to get the list of the log files along with snippet of the error message corresponding to each log file.

adop exiting with status = 1 (Fail)

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

Read more...

Issue:

While applying the OJVM patch on Exadata, the patch application fails on relinking.

Error:

OPatch failed: ApplySession failed in system modification phase... 'ApplySession::apply failed: Re-link fails on target "jox_refresh_knlopt ioracle".

OJVM Patch Installation:

Go to the patch directory.

[oracle@exadb01~]$ cd /u01/exadata_patch_apr2016/22738416/Database/11.2.0.4.0/11.2.0.4.160419OJVMPSU/22674697

OPatch Conflict Check

Determine whether any currently installed interim patches conflict with this patch.

[oracle@exadb01 22674697]$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./
Oracle Interim Patch Installer version 11.2.0.3.6
Copyright (c) 2013, Oracle Corporation. All rights reserved.

PREREQ session

Oracle Home : /u01/app/oracle/product/11.2.0.4/dbhome_1
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/11.2.0.4/dbhome_1/oraInst.loc
OPatch version : 11.2.0.3.6
OUI version : 11.2.0.4.0
Log file location : /u01/app/oracle/product/11.2.0.4/dbhome_1/cfgtoollogs/opatch/opatch2016-11-04_13-34-29PM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

Prereq "checkConflictAgainstOHWithDetail" passed.

OPatch succeeded.

Read more...

Symptoms:-

Dark blue background, mid-sized fonts, and incorrectly formatted buttons.

Solution:-

Read more...