How do you recover a damaged database. Just got a SQL1034C SQLSTATE=58031? Can you offer advise ASAP?

Hi all,

While writing my first piece from home, I just got a call that one of my database is receiving  a Just got a SQL1034C SQLSTATE=58031 with the exciting information that The database is damaged.  All applications processing the database have been stopped.

I have no illussion as to what to do, except the thought of doing database recovery? What and how would you recommend/suggest that handle this emergency? I will like to preserve some information for diagnostic before I try to recover. What would you?

Please good people this is an emergency. So respond soon
EnyinnayaAsked:
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.

sathyaram_sCommented:
Have a look at this tech note:

http://www-01.ibm.com/support/docview.wss?uid=swg21217963

See if it matches with your problem
0

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
mustaccioCommented:
What was being done when the error happened?

The error description in the manual really says it all regarding your options:
User response

Issue a RESTART DATABASE command to recover the database. If the RESTART command consistently fails, you may want to restore the database from a backup. In a partitioned database server environment, check the syslog to find out if the RESTART command fails because of node or communication failures before restoring the database from a backup. If so, ensure the database manager is up and running and communication is available among all the nodes, then resubmit the restart command.

If you encountered this error during roll-forward processing, you must restore the database from a backup and perform roll-forward again.


All diagnostic information remains in db2diag.log and possibly in FFDC files in sqllib/db2dump.
0
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
DB2

From novice to tech pro — start learning today.