Filter
Top Products
CHAPTER 4 Backup Server Error Messages
719
4.60.2 2 Archive device %1! does not support a valid tapemark.
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.
4.61.2 2 Archive device %1! does not support %2! operation.
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.
4.62.3 3 Multibuffering subprocesses died, archive %1!.
Explanation: This error message may indicate that
the Backup Server cannot find the sybmultbuf
program. Check $SYBASE/bin to see if sybmultbuf is
there.This can also happen if the Backup Server cannot
locate the sybmultbuf binary because it has received
an incorrect parameter.The correct use of the -M flag
is: $SYBASE/bin/backupserver -
M$SYBASE/bin/sybmultbuf A third possibility is that
the Backup Server has had trouble forking the
sybmultbuf process. Check the Backup Server's
srv.log, which may contain more information regarding
this problem. For emulator failure accompanied by
this error message, see Errors in Backup Server Error
Log.
4.63.2 2 End-of-volume reading labels, archive %1!.
Explanation: Backup Server encountered a tape file
mark when attempting to read the ANSI labels.
Indicates validation attempt on a blank tape (not an
error), a non-ANSI tape or programming error. The
tape volume should be examined off line with the
commands given above. If the volume was the final
volume of the load and the I/O has proceeded normally
to this point (as evinced by progress messages, etc.)
then the load I/O can be considered successful. If not,
the load should be reattempted.
4.64.3 3 SANITY: Scheduled ACK events exceed stripe count.
Explanation: Internal error, contact Sybase
Technical Support.
Number Severity Text and Explanation