|
Problem IC66990
|
Status: Closed |
SQLEPSTP AND DB2INSTANCESTOP FAILED WITH "SQL1652N FILE I/O ERROR OCCURRED" ON AIX6.1 |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Occasionally while stopping the instance using either API
db2InstanceStop or sqlepstp(),
an "SQL1625N File I/O error occurred" error would
be received.
This error is seen in the db2diag.log, with an entry like:
2010-03-05-14.01.22.952999-300 I64243A357 LEVEL: Severe
PID : 5067406 TID : 1 PROC :
darkstar
INSTANCE: db2inst NODE : 000
EDUID : 1
FUNCTION: DB2 UDB, base sys utilities, sqlepstp, probe:100
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.
2010-03-05-14.01.22.957922-300 I64601A296 LEVEL: Severe
PID : 5067406 TID : 1 PROC :
darkstar
INSTANCE: db2inst NODE : 000
EDUID : 1
FUNCTION: DB2 UDB, base sys utilities, sqlepstp, probe:105
MESSAGE : /home/db2inst/sqllib/tmp/db2stop.11760454.da |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* Occasionally while stopping the instance using either API *
* *
* db2InstanceStop or sqlepstp(), an "SQL1625N File I/O error *
* occurred" error would be received. *
* *
* *
* *
* This error is seen in the db2diag.log, with an entry like: *
* *
* *
* *
* 2010-03-05-14.01.22.952999-300 I64243A357 LEVEL: *
* Severe *
* PID : 5067406 TID : 1 PROC : *
* *
* darkstar *
* *
* INSTANCE: db2inst NODE : 000 *
* *
* EDUID : 1 *
* *
* FUNCTION: DB2 UDB, base sys utilities, sqlepstp, probe:100 *
* *
* RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not *
* found." *
* DIA8411C A file "" could not be found. *
* *
* *
* *
* 2010-03-05-14.01.22.957922-300 I64601A296 LEVEL: *
* Severe *
* PID : 5067406 TID : 1 PROC : *
* *
* darkstar *
* *
* INSTANCE: db2inst NODE : 000 *
* *
* EDUID : 1 *
* *
* FUNCTION: DB2 UDB, base sys utilities, sqlepstp, probe:105 *
* *
* MESSAGE : /home/db2inst/sqllib/tmp/db2stop.11760454.da *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v97 fixpack 2. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
This problem occurs when the db2sysc process id is 8 digits
long. This issue is first fixed in v97fixpack 2. With this fix
the customer should no longer see this error. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66992 IC67528 IC68134
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.03.2010
26.04.2010
26.04.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FIXPACK,
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
