Filter
Top Products
CHAPTER 4 Backup Server Error Messages
705
2.19.2 2 Invalid verbosity level: A verbosity level specifier
must be an integer from 0 to 3.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit.
3.1.2 2 Unrecognized RPC received--ignored.
Explanation: The session initiator sent an
unrecognized RPC. Indicates ad hoc RPC was sent, or
a programming bug in Adaptive Server or Backup
Server. Contact Sybase Technical Support.
3.2.2 2 Symbol %1! not found in TDS table.
Explanation: Internal message; customers will likely
never see it; it is only included here for completeness.
3.3.2 2 %1!: May not specify Backup Server scanning or free-
page clearing for a secondary phase.
Explanation: Internal error, contact Sybase
Technical Support. These errors indicate a violation of
the dump synchronization protocol of the RPC API.
3.4.2 2 %1!: Must specify Backup Server scanning in order to
clear free pages at LOAD time.
Explanation: Internal error, contact Sybase
Technical Support. These errors indicate a violation of
the dump synchronization protocol of the RPC API.
3.5.2 2 %1!: Could not lock session %2! to begin phase.
Explanation: Internal error, contact Sybase
Technical Support. This indicates an error or bug in the
Open Server MUTEX mechanism.
3.6.1 1 %1!: Phase %2! is currently active. Only one phase
may be active at a time.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.7.2 2 %1!: phase %2! already concluded.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
Number Severity Text and Explanation