I'm experiencing an issue with the Splunk DB Connect app under Data Inputs > Choose Table where the Schema dropdown fails to populate. The Connection status shows as healthy and connected.
When I use Preview Data and run a SQL query like:
SELECT * FROM ALL_USERS;
It successfully returns data, indicating that the schema can be queried manually.
To further test this, I created a simple Java collector that fetches schemas using the same JDBC driver:
java -cp .:tibero6-jdbc-14.jar TiberoGetSchemas
This custom collector successfully retrieves the schema list, confirming that the user has access. The user account has been granted the necessary privileges, including access to ALL_USERS, dictionary views, and the SELECT_CATALOG_ROLE, in collaboration with our Tibero DBA.
However, in Splunk DB Connect, the Schema dropdown remains empty and unselectable.
Has anyone encountered a similar issue with Tibero and Splunk DB Connect? Any suggestions would be greatly appreciated.
- db : Tibero 6
- Splunk db connect version : 3.2.0
As per harsmarvania57:
In DB, there are schemas available and each schema have different table. So in DB you need to provide schema access & table access to user from which splunk is trying to fetch data.
Thanks for your quickly answer!
I've already seen that case and DBA gave me the right permissions but I still can't get the schema.
Thanks for your support
First of all, Share error message on INFO mode,
I am going to change mode from INFO to DEBUG, then find and share error message
file path : $SPLUNK_HOME$/var/.../splunk_app_db_connect_server.conf
00 [dw-188176 - GET /api/connections/new_mdm/metadata/schemas?catalog=] ERROR
io.dropwizard.jersey.errors.LoggingExceptionMapper - Error handling a request 0455f2250e391159
java.lang.AbstractMethodError: Method
com/tmax/tibero/jdbc/TbDatabaseMetaData.getSchemas(Ljava/lang/String;Ljava/lang/String;)Ljava/sql/ResultSet; is abstract
.
@syleeI noticed that the screenshot contains a visible username and password. I highly recommend avoiding sharing sensitive information in public or community channels. For further assistance, please raise a support ticket with Splunk so they can investigate this securely.
Thanks for your help
I tested if JDBC has problem or not but,
This custom collector successfully retrieves the schema list using same JDBC
Is there a problem with the jdbc driver?
@sylee It seems like issue is with JDBC drivers.