Number
|
Severity
|
Text and Explanation
|
902
|
24
|
Hardware error detected reading logical page %ld, virtual page %ld in database `%.*s'.
Explanation: Hardware error detected. Report the error to your System
Administrator. The database may have to be reloaded. It may be necessary
to contact your hardware vendor.
|
903
|
23
|
Unable to find row in sysindexes for clustered index on system catalog %d in database %d. This index should exist in all databases. Run DBCC CHECKTABLE on sysindexes in the database.
Explanation: Refer to the writeup for this error.
|
904
|
22
|
Unable to find master database row in sysdatabases. Cannot open master database.
Explanation: A table or index may be corrupt. Report the error to your
System Administrator. Adaptive Server must be restarted and dbcc
diagnostics run.
|
905
|
17
|
Unable to allocate a DBTABLE descriptor to open database ’%S_DBID’. Close or drop another database before opening this one, or ask your System Administrator to raise the configuration parameter ’number of open databases’.
Explanation: Refer to the writeup for this error.
|
906
|
23
|
Could not locate row in sysobjects for system catalog %d in database %d. This system catalog should exist in all databases. Run DBCC CHECKTABLE on sysindexes in the database.
Explanation: Refer to the writeup for this error.
|
908
|
22
|
Unable to find any entries in sysusages for dbid `%d', database `%S_DBID'. Run DBCC CHECKTABLE on sysusages in the master database.
Explanation: A table or index may be corrupt. Report the error to your
System Administrator. Adaptive Server must be restarted and dbcc
diagnostics run.
|
909
|
21
|
More than %d entries required to build the logical-virtual translation table for database `%S_DBID'. The database is too fragmented.
Explanation: Adaptive Server encountered an internal error affecting all
processes in the current database. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics
run.
|
910
|
17
|
Could not allocate a new object descriptor for required system catalog in database `%d'. Another database must be closed or objects in another database dropped in order to open this database.
Explanation: Command failed due to resource limitation. Modify the command
to fit available resources, retry when the resource is available,
or contact your System Administrator to address the resource problem.
|
911
|
16
|
Attempt to locate entry in sysdatabases for database `%.*s' by name failed - no entry found under that name. Make sure that name is entered properly.
Explanation: Refer to the writeup for this error.
|
912
|
21
|
DBTABLE descriptor cannot be found for database `%.*s' which is supposed to be already open.
Explanation: Adaptive Server encountered an internal error affecting all
processes in the current database. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics
run.
|
913
|
22
|
Could not find row in sysdatabases with database id %d. Run DBCC CHECKTABLE on sysdatabases.
Explanation: Refer to the writeup for this error.
|
915
|
21
|
Descriptor for system catalog `%.*s' not found in DBTABLE chain for database `%.*s' - all system catalogs should reside permanently in this chain.
Explanation: Adaptive Server encountered an internal error affecting all
processes in the current database. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics
run.
|
916
|
14
|
Server user id %d is not a valid user in database `%.*s'
Explanation: Refer to the writeup for this error.
|
917
|
20
|
Illegal attempt to close the master database for the last time - this database must always be open.
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.
|
918
|
14
|
Database `%.*s' has not yet been recovered - please wait before accessing this database.
Explanation: Command failed. The database is not available at this time.
Wait and try again.
|
919
|
21
|
Database `%.*s' was marked `suspect' by an earlier attempt at recovery. Check the SQL Server errorlog for information as to the cause.
Explanation: Adaptive Server encountered an internal error affecting all
processes in the current database. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics
run.
|
920
|
22
|
Could not find syslogs row in sysindexes for database `%.*s'. Run DBCC CHECKTABLE on this system catalog.
Explanation: There may be a corrupt table or index. Adaptive Server must
be restarted and dbcc diagnostics run.
|
921
|
14
|
Database `%.*s' has not been recovered yet - please wait and try again.
Explanation: Refer to the writeup for this error.
|
922
|
14
|
Database `%.*s' is being recovered - will wait until recovery is finished.
Explanation: Command failed. The database is not available at this time.
Wait and try again.
|
923
|
14
|
User %d not allowed in database `%.*s' - only the owner of this database can access it.
Explanation: You do not have the permission to execute this command. Have
the object owner or a user with the needed role run this command.
|
924
|
14
|
Database `%.*s' is already open and can only have one user at a time.
Explanation: Refer to the writeup for this error.
|
925
|
19
|
Maximum number of used databases for each query has been exceeded. The maximum allowed is %d.
Explanation: Refer to the writeup for this error.
|
926
|
14
|
Database `%.*s' cannot be opened. An earlier attempt at recovery marked it `suspect'. Check the SQL Server errorlog for information as to the cause.
Explanation: Refer to the writeup for this error.
|
927
|
14
|
Database <%d> cannot be opened - it is in the middle of a load.
Explanation: Command failed. The database is not available at this time.
Wait and try again.
|
928
|
14
|
Database `%.*s' cannot be opened - it is currently being created. Wait and try query again.
Explanation: Command failed. The database is not available at this time.
Wait and try again.
|
929
|
21
|
Attempting to close a database which is not open. Please contact Technical support.
Explanation: Adaptive Server encountered an internal error affecting all
processes in the current database. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics
run.
|
930
|
14
|
Database `%.*s' cannot be opened because either an earlier system termination left LOAD DATABASE incomplete or the database is created with `for load' option. Load the database or contact a user with System Administrator (SA) role.
Explanation: Refer to the writeup for this error.
|
931
|
21
|
Database `%.*s' cannot be opened because of a failure to initialize the global timestamp. This indicates that a problem exists in the log for the current database. Please contact Technical support for assistance.
Explanation: Adaptive Server encountered an internal error affecting all
processes in the current database. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics
run.
|
932
|
22
|
Database `%.*s' cannot be opened because the log for the current database is corrupt. Page %ld of the log is linked to a page that belongs to a database object with id %ld. Please contact Technical support for assistance.
Explanation: A table or index may be corrupt. Report the error to your
System Administrator. Adaptive Server must be restarted and dbcc
diagnostics run.
|
933
|
22
|
Logical page %ld of the log encountered while retrieving highest timestamp in database `%.*s' is not the last page of the log and we are not currently recovering that database.
Explanation: Refer to the writeup for this error.
|
934
|
21
|
Fatal error encountered while freeing up DBTABLE structure.
Explanation: Adaptive Server encountered an internal error affecting all
processes in the current database. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics
run. (Not raised in Release 11.0 and higher.)
|
935
|
10
|
WARNING - the timestamp in database `%.*s' is approaching the maximum allowed.
Explanation: This is an informational message. Unless otherwise specified,
no action is required. Contact your System Administrator about any
warning issued in the message.
|
936
|
14
|
The Model database is unavailable. It is being used to create a new database.
Explanation: Command failed. The database is not available at this time.
Wait and try again.
|
937
|
14
|
Database `%.*s' is unavailable. It is undergoing LOAD DATABASE.
Explanation: Command failed. The database is not available at this time.
Wait and try again.
|
938
|
14
|
Database `%.*s' is unavailable. It is undergoing LOAD TRANSACTION.
Explanation: Command failed. The database is not available at this time.
Wait and try again.
|
939
|
20
|
Illegal dbtable unlock: %S_DBT.
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.
|
940
|
26
|
Dbtable in wrong state for operation: %S_DBT.
Explanation: An internal locking/synchronization rule was broken.
Report the error to your System Administrator. Shut down and restart
Adaptive Server.
|
941
|
20
|
Illegal database context operation.
Explanation: See the writeup for Error 941.
|
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.
|
952
|
20
|
Database '%.*s' cannot be opened because a system index descriptor cannot be installed.
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.
|
953
|
11
|
Page '%ld', passed to curunreservedpgs built-in function, is an invalid page number in database ID '%d'. The highest page number in this database is '% ld'.
Explanation: Command failed. Check your command and re-enter with the
correct parameters.
|
954
|
10
|
Warning: The database ’%.*s’ is using an unsafe virtual device ’%.*s’. The recovery of this database can not be guaranteed.
Explanation: This is an informational message. Unless otherwise specified,
no action is required. Contact your System Administrator about any
warning issued in the message.
|
955
|
16
|
This command attempts to modify data in database ’%.*s’, dbid ’%d’. Modifications are not allowed in this database.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
|
956
|
16
|
The database ’%.*s’ does not have separate log segment. Log pre-allocation is not feasible for this database.
Explanation: Adaptive Server could not perform the requested action. Contact
your System Administrator.
|
957
|
16
|
Server wide log pre-allocation is disabled. Log pre-allocation is not possible at this time.
Explanation: Adaptive Server could not perform the requested action. Contact
your System Administrator.
|
958
|
16
|
Enabling or disabling log prealloation is not allowed for system databases.
Explanation: Adaptive Server could not perform the requested action. Contact
your System Administrator.
|
959
|
16
|
Database ’%.*s’ cannot be opened because an earlier system termination left DROP DATABASE incomplete. Drop the database or run ’DBCC CHECKALLOC’ to correct allocation information.
Explanation: Adaptive Server could not perform the requested action. Contact
your System Administrator.
|
960
|
16
|
Operation ’%S_MSG’ is not currently supported for database ’%.*s’.
Explanation: Adaptive Server could not perform the requested action. Check
your query; contact your System Administrator.
|