Results 1 to 5 of 5
  1. #1
    Join Date
    Mar 2003
    Location
    Dallas, TX
    Posts
    2

    Unanswered: Trouble using jdbc 2 COM.ibm.db2.jdbc.app.DB2Driver

    Hi,
    I am using DB2 6.1 and I am trying to use
    the COM.ibm.db2.jdbc.app.DB2Driver via the JDBC 2 driver (db2java.zip).

    FYI, I am able to use COM.ibm.db2.jdbc.net.DB2Driver successfully.

    I set up the cllient side communication (on a Windows environment) using Client Configuration Assitant (the database instance resides
    on a Sun box).

    When I try use the COM.ibm.db2.jdbc.app.DB2Driver
    I keep on getting exceptions like:

    COM.ibm.db2.jdbc.app.DB2Exception: [IBM][CLI Driver][DB2/SUN] SQL0031C File "C:\SQLLIB\bnd\db2cliv2.bnd" could not be opened.

    at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_S QLException(SQLExceptionGenerator.java:225)
    at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_r eturn_code(SQLExceptionGenerator.java:403)
    at COM.ibm.db2.jdbc.app.DB2DatabaseMetaData.getSchema s(DB2DatabaseMetaData.java:1623)
    at MyDatabaseApp.describeDatabase(MyDatabaseApp.java: 88)
    at MyDatabaseApp.main(MyDatabaseApp.java:159)

    I clearly see that I am missing the above file? Is there something
    I missed in setting up the client communication via the
    Client Configuration Assitant? Is there some other utility that
    needs to be run so as to create the missing file?

    I appreciate any feedback.

  2. #2
    Join Date
    Sep 2002
    Posts
    456

    Re: Trouble using jdbc 2 COM.ibm.db2.jdbc.app.DB2Driver

    Take a look at under the bnd directory and see if that file is there. If not you have to reinstall the client again.

    dollar

    Originally posted by nsilva63
    Hi,
    I am using DB2 6.1 and I am trying to use
    the COM.ibm.db2.jdbc.app.DB2Driver via the JDBC 2 driver (db2java.zip).

    FYI, I am able to use COM.ibm.db2.jdbc.net.DB2Driver successfully.

    I set up the cllient side communication (on a Windows environment) using Client Configuration Assitant (the database instance resides
    on a Sun box).

    When I try use the COM.ibm.db2.jdbc.app.DB2Driver
    I keep on getting exceptions like:

    COM.ibm.db2.jdbc.app.DB2Exception: [IBM][CLI Driver][DB2/SUN] SQL0031C File "C:\SQLLIB\bnd\db2cliv2.bnd" could not be opened.

    at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_S QLException(SQLExceptionGenerator.java:225)
    at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_r eturn_code(SQLExceptionGenerator.java:403)
    at COM.ibm.db2.jdbc.app.DB2DatabaseMetaData.getSchema s(DB2DatabaseMetaData.java:1623)
    at MyDatabaseApp.describeDatabase(MyDatabaseApp.java: 88)
    at MyDatabaseApp.main(MyDatabaseApp.java:159)

    I clearly see that I am missing the above file? Is there something
    I missed in setting up the client communication via the
    Client Configuration Assitant? Is there some other utility that
    needs to be run so as to create the missing file?

    I appreciate any feedback.

  3. #3
    Join Date
    Mar 2003
    Location
    Dallas, TX
    Posts
    2
    I reinstalled the client twice. Once using the typical install options
    and again via the customized options (I did customized to see
    if there was an option to include the missing files). In either case,
    I do not see the missing file in the bnd directory.

    Is there somewhere to get this file? Does a patch exist for this problem
    concerning the client configuration assistant (db2 6.1) ?

  4. #4
    Join Date
    Mar 2003
    Posts
    33
    Have you remembered that:
    Before applications can access db2, the required paggages must be bound on the server. It will occur automatically on the first connection if the user has required authority to bind the packages. (It is still recommended that the administrator do this first with each version of the client on each platform that will access the server.)
    -r-

  5. #5
    Join Date
    Dec 2002
    Location
    Mumbai
    Posts
    19

    Re: Trouble using jdbc 2 COM.ibm.db2.jdbc.app.DB2Driver

    I think app driver is not suitable for db2 6 versions u can try by installing fix packs for it.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •