Sybase 11.9.x-12.5 User Manual
Page 35
CHAPTER 4 Backup Server Error Messages
709
3.32.2
2
Incorrect type for parameter #%1! for RPC %2!;
expected %3! got %4!.
Explanation:
Internal error, contact Sybase
Technical Support. Error in the session initiator
(Adaptive Server or Backup Server), a violation of the
RPC API.
3.33.2
2
SANITY: premature last run list.
Explanation:
Internal error, contact Sybase
Technical Support.
3.34.2
2
SANITY: more stripes than extents.
Explanation:
Internal error, contact Sybase
Technical Support.
3.35.2
2
RPC %1! refused following previous FAILURE return.
Explanation:
Internal error, contact Sybase
Technical Support. Error in the session initiator
(Adaptive Server or Backup Server), a violation of the
RPC API.
3.36.2
2
RPC %1!: parameter %2! may not be NULL.
Explanation:
Internal error, contact Sybase
Technical Support. Error in the session initiator
(Adaptive Server or Backup Server), a violation of the
RPC API.
3.37.2
2
SANITY: RPC %1!: expected parameter %2! got
parameter %3!.
Explanation:
Internal error, contact Sybase
Technical Support. Error in the session initiator
(Adaptive Server or Backup Server), a violation of the
RPC API.
3.38.2
2
There is no primary phase %1! for secondary phase
%2!.
Explanation:
Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.39.2
2
RPC %1! can only be executed in a slave server.
Explanation:
These errors indicate an Adaptive
Server programming error, violation of the RPC API.
Number
Severity
Text and Explanation