Rup 12.2.10 failed

[satish]

IMG20221205193028.jpgDear erman,

We have installed r12.2.0 and now we are applying rup 12.2.10 which failed.Need your support.

csmlobmf.sql
ecx_create_keyiv.sql

worker 1

sqlplus -s APPS/***** @/u01/R122_APPS/fs1/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql '/u01/R122_APPS/fs1/EBSapps/appl/csm/12.0.0/patch/115/sql/csmlobmf.sql &un_apps &pw_apps'
Connected.

PL/SQL procedure successfully completed.

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




Worker 2



Connected.

PL/SQL procedure successfully completed.

declare
*
ERROR at line 1:
ORA-04063: package body "APPS.FND_MESSAGE" has errors
ORA-06508: PL/SQL: could not find program unit being called: "APPS.FND_MESSAGE"
ORA-06512: at line 14
ORA-04063: package body "APPS.WF_CORE" has errors
ORA-06508: PL/SQL: could not find program unit being called: "APPS.WF_CORE"
ORA-06512: at "APPS.WF_LOG_PKG", line 72
ORA-04063: package body "APPS.FND_LOG_REPOSITORY" has errors
ORA-06508: PL/SQL: could not find program unit being called:
"APPS.FND_LOG_REPOSITORY"

There are 3800 invalids.We tried utlrp and we also compiled apps schema but still invalids exist. Please suggest


Thanks,
Satish

[ErmanArslansOracleBlog]

Interesting.. Running utlrp may be a good idea in this situation.. But let's check those reported objects, if they are not valid, compile them and try to make them valid.
Then, restart the workers and lets see.

Example check:

With APPS user & Sqlplus->
select owner, object_name, object_type, status from dba_objects where object_name='WF_CORE';

With APPS user;

alter package APPS.WF_CORE compile;
alter package APPS.WF_CORE compile body;

[satish]

Dear Erman,

Thanks for the update. We tried running utlrp but still invalids exist.

Compiled the package:

SQL> select owner, object_name, object_type, status from dba_objects where object_name='WF_CORE';

OWNER
--------------------------------------------------------------------------------
OBJECT_NAME
--------------------------------------------------------------------------------
OBJECT_TYPE             STATUS
----------------------- -------
APPS
WF_CORE
PACKAGE BODY            INVALID

APPS
WF_CORE
PACKAGE                 VALID

OWNER
--------------------------------------------------------------------------------
OBJECT_NAME
--------------------------------------------------------------------------------
OBJECT_TYPE             STATUS
----------------------- -------


SQL> alter package APPS.WF_CORE compile;

Warning: Package altered with compilation errors.

SQL> sho error;
No errors.
SQL> alter package APPS.WF_CORE compile body;

Warning: Package Body altered with compilation errors.


SQL> sho error
Errors for PACKAGE BODY APPS.WF_CORE:

LINE/COL ERROR
-------- -----------------------------------------------------------------
391/12   PLS-00323: subprogram or cursor 'CLIENT_TIMEZONE' is declared in
         a package specification and must be defined in the package body

430/12   PLS-00323: subprogram or cursor 'GETDEDICATEDCOMPONENTSCORRIDS'
         is declared in a package specification and must be defined in
         the package body

444/10   PLS-00323: subprogram or cursor 'MATCHCORRID' is declared in a
         package specification and must be defined in the package body

SQL> select owner, object_name, object_type, status from dba_objects where object_name='WF_CORE';

OWNER
--------------------------------------------------------------------------------
OBJECT_NAME
--------------------------------------------------------------------------------
OBJECT_TYPE             STATUS
----------------------- -------
APPS
WF_CORE
PACKAGE BODY            INVALID

APPS
WF_CORE
PACKAGE                 VALID

OWNER
--------------------------------------------------------------------------------
OBJECT_NAME
--------------------------------------------------------------------------------
OBJECT_TYPE             STATUS
----------------------- -------

Can we apply a different RUP like R12.2.11 or R12.2.12.
 In that case, can we run abandon=yes restart=no.
will this work OR do we have to restore the system?

Thanks,
Satish

[ErmanArslansOracleBlog]

These are unexpected errors Satish. 12.2.10 is already a stable RUP, and we have used it in lots of customer environments
12.2.11 may not be the cure. But of course, you need to go with 12.2.11 unless you have something (some reason) to prevent it.
The cause may be an action, a necessary action not taken before the patching activity.
So, I suggest you to review your pre-upgrade process. Review the readme of 12.2.10 and ensure you did what needs to be done before 12.2.10 RUP patching.

As for your other question;

In principal yes, but I don't recommend it. Because it is a big patch as you know.. So rather than rerunning adop with "abandon=yes restart=no", restore your backup, complete the missing work and then run adop for patching..