Fixing “SQL0980C A disk error occurred...” Error

Document Sample
Fixing “SQL0980C A disk error occurred...” Error Powered By Docstoc
					?Like any other database, a DB2 database can also be corrupted and become
unmountable. Few main causes for corruption in DB2 database could be improper
system shutdown, catalog file corruption, application malfunction, and virus attack.
Since the database becomes unmountable post corruption, the records saved in the
database also become inaccessible. In such situations, an ideal backup (hot, cold, or
standby) acts as a boon and enables the database user to access the database records.
However, if the database user has not maintained any backup or the backup file has
itself been corrupted, then the user needs to repair the logically damaged database
using effective third-party DB2 Database Recovery software.

For deep analysis of the above scenario, consider a real-time situation, wherein you
encounter the below error message while trying to mount your DB2 8.2.6 database
stored on Windows 2000 machine:

"SQL0980C A disk error occurred SQL0980C Subsequent SQL statements cannot be
processed. SQLSTATE=58005."

On viewing the db2diag file, you view the below information:

"2007-04-13-11.50.10.692000+600 I148443H443 LEVEL: Severe
PID : 5760 TID : 3580 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : AXISHSD1
APPHDL : 0-573 APPID: *LOCAL.DB2.070413015010
FUNCTION: DB2 UDB,data management, sqldLoadTCB, probe:4649
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.
…...
2007-04-13-11.50.10.692000+600 I149350H355 LEVEL: Severe
PID : 5760 TID : 3580 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : AXISHSD1
APPHDL : 0-573 APPID: *LOCAL.DB2.070413015010
MESSAGE : SQLD_TCB:
DATA #1 : String, 37 bytes
Perm Table(0:1)=TBSPACEID=0.TABLEID=1"

Cause

The above error message appears when the database is corrupt.

Resolution

To resolve the above error message and to access the database records, follow the
below steps:
Run 'db2dart' command to identify the cause and resolution of the problem.
However, if the command fails to report the issue, then you will need to restore the
data from an updated backup.
But, if the backup does not exists, then use a commercial DB2 Recovery utility. A db2
repair tool ensures complete repair of logically damaged databases by incorporating
powerful, yet safe mechanisms.

DB2 Recovery is the world's only third-party db2 database repair tool that repairs
logically damaged databases. The repair process includes few simple steps, which are
mentioned in the user-manual of the software. Compatible with IBM DB2 (UDB) v8
databases, the tool recovers all DB2 objects. The read-only tool is compatible with
Windows 2003, XP, and 2000.

				
DOCUMENT INFO