DB2 -SQL1036C An I/O error occurred while accessing the database SQLSTATE=58030

30 January,2012 by Tom Collins

I received the following error , when attempting to connect to a DB2 database

db2 connect to MYDB
SQL1036C  An I/O error occurred while accessing the database.  SQLSTATE=58030

#Checked in the db2diag.log file 

ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
          DIA8411C A file "" could not be found.

Log file S0000478.LOG not found.


Notes  to solution

1)       Verify if a log file is missing. Check the db2diag.log for the a related logging error (return code contains SQLO_FNEX).

2)       If present, this error will contain the name of the missing log file. Take steps to locate the file in the active log path directory.

3)       If the file cannot be located, restore and roll-forward the database to an earlier point in time referenced in a log file preceding the missing log file (use a timestamp that is earlier than that of the missing file).

4)       Other reasons can include database directory integrity

5)       Filesystem size constraint

 See Also

db2diag.log file delete on Linux and DB2


Author: Rambler(http://www.dba-db2.com)


Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment on DB2 -SQL1036C An I/O error occurred while accessing the database SQLSTATE=58030

Comments are moderated, and will not appear until the author has approved them.

dba-db2.com | DB2 Performance Tuning | DBA DB2:Everything | FAQ | Contact | Copyright