ORA-28112: failed to execute policy function - Revision history

Stuart: Blanked the page

2015-03-06T13:58:11Z

Blanked the page

10.250.159.106 at 12:58, 9 December 2011

2011-12-09T12:58:48Z

10.250.159.106 at 12:48, 9 December 2011

2011-12-09T12:48:48Z

10.250.159.106 at 12:48, 9 December 2011

2011-12-09T12:48:28Z

10.250.159.106: /* Reason */

2011-12-06T08:26:06Z

‎Reason

10.250.159.106: Created page with "===Problem=== Getting error "'''ORA-28112: failed to execute policy function'''" when exporting or importing using DataPump During expdp is accompanied by "'''ORA-31693: Table da..."

2011-12-06T08:25:37Z

Created page with "===Problem=== Getting error "'''ORA-28112: failed to execute policy function'''" when exporting or importing using DataPump During expdp is accompanied by "'''ORA-31693: Table da..."

New page

===Problem===
Getting error "'''ORA-28112: failed to execute policy function'''" when exporting or importing using DataPump
During expdp is accompanied by "'''ORA-31693: Table data object "SYSMAN"."MGMT_IP_REPORT_DEF" failed to load/unload and is being skipped due to error:'''"
===Reason===
This happens due to audit policies being defined on the table but the function is defined in another schema.
===Solution===
Either drop the policy after importing the table with:
begin
for rec in (select * from dba_audit_policies where object_schema = 'SYSMAN') loop
dbms_fga.drop_policy(object_schema => rec.object_schema,
object_name => rec.object_name,
policy_name => rec.policy_name);
end loop;
end;
/
or exclude the policies during export by adding this to the .par file:
exclude=FGA_POLICY

← Older revision		Revision as of 13:58, 6 March 2015
Line 1:		Line 1:
−	~~===Problem===~~
−	~~Getting error "'''ORA-28112: failed to execute policy function'''" when exporting or importing using [[DataPump]]~~
−	~~During expdp is accompanied by "'''ORA-31693: Table data object "SYSMAN"."MGMT_IP_REPORT_DEF" failed to load/unload and is being skipped due to error:'''"~~
−	~~===Reason===~~
−	~~This happens due to audit policies being defined on the table but the policy function is defined in another schema.~~

−	~~===Solution===~~
−	~~Either drop the policy after importing the table with:~~
−	~~begin~~
−	~~for rec in (select * from dba_audit_policies where object_schema = 'SYSMAN') loop~~
−	~~dbms_fga.drop_policy(object_schema => rec.object_schema,~~
−	~~object_name => rec.object_name,~~
−	~~policy_name => rec.policy_name);~~
−	~~end loop;~~
−	~~end;~~
−	/
−	~~or exclude the policies during export by adding this to the .par file:~~
−	~~exclude=FGA_POLICY~~
−	~~or even better, give the necessary grants to the exporting user...~~
−	~~grant exempt access policy to impexpusr;~~
−	~~The dba role and sysdba have this automatically.~~

@@ Line 18: / Line 18: @@
   exclude=FGA_POLICY
 or even better, give the necessary grants to the exporting user...
-  grant exempt access policy to impexpusr
+  grant exempt access policy to impexpusr;
 The dba role and sysdba have this automatically.

← Older revision		Revision as of 12:48, 9 December 2011
Line 17:		Line 17:
	or exclude the policies during export by adding this to the .par file:		or exclude the policies during export by adding this to the .par file:
	exclude=FGA_POLICY		exclude=FGA_POLICY
		+	or even better, give the necessary grants to the exporting user...
		+	grant exempt access policy to impexpusr
		+	The dba role and sysdba have this automatically.

@@ Line 1: / Line 1: @@
 ===Problem===
-Getting error "'''ORA-28112: failed to execute policy function'''" when exporting or importing using DataPump
+Getting error "'''ORA-28112: failed to execute policy function'''" when exporting or importing using [[DataPump]]
 During expdp is accompanied by "'''ORA-31693: Table data object "SYSMAN"."MGMT_IP_REPORT_DEF" failed to load/unload and is being skipped due to error:'''"
 ===Reason===

@@ Line 3: / Line 3: @@
 During expdp is accompanied by "'''ORA-31693: Table data object "SYSMAN"."MGMT_IP_REPORT_DEF" failed to load/unload and is being skipped due to error:'''"
 ===Reason===
-This happens due to audit policies being defined on the table but the function is defined in another schema.
+This happens due to audit policies being defined on the table but the policy function is defined in another schema.
 ===Solution===
 Either drop the policy after importing the table with: