Backup Server Error Messages 4.1.2 - 4.75.3

4.1.2

2

Device `%1!': volume `%2!' appears  to contain data written in a format that the Backup Server does  not recognize. Please use a different volume, or initialize this  volume through the operating system.

Explanation: Digital OpenVMS only: the tape may be of foreign origin. Digital OpenVMS volume init may know how to confirm that data can be overwritten. Will be followed by an additional operating system message elaborating on the situation.

4.2.3

3

Adaptive Server Enterprise sent an overlapping disk piece.

Explanation: Database is corrupt. Run dbcc diagnostics on your database and refer to Adaptive Server Error Messages for corrective measures.

4.3.2

2

Device %1! is not in use by any session on this server.

Explanation: Indicates user addressed sp_volchanged execution to an inactive device. Check parameters.

4.4.2

2

Device %1! does not belong to session <%2!>.   Notification failed.

Explanation: Indicates a device specified in an sp_volchanged execution does not belong to the named session. Check parameters.

4.5.2

2

Notification attempt failed--message channel for session <%1!> is  closed.

Explanation: Indicates user addressed sp_volchanged execution to a nonexistent session. Check parameters.

4.6.2

2

Failed to create or attach shared tape i/o buffers.

Explanation: Indicates unavailability of shared memory on the platform, possibly caused by memory shortage or kernel configuration limit reached. Check resource availability. This is probably a Backup Server problem.

4.7.2

2

Device %1! already in use.

Explanation: A session attempted to use an archive device owned by another session. Select a different archive device.

4.8.2

2

Mirror device types don't match: %1!.

Explanation: This error is part of a not yet implemented feature, included here only for completeness.

4.9.2

2

Label validation error: read returned %1! reading  label. Read:n%2!

Explanation: These errors indicate a mislabeled or illegal-format archive volume. User should use offline commands to verify that the tape contains Sybase information. The following commands submitted repeatedly in order will display the beginning and ending label characters for each file on the tape:

dd if=<tape_device> bs=2048 | od  -cmt 
-f <tape_device> fsf 1dd  if=<tape_device>
 bs=2048 | od  -c

Zero bytes reported from “dd” and “od” denotes no further data on the tape.

4.10.2

2

Label validation error: first label not VOL1.

Explanation: Same as Error # 4.9.2

4.11.2

2

Label validation error: seek to %1!s failed, %2!.

Explanation: Same as Error # 4.9.2

4.12.2

2

Label validation error: %1! label not found.

Explanation: Same as Error # 4.9.2

4.13.2

2

Device `%1!': can't determine  how to set density on channel %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. The session will exit.

4.14.2

2

Label validation error: too many header labels.

Explanation: Errors similar to 4.9.2–4.12.2.

4.15.2

2

Label validation error: seek to trailer labels failed.

Explanation: Errors similar to 4.9.2–4.12.2.

4.16.2

2

Label validation error: read of tape mark failed.

Explanation: Errors similar to 4.9.2–4.12.2.

4.17.2

2

The stripes on the specified devices have completed, but more  dump stripes exist.

Explanation: This message arises when loading from fewer stripes than the number used at dump time. At load time, there must be at least one instance of every device type used at dump time.

4.18.2

2

Unsupported device type. The stat() system call returned type '%1!' for '%2!'. Refer  to your operating system documentation for more details.

Explanation: The archive device type is either an operating system file, raw fixed disk, raw unloadable disk (for example, floppy disk), tape, or network location (device_name AT remote_backup_server_name). Select a device of a legal type.

4.19.2

2

Label validation error: too many trailer labels.

Explanation: Errors similar to 4.9.2–4.12.2.

4.20.2

2

Device `%1!': I/O error,  write of tape mark failed.

Explanation: Errors similar to 4.9.2–4.12.2.

4.21.2

2

Device `%1!' should be marked `list  only', but is not. Cannot continue this command.

Explanation: Errors similar to 4.9.2–4.12.2.

4.22.1

1

Option %1! is not valid for device `%2!'.

Explanation: Indicates a device option not appropriate for the device type. Review legal options for device types.

4.23.2

2

%1!: read %2!: %3!.

Explanation: Indicates a read or write system call error on a disk or file device. Investigate possible causes (for example, out-of-space condition.) This error aborts the dump or load.

4.24.2

2

%1!: write %2!: %3!.

Explanation: Indicates a read or write system call error on a disk or file device. Investigate possible causes (for example, out-of-space condition.) This error aborts the dump or load.

4.25.2

2

Device `%1!': %2! is an  inappropriate density value for this device.

Explanation: Digital OpenVMS only: the density value specified in the dump or load command is not valid. Expected values are: none specified, 800, 1600, 6250, 6666, 10000, and 38000.

4.26.2

2

Volume validation error: failed to obtain device information,  device: %1! error: %2!.

Explanation: Backup Server is unable to sense the type of a given device. Verify that the device is of a legal type and that the Backup Server process has operating system permission to access it.

4.27.2

2

Volume validation error: attempt to close %1! returned %2!.

Explanation: A UNIX file failed to close. The first parameter is the file name and the second is the UNIX error message that was returned.

4.28.2

2

Device `%1!': set mode failed on  channel %2!; status = 0x%3!.

Explanation: Digital OpenVMS only: could not set device density. The “status” line will contain the operating system error code.

4.29.2

2

Device `%1!': sense mode failed  on channel %2!; status = 0x%3!.

Explanation: Digital OpenVMS only: could not sense device characteristics. The “status” line will contain the operating system error code.

4.30.2

2

Volume validation error: attempt to open %1! returned %2!.

Explanation: Indicates an error opening or closing a database device.

4.31.2

2

Device `%1!': failed to skip back  to beginning of tape on channel %2!; status = 0x%3!.

Explanation: Digital OpenVMS only: volume init error. The “status” line will contain the operating system error code.

4.32.2

2

Failed to allocate memory for tape i/o buffer.

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.33.2

2

Header labels of rejected volume: 

Explanation: Display of the data Backup Server found where it expected ANSI volume labels. Verify that the proper volume is loaded.

4.34.1

1

Device `%1!':\nVolume  name:'%2!'\n

Explanation: Information, no user action necessary.

4.35.1

1

Device `%1!':\t\nLabel  name:\t'%2!'\nVolume  id:\t'%3!'\nAccess code:\t'%4!'\nReserved:\t'%5!'\nOwner  id:\t'%6!'\nReserved:\t'%7!'\nLabeling version:\t%8!\n 

Explanation: Information, no user action necessary.

4.36.1

1

Device `%1!':\t\nFile  name:\t'%2!'\nCreate  date & time:\t%3!, %4!\nExpiration  date & time:\t%5!, %6!\nDatabase  name:\t'%7!'\n 

Explanation: Information, no user action necessary.

4.37.1

1

Device '%1!':\t\nLabel  id:\t'%2!'\nFile name:\t'%3!'\nStripe count:\t%4!\nDevice  typecount:\t%5!\nArchive volume number:\t%6!\nStripe position:\t%7!\nGeneration  number:\t%8!\nGeneration version:\t%9!\n 

Explanation: Information, no user action necessary.

4.38.1

1

Device `%1!':\nLabel id:\t'%2!'\nRecord  format:\t'%3!'\nMax. bytes/block:\t%4!\nRecord  length:\t%5!\nBackup format version:\t%6!\nReserved:\t'%7!'\nDatabase  name:\t'%8!'\nBuffer  offset length:\t%9!\nReserved:\t'%10!'\n 

Explanation: Information, no user action necessary.

4.39.1

1

Device `%1!': illegible file date & time  found; continuing.

Explanation: This error is raised when Backup Server attempts to list the contents of a tape. Media failure or corruption could be indicated. Backup Server will continue listing contents (other files may be fine).

4.41.1

1

Creating new disk file %1!.

Explanation: This message occurs when attempting to dump to a non-existent disk FNAME.

4.42.2

2

Couldn't obtain channel to multibuffering subprocess,  error: %1!

Explanation: An attempt to fork a subprocess failed.

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 system to read or write %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.

4.53.2

2

The load command specifies too many devices of type `%1!':  expected %2!, got %3!.

Explanation: Similar to 4.52.2; however, this is the reverse case. Backup Server cannot load from more stripes than were used for the original dump.

4.54.2

2

The load command specifies too few devices of type `%1!':  expected %2!, got %3!.

Explanation: At least one type of each device must be specified in the load command

4.55.2

2

Device validation error: couldn't open raw device %1!,  error: %2!

Explanation: These errors denote failure to obtain hardware characteristics after establishing the device type. Check permissions on the device special file, investigate the returned operating system error message.

4.56.2

2

Device validation error: couldn't obtain tape drive  characteristics for device %1!, error: %2!

Explanation: These errors denote failure to obtain hardware characteristics after establishing the device type. Check permissions on the device special file, investigate the returned operating system error message.

4.57.2

2

Device validation error: couldn't obtain disk drive  characteristics for device %1!, error: %2!

Explanation: These errors denote failure to obtain hardware characteristics after establishing the device type. Check permissions on the device special file, investigate the returned operating system error message.

4.58.1

1

Database %1!: %2! kilobytes %3!ed.

Explanation: This message conveys the progress of the dump or load session. %3 is “DUMP” or “LOAD”.

4.59.3

3

Archive device %1! must either be a STRIPE or MIRROR.

Explanation: Internal error, contact Sybase Technical Support. This error can occur only if Adaptive Server incorrectly translated a dump command.

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.

4.67.2

2

Device %1!: This tape device requires the CAPACITY  option.

Explanation: Backup Server does not know how to detect end-of-tape on this device. Therefore capacity must be specified on dump, or you must specify the device as a logical device name from sysdevices.

4.68.2

2

Write data to a network device (slave site: %1!,  device: %2!) failed.

Explanation: This messages are self-explanatory. Further details will appear in a 4.82.2 message, which will immediately follow this message.

4.69.2

2

Read data from the network device (slave site: %1!,  device: %2!) failed.

Explanation: This messages are self-explanatory. Further details will appear in a 4.82.2 message, which will immediately follow this message.

4.70.2

2

Device %1!: Unable to query ODM database for device  attributes. ODM error code = %2!.

Explanation: RS6000 only: Since Backup Server has failed to determine device characteristics, it cannot ensure that the device is configured for extended file marks.

4.71.2

2

Device %1!: Is not configured for extended file marks.

Explanation: RS6000 only: Multi-file devices must be reconfigured with extended tape marks. This is so that tape marks can be overwritten on multi-file dumps.

4.72.2

2

Write data to the archive device `%1!' failed.  I/O error: %2!

Explanation: This messages are self-explanatory. Further details will appear in a 4.82.2 message, which will immediately follow this message.

4.73.2

2

Read data from the archive device `%1!' failed.  I/O error: %2!

Explanation: This messages are self-explanatory. Further details will appear in a 4.82.2 message, which will immediately follow this message.

4.74.2

2

Unable to %1! database information file %2!  : %3!.

Explanation: UNIX Backup Servers use a temporary file (created in /tmp) to pass database device names to the sybmultbuf program. An I/O error with this file has occurred. User should verify that /tmp is world-writable, has sufficient space, and contains no unused files of the form BS_servername.number.

4.75.3

3

Device %1!: %2! is not a legal virtual disk  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.