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
Who is Participating?
sathyaram_sConnect With a Mentor Commented:
Have a look at this tech note:

See if it matches with your problem
mustaccioConnect With a Mentor Commented:
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.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.