Environment:
Oracle OLAP – Version 11.2.0.3 and later
Symptoms:
OLAP is valid in dba_registry but the following OLAP objects are invalid:
SQL> select owner,object_name,object_type from dba_objects where status=’INVALID’ order by owner asc;
PUBLIC GENCURSORMANAGERINTERFACE SYNONYM
PUBLIC GENSERVERINTERFACE SYNONYM
PUBLIC GENCONNECTIONINTERFACE SYNONYM
PUBLIC DBMS_AW_XML SYNONYM
PUBLIC GENMETADATAPROVIDERINTERFACE SYNONYM
PUBLIC GENDATAPROVIDERINTERFACE SYNONYM
PUBLIC GENDEFINITIONMANAGERINTERFACE SYNONYM
SYS GENCURSORMANAGERINTERFACE PACKAGE BODY
SYS GENDEFINITIONMANAGERINTERFACE PACKAGE
SYS GENDEFINITIONMANAGERINTERFACE PACKAGE BODY
SYS GENDATAPROVIDERINTERFACE PACKAGE
SYS GENDATAPROVIDERINTERFACE PACKAGE BODY
SYS DBMS_AW_XML PACKAGE
SYS DBMS_AW_XML PACKAGE BODY
SYS INTERACTIONEXECUTE FUNCTION
SYS DBMS_CUBE_UTIL PACKAGE BODY
SYS GENCURSORMANAGERINTERFACE PACKAGE
SYS GENMETADATAPROVIDERINTERFACE PACKAGE BODY
SYS GENMETADATAPROVIDERINTERFACE PACKAGE
SYS GENSERVERINTERFACE PACKAGE BODY
SYS GENSERVERINTERFACE PACKAGE
SYS XOQ_VALIDATE PROCEDURE
SYS GENCONNECTIONINTERFACE PACKAGE
SYS GENCONNECTIONINTERFACE PACKAGE BODY
Solution:
spool olap.log
@ORACLE_HOME/olap/admin/catxoq.sql;
spool off
NOTE: In 12C catxoq can be run in the CDB without having to use catcon.pl
The catxoq.sql does the ORACLE_SCRIPT = true and then changes it back to false, and it can be run in the CDB via SYS as sysdba.
SQL> select owner,object_name,object_type from dba_objects where status=’INVALID’ order by owner asc;
You should not have any more invalid OLAP objects.
