Question : Oracle DB process trigger from different schema

I have a very weird situation.  I have four schema's in the db.  Two each for a application which are one for processing and one for history.  I imported under another set of schema names from a dev db two more schema to consolidate space on the server.

Now when the trigger fires on one of the schema....it tries to fire the trigger that has been imported even though the owner is different.  How can that be?  The trigger names are the same but they are owned by different schema.  The triggers are owned by the schema in which they reside.

I am at a loss on how this could happen.  

Any ideas?

Answer : Oracle DB process trigger from different schema

Yes - there was a problem when importing under other schema name.
The trigger are imported but not changed - see at the trigger definitions -
the use the old schema name and if the tables use qualified name - the
old schema name and table name.
So every event on original tables fires also the imported triggers.
Oracle Import do not changes the code in PL/SQL routines - it doesn't know
how correctly to do this.

The workaround could be using DBCA to create a new instance on the
computer you use as store and to import the schemas there.
So you will avoid the 'echo'effect.
Of course you can write a small PL/SQL procedure that will disable the
triggers after import, but you have also to enable them if you will
try to Export for usage the stored schemas.