home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC64727 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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.
Problem-Zusammenfassung:
**************************************************************** 
* 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.                       * 
****************************************************************
Local-Fix:
n/a
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in Version 9.7 Fix Pack 1.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC64787 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.11.2009
23.04.2010
23.04.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP1
Problem behoben lt. FixList in der Version
9.7.0.2 FixList