Viewing 15 posts - 31 through 45 (of 46 total)
No luck.. here is the message
Msg 824, Level 24, State 2, Line 1
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x6f9014c7; actual: 0x6f903ecb). It occurred during a...
February 9, 2011 at 10:47 am
msdbSIMPLEONLINECHECKPOINTCHECKSUM
February 9, 2011 at 10:46 am
Yes, the MSDB is online and status is Normal. I am trying to find out if we have critical data stored there. Yes, I should import the data somewhere now.....
February 9, 2011 at 10:39 am
1. I can't backup the database (full) because of the transaction log is full.
2. Yes, shutting down SQL is an option.
3. Yes, I used DBCC SQLPERF(LogSpace)
4. I checked...
February 9, 2011 at 10:37 am
Here is the result of DBCC CheckDB
Could not write a checkpoint record in database ID 4 because the log is out of space. Contact the database administrator to truncate the...
February 9, 2011 at 10:31 am
Ok.. After reading http://www.sqlskills.com/BLOGS/PAUL/post/TechEd-Demo-Creating-detaching-re-attaching-and-fixing-a-suspect-database.aspx. I agree it is not good idea to recreate the log file since I alreay knew there are active transations rolloing forward in MSDB...
February 8, 2011 at 6:26 pm
Hi GilaMonster,
Do you have more information of how to recreate the transaction log? I am worried about the situation you talked about (Error: log cannot be rebuilt because the database...
February 8, 2011 at 5:51 pm
More information..
When I tried to reduce the max allowed size for MSDB, I got the following error
SQL Server detected a logical consistency-based I/O error: incorrect checksm....
and there is one...
February 8, 2011 at 5:09 pm
Good to know that. Thank you!
1. There are over 100G free space in the drive
2. I and the other person checked the log file and the max setting of the...
February 8, 2011 at 10:46 am
Here is something I don't understand,
In the MSDB Log was defined as restricted growth to 2097152 MB but the actual size of the log file is just 2304KB. Why it...
February 7, 2011 at 6:02 pm
Ok.. I don't know which one is worse? There is another option..
I can stop SQL server and rename the log file for MSDB and let it generate a new...
February 7, 2011 at 3:37 pm
I tried to two different ways to add log size in MSDB
1. Add another log file - failed due to transaction log file is full
2. Increase the size of the...
February 7, 2011 at 3:24 pm
The MSDB is in Simple Recovery mode. I can't add file to the log because the transaction log is full and I can't increase the file size as it dose...
February 7, 2011 at 3:03 pm
I can't add file or add more space to the exsiting logfile in MSDB
I am thinking replace the .mdf and .ldf with the corresponding files from a working MSDB. Thoughts?
February 7, 2011 at 2:45 pm
Viewing 15 posts - 31 through 45 (of 46 total)