IBM Support

IC64727: IBM DATA SERVER DRIVER FOR JDBC 3 MAY NOT LOAD IN JRE 5.0+ WHEN USING SECURITY MANAGER.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • All connectivity types: On IBM Data Server Driver for JDBC and
    SQLJ driver version 3.53.95 (which was bundled with DB2 for
    Linux,  Unix, and Windows v9.5 Fixpack 4) and above, a
    java.security.AccessControlException can occur when loading the
    JDBC driver The application must use the Java SecurityManager,
    and not allow reflection privileges to the application for the
    error to occur.
    
    When sending or receiving data as a  DECFLOAT data type, a
    java.security.AccessControlException may occur on all IBM Data
    Server Driver for JDBC and SQLJ driver versions 3.0+  and
    4.0-4.3.  Like the problem above, this exception can only occur
    when connecting to a database which supports the DECFLOAT data
    type while running Java 5.0+ on the client, and the application
    uses the Java SecurityManager and does not allow reflection
    privileges to the application.  This problem has now been
    resolved.
    
    This problem has already been resolved in driver versions
    4.3.111 (which was bundled with DB2 for Linux, Unix, and Windows
    v9.5 Fixpack 4) and above.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * N/A                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * All connectivity types: On IBM Data Server Driver for JDBC   *
    * and                                                          *
    * SQLJ driver version 3.53.95 (which was bundled with DB2 for  *
    *                                                              *
    * Linux,  Unix, and Windows v9.5 Fixpack 4) and above, a       *
    *                                                              *
    * java.security.AccessControlException can occur when loading  *
    * the                                                          *
    * JDBC driver The application must use the Java                *
    * SecurityManager,                                             *
    * and not allow reflection privileges to the application for   *
    * the                                                          *
    * error to occur.                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    * When sending or receiving data as a  DECFLOAT data type, a   *
    *                                                              *
    * java.security.AccessControlException may occur on all IBM    *
    * Data                                                         *
    * Server Driver for JDBC and SQLJ driver versions 3.0+  and    *
    *                                                              *
    * 4.0-4.3.  Like the problem above, this exception can only    *
    * occur                                                        *
    * when connecting to a database which supports the DECFLOAT    *
    * data                                                         *
    * type while running Java 5.0+ on the client, and the          *
    * application                                                  *
    * uses the Java SecurityManager and does not allow reflection  *
    *                                                              *
    * privileges to the application.  This problem has now been    *
    *                                                              *
    * resolved.                                                    *
    *                                                              *
    *                                                              *
    *                                                              *
    * This problem has already been resolved in driver versions    *
    *                                                              *
    * 4.3.111 (which was bundled with DB2 for Linux, Unix, and     *
    * Windows                                                      *
    * v9.5 Fixpack 4) and above.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.7 Fix Pack 1.                       *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in Version 9.7 Fix Pack 1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC64727

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-11-20

  • Closed date

    2010-04-23

  • Last modified date

    2010-04-23

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IC64787

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC64727

Modified date: 23 April 2010