Server Error Messages 5200 - 5299

Number

Severity

Text and Explanation

5201

26

 Failure concurrent with dump in database %d:  DFL Manager caller must be DUMP DATABASE;  instead, command token was %d.

Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.

5202

26

 DUMP DATABASE for database %d failed:  DFL synchronisation is prematurely set.

Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.

5203

17

 DUMP DATABASE for database %d failed:  insufficient memory to allocate DFL.

Explanation: Command failed due to resource limitation. Modify the command to fit available resources, retry when the resource is available, or contact your System Administrator to address the resource problem.

5204

26

 DUMP DATABASE for database %d failed:  initial DFL allocation will not fit in initial memory block.

Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.

5205

26

 DUMP DATABASE for database %d failed:  duplicate dflheader found.

Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.

5206

26

 DUMP DATABASE for database %d failed:  dump flushlist structures have not been allocated.

Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.

5207

26

 DUMP DATABASE for database %d failed:  DFL synchronisation is not set.

Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.

5208

10

 User aborted DUMP DATABASE for database %d.

Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.

5209

26

 Failure during concurrent dump in database %d:  DFL Manager caller must not be DUMP DATABASE, but is.

Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.

5210

26

 Failure during dump in database %d:  caller does not possess dump lock.

Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.

5211

26

 Failure concurrent with dump in database %d:  caller does not possess flushlist lock.

Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.

5212

26

 Failure concurrent with dump in database %d:  no DFL pieces on not-full list.

Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.

5213

26

 Failure concurrent with dump in database %d:  caller improperly holds flushlist lock.

Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.

5214

20

 During DUMP DATABASE for database %d, flushlist closure not complete at end of synchronisation.

Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. Report the error to your System Administrator so dbcc diagnostics can be run.

5215

26

 DUMP DATABASE for database %d failed:  could not find dflinfohead to deallocate.

Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.

5216

26

 DUMP DATABASE for database %d failed:  trailing piece in not-full list proved not-empty.

Explanation: An internal locking/synchronization rule was broken. Report the error to your System Administrator. Shut down and restart Adaptive Server.

5217

20

 DFL Manager failed to sleep.

Explanation: Adaptive Server encountered an internal error affecting the current process. Report the error to your System Administrator.