|
Problem IC65992
|
Status: Closed |
EXTENDING THE RAW DEVICE TABLESPACE CONTAINER SHOWS THE EINVAL ERROR MESSAGE IN DB2DIAG.LOG. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Extending the raw device tablespace container shows the
following message in db2diag.log;
2009-05-28-20.01.26.686483+540 E10134A547 LEVEL: Severe (OS)
PID : 905446 TID : 1 PROC : db2agent (<dbname>) 0
INSTANCE: cdbinst1 NODE : 000 DB : <dbname>
APPHDL : 0-590 APPID: *LOCAL.cdbinst1.090528105700 AUTHID :
<authID>
FUNCTION: DB2 UDB, oper system services, sqloclose, probe:10
CALLED : OS, -, fsync
OSERR : EINVAL (22) "Invalid argument"
DATA #1 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes
0x0FFFFFFFFFFE9940 : 0000 0028 0000 0080 ...(....
- Calling fsync() during 'alter tablespace <> extend' [fsync() a
raw device] returns EINVAL message. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* Extending the raw device tablespace container shows the *
* *
* following message in db2diag.log; *
* *
* *
* *
* 2009-05-28-20.01.26.686483+540 E10134A547 LEVEL: Severe (OS) *
* *
* PID : 905446 TID : 1 PROC : db2agent (<dbname>) 0 *
* *
* INSTANCE: cdbinst1 NODE : 000 DB : <dbname> *
* *
* APPHDL : 0-590 APPID: *LOCAL.cdbinst1.090528105700 AUTHID : *
* *
* <authID> *
* *
* FUNCTION: DB2 UDB, oper system services, sqloclose, probe:10 *
* *
* CALLED : OS, -, fsync *
* *
* OSERR : EINVAL (22) "Invalid argument" *
* *
* DATA #1 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes *
* *
* 0x0FFFFFFFFFFE9940 : 0000 0028 0000 0080 ...(.... *
* *
* *
* *
* - Calling fsync() during 'alter tablespace <> extend' *
* [fsync() a *
* raw device] returns EINVAL message. *
****************************************************************
* RECOMMENDATION: *
* SQL will return successful and the tablespace is usable even *
* though the message is there in the db2diag.log. *
**************************************************************** |
| Local Fix: |
SQL will return successful and the tablespace is usable even
though the message is there in the db2diag.log. |
| 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 |
|
| Workaround |
SQL will return successful and the tablespace is usable even
though the message is there in the db2diag.log. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.02.2010
14.05.2010
14.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
