HY000 error (sql error 5242)- how to troubleshoot it

can you suggest how to troubleshoot this error: i dont see any DBCC check errors.. neither are any error message at that time in sql logs
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

25112Author Commented:
ERROR [HY000] [Microsoft][SQL Native Client][SQL Server]Warning: Fatal error 5242 occurred at Oct 1 2013 9:19AM. Note the error and time, and contact your system administrator.

is the error
Try setting the db into Emergency mode, running CheckDB, and then setting it back to normal. DBCC might catch more in emergency mode ...

alter database @database_name set emergency
dbcc checkdb ( '@database_name', Repair_rebuild )
alter database @database_name set multiuser


25112Author Commented:
this is a production database.. can i do a backup/restore to different server and run emergency mode.. will it still find any issues.. or the issues are disk related and cant be duplicated on another server?
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

Mostly a backup will show the same problems as the original, so try it out.
25112Author Commented:
i made a backup and tried to restore in the new system.. i get this error..

Msg 3167, Level 16, State 1, Line 1
RESTORE could not start database 'RATAS3rd'.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
Msg 211, Level 23, State 27, Line 1
Possible schema corruption. Run DBCC CHECKCATALOG.

when i check in
select * from sys.databases
i see that database listed in State_Desc as 'RECOVERY_PENDING'
recovery model is 'BULK_LOGGED'
page_verify_option_desc is NONE
log_reuse_wait_desc is NOTHING
25112Author Commented:
i ran
on the original database and i get

"DBCC execution completed. If DBCC printed error messages, contact your system administrator."

and no other error message.
25112Author Commented:
ok- i finally got it going.. it was a 2005db and i could not install on 2008.. but after i install in another 2005 box,
i tried repair build, but it says

The repair statement was not processed. This level of repair is not supported when the database is in emergency mode.

so I brought it online and then single user mode.. then repair rebuild.. it says
CHECKDB found 0 allocation errors and 0 consistency errors
so does that mean 100% it is good?
Well, it means that DBCC didn't find anything! You say that it is up ok on another 2005 box. Could you go and see what its compatibility level is? (see screen shot). Here is some info on compatibility levels. I'm not sure how far back 2005 will reach, but there are limits, and you may have reached them if your level is, say, from SQL Server 6.5.



Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.