|
|
1204 Severity Level 19 - Release 10.0 and Later SQL Server has run out of LOCKS. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure SQL Server wit SYBASE SQL Server
This error occurs when SQL Server runs out of locks, as controlled by sp_configure. Following is an example of the output from sp_configure locks, and a brief description of the output related to locks: name minimum maximum config_value run_value ----- ------- ---------- ------------ --------- locks 5000 2147483647 0 5000 • The minimum and maximum column entries represent the minimum and maximum number of configurable locks for SQL Server. • The config_value column contains the value to which the locks configuration parameter has been set with sp_configure. The default value of config_value, which corresponds to the minimum value, is 0 (zero). • The run_value column contains the value SQL Server is using. The default run value in sysconfigures is 5000.
Rerun the command when there are fewer active use ... Login to see more
Comments | | | 3201 Severity Level 16 - Release 10.0 and Later No dump device has been specified. SQL Server Releases Up to 4.9.x Can’t open dump device '%.*s', device error or device off line. Please consult the SQL Server error log SYBASE SQL Server
This error occurs when SQL Server is unable to access a dump device during a database dump. This error is fatal and stops the dump from completing. Error 3201 is most likely caused by one of the following: • The device you specified for the dump is offline or otherwise unavailable to SQL Server. • Permissions for the dump device are not set correctly for user “sybase” or the user performing the dump (read and write privileges are required). • A previous dump aborted and SQL Server believes the dump device is still in use. • For SQL Server releases previous to 10.0, you are trying to run more than one dump database command at the same time. You can only do this (for tape devices) if the cntrltype values (defined using sp_addumpdevice) of the devices to which you are dumping are different. For example, only one disk byte stream interface can be active at a time. You cannot dump multiple databases or transaction logs to the same tape device or disk dump. As of SQL Server 10.0, dumps are performed by the Backup Server. During dump and load commands, the Backup Server automatically determines whether a tape or disk device is being used and what its controller type is. It ignores the cntrltype parameters specified with sp_addumpdevice.
1. Check to make sure the device you specified is ... Login to see more
Comments | | | 3203 Severity Level 16 - Release 10.0 and Later Backup Server has detected a SQL Server error. Release 4.9.x and Earlier Read on dump device '%.*s' failed, vsn=%ld return=%d status=%ld. Please consult the SQL Server er SYBASE SQL Server
For SQL Server release 10.0 and later, Error 3203 is displayed when a problem occurs with a remote procedure call to the Backup Server. In this case, the error is on the SQL Server side. For SQL Server releases previous to 10.0, this message is displayed when an error occurs when doing a load from a SQL Server dump. The error message output includes: • vsn – the virtual socket number. • return – the return value: 0 means successful; -2 means failure. • status – the ending status, displayed in decimal value. The most common value is 524288 which usually means an I/O error. Some causes are: • Write protect is turned on (it must be off when loading a tape because the device is opened read/write). • No dump exists on the media being accessed (for example, a blank tape or the wrong device specified). • The media that contains the dump is not readable.
Release 10.0 and Later • Check the SQL Server and ... Login to see more
Comments | | | File Already in Use Error - basis_dlock: file '%s' already in use by a SQL Server SYBASE SQL Server
During startup, SQL Server tries to lock the master device. If SQL Server finds that the master device is already locked, the message “basis_dlock: file '%s' already in use by a SQL Server” is written to the error log and SQL Server does not start. %s is the name of the master device file. The most common reasons for this error are: • You are trying to start a SQL Server with a master device that is already being used by another SQL Server. • The SQL Server you are trying to start is already running.
At the operating system level, check the processe ... Login to see more
Comments | | | Character Set Error - SQL Server doesn't support use of character_set_name character set. SYBASE SQL Server
This error occurs when the client software default character set has not been installed on the SQL Server to which the client is trying to connect. This happens most often when the client is running on a different operating system from SQL Server.
To allow the client and SQL Server to communicate ... Login to see more
Comments | | | 701 Severity Level 19 - Release 10.0.2 and Later There is not enough procedure cache to run this procedure, trigger, or SQL batch. Retry later, or ask your SA to reconfigure SQL Server with more procedure cache. Relea SYBASE SQL Server
This error occurs when there is not enough procedure cache available to execute a stored procedure, trigger, or batch of one or more SQL statements. This can happen when loading a query plan into procedure cache or when resolving or compiling a procedure, trigger or batch. See “Procedure Re-resolution” in the SQL Server Troubleshooting Guide for a description of resolution. The amount of available procedure cache is based on SQL Server use, so this error may occur intermittently as procedure cache is used and released. Also, one or more procedures can repeatedly fail with this error while others complete normally. This is because query plans vary greatly in size. Therefore, while there may not be sufficient space to load a large query plan, several smaller plans may fit.
Correct this error by increasing the size of proc ... Login to see more
Comments | | | 3002 Severity Level 23 - For SQL Server Releases Up to 4.9.x Attempt to dump database %.*s found logical page %ld when logical page %ld expected. SYBASE SQL Server
This error occurs when SQL Server finds an unexpected page number during a database dump. This error is fatal and stops the dump from completing. Error 3002 is most likely caused by corruption of a database as a result of either: • Hardware failure • Inadvertently trying to use a raw partition for two separate purposes
Run dbcc checkalloc to determine whether your dat ... Login to see more
Comments | | | 7227 Severity Level 17 - Release 10.0 and Later Can't open a connection to site '%S_SRVID' because SQL Server is not configured for remote access. Ask a user with System Administrator (SA) role to reconfigure SQL Server SYBASE SQL Server
This error occurs when you try to execute a remote procedure call (RPC) and the initiating or receiving SQL Server is not configured for remote access.
Configure the local or remote SQL Server for remo ... Login to see more
Comments | | | 7205 Severity Level 18 - Can’t open a connection to site '%S_SRVID'. See the error log file in the SQL Server boot directory. SYBASE SQL Server
This error occurs when SQL Server is unable to execute a remote procedure call (RPC) on a remote SQL Server, Backup Server, or Open Server application. In this writeup, “Server” is used to indicate a SQL Server, Backup Server, or Open Server application.
To determine why this error is occurring, perform ... Login to see more
Comments | | | 707 Severity Level 20 - System error detected during attempt to free memory at address 0x%lx. Please consult the SQL Server error log for more details. SYBASE SQL Server
The Memory Manager allocates, deallocates, and manages memory for SQL Server. It manages an array of structures in the process header, each of which represents a physical page of memory in procedure cache and the current byte allocation of that page. As part of its memory deallocation process, SQL Server tries to release the pages of memory allocated to a process header when they are no longer needed. When SQL Server is unable to release that section of memory, Error 707 occurs. Error 707 is caused by memory corruption or a SQL Server problem.
Since process headers are stored in procedure cac ... Login to see more
Comments | | |
| |
|
|