Server error messages 12700 - 12799 – Sybase 11.9.x-12.5 User Manual
Page 515
CHAPTER 6 Adaptive Server Error Messages
1189
Server Error Messages 12700 - 12799
12537
16
Database ’%.*s’ is in QUIESCE DATABASE state. It will recovered as for LOAD
DATABASE and left off line.
Explanation:
This is an informational message showing how the specified database will
be treated upon server restart.
12538
10
Database ’%.*s’ is in QUIESCE DATABASE state, but the server is not booted with the
’-q’ flag. The QUIESCE DATABASE state will be ignored, and the database will be
recovered and brought on line normally.
Explanation:
This is an informational message showing how the specified database will
be treated upon server restart.
12539
10
Database ’%.*s’ is a system database. Its QUIESCE DATABASE state will be ignored,
and the database will be recovered and brought on line normally.
Explanation:
This is an informational message.
12540
10
Modified timestamp on page %ld of (%d, %d) which falls between log old ts (%d, %d)
and log new ts (%d, %d) during recovery of database id %d.
Explanation:
This is an informational message.
12541
10
Modified timestamp on page %ld of (%d,%d) which is older than log old
ts (%d, %d)
during recovery of database id %d.
Explanation:
This is an informational message.
12542
16
Load the next transaction log in the load sequence, or use ONLINE DATABASE with
nooptions to end the load sequence.
Explanation:
This informational message is displayed following a transaction load, and
requires one of the indicated actions.
12543
20
During recovery, quiescent first log marker was not found for database ’%.*s’. The
forward log scan was started on marker (%d, %d).
Explanation:
Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Number
Severity
Text and Explanation
Number
Severity
Text and Explanation
12700
18
Suspect Granularity: Bad suspect item type `%d' (`%d') due to an internal error. Please
contact Sybase Technical Support.
Explanation:
Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.