Splunk Enterprise

db query not working

pratapa
Explorer

Following db query not working.

| dbquery wmsewprd select REC_TYPE, CODE_TYPE, CODE_DESC, SHORT_DESC, USER_ID, To_Char(mod_date_time,'dd/mm/yyyy hh:mi:ss AM') AS MOD_DATE_TIME from SYS_CODE_TYPE where rec_type = 'C' and code_type = 'AWO'
and (sysdate - mod_date_time)*24*60 < 60"

 

Getting following error.

command="dbquery", A database error occurred: ORA-00942: table or view does not exist

 

But the table SYS_CODE_TYPE does exist.

 

When we run the following query it is returning events.

dbquery wmsewprd "select REC_TYPE, CODE_TYPE, CODE_DESC, SHORT_DESC, USER_ID from SYS_CODE_TYPE"

What could be the problem

0 Karma

richgalloway
SplunkTrust
SplunkTrust
Have you checked the logs to see if more detail is provided? Look at splunk_app_db_connect_dbx_log.* and splunk_app_db_connect_server.log.
Also, see what is reported in Oracle's logs.
---
If this reply helps you, Karma would be appreciated.
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...