Skip to Content
avatar image
Former Member

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

Hi

I request you to help for me to solve this issue. I encountered this issue while performing system copy. The error raised at GRANT DATABASE PRIVILAGES stage.

SELECT schemaname FROM syscat.schemata WHERE schemaname='SAPTOOLS'

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

TERMINATE

DB20000I The TERMINATE command completed successfully.

ERROR 2013-01-31 12:18:41.800

MDB-01999 Error occured, first error is: <SQL1036C An I/O error occurred while accessing the database. SQLSTATE=58030>

ERROR 2013-01-31 12:18:41.800

MUT-03025 Caught ESAPinstException in module call: Error occured, first error is: <SQL1036C An I/O error occurred while accessing the database. SQLSTATE=58030>.

ERROR 2013-01-31 12:18:41.980

FCO-00011 The step createSchemaSAPTools with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_DB6_DB|ind|ind|ind|ind|1|0|NW_DB6_Privileges|ind|ind|ind|ind|28|0|createSchemaSAPTools was executed with status ERROR ( Last error reported by the step :Error occured, first error is: <SQL1036C An I/O error occurred while accessing the database. SQLSTATE=58030>).

INFO 2013-01-31 12:18:42.590

Creating file /tmp/sapinst_instdir/ERPEhP5/LM/COPY/DB6/SYSTEM/CENTRAL/AS-ABAP/__instana_tmp.xml.

I tried to login database through command and recived below error.

SANBOX:db2huw 2> db2 connect to HUW

SQL1042C An unexpected system error occurred. SQLSTATE=58004

SANBOX:db2huw 3>

Please help to sort out this issue.

Regards,

Bharathi

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    Jan 31, 2013 at 05:00 PM

    Hi Bharathi,

    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

    Regards,

    Deepak Kori

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Deepak Kori

      Hi Deepak

      We faced the same problem after applying the latest kernel as well. The error was corrected by identifying the information in db2dilog.log and found that there was a problem in permissions for log folder. We have corrected the issue by providing required permissions at OS level for archive and log folders.

      Regards,

      Bharathi