Number
|
Severity
|
Text and Explanation
|
|---|
4.76.3
|
3
|
Device %1!: %2! is not a legal virtual block number.
Explanation: Internal error, contact Sybase Technical Support. Backup Server
cannot determine what portions of the specified database device
should be backed up because information about the device sent from
Adaptive Server does not correspond with the actual physical device.
|
4.77.2
|
2
|
Device %1! may not be used: minimum blocksize for I/O exceeds device maxiumum of %2!.
Explanation: Backup Server requires tape devices to support an I/O
size of at least 2K. The tape device found has a maximum I/O
size less than 2K. This message should never appear. If it does,
user should check device name specification. If correct, user must
use another device.
|
4.78.2
|
2
|
Option %1!: illegal value %2!.
Explanation: This indicates the user has supplied an illegal value for
a device option. Review the device options and legal values.
|
4.79.2
|
2
|
Server %1!, device %2!: illegal I/O size %3!--max %4!.
Explanation: Indicates a programming bug in a local or remote Backup Server.
The I/O service layer has received a read or write request
size that exceeds the available buffer size.
|
4.80.2
|
2
|
Server %1!, device %2!: You must use the no-rewind-on-close tape device.
Explanation: Backup Server requires all tape devices to use the no-rewind-on-close
option, so that it can fully control tape positioning.
|
4.81.2
|
2
|
Server %1!: device %2! is open for writing; you may not specify the @fname parameter when changing volumes.
Explanation: The @fname parameter is meaningful only at load time,
to select a certain file to load from a multi-file volume. At dump
time, the Backup Server assigns a name to the file that will contain
the dump. Message 6.28.1 returns the assigned name.
|
4.82.2
|
2
|
Operating system error, server %1! device %2!: code %3! message %4!.
Explanation: This message appears when a system call (perhaps performed
as part of a higher-level operation) has failed. It is intended
primarily for diagnostic use and should be interpreted in the context
of immediately preceding messages.
|
4.83.2
|
2
|
Device %1!: The specified blocksize %2! is not within the range of %3! to %4!.
Explanation: The user-specified block size is out of range. Respecify block
size within the listed limits.
|
4.84.1
|
1
|
Device %1!: The specified blocksize of %2! will be truncated to %3! which is a multiple of %4!.
Explanation: The user-specified block size was truncated to be a multiple
of 2048.
|
4.85.1
|
1
|
Device %1!: Disk model %2! does not exist in the /etc/disktab file. Using default values for this device.
Explanation: The disk device is not configured in /etc/disktab,
so a default disk block size will be used.
|
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.
|
4.92.2
|
2
|
Unregistering 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.
|
4.93.2
|
2
|
Read from %1! failed: OS error returned %2!, errno %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.
|
4.94.2
|
2
|
Write to %1! failed: OS error returned %2!, errno %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.
|
4.95.2
|
2
|
Unable to expand file %1!. OS error returned %2!.
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.96.2
|
2
|
Unable to set end of file for %1!. OS error returned %2!.
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.97.2
|
2
|
Asynchronous I/O failed for %1!. OS error returned %2!.
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.98.2
|
2
|
Unable to reserve device %1! in Control Mode. OS error returned %2!.
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.99.2
|
2
|
Open unable to mount media for device %1! : OS error returned %2!.
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.100.2
|
2
|
Unable to dismount media for device %1! : OS error returned %2!.
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.101.2
|
2
|
Unable to reserve device %1! in IO Mode. OS error returned %2!.
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.102.2
|
2
|
Unable to locate device %1! in the Media Manager database.
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.103.2
|
2
|
Requested seek type %1! is invalid.
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.104.2
|
2
|
Memory Allocation for I/O buffer 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.105.2
|
2
|
Received invalid return code %1! in I/O completion status.
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.106.2
|
2
|
Unable to forward a file mark: 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.
|
4.107.2
|
2
|
Error in forwarding %1! file marks.
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.108.2
|
2
|
Unable to back over a file mark: 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.
|
4.109.2
|
2
|
Error in backing over %1! file marks.
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.110.2
|
2
|
Attepmt to write EOF on device %1! failed. OS error returned %2! .
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.111.2
|
2
|
Unable to rewind device %1!: OS error returned %2!.
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.112.2
|
2
|
Unable to unload media in device %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.
|
4.113.2
|
2
|
Unable to go to end of media.
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.114.2
|
2
|
Unable to retension device.
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.115.2
|
2
|
Open of %1! failed, unable to expand device name to fullpath.
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.116.2
|
2
|
Open of %1! failed, unable to determine volume number. Volume = %2! Fullpath = %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.
|
4.117.2
|
2
|
Unable to get volume mapping information for volume %1! in path %2!.
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.118.3
|
3
|
Unable to detect database device %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.
|
4.119.2
|
2
|
Unable to release device %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.
|
4.120.3
|
3
|
Unable to locate state information for this stripe.
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.121.3
|
3
|
Local semaphore handle is NULL for asynchronous disk i/o.
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.122.2
|
2
|
Unable to allocate semaphore for disk operations on device %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.
|
4.123.2
|
2
|
Operating system error, server %1! device %2! errcode %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.
|
4.124.2
|
2
|
Archive API error for device='%1!': Vendor application name=%2!, Library version=%3!, API routine=%4!, Message=%5!
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.125.1
|
1
|
Archive API information for device='%1!': Vendor application name=%2!, Library version=%3!, Message=%4!.
Explanation: Information, no user action necessary.
|
4.126.3
|
3
|
Unable to get current date and time. Internal error.
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.127.2
|
2
|
Internal Error on device %1!: Attempting to determine if device is non-rewinding. Failed to get the OS version when converting data returned from uname(2).
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.128.2
|
2
|
Failed to start multibuffering subprocesses for archive device `%1!'. Look at the Backup Server error log for more information.
Explanation: Either the sybmultbuf process was not created successfully
or the sybmultbuf process died immediately after creation. Check
the backup server error log for any error message from the sybmultbuf
process.
|
4.129.2
|
2
|
Device %1! may not be used with physical blocksize configured as %2!. In order to be usable by Backup Server a device's blocksize must be configured to be both less than or equal to %3! and to be an even divisor of that value.
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.130.2
|
2
|
Device: `$1!'. The stream identifier `%2!' contains invalid characters. The valid character are, alphabetic, numeric, and underscore.
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.131.2
|
2
|
Device: `%1!'. The stream identifier `%2!' has an incorrect length. A valid length is from 1 to 30 bytes long.
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.132.1
|
1
|
Attempting to open bytestream: `%1!'
Explanation: Information, no user action necessary.
|
4.132.1
|
1
|
Attempting to open byte stream device: `%1!'
Explanation: Information, no user action necessary.
|
4.133.2
|
2
|
Invalid path or no execute permission for multibuffering subprocess binary: %1!
Explanation: The sybmultbuf binary could not be found. Check the pathname
in the -M option or $SYBASE/bin for
the existence of sybmultbuf binary (in NT sybmbuf.exe).
Also, check if the binary has execute permissions.
|
4.134.2
|
2
|
Invalid Device: you cannot dump to or load from the null device, '%1!'.
Explanation: You cannot dump to null device since you cannot recover the
dump from it. Select a device of a legal type.
|
4.135.2
|
2
|
Invalid Device: you cannot dump to or load from a directory, '%1!'.
Explanation: The specified archive device is a directory name. Specify
a device name or a disk file name.
|
4.136.2
|
2
|
uname failed with OS error '%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.
|
4.137.2
|
2
|
Invalid OS release number '%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.
|
4.138.2
|
2
|
Device '%1!': operating system call 'readlink' failed with error '%2!'.
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.139.2
|
2
|
[%1!] The '%2!' call failed for device '%3!' with error number %4! (%5!). Refer to your operating system documentation for further details. Look for '%6!' in the backup server errorlog for additional information from SYBMULTBUF.
Explanation: The message has 93 secondary state values used to determine
where a failure occurred in sybmultbuf.
|
4.140.2
|
2
|
[%1!] The '%2!' call failed with error number %3! (%4!). Refer to your operating system documentation for further details. Look for '%5!' in the backup server errorlog for additional information from SYBMULTBUF.
Explanation: The message has 93 secondary state values used to determine
where a failure occurred in sybmultbuf.
|
4.141.2
|
2
|
[%1!] The '%2!' call failed for device '%3!' with error number %4! (%5!). Refer to your operating system documentation for further details.
Explanation: The message has 93 secondary state values used to determine
where a failure occurred in sybmultbuf.
|
4.142.2
|
2
|
[%1!] The '%2!' call failed with error number %3! (%4!). Refer to your operating system documentation for further details.
Explanation: The message has 93 secondary state values used to determine
where a failure occurred in sybmultbuf.
|
4.143.2
|
2
|
[%1!] A failure occurred for device '%2!'. Look for '%3!' in the backup server errorlog for additional information from SYBMULTBUF.
Explanation: The message has 93 secondary state values used to determine
where a failure occurred in sybmultbuf.
|
4.144.2
|
2
|
[%1!] A failure occurred. Look for '%2!' in the backup server errorlog for additional information from SYBMULTBUF.
Explanation: The message has 93 secondary state values used to determine
where a failure occurred in sybmultbuf.
|
4.145.2
|
2
|
[%1!] Error for device '%2!'. %3!
Explanation: The message has 93 secondary state values used to determine
where a failure occurred in sybmultbuf.
|
4.146.2
|
2
|
[%1!] Error occurred. %2!
Explanation: The message has 93 secondary state values used to determine
where a failure occurred in sybmultbuf..
|
4.147.2
|
2
|
Operating system error. Code %1! message %2!.
Explanation: The message has 93 secondary state values used to determine
where a failure occurred in sybmultbuf.
|
