Bundled Oracle JDBC driver can incorrectly report Oracle Advanced Security errors (since 5.2.0.0).

Even when Oracle Advanced Security is not turned on for the server, the following error can occur during connect:

To work around the issue, set the connection URL option randomNumberGenerationOptions to one of the following values:

“1” - The driver uses secure random numbers for handshake. The driver generates secure random numbers before the start of handshake, thus preventing this issue to occur due to the amount of time the connection needs to be made.

“2” - The driver uses random numbers instead of secure random numbers for handshake. This is less secure but provides a faster connection to occur.DataDirect recommends setting this to the value of “1” and then re-testing. If the issue still occurs, then try the value of “2”.

Occasional connection errors with some JDBC drivers. It is not recommended to use multiple correlators against a single IAF, as the message IDs might not be unique and therefore could result in failures.

Some supported databases store empty strings as NULL (since 5.3.0.0).

Some databases such as Oracle are known to store empty strings as NULL values, which can lead to confusion when executing queries where a field is compared to the empty string. For example, the following would not match rows where the field was null for such databases:

To ensure the desired results are returned when running queries against databases that store empty strings as null, we recommend queries to be written to check for NULL instead of empty string literals.

Support for NaN in Apama ADBC adapter (since 5.0).

Support for storing and retrieving a NaN value is not supported with all databases. The following databases have been tested: