Why does an invalid trigger in one schema stop processing in another?
From: Robert Nicholson <robert.nicholson_at_gmail.com>
Date: Sat, 10 Jul 2010 09:20:22 -0700 (PDT)
Message-ID: <ed8ec723-edf1-41f2-aa74-6e84e127ecdb_at_a30g2000yqn.googlegroups.com>
So, yesterday I saw something disturbing in the log of one of our processes. We have a process that writes to data in schema A but it's log was complaining about an invalid trigger in schema B where there is no relationship defined that should create any dependency b/w these two schemas A and B.
Date: Sat, 10 Jul 2010 09:20:22 -0700 (PDT)
Message-ID: <ed8ec723-edf1-41f2-aa74-6e84e127ecdb_at_a30g2000yqn.googlegroups.com>
So, yesterday I saw something disturbing in the log of one of our processes. We have a process that writes to data in schema A but it's log was complaining about an invalid trigger in schema B where there is no relationship defined that should create any dependency b/w these two schemas A and B.
Why is it that when I was writing to objects in Schema A that it complained about an invalid trigger in Schema B when there is no relationship b/w these two schemas or sets of objects?
The only relationship is that the objects and schemas are sharing the same tablespaces.
This was in Oracle 11g RAC Received on Sat Jul 10 2010 - 11:20:22 CDT