May 26, 2005 at 9:56 am
I am posting this here and in the replication area.
My log shipping database on the failover server shows: (Loading\Read-Only\Suspect). The database in question is approximately 54 GB. This problem was cause by two power outages within the last three days. Every server in the datacenter died very hard when the battery backup died.
I received the followings emails from SQL Server Agent Alerts:
1 - DATE/TIME:
DESCRIPTION: Error: 1102, Severity: 22, State: 1
IAM page (4:62991) for object ID 2073058421 is incorrect. The table ID on page is 413960551; should be 2073058421. The entry in sysindexes may be incorrect or the IAM page may contain an error.
COMMENT: (None)
I don't have a clue what an IAM file is.
2 - DATE/TIME:
DESCRIPTION: Error: 3314, Severity: 21, State: 3
Error while undoing logged operation in database 'AxS'. Error at log record ID (14694:100314:7).
COMMENT: (None)
I looked at the SQL log and is does show the dB as being in 'IN LOAD' mode. The dB has fourteen data files with the first having an extension of mdf and the remaining as extension of ndf. The transaction log is available. All the datafiles and logfiles are where they are supposed to be. Needless to say, you cannot backup a database that is in warm-standby mode or I would not have this problem.
I am running Windows 2000 Server EE SP4 and SQL Server EE SP3a.
I haven't a clue where to starting looking for a solution to the problem. The only choice I have come up with so far is to delete that part of the logshipping and rebuild the database from scratch - (not that hard to do, just a pain).
Any suggestions are appreciated.
May 26, 2005 at 12:49 pm
****IAM page (4:62991) for object ID 2073058421 is incorrect. The table ID on page is 413960551; should be 2073058421. The entry in sysindexes may be incorrect or the IAM page may contain an error.
The above error suggests that the sysindexes is corrupt - normally if any of the system tables is corrupt, it is hard to recover the database. And the one below suggests that the transaction log file for the database is also corrupt.
****DESCRIPTION: Error: 3314, Severity: 21, State: 3
Error while undoing logged operation in database 'AxS'. Error at log record ID (14694:100314:7).
Your best bet would be to restore the database from last known good backup.
May 26, 2005 at 12:56 pm
Sorry, I forgot - U will have to setup log shipping again, after deleting the current log-shipped copy of the database.
May 26, 2005 at 1:44 pm
Thanks very much.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply