How to Prevent EXP-00079 EXP-00056 and ORA-28112 Errors When Exporting Grid Control OMS Databases Using Traditional Export or Datapump Export (Doc ID 778864.1)

Goal

The goal is to walk you through resolving EXP-00079 EXP-00056 and ORA-28112 errors when using Grid Control Repository Database and Traditional Export or Datapump Export functionality.

Running as SYS or SYSTEM  may not be a problem and other exports may run without error.

When exporting Grid Control Repository database from a Oracle10g database you will see the following errors in the traditional export or datapump log files.  The exports may fail even after granting the required roles. (  Note that the table name may be different )

SQL> select grantee, granted_role from dba_role_privs where grantee = '<USER_NAME>';

GRANTEE GRANTED_ROLE
------------------------------ ------------------------------
<USER_NAME> CONNECT
<USER_NAME> MGMT_USER
<USER_NAME> EXP_FULL_DATABASE
<USER_NAME> AQ_ADMINISTRATOR_ROLE
<USER_NAME> DBA
<USER_NAME> RESOURCE

1.  The Traditional Export can fail with the following errors:

EXP-00079: Data in table "MGMT_TARGETS" is protected. Conventional path may only be exporting partial table.
. . exporting table MGMT_TARGETS
EXP-00056: ORACLE error 28112 encountered
ORA-28112: failed to execute policy function
. . exporting table MGMT_TARGETS_DELETE 0 rows exported

2.  The Data Pump Export can fail with the following errors:

ORA-31693: Table data object "SYSMAN"."MGMT_TARGETS" failed to load/unload and
is being skipped due to error:
ORA-28112: failed to execute policy function

3.  Try to perform a select count from the above table can trigger this error.

SQL> select count(1) from sysman.mgmt_targets;
select count(1) from sysman.mgmt_targets
*
ERROR at line 1:
ORA-28112: failed to execute policy function

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.