Adding a license key jar when using a specific JDBC driver to connect to Veridata source and target DBs
Last updated on JULY 17, 2017
Applies to:Oracle GoldenGate Veridata - Version 220.127.116.11.1 and later
Information in this document applies to any platform.
We are testing Veridata v12.1.3 and because of security requirements, we need to use a specific driver for the Veridata agent connection to the source and target DB2 DBs.
The db2 jdbc driver requires a license key "db2jcc_license_cisuz.jar" to
connect to the db2. The license jar file must be placed in a location listed
in the CLASSPATH variable.
Where can we set CLASSPATH=<path/value> to allow the Jagent to pickup and
use the key in v12.1.3 jagent?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms