*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
-
Created by
Sharon Helen Markus, last updated by Joanne Elisa Leary on Apr 17, 2025
3 minute read
The errors we have been experiencing for the last few days have been intermittent and unpredictable. It is also impacting connections from multiple applications used to connect to the Metadb reporting database.
| User | Date | Time | Tool | Query or Dashboard | problem | resolution? |
|---|---|---|---|---|---|---|
| Sharon Markus | 4-15-25 | 3pm | DBeaver EE | multiple queries | Connection Timed Out Errors | deleted and rebuilt connection setting for Metadb |
| Sharon Markus | 4-16-25 | 4am | Tableau | FBO dashboards | Data Extract failed - unable to connect | ran extract manually at 7am |
| Jean Pajerek | 4-16-25 | 8am | DBeaver EE | Connection Timed Out Errors | ||
| Natalya Pikulik | 4-16-25 | 8am | Tableau | Unable to Connect within Tableau | ran manually around 9:30am and it updated successfully | |
| Natalya Pikulik | early April | DBeaver EE | Idle Connection Messages | |||
| Joanne Leary | April 11 | MCR204 Tableau Dashboard | data not updating | |||
| Joanne Leary | months | metadb log shows warnings about 2 IP addresses | ||||
| Joanne Leary | 4-16-25 | 9am | CloudBeaver AWS | Connection Timed Out Errors | ||
| Annie Keville | 4-16-25 | 10am | CloudBeaver AWS | MCR126 | Connection Timed Out Errors | Tried 2 times to run query and got error. On 3rd try, was able to click Restore (to restore the database connection) and run the query successfully |
| Joanne Leary | 4-16-25 | 1:39pm 1:54pm | DBeaver EE and CloudBeaver AWS DBeaver EE | EE: query to extract holdings notes (very short but uses a cross join). Query is normally very fast running CloudBeaver: same short query as above; no connection errors, but query kept grinding. Update: query finished in 6.6 minutes Update for EE: 1:54pm - was able to connect and query ran in .06 sec | EE: Connection time out errors CloudBeaver: no connection errors but query seemed to be stuck and never finished. Update: query finished in 6.6 minutes. | EE: Tried with metadb_user connection and with jl41 connection; neither worked CloudBeaver: took 6.6 mins |
| Sharon Markus | 4-16-25 | 2;21pm | DBeaver EE | MCR204 | Can't open editor connection Reason: | none |
| Natalya Pikulik | 3:30pm | Dbeaver EE, Cloudbeaver Tableau is OK | 100e | Error connecting to database: Connection attempt timed out. Error connecting to database: Connection attempt timed out. CONNECTED | ||
| Joanne Leary | 4-16-26 | 4:30pm | CloudBeaver | Short query to get holdings notes from holdings_record table | Firefox browser: kept grinding away; not done yet Chrome: ran instantly Chrome (second try a few minutes later): bogged down; however, I was trying to run a different much more complicated query at the same time. That query was probably causing the problem (had many subqueries and data array extracts). Neither query could execute. | |
| Linda Miller | 4-16-25 | 4:40 | Cloudbeaver | MCR134 someone saved there | Got this error at restore connection: Server Error. Error connecting to database: Connection attempt timed out. Then click on again, and it was fine. took about 30 minutes. Things seem to be working in Enterprise. | |
| Natalya Pikulik | 4/17/25 | 8am | DBeaver EE and Tableau CloudBeaver | Connection attempt timed out. Connected | ||
| Joanne Leary | 4-17-25 | all day | DBeaver EE CloudBeaver | I literally can't work under these conditions - nothing is consistent or reliable, in either platform | The Vet inventory query that doesn't use derived tables does not run, but I can't figure out why. The constant connection errors make it impossible to diagnose the problem. I have created a version that uses two derived tables (holdings_notes and item_notes) and that runs in about 1 minute, when it gets a connection. Other queries either run or not - no consistency. Some have array extracts and some don't; some are long and some are short. There is no way to figure out if there is something in the queries that is conflicting with the system or if there is an external problem. |