Known issues and limitations
Known issues or limitations that you might encounter in specific system environments, or configurations.
Some of the problems described in this topic might not be limitations with the release because instructions are provided to work around problems, where possible.
- Error when using JavaFX application launcher
-
The JavaFX application launcher is a feature provided by Oracle in Java™ SE V8. However, JavaFX is not currently supported by the IBM® release. An error occurs if you attempt to run a JavaFX application from the command-line.
- Chinese characters stored as ? in an Oracle database
-
When you configure an Oracle database to use the ZHS16GBK character set, some Chinese characters or symbols that are encoded with the GBK character set are incorrectly stored as a question mark (?). This problem is caused by an incompatibility of the GBK undefined code range Unicode mapping between the Oracle ZHS16GBK character set and the IBM GBK converter. To fix this problem, use a new code page, MS936A, by including the following system property when you start the JVM:
-Dfile.encoding=MS936A
For IBM WebSphere® Application Server users, this problem might occur when web applications that use JDBC configure Oracle as the WebSphere Application Server data source. To fix this problem, use a new code page, MS936A, as follows:- Use the following system property when you start the JVM:
-Dfile.encoding=MS936A
- Add the following lines to the
WAS_HOME/properties/converter.properties file, where
WAS_HOME is your WebSphere
Application Server installation directory.
GBK=MS936A GB2312=MS936A
- Use the following system property when you start the JVM:
- Accessibility issues with the policytool graphical user interface (GUI) utility
-
The Policy File Creation and Management Tool, policytool, is provided in two formats: command-line utility and GUI utility. For consistency, IBM is including the standard Oracle utilities with this release. The GUI utility has a slightly different look and feel to the equivalent tool provided in earlier versions of the release. If you have issues with the accessibility features of this utility, use the command-line version instead.
- Accessibility issues with the jconsole utility
-
For consistency, IBM has included the standard Oracle jconsole utility from version 8 of the product. The graphical user interface of this utility has a slightly different look and feel to the equivalent tool provided in earlier versions. If you have issues with the accessibility features of the replacement utility, use the IBM Health Center tool, which has equivalent function. For more information about this IBM Monitoring and Diagnostic tool, see the IBM Monitoring and Diagnostic Tools product documentation.
- JDBC V4.2 incompatible drivers
-
Version 4.2 of this data access application programming interface is available with the IBM SDK. JDBC V4.2 functions properly only with supported JDBC drivers. If you use an incompatible driver, or an older driver, an exception of type SQLFeatureNotSupportedException is thrown. Consult the product documentation for your driver to check whether you have the correct version. For example, to access an Apache Derby database, the Derby driver version must be 10.10.2.1.1597921 or later.
Unexpected XSLT error on extension elements or extension functions when security is enabled
Any attempt to use extension elements or extension functions when security is enabled, results in
a javax.xml.transform.TransformerException
error during XSLT processing.
The following XSLT message is generated when extension functions are used: Use of the extension function '<method name>' is not allowed when Java security is enabled. To override this, set the com.ibm.xtq.processor.overrideSecureProcessing property to true. This override only affects XSLT processing.
The following XSLT message is generated when extension elements are used: Use of the extension element '<element name>' is not allowed when Java security is enabled. To override this, set the com.ibm.xtq.processor.overrideSecureProcessing property to true. This override only affects XSLT processing.
To allow extensions when security is enabled, set the com.ibm.xtq.processor.overrideSecureProcessing system property to true. For more information about this system property, see -Dcom.ibm.xtq.processor.overrideSecureProcessing.