When an object becomes interrupted, the session also becomes interrupted. Looking at the alert Unity sends to the DBA shows you what the SQL statement was and any difference in response.
Common reasons for interrupted objects include the following:
- A GRANT statement was run on one system but not the other, causing a permissions violation on one system.
- One system running out of perm space for a query.
- One system running out of spool space for a query.
- An external load job failed and left a load lock on a table on one system.
- An external cleanup script dropped an object on one system.
-
At unityadmin, run the following command:
SESSION LIST INTERRUPTED;
Unity displays the session list. For example:unityadmin> session list interrupted; --------------------------------------------- Unity Session Number : 1000 Unity Transaction ID : 13 System : exampledb2 Root Cause : Yes Interrupt Time : 03/27 13:45:45 Time of Original Query : 03/27 13:15:42 Error Code : 3807 Error Text : Object 'example' does not exist. SQL Text : insert into example values (25); Statement Type : Insert
The error in this example indicates the object example does not exist on the system exampledb2. When you create the object example on the system, the interrupt recovers automatically.