[This topic is migrated from our old forums. The original author name has been removed]
I upgraded to DB2 9 and now explain plan throws a NullPointerException (everything else works fine):
java.lang.NullPointerException at com.onseven.dbvis.T.D.?(Unknown Source) at com.onseven.dbvis.sql.U.?(Unknown Source) at com.onseven.dbvis.sql.U.?(Unknown Source) at com.onseven.dbvis.sql.U.?(Unknown Source) at com.onseven.dbvis.db.db2.DB2ExplainPlanHandler.init(Unknown Source) at com.onseven.dbvis.db.db2.DB2ExplainPlanHandler.fetchExplainPlan(Unknown Source) at com.onseven.dbvis.M.C.?(Unknown Source) at com.onseven.dbvis.M.C.access$500(Unknown Source) at com.onseven.dbvis.M.C$A.construct(Unknown Source) at se.pureit.swing.util.SwingWorker$2.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
Version: Product: DbVisualizer Personal 5.1.1 Build: #1162 (2006/10/16 14:11) Java VM: Java HotSpot(TM) Client VM Java Version: 1.5.0_10-b03 Java Vendor: Sun Microsystems Inc. OS Name: Windows XP OS Arch: x86 OS Version: 5.1
anonymous
java.lang.NullPointerException
at com.onseven.dbvis.T.D.?(Unknown Source)
at com.onseven.dbvis.sql.U.?(Unknown Source)
at com.onseven.dbvis.sql.U.?(Unknown Source)
at com.onseven.dbvis.sql.U.?(Unknown Source)
at com.onseven.dbvis.db.db2.DB2ExplainPlanHandler.init(Unknown Source)
at com.onseven.dbvis.db.db2.DB2ExplainPlanHandler.fetchExplainPlan(Unknown Source)
at com.onseven.dbvis.M.C.?(Unknown Source)
at com.onseven.dbvis.M.C.access$500(Unknown Source)
at com.onseven.dbvis.M.C$A.construct(Unknown Source)
at se.pureit.swing.util.SwingWorker$2.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Version:
Product: DbVisualizer Personal 5.1.1
Build: #1162 (2006/10/16 14:11)
Java VM: Java HotSpot(TM) Client VM
Java Version: 1.5.0_10-b03
Java Vendor: Sun Microsystems Inc.
OS Name: Windows XP
OS Arch: x86
OS Version: 5.1
DB Connection:
Database Product Name: DB2/NT
Database Product Version: SQL09010
Driver Name: IBM DB2 JDBC Universal Driver Architecture
Driver Version: 3.1.57
I tried different JDBC driver versions with the same result.
It works when connected to DB2 8.
Thanks
Bernd