Way to success...

--"Running Away From Any PROBLEM Only Increases The DISTANCE From The SOLUTION"--.....--"Your Thoughts Create Your FUTURE"--.....--"EXCELLENCE is not ACT but a HABIT"--.....--"EXPECT nothing and APPRECIATE everything"--.....

Wednesday, November 2, 2016

u6678700.drv: FAILED: file MSDODPCODE.sql

Action plan to avoid MSDODPCODE.sql job issue:

Issue:


begin
*
ERROR at line 1:
ORA-33292: Insufficient permissions to access analytic workspace APPS.ODPCODE
using the specified access mode.
ORA-06512: at "SYS.DBMS_AW", line 67
ORA-06512: at "SYS.DBMS_AW", line 131
ORA-06512: at "SYS.DBMS_AW", line 977
ORA-06512: at "SYS.DBMS_AW", line 930
ORA-33262: Analytic workspace APPS.ODPCODE does not exist.
ORA-06512: at "SYS.DBMS_AW", line 901
ORA-06512: at "APPS.MSD_AW_LOADER", line 10
ORA-06512: at line 3


Cause:

•The OLAP user account is locked.
•The Analytic Workspace (AW) odpcode does not yet exist


Solution:

To implement the solution, please execute the following steps:

1.Verify the status for the account OLAPSYS, checking that the account is not EXPIRED or LOCKED:

SQL> select username ,account_status from dba_users where username like '%OLAP%';

2.If the above query showed that the user is locked, unlock using the following sql command:

SQL> ALTER USER OLAPSYS IDENTIFIED BY "olapsys" ACCOUNT UNLOCK;

3.Please run the following as APPS User in SQL*Plus to create the analytic workspace (AW) odpcode:

begin
dbms_aw.execute('aw create odpcode');
end; 

4.Stop Database listener and restart the database.


Restart the failed Worker using the adctrl utility in a second Shell session and continue.


No comments:

Post a Comment