November 26, 2007 at 9:15 pm
I admit it. It was most likley something that I did.
I had to install some hardware and move the server. In all the fuss a scandisk fired off after a reboot and now the reporting services tempdb is (suspect). The rest of the data (the main data) is fine and can be queried .
I am new to SQL server troubleshooting and need to see if I can get a few tips on starting to get this DB back online, or if anyone knows if I can just recreate the DB with no tables...I just do not want to have to reonstall reporting services and start all over.
November 27, 2007 at 4:54 am
First try running DBCC CHECKDB(). From the sounds of things, that'll probably fix it. If not, you've got work to do. Can you restore it from backup? If not, you can try setting it to EMERGENCY mode using ALTER DATABASE. From there you can pull the data out & try recreating the database. After that, look at a reinstall. I hope this isn't a production system.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
November 27, 2007 at 5:28 am
Hi,
Check the following
http://www.simple-talk.com/sql/backup-and-recovery/pop-rivett-and-the-suspect-database/
http://support.microsoft.com/kb/224071
Regards,
ahmed
November 28, 2007 at 12:34 pm
I have successfully been able to get the database into emergency status, but after that I took the SQL service down and renamed the log firl. After I started the service back up the database was not listed and I was not able to reattach.
I do not want to have to reinstall reporting services, but it may have to be done that way.
Since this is a TempDB it is empty until people start running queries on the reporting services. I am trying to find a way to get the database reattached without having the log file present.
Maybe I just need to stick to front end programming...LOL.
Here is the error that I get:
TITLE: Microsoft SQL Server Management Studio
------------------------------
Attach database failed for Server 'localhost'. (Microsoft.SqlServer.Smo)
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
The log scan number (191:73:1) passed to log scan in database 'ReportServerTempDB' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
Could not open new database 'ReportServerTempDB'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 9003)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=9003&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
November 29, 2007 at 6:43 am
If you don't have a valid log file you can use sp_attach_single_file_db which will create an new log file. Use BOL for syntax. I had to use this yesterday on a SQL 2000 DB.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply