I haven’t done much JDBC tracing yet, but recently for a Kerberos KCM + ANO case I wanted more traces. In the old doc, on google and myoraclesupport, you’ll often see about the _g suffix. Like using ojdbc8_g.jar and -Doracle.jdbc.Trace=true and -Doracle.jdbc.diagnostic.enableLogging=true. But chance are, you use a recent jar and find no _g one. […]
Tag: jdbc
sqlnet.ora and ldap.ora parameters in jdbc thin url
Using the latest instant client, the Easy Connect Plus improvement let you parametrise your jdbc url more intensively jdbc:oracle:thin:@ldaps://ldap.example.com/db01?WALLET_LOCATION=/db00/mywallet&AUTHENTICATE_BIND=true&AUTHENTICATE_BIND_METHOD=none&DIRECTORY_SERVER_TYPE=OID EasyConnect Plus appeared in 19c, but was further improved in 21c and 23ai. See more JDBC Developer’s Guide https://docs.oracle.com/en/database/oracle/oracle-database/19/jjdbc/data-sources-and-URLs.html#GUID-44572C63-10D2-478A-BB2E-ACF6674C59CC
jdbc url with ldap ssl in 21c
the basic : you have tns resolution over ldap. To change from ldap to ldaps, you modify : jdbc:oracle:thin:@ldap://ldap.example.com:389/DB01,cn=OracleContext,dc=example,dc=com to jdbc:oracle:thin:@ldaps://ldap.example.com:636/DB01,cn=OracleContext,dc=example,dc=com now the advanced : Oracle Support mentions, there is no support for Mode 2 SSL (note 1664857.1) So one approach was to either not use ldaps, or to use level 1, which means no […]