October 28, 2004 at 6:03 am
I know I will lose all the DTS and jobs/backup information (Which I've backed up anyway) but will the system create a new msdb on the next sql restart or will I have to create it manually.
The reason I have to do this is because
1) All my backup jobs actually work but fail to write record to msdb
2) cannot create and save any new dts packages.
I have tried restoring msdb from back up in QA with recover but still in the same situation. Any advice greatly appreciated. Regards. This is the message I get from my back up job.
Processed 19064 pages for database 'msdb', file 'MSDBData' on file 3.
Processed 1 pages for database 'msdb', file 'MSDBLog' on file 3.
Server: Msg 3009, Level 16, State 3, Line 1
Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful.
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 51 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
RESTORE DATABASE successfully processed 19065 pages in 16.812 seconds (9.289 MB/sec).
October 28, 2004 at 6:41 am
See if this helps:
http://support.microsoft.com/default.aspx?scid=kb;en-us;319701
http://support.microsoft.com/default.aspx?scid=kb;en-us;198572
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
October 28, 2004 at 8:48 am
Ramesh,
Try this..this is a unorthodox way but you have to try it to see if it works...I have tried it and it works fine on user databases. Create a blank database. Then Use a DTS package to copy all data and objects to that new database from MSDB. Once you have that. Rename the msdb and rename the new database MSDB.
This way it will give you a blank new database with new log file. Looking at errors..it looks like your ldf file is full and it cant write any more changes to that file.
Good luck...anytime there is a problem with system DB's it gives me hiccups.
Hope it workss...
Tajammal Butt
October 29, 2004 at 2:10 pm
Does this work with TempdB as well. My TempdB is getting really huge. I tried shutting down, and even though it made some difference. the dB is still way too big.
I actually wanted to move it to another drive, but it wouldn't let me. Anyway to get around that?
Thanks!
Paul
October 30, 2004 at 1:02 pm
See, if this helps:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;307487
for shrinking tempdb. And this
http://support.microsoft.com/default.aspx?scid=kb;en-us;224071
how to move it
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
November 1, 2004 at 10:00 am
tempdb rebuilds itself everytime a sql server is started. Trying shutting down sql server and restarting and see if that helps...
taj
Tajammal Butt
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply