(inside a VMWare Fusion Pro 6 on OS X)
Version: 15.0.11-1
Build #: 41121
Build Date: 2014-Nov-18 12:32:10 PM
Operating Environment: Windows 8 (6.2, amd64) / Cp1252 / en / US / Oracle Corporation 1.7.0_60-b19
Memory: Max=1,037,959,168; Total=199,274,496; Free=101,977,680; CPUs=1
When attempting to view sessions via the DB2 DBA Tools > Session Manager for DB2 10.1 on 10.168.11.59
Launching the Session Manager displays no rows (see attached). Refreshing with SQL Log open produces exceptions.
When viewing the SQL Log, the following query is executed
SELECT
APPLICATION_HANDLE AS AGENT_ID,
CLIENT_IPADDR||' '||CLIENT_PORT_NUMBER AS INBOUND_COMM_ADDRESS,
SESSION_AUTH_ID AS AUTH_ID,
current server AS DB_NAME,
APPLICATION_NAME AS APPL_NAME,
CLIENT_PROTOCOL,
CLIENT_PLATFORM,
CLIENT_HOSTNAME AS CLIENT_NNAME,
CONNECTION_START_TIME AS APPL_CON_TIME,
APPLICATION_ID AS APPL_ID,
EXECUTION_ID,
-1 AS APPL_STATUS
FROM
TABLE(MON_GET_CONNECTION(cast(NULL as bigint), -2))
ORDER BY
APPLICATION_HANDLE
The following exception appears in the SQL Log
com.ibm.db2.jcc.am.SqlSyntaxErrorException: "EXECUTION_ID" is not valid in the context where it is used.. SQLCODE=-206, SQLSTATE=42703, DRIVER=3.67.28
at com.ibm.db2.jcc.am.gd.a(gd.java:749)
at com.ibm.db2.jcc.am.gd.a(gd.java:66)
at com.ibm.db2.jcc.am.gd.a(gd.java:135)
at com.ibm.db2.jcc.am.so.c(so.java:2763)
at com.ibm.db2.jcc.am.so.d(so.java:2751)
at com.ibm.db2.jcc.am.so.a(so.java:2200)
at com.ibm.db2.jcc.t4.ab.h(ab.java:141)
at com.ibm.db2.jcc.t4.ab.b(ab.java:41)
at com.ibm.db2.jcc.t4.o.a(o.java:32)
at com.ibm.db2.jcc.t4.tb.i(tb.java:145)
at com.ibm.db2.jcc.am.so.ib(so.java:2169)
at com.ibm.db2.jcc.am.so.a(so.java:3248)
at com.ibm.db2.jcc.am.so.a(so.java:691)
at com.ibm.db2.jcc.am.so.executeQuery(so.java:670)
at \\...\\ .\\हिñçêČάй語简??한\\.xꋷꁩꐘꌐ switch super.executeQuery(Unknown Source)
at \\...\\ .\\हिñçêČάй語简??한\\.Iꌸꌹꄢ̵ char switch.at(Unknown Source)
at \\...\\ .\\हिñçêČάй語简??한\\.Iꌸꌹꄢ̵ char switch.aR(Unknown Source)
at \\...\\ .\\हिñçêČάй語简??한\\.Wꎓ⠌ᝍꇮ 5 native.c(Unknown Source)
at \\...\\ .\\हिñçêČάй語简??한\\.jꃑ⡰ꍌᡡ.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Using the same build of ADS I am able to see the session manager session when connecting to DB2 9.7 without exceptions in the SQL Log.