|
Problem IC63214
|
Status: Closed |
ALTER TABLESPACE NO FILE SYSTEM CACHING ON LINUX FOR S/390 MAY RESULT IN TABLESPACE NOT BEING ACCESSIBLE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Currently, DIO on Linux for S/390 is only supported by DB2 if
the underlying device is of the SCSI type. However, due to
a bug in detecting SCSI devices, the ALTER TABLESPACE NO FILE
SYSTEM CACHING statement issued on Linux for S/390 may result
in the target tablespace becoming inaccessible.
.
The db2diag.log will contain messages similar to:
.
2007-11-12-12.28.11.905554-300 E1344A561 LEVEL: Warning
PID : 9440 TID : 2199111563136PROC : db2age
INSTANCE: dbguest5 NODE : 000
APPHDL : 0-21 APPID: *LOCAL.dbguest5.0711121728
AUTHID : DBGUEST5
FUNCTION: DB2 UDB, oper system services, sqloseekread64,
probe:20
MESSAGE : ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic erro
DIA8501C A buffer pool logic error has occurred.
CALLED : OS, -, unspecified_system_function
OSERR : EINVAL (22) "Invalid argument"
.
and
.
ADM6023I The table space "<name>" (ID "<id>") is in state 0x"0"
The table space cannot be accessed. Refer to the
documentation for SQLCODE -290.
.
Any attempt to access the tablespace, even for the purpose of
re-enabling file system caching, results in:
.
SQL0290N Table space access is not allowed.
.
If the affected tablespace is SYSCATSPACE, the database will
become unusable as its activation will fail with:
.
SQL0902C A system error (reason code = "") occurred. |
| Problem Summary: |
Currently, DIO on Linux for S/390 is only supported by DB2 if
the underlying device is of the SCSI type. However, due to
a bug in detecting SCSI devices, the ALTER TABLESPACE NO FILE
SYSTEM CACHING statement issued on Linux for S/390 may result
in the target tablespace becoming inaccessible.
.
The db2diag.log will contain messages similar to:
.
2007-11-12-12.28.11.905554-300 E1344A561 LEVEL: Warning
PID : 9440 TID : 2199111563136PROC : db2age
INSTANCE: dbguest5 NODE : 000
APPHDL : 0-21 APPID: *LOCAL.dbguest5.0711121728
AUTHID : DBGUEST5
FUNCTION: DB2 UDB, oper system services, sqloseekread64,
probe:20
MESSAGE : ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic erro
DIA8501C A buffer pool logic error has occurred.
CALLED : OS, -, unspecified_system_function
OSERR : EINVAL (22) "Invalid argument"
.
and
.
ADM6023I The table space "<name>" (ID "<id>") is in state 0x"0"
The table space cannot be accessed. Refer to the
documentation for SQLCODE -290.
.
Any attempt to access the tablespace, even for the purpose of
re-enabling file system caching, results in:
.
SQL0290N Table space access is not allowed.
.
If the affected tablespace is SYSCATSPACE, the database will
become unusable as its activation will fail with:
.
SQL0902C A system error (reason code = "") occurred. |
| Local Fix: |
The cleanest workaround is to restore the database. If this is
not feasible, please contact IBM Service for patching the
SQLSPCS.1 and SQLSPCS.2 tablespace control files. |
| 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 |
apar IC63214
module engn_sqo
fixed >= v97 fpk2 |
| Workaround |
The cleanest workaround is to restore the database. If this is
not feasible, please contact IBM Service for patching the
SQLSPCS.1 and SQLSPCS.2 tablespace control files. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.09.2009
06.07.2010
06.07.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FPk2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
