Blogs

Upgrade to Oracle EBS 12.2.11 – Issues and Solutions Part 3

In this last and final blog post (previous ones Part 2 & Part 1) we will explore the issues specific to RUP Oracle 12.2.11.

Let’s dive in…

RUP 12.2.11 — Patch 31856789

a. Relinking failed due to Environment Variables

vi adrelink.log

Removing extra variables from the environment…
  adrelink will save the following variables (if set):
  - Generic:
“PATH ORACLE_HOME TMPDIR TZ APPL_TOP APPLFENV PLATFORM LD_LIBRARY_PATH COBDIR
LIBPATH NLS_LANG JAVA_TOP PERL5LIB”
  - Shell-Specific: “PS1 PS2 PS3 PS4 IFS MAILCHECK _ LOGNAME A__z”
  Beginning pass 1.
   Processing 383 environment variables…
/d01/apps/*****/fs1/EBSapps/appl/ad/12.0.0/bin/adrelinknew.sh: line 1078:
unset: `}’: not a valid identifier
/d01/apps/*****/fs1/EBSapps/appl/ad/12.0.0/bin/adrelinknew.sh: line 1078:
unset: `which%%’: not a valid identifier
/d01/apps/*****/fs1/EBSapps/appl/ad/12.0.0/bin/adrelinknew.sh: line 1078:
unset: `${which_declare}’: not a valid identifier
/d01/apps/*****/fs1/EBSapps/appl/ad/12.0.0/bin/adrelinknew.sh: line 1078:
unset: `|’: not a valid identifier
/d01/apps/*****/fs1/EBSapps/appl/ad/12.0.0/bin/adrelinknew.sh: line 1078:
unset: `/usr/bin/which’: not a valid identifier
/d01/apps/*****/fs1/EBSapps/appl/ad/12.0.0/bin/adrelinknew.sh: line 1078:
unset: — : invalid option
unset: usage: unset [-f] [-v] [-n] [name …]

adrelink is exiting with status 2

End of adrelink session

The Solution:

Unset the variables (as directed by Oracle Support) and re-try.

unset which_declare
unset which_opt
unset which_shell
unset which
unset _

b. Forms objects did not generate successfully

After running for more than 6 hours and just when I had visualized “light” on the other end of the tunnel, the RUP failed!

The following Oracle Forms objects did not generate successfully:

inv   forms/US   INVIDTMP.fmx
inv   forms/US   INVIVCSU.fmx
inv   forms/US   INVIDITM.fmx

An error occurred while generating Oracle Forms files.

On compiling the Forms binaries manually, this is what the error message looked like:

Compiling package body MTL_ITEM_TEMPL_ATTRIBUTES_02…
Compilation error on package body MTL_ITEM_TEMPL_ATTRIBUTES_02:
PL/SQL ERROR 201 at line 955, column 12
identifier ‘CS_LOOKUPS’ must be declared
PL/SQL ERROR 0 at line 953, column 5
SQL Statement ignored

Form not created

The Solution: Remember to talk to your colleagues

My senior’s wisdom saved me a lot of time! And the Forms were generated successfully!

USER is “APPS”
SQL> desc CS_LOOKUPS;
ERROR:
ORA-04043: object CS_LOOKUPS does not exist

CREATE OR REPLACE FORCE EDITIONABLE VIEW “APPS”.”CS_LOOKUPS” (“LOOKUP_TYPE”, “LOOKUP_CODE”, “LAST_UPDATE_DATE”, “LAST_UPDATED_BY”, “LAST_UPDATE_LOGIN”, “CREATION_DATE”, “CREATED_BY”, “MEANING”, “ENABLED_FLAG”, “START_DATE_ACTIVE”, “END_DATE_ACTIVE”, “DESCRIPTION”, “ATTRIBUTE_CATEGORY”, “ATTRIBUTE1”, “ATTRIBUTE2”, “ATTRIBUTE3”, “ATTRIBUTE4”, “ATTRIBUTE5”, “ATTRIBUTE6”, “ATTRIBUTE7”, “ATTRIBUTE8”, “ATTRIBUTE9”, “ATTRIBUTE10”, “ATTRIBUTE11”, “ATTRIBUTE12”, “ATTRIBUTE13”, “ATTRIBUTE14”, “ATTRIBUTE15”, “TAG”) AS
SELECT LV.LOOKUP_TYPE, LV.LOOKUP_CODE, LV.LAST_UPDATE_DATE, LV.LAST_UPDATED_BY, LV.LAST_UPDATE_LOGIN, LV.CREATION_DATE, LV.CREATED_BY, LV.MEANING, LV.ENABLED_FLAG, LV.START_DATE_ACTIVE, LV.END_DATE_ACTIVE, LV.DESCRIPTION, LV.ATTRIBUTE_CATEGORY, LV.ATTRIBUTE1, LV.ATTRIBUTE2, LV.ATTRIBUTE3, LV.ATTRIBUTE4, LV.ATTRIBUTE5, LV.ATTRIBUTE6, LV.ATTRIBUTE7, LV.ATTRIBUTE8, LV.ATTRIBUTE9, LV.ATTRIBUTE10, LV.ATTRIBUTE11, LV.ATTRIBUTE12, LV.ATTRIBUTE13, LV.ATTRIBUTE14, LV.ATTRIBUTE15, LV.TAG FROM FND_LOOKUP_VALUES LV WHERE lv.LANGUAGE = userenv(‘LANG’) and lv.View_APPLICATION_ID = 170 and lv.SECURITY_GROUP_ID = fnd_global.lookup_security_group(LV.LOOKUP_TYPE, LV.VIEW_APPLICATION_ID); 2

View created.

c. Generating library INVISMMX.pll failed with the error shown

/d01/apps/*****/fs1/EBSapps/10.1.2/bin/rwconverter: error while loading shared libraries: libXm.so.2: cannot open shared object file: No such file or directory

ERROR [code=127] generating library “INVISMMX.pll” from input file
/d01/apps/*****/fs1/EBSapps/appl/au/12.0.0/plsql/INVISMMX.pll

Generated 0 files successfully.
Generated 0 files with non-fatal warnings.
Generated 1 files with fatal errors.

adrepgen is exiting with status 1

The Solution:

As Root, run the following commands:

[root@******* lib]# cd /usr/lib
[root@******* lib]# ln -s libXm.so.4.0.4 libXm.so.2

d. Post 12.2.11 RUP Cleanup phase displayed a strange message

adop phase=cleanup

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

[UNEXPECTED]The following patches failed to apply on admin node <*******> in hotpatch mode, session ID <2>
     Patches: <2394134,33441060>
You can either resolve the failure and reapply the patches, or ignore the failure and allow processing to continue.
[WARNING] Only continue if you are sure it is safe to do so — continuing without first resolving the failure may lead to inconsistency and data loss.
To reapply the patches in the existing session, answer ‘N’.
To ignore the failure and continue processing, answer ‘Y’.
Do you want to continue (Y/N)? [N]

The patches were already applied..so why???

SQL> select BUG_NUMBER, CREATION_DATE from apps.ad_bugs where bug_number in(‘32394134’,’33441060');

BUG_NUMBER     CREATION_
— — — — — — — — — — — — — — — — — — — -
32394134       31-MAR-22
33441060       31-MAR-22

Still not satisfied with the conflicting messages, I ran the Upgrade Analyzer tool to lay the doubts to rest.

The Solution:

And continued with the Cleanup phase…

Do you want to continue (Y/N)? [N]Y

Processing cleanup actions in parallel.
   Log: /d01/apps/*****/fs_ne/EBSapps/log/adop/2/20220404_170752/cleanup/*******/log/cleanup.log

Generating report of queued DDL actions.
   Output: /d01/apps/*****/fs_ne/EBSapps/log/adop/2/20220404_170752/cleanup/*******/adzdallddls.out

Running cleanup in STANDARD mode.
   Log: @ADZDSHOWLOG.sql “2022/04/05 04:03:21”

Generating log report.
   Output: /d01/apps/*****/fs_ne/EBSapps/log/adop/2/20220404_170752/cleanup/*******/adzdshowlog.out

The cleanup phase completed successfully.

adop exiting with status = 0 (Success)

Hope this helps and see you on the other side of a successful, unscathed upgrade to EBS 12.2.11!

More from this Author