MSDODPCODE.sql Fails When Applying Patch 7303030 (Doc ID 1272460.1)

Last updated on FEBRUARY 08, 2017

Applies to:

Oracle Demand Planning - Version 12.1.1 and later
Information in this document applies to any platform.
*** Checked for relevance on 18-Jun-2012 ***
*** Checked for relevance on 29-Jan-2014 ***

Symptoms

When you upgrade your EBS system from 12.0.4 to 12.1.1 by applying <patch 7303030> (as per <note 752619.1>), you get the following error.

Completed: file XDOLoader.class on worker 5 for product xdo username XDO.
FAILED: file MSDODPCODE.sql on worker 6 for product msd username MSD.
Deferred: file MSDODPCODE.sql on worker 6 for product msd username MSD.(Deferment number 2 for this job)
Assigned: file MSDODPCODE.sql on worker 1 for product msd username MSD.
FAILED: file MSDODPCODE.sql on worker 1 for product msd username MSD.

ATTENTION: All workers either have failed or are waiting:

FAILED: file MSDODPCODE.sql on worker 1.

ATTENTION: Please fix the above failed worker(s) so the manager can continue.



You can see the following error in adwork001.log:

ERROR at line 1:
ORA-35786: An exception (ORA-35786) occurred. The message for this exception
could not be found.
ORA-06512: Message 6512 not found; No message file for product=RDBMS,
facility=ORA; arguments: ["SYS.DBMS_AW", ] [93]
ORA-06512: Message 6512 not found; No message file for product=RDBMS,
facility=ORA; arguments: ["SYS.DBMS_AW", ] [122]
ORA-06512: Message 6512 not found; No message file for product=RDBMS,
facility=ORA; arguments: [] [13]

Changes

Application of <patch 7303030>.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms