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

[Former Member]

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

[former_member188883 · Accepted solution]

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

[Former Member · Accepted solution]

Hi Deepak

Thanks for your support.

I used ACTIVATE command at DB level after that the database was opened and SAP Inst contiunes. Now I am facing problem at next level - Adjust Nametab

Inst Log

INFO 2013-02-02 10:01:59.460
Creating file /tmp/sapinst_instdir/ERPEhP5/LM/COPY/DB6/SYSTEM/CENTRAL/AS-ABAP/dipgntab.log.

INFO 2013-02-02 10:01:59.550
Output of /usr/sap/HUW/SYS/exe/run/dipgntab -rwr40 -srctt DDNTT -srctf DDNTF -dsttt DDNTT -dsttf DDNTF -ttonly TT is written to the logfile dipgntab.log.

WARNING 2013-02-02 10:02:01.790
Execution of the command "/usr/sap/HUW/SYS/exe/run/dipgntab -rwr40 -srctt DDNTT -srctf DDNTF -dsttt DDNTT -dsttf DDNTF -ttonly TT" finished with return code 255. Output:
ERROR in initialization (can't get R/3-version)
ERROR in initialization (can't get R/3-version)

ERROR 2013-02-02 10:02:01.800
CJS-30023  Process call '/usr/sap/HUW/SYS/exe/run/dipgntab -rwr40 -srctt DDNTT -srctf DDNTF -dsttt DDNTT -dsttf DDNTF -ttonly TT' exits with error code 255. For details see log file(s) dipgntab.log.

ERROR 2013-02-02 10:02:01.980
FCO-00011  The step adjustNametab 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_Postload|ind|ind|ind|ind|11|0|NW_Postload_DB6|ind|ind|ind|ind|5|0|adjustNametab was executed with status ERROR ( Last error reported by the step :Process call '/usr/sap/HUW/SYS/exe/run/dipgntab -rwr40 -srctt DDNTT -srctf DDNTF -dsttt DDNTT -dsttf DDNTF -ttonly TT' exits with error code 255. For details see log file(s) dipgntab.log.).

INFO 2013-02-02 10:02:02.640
Creating file /tmp/sapinst_instdir/ERPEhP5/LM/COPY/DB6/SYSTEM/CENTRAL/AS-ABAP/__instana_tmp.xml.

dipgntab.log

ERROR in initialization (can't get R/3-version)

ERROR in initialization (can't get R/3-version)

Can you please help me to find out the solutions

OS HPUX 11.3i

DB2 9.7 Fix 5

ECC 6.0 EHP5

Installation sw - BS7i2010_Installation_Master_

Kernel NW_7.02_Kernel_7.20_HP_AIX_SOL_z_OS

Thanks

Bharathi

[former_member188883 · Accepted solution]

Hi Bharathi,

Could you apply latest kernel and repeat the installation steps.

Regards,

Deepak Kori

[Former Member · Accepted solution]

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