Filter
Top Products
CHAPTER 6 Adaptive Server Error Messages
811
942 20 Database cannot be opened because a system descriptor cannot be installed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
943 14 Database `%.*s' cannot be opened since an attempt to upgrade it was unsuccessful.
Explanation: Command failed. The database is not available, this may be due to an
upgrade failure. Contact your System Administrator.
944 20 Function %s requires that the user be in the database being worked on. Process %d
passed it a dbtable for database %d, but is using database %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
945 21 Unable to locate page %ld for database id %d in the in-memory copy of Sysusages
(spid=%ld). This is an internal error. Please contact Sybase Technical Support.
Explanation: Refer to the writeup for this error.
946 10 A %S_MSG has prevented Sysusages changes for database %.*s from being copied into
memory. Please run sp_dbremap to complete database space changes.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
947 14 Database `%.*s' has been marked as having corrupt security labels. Please contact a user
with the System Administrator, System Security Officer, or Oper role or the Database
Owner.
Explanation: Command failed. The database is not available at this time. Wait and try
again.
948 14 Database `%.*s' is unavailable. It is undergoing a security label consistency fix.
Explanation: Command failed. The database is not available at this time. Wait and try
again.
949 14 Database `%.*s' is unavailable. It is being bound to a named cache.
Explanation: When a database is bound to a named cache, all objects in that database
are bound to that cache unless they are explicitly bound to a different cache. Binding a
database to a named cache requires an exclusive lock on the database. Error 949 occurs
when you try to access an object in a database that is in the process of being bound to a
named cache. Try again later, once the bind has completed.
950 14 Database `%.*s' is currently offline. Please wait and try your command again later.
Explanation: See the writeup for Error 950.
951 14 Database identity for server user id %d changed after permission checking in database
`%.*s'. Please try again.
Explanation: Command failed. The database is not available at this time. Wait and try
again.
Number Severity Text and Explanation