Getting Data In

DB Connect: Why am I getting an error: "column does not exist" when trying to search query of new added field?

saeki_takuya_mk
Engager

Hi,

I had connected to PostgreSQL view using DB Connect.
After I add new fields to the view, I tried to select the new fields on 'Database Query' tab but failed with follow error : "column does not exist".

It seems DB Connect doesn't recognize to be changed schema.
But I can get complete schema data on 'Database Info'.

How can I use the new field on query?

I did restart Splunk on browser , but couldn't resolve it.
Configuration > Server Control > restart Splunk

Thanks

Tags (1)
0 Karma
1 Solution

saeki_takuya_mk
Engager

The problem has been resolved.

Solution is that specify view-name with double quote ' " '.

like this..

| dbquery "myDB" "SELECT * FROM \"the_view_name\"" limit=1000

View solution in original post

0 Karma

saeki_takuya_mk
Engager

The problem has been resolved.

Solution is that specify view-name with double quote ' " '.

like this..

| dbquery "myDB" "SELECT * FROM \"the_view_name\"" limit=1000
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!

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 ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...