CHAPTER 4 Backup Server Error Messages
717
4.43.2 2 Couldn't create multibuffering subprocess.
Explanation: Backup Server was unable to complete
start-up of the multibuffering subprocess. File
descriptors may be exhausted (Error 4.42). Retry
session when Backup Server activity is lower. Possible
virtual memory shortage (Error 4.43).
4.45.2 2 The maximum number of %1! stripe devices has been
exceeded.
Explanation: A single dump or load session may use
a maximum of 32 archive stripes. Reduce the number
of archive devices in the dump or load command.
4.46.2 2 Length error on I/O -- transferred %1! bytes, expecting
to transfer %2! bytes.
Explanation: Digital OpenVMS only: Backup
Server requested the operating syst em to read o r wri te
%2 bytes and only %1 bytes were actually transferred.
Probably device or media failure.
4.50.2 2 Device %1!: The blocksize %2! of the dump file is not
within the range of %3! to %4!.
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 will exit.
4.51.2 2 Archive devices `%1!' and `%2!' do not belong to the
same file group.
Explanation: Internal error, contact Sybase
Technical Support. The tapes/devices do not belong to
the same archive group. To the Backup Server, it
appears that “tapes” from two different dumps are
mounted in devices requested by the current load.
4.52.2 2 There should be %1! load stripes, but the command
only specifies %2!. One or more required devices have
been omitted from the command line.
Explanation: Backup Server supports database loads
on fewer devices than were used for the dump.
However, at least one device of each type (4 mm, 8
mm, and so on) must be supplied. Backup Server
verifies that a load command specifies all needed
device types. If it does not, this error is raised.
Number Severity Text and Explanation