DB2 - Problem description
Problem IC61815 | Status: Closed |
"AUTH_ID" IS NOT VALID IN THE CONTEXT WHERE IT IS USED FROM THE ACTIVITY MONITOR TOOL | |
product: | |
DB2 CONNECT / DB2CONNCT / 970 - DB2 | |
Problem description: | |
When AUTH_ID is used as a part of the filter in the Activity Monitor tool the error is being reported back: "AUTH_ID" is not valid in the context where it is used The SQL statement generated by Activity Monitor is failing as well: C:\Program Files\IBM\SQLLIB_02\BIN>db2 CALL SYSPROC.AM_GET_RPT(-2, 3, 'AUTH_ID = ''DB2INST2''', 10) SQL0206N "AUTH_ID" is not valid in the context where it is used. SQLSTATE=42703 The reason for this is: v8 is using AUTH_ID in the call of SYSPROC>AM_GET_RPT, but starting from v9.1 we started to use PRIMARY_AUTH_ID. GUI part of Activity Monitor has to be changed to use PRIMARY_AUTH_ID instead of AUTH_ID while calling SYSPROC.AM_GET_RPT SP. Description of SYSPROC.AM_GET_RPT on Infocenter also needs to be changed. This APAR will address those changes. | |
Problem Summary: | |
User's affected: All Problem Sumamry: When AITH_ID is used as a part of the filter in the Activity Monitor tool the error is being reported back: "AUTH_ID" is not valid in the context where it is used | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 Fix Pack 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 02.07.2009 21.12.2009 21.12.2009 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP1 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |