Applying RUP patch 30399999 R12.2 upgrade

[satish]

Dear Erman,

We are upgrading R12.1.3 to R12.2.10

Now we are at R12.2.0

We have applied AD/TXK patches and now, wee are applying RUP 30399999 but it failed at MSDODPCODE.sql.


begin
*
ERROR at line 1:
ORA-33272: Analytic workspace APPS.ODPCODE cannot be opened.
ORA-33300: Analytic workspace APPS.ODPCODE encountered an error that may
indicate that it was created on a different platform.
ORA-00600: internal error code, arguments: [XsPgObjRead02], [1004], [2], [1],
[], [], [], [], [], [], [], []
ORA-06512: at "SYS.DBMS_AW", line 101
ORA-06512: at "SYS.DBMS_AW", line 165
ORA-06512: at "SYS.DBMS_AW", line 1174
ORA-06512: at "SYS.DBMS_AW", line 1111
ORA-06512: at "APPS.MSD_AW_LOADER", line 19
ORA-06512: at line 3

Can you please guide what can be done.

Thanks,
Satish

[ErmanArslansOracleBlog]

There is bug -> Bug 30121009  ORA-33300: Analytic workspace encountered an error that may indicate that it was created on a different platform

You may be hitting that one.

The fix is for that bug is first included in 20.1.0 and 19.15.0.0.220419 (April 2022) DB Release Update (DB RU).

Please check your DB layer accordingly..

[satish]

Dear Erman,

We are on 19.17 database version.

-bash-4.2$ $ORACLE_HOME/OPatch/opatch lsinventory|grep 30121009
     30121009, 33447602, 33127312, 32720344, 32988028, 28375383, 33821145
-bash-4.2$

Can we skip the worker, will there be any impact? Any idea.

Thanks,
Satish

[ErmanArslansOracleBlog]

Analytic workspace (AW) may have a single writer limitation. So coming to it in parallel may cause this. What happens when you restart the failed worker?

You may also create an SR and get the approval from Oracle Support about the following:

Dropping and Recreating the APPS.ODPCODE AW... This may also help, but Oracle Support should tell you this. Also you got an Ora-00600 (XsPgObjRead02) there and it is not documented on MOS or anywhere.

MSDODPCODE.sql fails with ORA-00600: internal error code, arguments: [xspsELMAINT02] while Applying Patch 14247039 (Doc ID 1531469.1)
ORA-33272: Analytic Workspace ODPCODE Cannot be Opened Error When Installing Patch 4398235 (Doc ID 462412.1)

[satish]

Hi erman,

Sure, we will check with support.

This product ODP shows as not installed.Can we skip this.

Oracle support says:



I've found some SRs with the same issue and below you can find the response from Oracle Demand Planning team.

"Oracle Demand Planning (ODP) has been replaced by Demantra, which is now the strategic product going forward. ODP is the legacy product.
There are no plans for new features, product enhancements or bug fixes for ODP.

Oracle has been recommending to all customers for the last 10 years to migrate to Oracle Demantra as that is the strategic solution.
If you are starting a new implementation, I strongly recommend that you go with Oracle Demantra.

In this case, you can safely skip the worker using adctrl utility to skip MSDODPCODE.sql and let the patch set continue running to work on the other workers as ODP is a de-supported product that should not be used anymore."

Need your advice.


Thanks
Satish

[ErmanArslansOracleBlog]

Yes. Oracle Demand Planning (ODP), the legacy planning application, is not used  Similar things are documented in some MOS notes as well.. For instance -> MSDODPCODE.SQL Fails Applying U6678700.Drv (Doc ID 1151274.1)

Bytheway; these AW(s) contain binary structures on disk that and they are stored there in an architecture-dependent manner.  ORA-33300 made me think that some kind of a problem due to your arch/platform triggered this error condition. However; that ORA-00600 seems like the reason and it is ugly.
You may skip the failed work and continue patching, but you need to be sure that there will be no ORA-00600 errors reported afterwards.

[satish]

Dear erman,

We skipped the worker and continued with patching.It waa completed and no invalids.Application is accessible.But we are worried whether there will be any impact.

How can I make sure that there will be no ORA-00600 errors reported afterwards.

Thanks,
Satish

[ErmanArslansOracleBlog]

You have to check the DB alert log + monitor that for a while.