Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Autosequence for Purge is showing Deadlock error.

Status
Not open for further replies.

Rahulsh

Technical User
May 29, 2020
11
IN
Purge Historical Totals is giving error in 3700d logs

ri May 29 00:15:01 2020 | SERVER | AutoSeqServer | 0 | Autosequence 10211 step 9 of type S has begun. |
Fri May 29 00:15:01 2020 | SERVER | AutoSeqServer | 0 | Purge Historical Totals |
Fri May 29 00:15:01 2020 | SERVER | Autosequence.dll | 0 | {CALL MICROS.sp_PurgeHistory} |
Fri May 29 00:15:52 2020 | SERVER | Autosequence.dll | [highlight #FCE94F]0 | SQLExecDirect: (40001)[Sybase][ODBC Driver][SQL Anywhere]Deadlock detected |[/highlight] [highlight #FCE94F][/highlight]
Fri May 29 00:15:52 2020 | SERVER | AutoSeqServer | 0 | Autosequence 10211 step 9 of type S has encountered a stored procedure error...Error executing stored procedure. |
Fri May 29 00:15:52 2020 | SERVER | Autosequence.dll | 0 | Step completed. |
Fri May 29 00:15:52 2020 | SERVER | Autosequence.dll | 0 | Autosequence 10211 step 9 of type S has completed in 51 seconds.

Any Idea how we can fix this issue?
 
I would try validating the database to see if you can find further error. note than validating on a live environment might render you db unusable set up a test environment and post back with the findings.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top