Thanks Marcin. I wasn't sure what the difference between the App and Net drivers was. I tried the Net driver again, with the Extra Classpath you specified, and I got closer. Now it's failing because of a user/pswd problem: java.util.concurrent. Execution Exception: java.lang. Runtime Exception: com.ibm.db2.jcc.am. Sql Invalid Authorization Spec Exception: [jcc][t4][2013][11249][ ] Connection authorization failure occurred. Reason: User ID or Password invalid. ERRORCODE=-4214, SQLSTATE=28000 I tried using db2admin, both with the password I changed it to have in Active Directory and the default of db2admin; I also tried the Administrator userid/pswd. I realize this is not strictly a Squirrel SQL Client issue, but I'm new to both it and DB2 for LUW. I'm more used to DB2 for i. On 5:59 AM, Marcin Krol wrote: > - BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello Peter, > > I'm not sure that app driver even works well enough or it is updated. > Around here (big blue) everybody I know is using net driver. > > IBM DB2 Net Driver > example url: jdbc:db2 :<6789>/ website: > > extra classpath contains: db2jcc4.jar, db2jcc_license_cu.jar > > class name: com.ibm.db2.jcc. DB2 Driver > > > Above settings have worked for me for every 10.1 instance I worked with. > > > Regards, > Marcin Krol > > > > Peter Dow wrote: > I've created an IBM DB2 database named MIRdb, and then tried to connect > to it using the Squirrel SQL Client version. > > The driver is: > Name: IBM DB2 App Driver > Example URL: jdbc:db2: > Class Name: COM.ibm.db2.jdbc.app. DB2 Driver > Extra Class Path: > C:\ Program Files\ IBM\ SQLLIB\java\db2java.zip > C:\ Program Files\ IBM\ SQLLIB\java\db2jcc.jar > C:\ Program Files\ IBM\ SQLLIB\java\db2jcc4.jar > C:\ Program Files\ IBM\ SQLLIB\java\sqlj.zip > C:\ Program.
Introduction The most recent step in the evolution of Java development in the DB2 environment is the DB2 UDB JDBC Universal Driver. This new driver offers many advantages and improvements that make it the optimal choice for application development. In this article, gain an understanding of the inner workings of the driver and see how it can fit in with your overall application development plan. Let's start by comparing two types of drivers that are available: The legacy based CLI driver The new JDBC Universal driver In the first section, the differences between the drivers are highlighted by concentrating on the following topics: Installation Connection Driver initialization Features Error handling Transaction management The second section will deal with diagnosing problems and analyzing traces. In order to understand how to do this, you need to know the different parts of an SQLException and how it relates to JDBC. With the new JDBC universal driver, we will try to understand how exactly to take the JCC trace and what is needed to take the JCC trace. Once the trace is taken, we will look deep into what makes up this trace and how to use it to your advantage to get to the bottom of a problem. Compare the legacy JDBC driver with the new universal JDBC driver In order to understand how we came to the development of the DB2 Universal Driver, you need to understand how the JDBC specification defines the different types of drivers in the Java world. Type 1 driver: This type of driver code maps directly to a high level native API. JDBC and ODBC are similar APIs, so this type of driver is usually associated with the JDBC- ODBC bridge. This driver does not have too much context with respect to the DB2 UDB product. Type 2 driver: A T2 driver has a native component that is part of the driver, but separate from the data access API. The native component and the Java component make up this.
Listed below are connection examples for three common JDBC drivers for IBM DB2: IBM DB2 Universal Driver Type 4 DRIVER CLASS: com.ibm.db2.jcc. DB2 Driver DRIVER LOCATION: db2jcc.jar and db2jcc_license_cu.jar ( Both of these jars must be included) JDBC URL FORMAT: jdbc:db2 [:]/ JDBC URL Examples: jdbc: IBM DB2 Universal Driver Type 2 DRIVER CLASS: com.ibm.db2.jcc. DB2 Driver DRIVER LOCATION: db2jcc.jar and db2jcc_license_cu.jar ( Both of these jars must be included) JDBC URL FORMAT: jdbc:db2: JDBC URL Examples: jdbc:db2:sample App JDBC Driver In order to be able to use the DB2 App driver, certain software must be installed on your machine. This usually entails installing the IBM DB2 Client software. See IBM's site for more information. DRIVER CLASS: COM.ibm.db2.jdbc.app. DB2 Driver DRIVER LOCATION: To use the App driver, the DB2 client software should be installed on your machine. The name of the file that contains the DB2 App driver is usually db2java.zip. However, this may change depending on the version of the client software that is installed. Usually, the DB2 client software is installed in the SQLLIB directory. For example, if you are using Windows, the following may be the location of the db2java.zip file: c:\ SQLLIB\java12\db2java.zip JDBC URL FORMAT: jdbc:db2: JDBC URL Examples: jdbc:db2:test Net JDBC Driver DRIVER CLASS: COM.ibm.db2.jdbc.net. DB2 Driver DRIVER LOCATION: The DB2 Net drivers can be obtained by installing the DB2 client software from IBM. Depending on the version of the client software, the net drivers are usually contained in the db2java.zip file. For example, if using Windows, the following may be the location of the db2java.zip file that contains the drivers: c:\ SQLLIB\java12\db2java.zip JDBC URL FORMAT: jdbc:db2 :/ The default port for.
Download Now