Filter
Top Products
CHAPTER 4 Backup Server Error Messages
723
4.86.2 2 Unable to initialize Async IO on the database device
%1!. Backup Server must use Async IO on a block
special devices because Adaptive Server Enterprise is
doing the same.
Explanation: This is an HP-specific error. If
Adaptive Server Enterprise is using asynchronous I/O
for a block special device, then backup Server must do
the same in order to guarantee disk coherency. Block
I/O without asynchronous isa buffered I/O operation.
With asynchronous I/O, it is not buffered. If two
processes access the same disk, one using buffered I/O
and the other using nonbuffered I/O, the current image
of a disk page may be ignored by one of the processes.
4.87.2 2 Device %1!: uname() failed with error: %2!.
Explanation: HP only: Backup Server is trying to
identify the machine as an HP 800 or HP 700. The
uname call (which gets this information) failed.
4.88.2 2 Device %1!: Could not determine device type due to
unknown machine model. Expected models are
HP9000/800 & 700 series.
Explanation: Related to Error 4.87.2. After getting
the machine name with the uname call, Backup Server
could not identify the device type because it could not
identify the machine type. Only 800 and 700 series
machines are expected.
4.89.2 2 Allocation of Resource Tag failed.
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.90.2 2 Allocation of Resource Tag for tape i/o failed.
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.91.2 2 Registering of application failed. OS error returned
%1!.
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.
Number Severity Text and Explanation