Issue with triggers while importing (imp) to another user

Question

hi all,
we have two oracle databases (oracle 10g R2)
1. production
2. test (clone of production)
whenever we need to update the test database for the developers we take a full export dump of the production (hardly 20GB) and import the same into test after dropping the tables in the required schema
export system/***@production file=exp.dmp log=log.log full=y statistics=nonewe have a schema named user1, in production.
same is the case in test
I got a request to refresh the user1 schema in test, but with a different schema user2 (new schema created), as there was some critical dev. work going on with user1 schema.
hence i didnt want to touch the user1 schema in test environment & after taking an export dump of the production i didnt import it into the same schema.
i imported the dump data to user 2 schema
imp system/***@test file=exp.dmp log=implog.log fromuser=user1 touser=user2 statistics=nonethe moment i did this developers working with user1 schema started facing issues when their code hit triggers on user1 schema. all insert/update triggers in the user1 schema started pointing to corresponding tables in user2.
any clues why something like this happened? what was the mistake in he imp command i used?
thanks for your time

Answer 1

Hi,
Check for the trigger source in your original schema. If it has schema name mentioned before the tables on which the trigger is created, it would create problem during import. While importing, it will reference the previous schema , though you are importing it in new schema.
If this is the case, remove the schema name from the source and then export and re import.
Regards
Vinitaa