|
Problem IC62721
|
Status: Closed |
SQL0901N MAY BE ISSUED (OR THE INSTANCE MAY ABEND) DURING EVENT MONITOR CREATION WITH DB2_COMPATIBILITY_VECTOR SET |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
SQL0901N may be issued (or the instance may abend) if an EVENT
MONITOR (EM) is being
created with an event-condition, i.e., WHERE clause, specified.
For this to occur, these conditions must be satisfied:
- EM is for STATEMENTS, TRANSACTIONS or CONNECTIONS
- The database varchar2_compat configuration parameter was set
at database creation time
- The DB2_COMPATIBILITY_VECTOR registry variable is set to ORA
or has the 9th bit set (0x100) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Performance Expert *
****************************************************************
* PROBLEM DESCRIPTION: *
* Creation of an event monitor for statements ( CREATE EVENT *
* MONITOR ... FOR STATEMENTS ... ) fails if the db2 registry *
* variable DB2_COMPATIBILITY_VECTOR has been set to ORA. The *
* DB2 server returns the following error message: *
* *
* DB2 SQL Error: SQLCODE=-901, SQLSTATE=58004, *
* SQLERRMC=sqlnq_evmon_pack_pred [250]:rc( 0) *
* , DRIVER=3.53.95, SQLState=<58004>, ErrorCode=<-901>. *
* SQLCA=<The SQL statement failed because of a non-severe *
* system error. Subsequent SQL statements can be processed. *
* (Reason "sqlnq_evmon_pack_pred [250]:rc( 0) *
* ".). SQLCODE=-901, SQLSTATE=58004, DRIVER=3.53.95>. *
****************************************************************
* RECOMMENDATION: *
* apply FP1 *
**************************************************************** |
| Local Fix: |
No workaround exists if the database was created with the
varchar2_compat database configuration parameter set.
Otherwise, temporarily unset the DB2_COMPATIBILITY_VECTOR
registry variable prior to creation of EM. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 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 |
In the given ORACLE semantics, the shorter string is upcasted
to the length of the longer string and padded with blanks. In
this case, the APPL_ID is upcasted and has blanks at the end.
The length comparison checking for the MONITOR identifiers
consequently fail. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.08.2009
19.02.2010
19.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
