Blogs

Upgrade to Oracle EBS 12.2.11 – Issues and Solutions Part 2

Continuing from the previous blog where issues prior to configuring the release of the Oracle 12.2.0 environment were charted out.

This topic is related to post configuration steps, the Online Patching Enablement phase and applying AD, TXK Delta 13 patches.

 

#1: Adgrants warning on DBMS_UPG_* objects

A pre-requisite step of the latest Oracle E-Business Suite Online Patching Readiness and GSCC Report Patch for 12.2 is to run adgrants.sql as an APPS user.

The warning messages below are the aftermath of running the grants. But these can be ignored.

2022/03/11 21:32:28 38 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE WARNING
ORA-00942: table or view does not exist, SQL: grant SELECT on “DBMS_UPG_CURRENT_STATUS” to “APPS”

2022/03/11 21:32:28 38 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE WARNING
ORA-00942: table or view does not exist, SQL: grant SELECT on “DBMS_UPG_CURRENT_STATUS” to “SYSTEM” with grant option

2022/03/11 21:32:28 38 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE WARNING
ORA-00942: table or view does not exist, SQL: grant SELECT on “DBMS_UPG_DEBUG” to “APPS”

2022/03/11 21:32:28 38 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE WARNING
ORA-00942: table or view does not exist, SQL: grant SELECT on “DBMS_UPG_DEBUG” to “SYSTEM” with grant option

2022/03/11 21:32:28 38 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE WARNING
ORA-00942: table or view does not exist, SQL: grant SELECT on “DBMS_UPG_STATUS” to “APPS”

2022/03/11 21:32:28 38 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE WARNING
ORA-00942: table or view does not exist, SQL: grant SELECT on “DBMS_UPG_STATUS” to “SYSTEM” with grant option

2022/03/11 21:32:28 38 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE WARNING
ORA-00942: table or view does not exist, SQL: grant SELECT on “DBMS_UPG_STATUS$” to “APPS”

2022/03/11 21:32:28 38 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE WARNING
ORA-00942: table or view does not exist, SQL: grant SELECT on “DBMS_UPG_STATUS$” to “SYSTEM” with grant option

2022/03/11 21:32:34 38 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE WARNING
ORA-04042: procedure, function, package, or package body does not exist, SQL: grant EXECUTE on “DBMS_SCHEMA_COPY” to “APPS”

2022/03/11 21:32:34 38 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE WARNING
ORA-04042: procedure, function, package, or package body does not exist, SQL: grant EXECUTE on “DBMS_SCHEMA_COPY” to “SYSTEM” with grant option

2022/03/11 21:32:36 38 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE WARNING
ORA-00942: table or view does not exist, SQL: grant WRITE on “DIRECTORY FND_DIAG_DIR” to “APPS”

2022/03/11 21:32:36 38 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE WARNING
ORA-00942: table or view does not exist, SQL: grant READ on “DIRECTORY FND_DIAG_DIR” to “APPS”

12 rows selected.

 

The Solution:

So as per Doc ID 2507343.1, the messages imply DB Vault is disabled and that is not an “EBS Requirement”.

 

#2: Apps Tables listed in Online Patching Readiness Reports Violations

Section — 19 of ADZDDBCC report shows tables including Apps owned EBS_UTLFILE_PARAM and EBS_UTLFILE_PARAM2 which is a bug.

As per Doc ID 2823792.1, this affects 12.2.10 & 12.2.11.

 

The Solution:

In our case, this was done –

1. Assess the necessity of all tables except EBS_UTLFILE_PARAM, EBS_UTLFILE_PARAM2
2. Take an export backup of those other tables before dropping
3. Leave EBS_UTLFILE* tables as it is

The note ID 2823792.1 however, suggests applying a patch, which in turn will update ADZDDBCC.sql version and thus subsequent re-runs will de-list the two tables from under Section -19 of the Database Compliance Checker report.

 

#3: Online Patching Enablement patch failed with the following error

The error is because of the already existing database Service name ebs_patch.

FAILED: file ADZDPREP.sql on worker 1.

vi adwork001.log
begin
*
ERROR at line 1:
ORA-44303: service name exists
ORA-06512: at “SYS.DBMS_SERVICE_ERR”, line 21
ORA-06512: at “SYS.DBMS_SERVICE”, line 316
ORA-06512: at “APPS.AD_ZD_PREP”, line 392
ORA-01403: no data found
ORA-06512: at “APPS.AD_ZD_PREP”, line 386
ORA-06512: at line 4

 

Solution:

Stop and delete ebs_patch service name: Doc ID 2060543.1.

Then re-start the failed job and continue.

SQL> select SERVICE_ID,NAME from dba_services;

SERVICE_ID NAME
— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —
         1 SYS$BACKGROUND
         2 SYS$USERS
         3 ******
         4 EBS_PATCH
         5 ******
         6 ******

SQL> begin

DBMS_SERVICE.STOP_SERVICE(service_name =>’ebs_patch’);
DBMS_SERVICE.DELETE_SERVICE(service_name =>’ebs_patch’);
end;
/

PL/SQL procedure successfully completed.

SQL> commit;

Commit complete.

 

#4: Adgrants.sql — pre-requisite of AD patch 33441060 completed with warning

The following ERRORS and WARNINGS have been encountered during this adgrants session:

TIME_STAMP SESSION_ID     LOG_MODULE     LOG_LEVEL
— — — — — — — — — — —     — — — — — —    — — — — — — — — — — 
LOG_MESSAGE
— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

2022/03/30 16:26:01               839    ad.plsql.ad_grants.exec_obj_grant WARNING
ORA-00942: table or view does not exist,SQL: grant SELECT on “APPLSYS”.”FND_PRODUCT_INSTALLATIONS#” to “EBS_SYSTEM” with grant option

2022/03/30 16:26:01               839    ad.plsql.ad_grants.exec_obj_grant WARNING
ORA-00942: table or view does not exist,SQL: grant SELECT on “APPLSYS”.”FND_PRODUCT_INSTALLATIONS#” to “APPLSYSPUB” with grant option

 

Solution:

“Can be safely ignored…” — wrote the engineer from Oracle.

Also, don’t forget to unlock the newly created schema EBS_SYSTEM and set the same password as that of the SYSTEM schema. Future ADOP patching phases will be prompt for EBS_SYSTEM’s password instead of SYSTEM’s.

 

#5: AD Patch 33862025 failed because AD executables got lost or corrupted

After AD Delta 13(32394134) and 33441060 patches were applied successfully, additional AD patch 33862025 failed due to an unexpected issue.

adop phase=apply patches=33862025 hotpatch=yes

************
************
************

Validating system setup.

error:
Wrong Usage: Please use:
<binary_name> <apps_schema_name> <apps_schema_pwd> <xml_file_name>

You should check the file
/d01/apps/*****/fs1/EBSapps/appl/admin/*****/log/adpawc.log

for errors.

[UNEXPECTED]Error occurred running adpawc APPS **** /d01/apps/*****/fs1/EBSapps/appl/admin/*****/log/adpawc.xml.

[UNEXPECTED]Error determining recommended worker count

On digging further, it was determined that the cause might be that AD executables got lost or corrupted.

 

Solution: Run Adrelink with the “Force” Option

Reference: Doc ID 2851088.1

cd $AD_TOP/bin
adrelink.sh force=y “ad all”

 

#6: TXK Delta 13 failed due to missing files

TXK Delta 13(32392507) plus critical TXK patches 33550674, 33535778 failed because of missing files adsign.txt and adkeystore.dat under $APPL_TOP_NE/ad/admin.

AutoPatch error:
ERROR : File /d01/apps/*****/fs_ne/EBSapps/appl/ad/admin/adsign.txt does not exist.

AutoPatch error:
Failed to generate the product JAR files

AutoPatch error:
ERROR File /d01/apps/*****/fs_ne/EBSapps/appl/ad/admin/adkeystore.dat doesnot exist.

AutoPatch error:
Failed to generate the product JAR files

 

The Solution:

The apply phase failed twice, once when looking for adsign.txt and then for adkeystore.dat. So copy both the files from $APPL_TOP/admin to $APPL_TOP_NE before re-trying.

Only Step 1 of Doc ID 1595449.1 was implemented, for both the files, though the issue in the document was specifically about missing adsign.txt and about a different issue altogether.

cp $APPL_TOP/admin/adsign.txt $APPL_TOP_NE/ad/admin/

cp $APPL_TOP/admin/adkeystore.dat $APPL_TOP_NE/ad/admin/

More from this Author