Number
|
Severity
|
Text and Explanation
|
|---|
1.1.2
|
2
|
Memory allocation failed in %1! for a %2! allocation. This DUMP or LOAD session must exit.
Explanation: Indicates shortage of virtual memory on the machine running
Backup Server. User should terminate unnecessary processes.
|
1.2.0
|
0
|
WAIT
Explanation: This informational text may be a component of another message.
No action is necessary.
|
1.3.0
|
0
|
NOWAIT
Explanation: This informational text may be a component of another message.
No action is necessary.
|
1.4.0
|
0
|
PROCEED
Explanation: This informational text may be a component of another message.
No action is necessary.
|
1.5.4
|
4
|
Failed to install CS-Library message callback routine.
Explanation: Backup Server's attempt to install an event handler failed.
Backup Server cannot run.
|
1.6.0
|
0
|
RETRY
Explanation: This informational text may be a component of another message.
No action is necessary.
|
1.7.1
|
1
|
Cannot allocate the locale info of the task. Use the Backup Server default language `%1!' instead.
Explanation: The local structure for the client connection to Backup Server
could not be allocated, and the thread property for the local information
could not be captured. Refer to the Backup Server error log for
more information.
|
1.8.0
|
0
|
ABORT
Explanation: This informational text may be a component of another message.
No action is necessary.
|
1.9.0
|
0
|
Backup Server
Explanation: This informational text may be a component of another message.
No action is necessary.
|
1.10.0
|
0
|
DUMP
Explanation: This informational text may be a component of another message.
No action is necessary.
|
1.11.0
|
0
|
LOAD
Explanation: This informational text may be a component of another message.
No action is necessary.
|
1.12.0
|
0
|
volume
Explanation: This informational text may be a component of another message.
No action is necessary.
|
1.13.0
|
0
|
OPERATOR
Explanation: This informational text may be a component of another message.
No action is necessary.
|
1.14.2
|
2
|
Unrecoverable I/O or volume error. This DUMP or LOAD session must exit.
Explanation: This message is usually preceded by a more specific message
describing a fault encountered in the lower I/O layers.
One exception: this message is the only error indication when the
Backup Server fails to start the multi-buffering subprocess that
it uses to perform backup I/O.Reasons for this failure
are the non-existence of the sybmultbuf program
in the standard locations (-M option argument, Backup Server's
current directory or $SYBASE/bin). User should
check the installation. If the sybmultbuf program
can be installed in the current directory or $SYBASE/bin,
it is not necessary to restart the Backup Server.
|
1.15.4
|
4
|
UNRECOVERABLE CONDITION: ALL SESSIONS WILL TERMINATE ABNORMALLY. THE BACKUP SERVER MUST EXIT.
Explanation: This message is preceded by other messages describing the
failure.
|
1.16.2
|
2
|
Error (major = %1!, minor = %2!) raised with unknown severity %3!.n
Explanation: Indicates a programming bug in an instance of error reporting.
|
1.17.2
|
2
|
Major = %1!, Minor = %2!, Severity = %3!, state = %4!: error text is missing.
Explanation: Indicates that localization files are out-of-date with the
code. Check installation with Sybase Technical Support.
|
1.18.1
|
1
|
WARNING: Requested %1! file descriptors, was allocated %2!; Backup Server will run out of file descriptors if this number is less than the number of database devices plus twice the number of stripes in concurrent use.
Explanation: The Backup Server attempts to obtain the highest number of
file descriptors allowed to a user program. This message indicates
that the Backup Server found a lower quota. Concurrent activity
must be restricted as directed or the platform administrator can
increase the HDESLIM.
|
1.19.4
|
4
|
Cannot allocate the configuration structure
Explanation: Indicates either a basic Open Server failure or an extreme
shortage of memory and swap space.
|
1.20.4
|
4
|
CS_CONTEXT allocation failed.
Explanation: The context allocation routine failed when it tried to load
localization files. The SYBASE environment variable is set incorrectly
or the localization files are missing.
|
1.21.2
|
2
|
Unable to configure the maximum number of user events to %1!.
Explanation: An error occurred when you tried to configure the Open Server's
run-time maximum number of application-specific defined event types.
Refer to the Open Server Server-Library Reference Manual for
an explanation of events. Refer to the Backup Server error log
for more information, and contact Sybase Technical Support.
|
1.22.2
|
2
|
Unable to configure the maximum number of SRV_PROCS to %1!.
Explanation: An attempt to configure the Open Server run-time values to
allow the specified number of Server threads failed. Backup Server
uses one thread per dump or load connection plus an additional thread
for each stripe. Use the -P option to increase the number of threads.
|
1.23.2
|
2
|
Unable to configure the maximum number of network read buffers to %1!.
Explanation: An attempt to configure the Open Server run-time values to
allow the specified number of network read buffers failed. These
buffers are used for Server to Server connections, and the configuration
value is hard coded to 10.
|
1.24.2
|
2
|
Unable to configure the maximum number of connections to %1!.
Explanation: Attempt to configure the Open Server run-time values to allow
the specified number of network connections failed. The value of
the -C option (/connections in Digital OpenVMS) to the backupserver command
is used for the configurable value. Check the line in your RUN_servername file
and see the entry for backupserver in Adaptive
Server Utility Programs for your platform.
|
1.25.1
|
1
|
Logging Backup Server messages in file `%1!'\n
Explanation: Indicates that Backup Server messages are being written to
the file named.
|
1.26.1
|
1
|
Unable to open Backup Server message log file `%1!'\n
Explanation: Check the path to the message log file. Make sure that the
SYBASE environment variable is set correctly.
|
1.27.1
|
1
|
Operating system swap space is low. The operating system may kill the Backup Server.
Explanation: This is an RS6000 error only. The operating system will kill “random” processes
in an effort to free space for critical processes. This message indicates
that the Backup Server could be chosen. If necessary, reconfigure
the Backup Server process as critical.
|
1.28.2
|
2
|
Open Server routine %1! failed. See Backup Server error log for additional information. \n
Explanation: Internal error, contact Sybase Technical Support. This is
a catch-all message for any Open Server function that raises an
error for which Backup Server has determined the affected routine
but not the exact error.
|
1.29.2
|
2
|
Unable to start the Backup Server. See Backup Server error log for additional information. \n
Explanation: At Backup Server initialization time, the attempt to put Backup
Server into a state in which it can run failed. Refer to any Open
Server messages that are displayed.
|
1.30.2
|
2
|
Backup Server encountered error freeing memory.\n
Explanation: Internal error, contact Sybase Technical Support. An error
occurred when an attempt was made to free a block of memory from
Backup Server's run-time heap. Either the memory was previously
freed or there is another error in the Open Server routines for
freeing memory. Check the Backup Server error log for any Open
Server messages pertinent to this problem.
|
1.31.2
|
2
|
Unable to configure the maximum number of network connections to %1!. The number of network dump/load stripes that the Backup Server can run simultaneously is %2!.
Explanation: Attempt to set the maximum number of network connections (DBPROCESSes)
that the Server can originate failed. Refer to the usage of the
-N command line option. It may be too large for DB-Library to handle.
|
1.32.2
|
2
|
Unexpected failure in `cs_strcmp()' routine.
Explanation: Internal error, contact Sybase Technical Support. An error
occurred when comparing two strings to see if they are equal, greater
than, or less than each other. The cause of the error could be
an illegal string in length or content or that the character sets
of the two strings are incompatible for comparison.
|
1.33.0
|
0
|
Backup Server Internal Error
Explanation: This informational text may be a component of another message.
|
1.34.1
|
1
|
Unable to set one or more trace flags; continuing.
Explanation: Attempt to set the Open Server run-time trace flags failed.
Check to see that the trace flags are valid and in the proper format.
|
1.35.0
|
0
|
<new_volume_name>
Explanation: This informational text may be a component of another message.
No action is necessary.
|
1.36.1
|
1
|
Unable to configure Async IO. If Adaptive Server is using Async IO on block special devices, then dump and loads may be inconsistent. Refer to the server release notes.
Explanation: HP only: could not initialize and configure the asynchronous
I/O system to be used when accessing database devices.
Check the Backup Server error log and contact Sybase Technical
Support.
|
1.37.4
|
4
|
Could not allocate event flag, server %1!: code %2! message %3!.
Explanation: This is an Digital OpenVMS error only. An attempt to allocate
an event flag failed. Backup Server cannot start. Probably an internal
error.
|
1.38.4
|
4
|
Could not get master lock on server name, server %1!: code %2! message %3!.
Explanation: Digital OpenVMS only: an attempt to obtain a lock identifying
this as the “master” Backup Server failed for
the reason specified in %3!. Backup Server cannot start.
|
1.39.4
|
4
|
This backup server is unnamed, and so cannot acquire the master lock it needs to boot successfully. Backup Server must shut down.
Explanation: Digital OpenVMS only: no Server name was given when attempting
to acquire an exclusive lock on the master lock name, which is constructed
from the Server name. Use showserver to check
whether Backup Server was started with a Server name by means of
the /SERVER_NAME qualifier or the translation
of the DSLISTEN logical name.
|
1.41.4
|
4
|
A server named %1! is already running. Could not obtain stop-lock.
Explanation: Digital OpenVMS only: another Backup Server with the same
logical name is already running. This Backup Server cannot start.
|
1.42.4
|
4
|
STOP semaphore failed, code %1! message %2!.
Explanation: Digital OpenVMS only: failed to queue the lock required to
shut down Backup Server via stopserver. Backup
Server cannot start.
|
1.43.4
|
4
|
Failed getting system information: sys$getsyi failed, code %1! message %2!.
Explanation: An unexpected condition, fatal to the execution of the Backup
Server, has occurred. The session must exit immediately.
|
1.44.1
|
1
|
Backup Server could not set the server language to `%1!'. The specified language may not be a valid language, or the language may not be installed under $SYBASE/locales. The default language is in use.
Explanation: Attempt to set the Backup Server's language failed. Refer
to the Backup Server error log for more information. The specified
language may not be a valid language, or the language may not be
installed under $SYBASE/locales.
|
1.45.1
|
1
|
Backup Server could not set the server character set to `%1!'. The specified character set may not be a valid character set, or the character set may not be installed under $SYBASE/locales. The default character set is in use.
Explanation: Attempt to set the Backup Server's character set failed.
Refer to the Backup Server error log for more information. The
specified character set may not be a valid character set or the
character set may not be installed under $SYBASE.
|
1.46.1
|
1
|
CSLIB routine %1! failed. See Backup Server error log for additional information.
Explanation: This is the catch-all message for CS-Library (Client/Server
Library) functions that return an error. Currently, the only reference
to this error occurs when Backup Server is attempting to configure
the localization properties of the process. Refer to the Backup
Server error log for more information. There could be something
wrong with the specified language or character set, for example
the specified character set is not valid for the specified language.
Contact Sybase Technical Support if a resolution cannot be determined.
|
1.47.1
|
1
|
Backup Server could not set the server language/character set to `%1!/%2!'. The specified language/character set combination may not be valid, or the language/character set combination may not be installed under $SYBASE/locales. The default language/character set is in use.
Explanation: Attempt to set the Backup Server's language and character
set failed. Refer to the Backup Server error log for more information.
The specified language or character set may not be valid or the
language or character set may not be installed under $SYBASE/locales.
|
1.48.2
|
2
|
Attempt to dispatch Backup Server by Service Control Manager returned operating system error = %1!(%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 must exit. This is an NT specific
message.
|
1.49.2
|
2
|
Attempt to register Service Control Handler returned operating system error = %1!(%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 must exit. This is an NT specific
message.
|
1.50.2
|
2
|
Attempt to set Control Status returned operating system error = %1!(%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 must exit. This is an NT specific
message.
|
1.51.2
|
2
|
Service Control Handler received an invalid control code = %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. The session must exit. This is an NT specific
message.
|
1.52.1
|
1
|
Backup Server terminating because of system shutdown
Explanation: Information, no user action necessary.
|
1.53.2
|
2
|
Attempt to create thread returned operating system error = %1!(%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 must exit. This is an NT specific
message.
|
1.54.2
|
2
|
Attempt to connect to registry returned operating system error = %1!(%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 must exit. This is an NT specific
message.
|
1.55.2
|
2
|
Attempt to open registry key returned operating system error = %1!(%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 must exit. This is an NT specific
message.
|
1.56.2
|
2
|
The SYBASE environment variable must be set.
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 must exit. Follow any instructions
given.
|
1.57.2
|
2
|
Backup Server encountered an error while attempting to create a message queue. The Open Server routine srv_createmsgq failed. This session cannot continue.
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 must exit.
|
1.58.2
|
2
|
Error: Unable to disable the `%1!' system registered procedure.
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 must exit.
|
1.59.2
|
2
|
Error: Unable to spawn thread to drop the disallowed system registered procedures.
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 must exit.
|
1.60.2
|
2
|
Unable to configure %1! connections and %2! service threads which requires %3! message queues. The maximum number of message queues is %4!.
Explanation: The value of the -C and -P option are such that the number
of message queues exceed the allowed maximum. Restart the Backup
Server with reduced values for these parameters.
|
1.61.2
|
2
|
The SYTAPE environment variable must be set.
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 must exit. Follow any instructions
given.
|
1.62.2
|
2
|
Unable to load the Sytos DLL that SYTAPE is set to.
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 must exit.
|
1.63.2
|
2
|
Unable to configure %1! connections and %2! service threads which requires %3! messages. The maximum number of messages is %4!.
Explanation: The value of the -C and -P option are such that the number
of message queues exceed the allowed maximum. Restart the Backup
Server with reduced values for these parameters.
|
