Trigger Code Points to Old Schema After Import Tables to Different Schema
Last updated on JUNE 15, 2015
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 8.1.7 to 11.1]
Oracle Database - Enterprise Edition - Version 10.1.0.2 and later
Information in this document applies to any platform.
***Checked for relevance on 19-Dec-2013***
An import has been done with FROMUSER=... and TOUSER=... parameters using the original exp/imp utilities.
- OR -
A data pump import has been done using the REMAP_SCHEMA parameter using expdp/impdp.
On the target database, the trigger code is still pointing to the old schema.
Also, an error
may occur during import because the trigger in the new schema points to a nonexistent schema.table or the new user does not have privileges on the original schema.table.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms