Problems with triggers at import
663283Feb 12 2009 — edited Feb 12 2009There is a production schema with the name PRO at Oracle 10g database. Export at night is automatically made. By deliveries of new versions of applications the dump is imports on the test schema (TEST) and the application tested on it. Some time ago at import began to throw errors for all triggers:
IMP-00017: following statement failed with ORACLE error 23308:
"BEGIN DBMS_DDL.SET_TRIGGER_FIRING_PROPERTY('"PRO"', '"TRIGGE"
"RBI"', FALSE); END;"
IMP-00003: ORACLE error 23308 encountered
ORA-23308: object PRO.TRIGGERBI does not exist or is invalid
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.DBMS_DDL_INTERNAL", line 41
ORA-06512: at "SYS.DBMS_DDL", line 335
ORA-06512: at line 1
It is natural that "PRO.TRIGGERBI does not exist", because of TEST.TRIGGERBI must exists.
At once I will make a reservation that it occurs for the customer. It is said that did nothing. Type itself so became.
Tried to play back - to create the trigger together with a schema name (create or replace schema.trigger), and then to make export and import - has not helped.
Not clearly, why at these strings there is a schema name from which export is made, and is even not clearer, why it in "", instead of is simple 'PRO'.
Thanks.