|
|
3202 Severity Level 16 - Release 10.0 and Later Received MULTARG is not for device name as expected. Releases 4.9.x and Earlier Write on dump device '%.*s' failed, vsn=%ld return=%d status=%ld. Please consult the SQL SYBASE SQL Server
Release 10.0 and Later The meaning of Error 3202 for SQL Server 10.0 and later is different from the meaning when it is raised on SQL Server 4.9.x and earlier. A MULTARG is a structure SQL Server stores in memory to keep information about the device being dumped to. If the dump routine was passed a MULTARG which is not for a dump device and you are running the Diagnostics Server (not likely), Error 3202 will be raised. If you receive Error 3202 when using SQL Server 10.0 or later, call Sybase Technical Support. Releases 4.9.x and Earlier For SQL Server 4.9.x and earlier versions, Error 3202 means that an error occurred when “writing” out a packet of data to the backup. Common causes are: • Running out of space for your dump (to disk) • A bad tape • A bad tape size • A bad block size • Hardware failure This error is fatal and stops the dump from completing. This invalidates the backup and makes it unusable for recovery purposes. 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. This status is Sybase-specific and has no operating system correlation.
The following actions apply only to SQL Server 4 ... Login to see more
Comments | | | 3104 Severity Level 16 - LOAD DATABASE encountered page with invalid logical page number %ld. SYBASE SQL Server
This error occurs when SQL Server detects an invalid page number within a database dump. The invalid page number is greater than the highest page number for the database to be loaded into. This is a serious error and it indicates a corrupted database dump. Attempts to access this database after it encounters Error 3104 may result in Error 930. Some potential causes of the error are: • Overlapping partitions. • Using UNIX operating system files for Sybase database devices (that is, if the file system fills up). This error only occurs in SQL Server releases earlier than 10.0.
1. Examine your operating system error log file a ... Login to see more
Comments | | | 2509 Severity Level 16 - Table Corrupt: The row number and offset of each row in the page should have a matching entry in row number table; check this page (page#=%ld row#=%d offset in row number table=%d) SYBASE SQL Server
The offsets for data or index rows are stored at the end of every page (in the row number table) and indicate where a certain row is located on that page. Error 2509 occurs when the dbcc checkdb or dbcc checktable command detects that a row does not have an entry matching its offset (location) on the page in the row offset table. Attempts to delete the offending row will result in Error 631, while attempts to select the offending row may be successful. This problem is probably a result of a problem within SQL Server but may also be caused by one of the following: • Hardware failure • Sybase System Administration problems • UNIX System Administration problems
First, make sure that you ruled out any of the ab ... Login to see more
Comments | | | 806 Severity Level 21 - Could not find virtual page for logical page %ld in database '%S_DBID'. SYBASE SQL Server
This error occurs when SQL Server fails to convert a logical page number to a virtual page number. Depending on what caused the error, it can be serious or transient. A virtual page is the page within a Sybase device whereas a logical page is the page in a SQL Server database. There is a one-to-one correspondence between the two types of pages. If Error 806 appears with a stack trace and exec_dbcc appears in the stack trace, it means you used dbcc page with an invalid parameter. This is not a serious problem. If Error 806 occurs on recovery, it may be transient or serious (see information under “Explanation” for specifics). Error 806 can occur during normal processing, such as creating an index or running a stored procedure. In this case, the error is probably caused by corruption or a problem with SQL Server and it is a serious error.
If Error 806 specifies tempdb in the message outp ... Login to see more
Comments | | | 614 Severity Level 21 - A row on page %ld was accessed that has an illegal length of %d in database '%.*s'. SYBASE SQL Server
This error occurs when SQL Server accesses a data or index row whose length is smaller than the minimum row size or greater than the maximum row size. The minimum length of a row for each object is stored in the minlen column of sysindexes and in each data or index page header. The maximum size allowed for a data row or index row is 1962 bytes. (On Stratus platforms, the row size can be up to 4010 bytes because Stratus platforms have a larger page size than other platforms.) This error can occur under the following conditions: • During normal processing, when SQL Server tries to access the row specified by the error message. • During database recovery (database recovery occurs during SQL Server start-up or when a load database or load transaction command is processed). Error 614 can be caused by data corruption during normal processing (for example, an operating system panic occurs, causing interruption in disk writes when using UNIX files for SYBASE database devices). This may be due to a problem with SQL Server, the operating system, or hardware.
Error 614 is usually the result of a more serious ... Login to see more
Comments | | | 629 Severity Level 21 - Fatal attempt to delete clustered index entry for page %ld - index row contains page %ld. SYBASE SQL Server
This error occurs when SQL Server fails to delete a clustered index entry because the index entry did not point to the expected page. In the error message text, the first page number refers to the data page and the second page number refers to the node-level index page that points to the data page. Error 629 can occur when you attempt to delete a row (for example, when a table that has a clustered index is dropped, the row in sysindexes is deleted). The error is caused by data corruption that occurred during SQL Server processing (for example, an operating system panic occurs, causing interruption in disk writes when using UNIX files for SYBASE database devices). This may be due to a problem with SQL Server, the operating system, or hardware.
1. Use the procedure in “How to Find an Object Na ... Login to see more
Comments | | | 631 Severity Level 21 - The length of %d passed to delete row routine for the row at offset %d is incorrect on the following page: %S_PAGE. SYBASE SQL Server
This error occurs when SQL Server attempts to delete a row (via a direct delete or inherently through updating) from an index or data page by specifying the row offset and the row length, and the action fails because the specified values of the offset or row length did not match the actual values. Error 631 can happen under the following conditions: • During normal processing, when SQL Server tries to delete the row specified by the error message. • During database recovery (database recovery occurs during SQL Server start-up or when a load database or load transaction command is processed). Some potential causes of Error 631 are: • Data corruption during normal processing (for example, an operating system panic occurs, causing interruption in disk writes when using UNIX files for SYBASE database devices). This may be due to a problem with SQL Server, the operating system, or hardware. • Hardware failure during loading or dumping
Error 631 is probably the result of a more seriou ... 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 | | | 3307 Severity Level 21 - Process %d was expected to hold logical lock on page %ld. SYBASE SQL Server
This error occurs when SQL Server, while committing or aborting a transaction, attempts to release a lock on the page displayed by the error message and the page is not locked. This error may occur during recovery as well as during run time. Common causes of this error are: • Software failures. • When SQL Server was performing a rollback, it expected a logical lock on the page displayed in the error message but the lock could not be found. • When SQL Server attempted to deallocate a page, it expected a logical lock on that page but one did not exist. • SQL Server tries to undo a page deallocation. • SQL Server tries to roll back a user transaction which has executed a stored procedure that required reresolution. Reresolution is required for stored procedures that reference objects which have been dropped and re-created between executions. Refer to “Procedure Re-resolution” in the SQL Server Troubleshooting Guide for more information about reresolution.
Look for other errors in the Sybase error log as ... Login to see more
Comments | | | 3425 Severity Level 21 - Transaction (%ld, %d) not found in transaction table. SYBASE SQL Server
This error occurs when, during SQL Server recovery, load transaction, or load database, an end (commit or rollback) transaction log record was found that does not have a corresponding begin transaction record. Therefore, the transaction could not be rolled back or committed and recovery or load could not complete for that database. You cannot use the affected database until whatever caused the error has been corrected because SQL Server marks the database suspect.
If the error occurred during recovery, determine ... Login to see more
Comments | | |
| |
|
|