Example Object Interrupt Alert
Every interrupted object raises an alert that remains open until the object is recovered and becomes active. For example:
Alert No. : 21 Alert Type : 40053 Alert Description : An inconsistent response was detected from a Teradata system. As a result the object has been placed in the Interrupted state. Alert Details : System 1 (manageddb1) sent an inconsistent message, table sample.base is interrupted: Transaction: 14 SQL: 'INSERT INTO base VALUES(1);' Response 1 from system 1 (manageddb1): row count 0 Code: 3807 Message: Object 'base' does not exist. Response 2 from system 2 (manageddb2): row count 1 Code: 0 Message: Success. Note the alert text contains: - The system it failed on (manageddb1) - The object(s) it failed on (sample.base) - The expected success message and code (success, 0) - The actual failure message and code (Object ‘base’ does not exist, 3807)
The alert remains open until the SQL statement succeeds.
Example Object Interrupt Alert During Recovery Operation
Object interrupt alerts may be raised during recovery operations. For example:
Alert No. : 25 Alert Type : 40033 Alert Description : A recovery operation on an object has been interrupted. Recovery can continue when the current condition is resolved. Refer to the User Guide for more information. Alert Details : System 1 (manageddb1) sent an inconsistent message, table: sample.base, session: 1000 are interrupted: Transaction: 14 SQL: 'insert into base values(1);' Expected response: [success] row count 1 Code: 0 Message: Success Actual response: row count 0 Code: 3807 Message: Object 'base' does not exist.