8 Known Issues and Workarounds

This chapter details known issues in this release, and their workarounds.

Mismatch in Server Certificate DN with connection details having tls for ATP/ADW-D:

When you navigate to Dataserver configured with ATP/ADW-D and select Connection details with TLS, Test connection fails due to server certificate issue. It happens when you force JDBC driver to match DN (Server's Distinguished Name) by setting the property oracle.net.ssl_server_dn_match=true and DN mentioned in JDBC URL does not match with the DN mentioned in server certificate.

As a workaround, mention the correct DN in JDBC URL or set oracle.net.ssl_server_dn_match=false in the JDBC tab of ATP/ADW data server.

For example, the expected DN in the JDBC URL is:

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=servername)(PORT=
2484))(CONNECT_DATA=(SERVICE_NAME=servicename))(SECURITY=(SSL_SERVER_CERT_DN=\
"CN=server_test,C=US\")))

Issue with ODI Studio when rebooting the ODI instance

When starting ODI studio after rebooting an ODI instance, an exception is observed. As a workaround, start the ODI studio with -clean option to clear the cache.