I try to use Teradata Enterprise Stage to write data back to Teradata. It is a simple job.
And if I set Teradata Enterprise Stage as sequencial mode, it works well. And if I make it as parallel mode, always get deadlock error ? I leave the partition option as auto.
Why ? or I need to explicit set up the partition method ?
Thanks
Teradata Enterprise Stage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Be more precise about where the deadlock occurs. For example, is it in the sync table or in the target table itself? What level of locking is being requested? (If multiple nodes request table-level locking you will definitely get a deadlock.)
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 161
- Joined: Wed Aug 02, 2006 4:30 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 161
- Joined: Wed Aug 02, 2006 4:30 am
The detailed error message is like
Teradata_Enterprise_122,78: TeraSync:DB Call Failure(success check) Info = 0, Code = 2631, Message = Transaction ABORTed due to Deadlock.error code = 1
TeraSync:DB Call Failure(success check) Info = 0, Code = 2631, Message = Transaction ABORTed due to Deadlock. error code = 1
DBCAREA msg_txt: Completed successfully. CLI Error Message: Completed successfully.
TeraSync:ExecuteImmediate failed for 'update Schema.terasync set ctlstate = 2, eventCount = eventCount + 1 where cookie = 1269828913'. Error Code = 2631error code = 1
TeraSync:ExecuteImmediate failed for 'update Schema.terasync set ctlstate = 2, eventCount = eventCount + 1 where cookie = 1269828913'. Error Code = 2631 error code = 1
DBCAREA msg_txt: Completed successfully. CLI Error Message: Completed successfully.
TeraSync: error advancing to state 2.0, unable to execute 'update Schema.terasync set ctlstate = 2, eventCount = eventCount + 1 where cookie = 1269828913'.
slave session failed to signal eSlaveReady.
Teradata_Enterprise_122,78: TeraSync:DB Call Failure(success check) Info = 0, Code = 2631, Message = Transaction ABORTed due to Deadlock.error code = 1
TeraSync:DB Call Failure(success check) Info = 0, Code = 2631, Message = Transaction ABORTed due to Deadlock. error code = 1
DBCAREA msg_txt: Completed successfully. CLI Error Message: Completed successfully.
TeraSync:ExecuteImmediate failed for 'update Schema.terasync set ctlstate = 2, eventCount = eventCount + 1 where cookie = 1269828913'. Error Code = 2631error code = 1
TeraSync:ExecuteImmediate failed for 'update Schema.terasync set ctlstate = 2, eventCount = eventCount + 1 where cookie = 1269828913'. Error Code = 2631 error code = 1
DBCAREA msg_txt: Completed successfully. CLI Error Message: Completed successfully.
TeraSync: error advancing to state 2.0, unable to execute 'update Schema.terasync set ctlstate = 2, eventCount = eventCount + 1 where cookie = 1269828913'.
slave session failed to signal eSlaveReady.
-
- Charter Member
- Posts: 47
- Joined: Fri Mar 18, 2005 5:59 am
There is no transaction handling in teradata enterprise stage compared to oracle stages.
enterprise stage will have error tables created, if there is a problem,
however it is not the same as transaction handling.
As for the deadlock, as ray suggested as well as from the log, it is trying to update the terasync table, which causes the problem.
enterprise stage will have error tables created, if there is a problem,
however it is not the same as transaction handling.
As for the deadlock, as ray suggested as well as from the log, it is trying to update the terasync table, which causes the problem.