21
Invalid log record found in syslogs (logop %d).
This error can be caused by a hardware problem.
The syslogs table
is the Adaptive Server transaction log that contains a record of
changes made in the database and in the order in which they occur.
Adaptive Server scans the records in the transaction log during database recovery and other
activities. Error 3301 occurs if Adaptive Server encounters an invalid
record while scanning the transaction log. logop refers
to the type of record (log operation) encountered. For example,
a logop of 18 is logged
by a save transaction command.
Error 3301 is raised with the following states:
State |
Meaning |
|---|---|
1 |
An unexpected log record was encountered during recovery. |
9 |
An unexpected log record was encountered while translating log records associated with an obsolete log format (for a previous Adaptive Server version) to the format for the current Server version. |
10 |
An out-of-range |
11 |
An invalid log record was found in the the analysis, undo, or redo log operations handling. |
12 |
An invalid log record was found while running the analysis pass of recovery. |
13 |
An update log record marked part of a twin did not have either an undo-only or redo-only status set. |
14 |
An out-of-range |
This is a serious error that indicates a problem with the transaction log. Corrective action depends on the source of the error.
A 3301 error during recovery (boot time, load database, or load transaction recovery) marks the database suspect. The database is identified in the error log. Restore the database from a good backup as follows:
Drop the database. If the drop fails, follow the instructions in “Dropping a database when drop database fails” in Chapter 4 of the most recent version of the Troubleshooting and Disaster Recovery guide.
Create a database for loading. Verify that the database you create is at least as large as the original database, and that its sysusages values match the original values. For more information, refer to “create database” in the Reference Manual: Commands.
Load the database from backup. (Refer to “load database” in the Reference Manual: Commands.)
Use the online database command to make the database available for use.
A 3301 error during rollback of a transaction will generally result in a “phantom” process that continues to hold locks that in time may block other transactions that require the same locks. Contact Sybase Technical Support for assistance.
Refer to “Developing a Backup and Recovery Plan” in the System Administration Guide: Volume 2 for instructions about how to safely create, dump, load, and re-create databases.
All versions
