Issues Querying the CONFIGURATION table for 'channelMetdata' in my Derby Database

[Hammer2233]

Good afternoon,

Background:
This is my first post in the forum. I am working to attempt to export the settings held in the CONFIGURATION channel, mainly settings like "pruning information".

I am using SQL to query the derby database. I am using DBeaver 24.2.2 (I have used other database visualizers, but this is my current one). I am able to query other critical tables such as the "CHANNEL" and "CHANNEL_GROUP" tables
Mirth version 4.4.2

Current Issue:
I always get a conglomerate error on the "CONFIGURATION" table.
Example query: SELECT * FROM app.CONFIGURATION
Returns: SQL Error [30000] [XSAI2]: The conglomerate (20,768) requested does not exist.

Troubleshooting steps:
While most searches and walkthroughs with various AIs point towards missing tables or database corruptions, I have taken the following steps to dispel this:

1. created new Mirth Databases from scratch
2. Imported various Mirth databases with pruning settings and encounter the same error
3. Had other coworkers test querying their Mirth Databases and they encounter the same error

Questions:
-Is there a "correct" way to query the configuration table via SQL?
-From my research on the Mirth forums, the "CONFIGURATION" table should contain the pruning/other information. Is that correct?

I appreciate any help I can get. Thank you!

[jonbartels]

From my research on the Mirth forums, the "CONFIGURATION" table should contain the pruning/other information. Is that correct?

Absolutely yes. You can see how the config table is queried to get pruning information here (though for postgres): https://gist.github.com/MichaelLeeHobbs/67980d165fc68880eb2ab283c673244b

Is there a "correct" way to query the configuration table via SQL?

The SQL you showed is correct, SELECT * FROM configuration. Can you share a link to the Derby documentation about the XSAI2 error that you get from Derby?

[Hammer2233]

Good morning, Jon,

Apologies for the delay. Thank you for the other github link for review. I was able to find the error referenced on the Apache Derby reference manual:
https://db.apache.org/derby/docs/10.16/ref/rrefexcept71493.html

Unfortunately, it doesn't have any more information than pictured above.
I believe I was able to determine my issue and have since been able to Query the CONFIGURATION table in the database. I was not able to determine what I did different, other than I used a JAVA application I'm developing to run the "Select * from CONFIGURATION" rather than a DB visualizer tool.

I will share my findings and progress on the application on my github page. Thank you for helping point me in a better direction.

Edit: I believe the issue I was encountering in the DB Visualizer vs my Mirth application, was that the Mirth service was running when the DB Visualizer was open. This was causing the conglomerate error