We are using OPODs and the internal Oracle structure is kind of a black box for anyone but DBAs. They have provided us the following connection string. In Splunk DB connect, the requirement is to have the host name and port number for Oracle, so instead, can we use following string to make a connection to the underlying Oracle DB server?
You can use LDAP to lookup the connect string by installing an Oracle Client on your Splunk system and altering the connect string prototype in the DB Connect db_connection_types.conf file to use a JDBC-Thick (OCI) connection instead of JDBC-Thin, something like this:
jdbcUrlFormat = jdbc:oracle:oci:@TNSALIAS
This would allow you to use TNSNAMES, say to define a connection string with SOURCE_ROUTE, enable strong network encryption, or to use LDAP resolution instead of tnsnames.ora.
Our DBA group is insisting to use the LDAP lookup using JDBC connection string instead of hardcoding the host name and the port number for ORACLE DB connection. Can anyone please comment on how to override the Splunk DB Connect App required "host name" and "host port" fields?
I talked to DBA and found the host name and the port number associated with the oracle database and succesfully made a connection. This is not a preferred way to connect to database as per the DBA however with Splunk's limitation, this is the only way to make a connection as this time.