Trigger Code Points to Old Schema After Import Tables to Different Schema
(Doc ID 787556.1)
Last updated on MARCH 08, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 8.1.7 to 11.1]
Oracle Database - Enterprise Edition - Version 10.1.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document