This use to work on dbx 1.x and not db connect version 2.0 . The following error occurs when user try to connect to oracle RAC using service name instead of SID
2015-05-01 12:33:27 ERROR Connector:310 - Validating connection with URL [jdbc:oracle:thin:@xymi4600xy.wsymmxx.com:1521:XYZB] failed, please verify that the connection is configured correctly.:java.sql.SQLException:Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
2015-05-01 12:33:27 DEBUG ServiceResponder:423 - Service Responder Responds Error:
1) Copy <SPLUNKHOME>/etc/apps/ splunk_app_db_connect/default/db_connection_types.conf to Copy <SPLUNKHOME>/etc/apps/ splunk_app_db_connect/local/.
2) Edit <SPLUNKHOME>/etc/apps/ splunk_app_db_connect/local/db_connection_types.conf and change the jdbcUrlFormat in the [oracle] stanza, as shown below.
3) Restart Splunk.
[oracle]
displayName = Oracle
serviceClass = com.splunk.dbx2.OracleJDBC
jdbcUrlFormat = jdbc:oracle:thin:@//<host>:<port>/<database>
jdbcDriverClass = oracle.jdbc.OracleDriver
database = XE
testQuery = SELECT 1 FROM DUAL
port = 1521
1) Copy <SPLUNKHOME>/etc/apps/ splunk_app_db_connect/default/db_connection_types.conf to Copy <SPLUNKHOME>/etc/apps/ splunk_app_db_connect/local/.
2) Edit <SPLUNKHOME>/etc/apps/ splunk_app_db_connect/local/db_connection_types.conf and change the jdbcUrlFormat in the [oracle] stanza, as shown below.
3) Restart Splunk.
[oracle]
displayName = Oracle
serviceClass = com.splunk.dbx2.OracleJDBC
jdbcUrlFormat = jdbc:oracle:thin:@//<host>:<port>/<database>
jdbcDriverClass = oracle.jdbc.OracleDriver
database = XE
testQuery = SELECT 1 FROM DUAL
port = 1521
Reviving old thread, above configuration intermittently give me Internal Server Error, the same as when I swap the display name to "Oracle Service". Anyone can advise this is because the target ODB is not configured properly? If so, can suggest what to do on target ODB?
Thanks!
In DBX2 - sometime this could be a temp issue. So, please try again after sometime - http://docs.splunk.com/Documentation/DBX/2.3.0/DeployDBX/Troubleshooting