Number
|
Severity
|
Text and Explanation
|
|---|
5.1.2
|
2
|
The mirror devices (site: %1!) and the primary device(site: %2!) must reside at the same site.
Explanation: This message is part of the uncompleted dump mirroring feature.
All mirrors for a stripe must reside on the same host.
|
5.2.2
|
2
|
Cannot allocate the login record.
Explanation: This error occurs when the dblogin call fails, probably due
to a memory resource problem.
|
5.3.2
|
2
|
Cannot open a connection to the slave site `%1!'.
Explanation: An attempt to connect to a remote Backup Server encountered
this failure. Look for:
|
5.4.2
|
2
|
RPC (`%1!') initialization fails.
Explanation: Internal error, contact Sybase Technical Support. Failure
in dbrpcinit.
|
5.5.2
|
2
|
Cannot add a parameter to the RPC (`%1!') call
Explanation: Internal error, contact Sybase Technical Support. Failure
in dbrpcparam.
|
5.6.2
|
2
|
Cannot send the RPC (`%1!').
Explanation: Check to see that the local or remote Backup Server is still
available.
|
5.7.2
|
2
|
RPC (`%1!') execution failed.
Explanation: These messages point to difficulties in issuing an RPC to
a remote Backup Server. Probable cause is an Open Server programming
error.
|
5.8.2
|
2
|
RPC as_cmd execution failed - slave server: %1!, device: %2!, command type: %3!.
Explanation: These messages point to difficulties in issuing an RPC to
a remote Backup Server. Probable cause is an Open Server programming
error.
|
5.9.2
|
2
|
RPC as_pagerun execution failed - slave server: %1!, device: %2!.
Explanation: These messages point to difficulties in issuing an RPC to
a remote Backup Server. Probable cause is an Open Server programming
error.
|
5.11.2
|
2
|
RPC bs_end_load execution failed - slave server: %1!, device: %2!.
Explanation: These messages indicate failure to deliver the named RPCs
to the remote Backup Server. Adjacent messages provide more detail.
Probable causes are sudden death of the remote Backup Server, or
a programming error.
|
5.12.2
|
2
|
Missing device name parameter @devname, RPC: %1!, command: %2!.
Explanation: Internal error, contact Sybase Technical Support. Check the
compatibility of local and remote Backup Servers.
|
5.13.2
|
2
|
Received an unknown command. RPC: %1!, command: %2!.
Explanation: Internal error, contact Sybase Technical Support. Check the
compatibility of local and remote Backup Servers.
|
5.14.2
|
2
|
Cannot set the value of an RPC return parameters, RPC: %1!
Explanation: Internal error, contact Sybase Technical Support. Check the
compatibility of local and remote Backup Servers.
|
5.15.2
|
2
|
Slave server received %1! bytes of data that is more than @count %2! specified in as_pagerun.
Explanation: Internal error, contact Sybase Technical Support. Violation
of the RPC API.
|
5.16.2
|
2
|
DB-Library error, error number %1!, severity %2!: %3!
Explanation: The installed DB-Library error handling function returns this
error. Adjacent messages provide more detail.
|
5.17.2
|
2
|
Cannot get the character set currently in use.
Explanation: The remote Backup Server could not set the character set to
its default setting for the initial connection from a client of
the local Backup Server.
|
5.18.2
|
2
|
Cannot set character set `%1!' in the login record.
Explanation: The remote Backup Server could not set the character set to
the set specified by the remote connection.
|
5.19.2
|
2
|
Cannot get the language currently in use.
Explanation: The remote Backup Server could not set the language to its
default setting for the initial connection from a client of the
local Backup Server.
|
5.20.2
|
2
|
Cannot set language `%1!' in the login record.
Explanation: The remote Backup Server could not set the language specified
by the remote connection.
|
5.21.2
|
2
|
Remote DUMP/LOAD is not allowed when interfacing to a stripe for 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.
|
6.28.1
|
1
|
Dumpfile name `%1!' section number %2! mounted on %3! `%4!'
Explanation: This message has a critical role. It contains the file name
assigned to the archive file at dump time. If the dump goes to
a multifile volume, the user or the application must record the
dumpfile name in persistent storage and specify it at load time
in order to locate the file for loading from the multifile archive. If
the dumpfile name is lost, it will be necessary to scan the tape
off- line with the commands given under message 4.12.2 to locate
the dumpfile name.
|
6.29.1
|
1
|
unnamed dumpfile, section number %1! mounted on device `%2!'
Explanation: Dumpfile name is lost. See above message.
|
6.30.1
|
1
|
Device %1!: Volume cataloguing complete.
Explanation: This is an informational message indicating that the load
with listonly command has completed successfully for
the specified archive device.
|
6.31.2
|
2
|
Volume rejected.
Explanation: Backup Server refuses to use the mounted volume. Adjacent
messages provide more detail. The volume either has non-ANSI structure
or there is a Backup Server programming error.
|
6.32.2
|
2
|
%1!: volume not valid or not requested (server: %2!, session id: %3!.)
Explanation: The data on the device is not in proper dump format. If you
are loading, use another volume. If you are dumping, user may overwrite.
|
6.33.2
|
2
|
%1!: Volume already contains %2! kilobytes, which is larger than the specified capacity of %3! kilobytes.
Explanation: A multi-file dump device contains more data than was specified
in the capacity clause.
|
6.34.2
|
2
|
\n%1!\n%2!\n%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.
|
6.35.2
|
2
|
Volume validation error: bad magic number %1!, expected %2!.
Explanation: Indicates a non-Sybase archive mounted on the drive. Replace
with a Sybase dump archive.
|
6.36.2
|
2
|
Header labels of rejected volume:
Explanation: Preamble message to display labels of rejected volume.
|
6.37.2
|
2
|
Volume validation error: Load block size of %1! must equal volume block size of %2!.
Explanation: Indicates a non-Sybase archive (illegal block size) mounted
on the drive. Replace with a Sybase dump archive.
|
6.38.1
|
1
|
Header labels of volume on `%1!':
Explanation: Information, no user action necessary.
|
6.39.0
|
0
|
tape drive
Explanation: Internal informational message, usually a component of another
message. No user action necessary.
|
6.40.0
|
0
|
disk
Explanation: Internal informational message, usually a component of another
message. No user action necessary.
|
6.41.1
|
1
|
Header labels of mounted volume:
Explanation: Preamble message to display labels of mounted volume.
|
6.42.0
|
0
|
disk file
Explanation: Internal informational message, usually a component of another
message. No user action necessary.
|
6.43.0
|
0
|
floppy disk
Explanation: Internal informational message, usually a component of another
message. No user action necessary.
|
6.44.0
|
0
|
device
Explanation: Internal informational message, usually a component of another
message. No user action necessary.
|
6.45.1
|
1
|
Be sure to remove the tape/floppy from drive %1! (server: %2!, session id: %3!).
Explanation: Reminder message appears when nounload (default) is specified
for an unloadable device.
|
6.46.1
|
1
|
%1!: Mount the next volume to read.
Explanation: Requests mounting of the next volume in sequence for load.
|
6.47.1
|
1
|
%1!: Mount the next volume to write.
Explanation: Requests mounting of the next volume in sequence to continue
dump.
|
6.48.1
|
1
|
%1!: Volume on device `%2!' has restricted access (code %3!).
Explanation: Reports ANSI restricted-access code in label prior to confirming
overwrite request.
|
6.49.1
|
1
|
%1!: Volume to be overwritten on `%2!' has not expired: creation date on this volume is %3!, expiration date is %4!.
Explanation: Requests verification of overwrite of unexpired volume.
|
6.50.1
|
1
|
%1!: Dumpfile `%2!' section %3! found instead of `%4!' section %5!.
Explanation: The volume just read is out of order. Mount the correct volume.
|
6.51.1
|
1
|
%1!: Mount the next volume to search.
Explanation: Reports that the requested dumpfile (specified by the file
option) was not found on the volume.
|
6.52.1
|
1
|
%1!: Volume to be overwritten on `%2!' has unrecognized label data.
Explanation: A single file dump device has non-Sybase dump data. This is
a prompt set to the user asking if the data is to be overwritten.
|
6.53.1
|
1
|
%1!: Volume on device `%2!' cannot be opened for write access. Mount another volume.
Explanation: Check write protection.
|
6.54.1
|
1
|
%1!: Volume on device `%2!' is expired and will be over written.
Explanation: A single dump file device has media with expired dump data
on it. The user is prompted whether the data is to be overwritten.
|
6.55.1
|
1
|
The volume mounted on `%1!' does not belong to the same archive as other, previously mounted volumes.
Explanation: The creation time of this volume does not match the other
volumes or stripes.
|
6.56.2
|
2
|
The volume mounted on device `%1!' could not be positioned to append another dump file. This dump device may only support one dump file per volume set.
Explanation: The mounted volume is either full, or can only hold one dump
file.
|
6.57.1
|
1
|
Device `%1!' supports one dump file per volume set.
Explanation: Information, no user action necessary.
|
6.58.1
|
1
|
Device `%1!' supports multiple dump files per volume set.
Explanation: Information, no user action necessary.
|
6.61.2
|
2
|
Volume validation error: Volume change request not allowed on non-mountable devices, device name: %1!.
Explanation: Requests mounting of next volume in sequence to locate requested
dump file.
|
6.65.2
|
2
|
Volume validation error: illegal volume change, device %1!: volume for stripe %2! mounted while stripe %3! loading still in progress.
Explanation: Reminds user that all volumes of a dump-time stripe must complete
loading on the device before the first volume of another dump-time
stripe may begin loading.
|
6.66.2
|
2
|
Volume validation error: illegal volume change, device %1!: volume mounted out of order, expected volume %2!, got volume %3!
Explanation: Volumes must be loaded in the same order in which they were
dumped.
|
6.78.1
|
1
|
EXECUTE sp_volchanged\n\t@session_id = %1!,\n\t@devname = `%2!%3!',\n\t@action = { `%4!' | `%5!' | `%6!' }%7!%8!
Explanation: Template for sp_volchanged execution.
proceed means continue operation with the currently mounted volume.
retry means redo the validation check that led to the prompt (presumably
on a new volume). abort means abort the entire dump or load session.
|
6.80.2
|
2
|
Session %1! is exiting by request from sp_volchanged.\nData written in this session are incomplete and invalid.\nAborting session.
Explanation: The user requested an abort through sp_volchanged.
|
6.81.2
|
2
|
Unrecognized volume change prompt id (internal error); task must exit.
Explanation: Indicates a Backup Server programming error. Retry the dump
or load command, avoiding unnecessary volume manipulations.
|
6.82.2
|
2
|
%1! is not a recognized sp_volchanged action.
Explanation: User provided an illegal @action value to sp_volchanged.
The value must be proceed, retry, or abort.
|
6.83.2
|
2
|
Volume validation error: Volume name mismatch, volume name %1!, expected volume name %2!.
Explanation: Volumes within a stripe must have the same name in the ANSI
VOL1 label. It is possible for a user to execute the dump command
properly and still receive this error at load time, if the first
volume was overwritten using the dumpvolume option
and the second volume, with a different name, was appended to.
|
6.84.2
|
2
|
Volume validation error: illegal volume change, device %1!: stripe %2! is already loaded.
Explanation: User remounted a tape for a stripe that has already been loaded.
|
6.85.0
|
0
|
byte stream
Explanation: Internal informational message, usually a component of another
message. No user action necessary.
|
6.86.2
|
2
|
Unexpected error reading from volume change response message queue for device '%1!'.
Explanation: Failed to read from volume change message queue.
|
6.87.1
|
1
|
%1!: Volume on device `%2!' contains user data. Erase it or mount another volume.
Explanation: The mounted volume is not ready for use. Erase it or exchange
it for another.
|
6.88.1
|
1
|
Volume on device `%1!' has unrecognized format or not formatted.
Explanation: The mounted volume is not ready for use. Format it or exchange
it for another.
|
6.89.2
|
2
|
The SYTAPE environment variable must be set.
Explanation: The SYTAPE environment variable must be set before continuing.
|
