Transaction log got full while a cluster index online rebuild (sort in tempdb) was in progress, this crashed the database and put in Recovery mode for long hours. I have extracted the events from error log in sequence:
- Error: 9002, Severity: 17, State: 2.
- The transaction log for database 'xyz' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
- Error: 3314, Severity: 21, State: 4.
- During undoing of a logged operation in database 'xyz', an error occurred at log record ID (53722:210539:203). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
- Error: 3041, Severity: 16, State: 1.
- BACKUP failed to complete the command BACKUP LOG xyz. Check the backup application log for detailed messages.
- Database xyz was shutdown due to error 9002 in routine 'XdesRMReadWrite::RollbackToLsn'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
- Error: 9001, Severity: 21, State: 1.
- The log for database 'xyz' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
- Error: 3314, Severity: 21, State: 5.
- During undoing of a logged operation in database 'xyz', an error occurred at log record ID (53722:201192:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
- Database mirroring is inactive for database 'xyz'. This is an informational message only. No user action is required.
I am running SQL Server 2008 R2 Enterprise Edition with SP1.
Appreciate any details available on this issue.
Thanks & Regards,
Romanth.