New Oracle Views Not Detected with Date Filters in Metabase v0.56.2.2

Hello everyone,

I’m running Metabase v0.56.2.2 in Docker, using PostgreSQL as the application database.
I connected it to Oracle using the official driver, and initially, all tables and views were detected correctly.

Recently, we created two new views in Oracle. BPM_MAPA_EVOLUCAO_V and BPM_PROCED_V
The strange behavior is:

  • I can run manual SQL queries against these views in Metabase (data is returned correctly).

  • But they don’t appear as full data sources in the GUI, and I cannot add date filters (Metabase doesn’t recognize date columns as such).

The sync logs don’t show any errors — they just confirm SELECT privileges for all views (including the new ones).

Excerpt from the last sync log:

[f2aa138f-8f9a-4651-85af-57b71a066cd0] 2025-09-10T16:07:43-03:00 INFO metabase.driver.sql-jdbc.sync.describe-database "TASY"."BPM_ATEND_PA_V": SELECT privileges confirmed
[f2aa138f-8f9a-4651-85af-57b71a066cd0] 2025-09-10T16:07:43-03:00 INFO metabase.driver.sql-jdbc.sync.describe-database "TASY"."BPM_AUTORIZACOES_V": SELECT privileges confirmed
[f2aa138f-8f9a-4651-85af-57b71a066cd0] 2025-09-10T16:07:44-03:00 INFO metabase.driver.sql-jdbc.sync.describe-database "TASY"."BPM_CHEC_ADEP_V": SELECT privileges confirmed
[f2aa138f-8f9a-4651-85af-57b71a066cd0] 2025-09-10T16:07:44-03:00 INFO metabase.driver.sql-jdbc.sync.describe-database "TASY"."BPM_CICLO_RECEITA_V": SELECT privileges confirmed
[f2aa138f-8f9a-4651-85af-57b71a066cd0] 2025-09-10T16:07:44-03:00 INFO metabase.driver.sql-jdbc.sync.describe-database "TASY"."BPM_CONTA_PENDENTE_V": SELECT privileges confirmed
[f2aa138f-8f9a-4651-85af-57b71a066cd0] 2025-09-10T16:07:44-03:00 INFO metabase.driver.sql-jdbc.sync.describe-database "TASY"."BPM_EVOLUCAO_DESFECHO_V": SELECT privileges confirmed
[f2aa138f-8f9a-4651-85af-57b71a066cd0] 2025-09-10T16:07:44-03:00 INFO metabase.driver.sql-jdbc.sync.describe-database "TASY"."BPM_FECH_CONTA_V": SELECT privileges confirmed
[f2aa138f-8f9a-4651-85af-57b71a066cd0] 2025-09-10T16:07:44-03:00 INFO metabase.driver.sql-jdbc.sync.describe-database "TASY"."BPM_FECH_PROT_V": SELECT privileges confirmed
[f2aa138f-8f9a-4651-85af-57b71a066cd0] 2025-09-10T16:07:44-03:00 INFO metabase.driver.sql-jdbc.sync.describe-database "TASY"."BPM_FLUXO_RECEBIMENTO": SELECT privileges confirmed
[f2aa138f-8f9a-4651-85af-57b71a066cd0] 2025-09-10T16:07:44-03:00 INFO metabase.driver.sql-jdbc.sync.describe-database "TASY"."BPM_MAPA_EVOLUCAO_V": SELECT privileges confirmed
[f2aa138f-8f9a-4651-85af-57b71a066cd0] 2025-09-10T16:07:44-03:00 INFO metabase.driver.sql-jdbc.sync.describe-database "TASY"."BPM_PAC_ESPERA_PA_V": SELECT privileges confirmed
[f2aa138f-8f9a-4651-85af-57b71a066cd0] 2025-09-10T16:07:44-03:00 INFO metabase.driver.sql-jdbc.sync.describe-database "TASY"."BPM_PRESCRICAO_V": SELECT privileges confirmed
[f2aa138f-8f9a-4651-85af-57b71a066cd0] 2025-09-10T16:07:44-03:00 INFO metabase.driver.sql-jdbc.sync.describe-database "TASY"."BPM_PROCED_V": SELECT privileges confirmed
[f2aa138f-8f9a-4651-85af-57b71a066cd0] 2025-09-10T16:07:44-03:00 INFO metabase.driver.sql-jdbc.sync.describe-database "TASY"."BPM_PROTOC_XML_V": SELECT privileges confirmed
[f2aa138f-8f9a-4651-85af-57b71a066cd0] 2025-09-10T16:07:44-03:00 INFO metabase.driver.sql-jdbc.sync.describe-database "TASY"."BPM_RELAC_MEDICO": SELECT privileges confirmed

Additional context:

  • The Oracle database has more than 25k tables/views (I’m not sure if this amount might impact sync or column type detection).

  • Database connection is stable, and connection pools are not saturated.

Environment details:

  • Metabase: v0.56.2.2 (9baacec, 2025-08-13)

  • Application database: PostgreSQL 13.21 (running on the same host as Metabase)

  • Oracle connection via official driver

  • Timezone: America/Sao_Paulo

  • JVM: OpenJDK 21.0.8

Questions for the community:

  1. Is there an internal cache or metadata that needs to be cleared to force Metabase to detect new views/columns correctly?

  2. Are there any best practices for very large Oracle databases (with thousands of objects)?

  3. Is there a way to sync only a specific view without reprocessing the entire database schema?

{ "browser-info": { "language": "pt-BR", "platform": "Win32", "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36", "vendor": "Google Inc." }, "metabase-info": { "databases": [ "oracle", "h2" ], "run-mode": "prod", "plan-alias": "", "version": { "date": "2025-08-13", "tag": "v0.56.2.2", "hash": "9baacec" }, "settings": { "report-timezone": "America/Sao_Paulo" }, "hosting-env": "unknown", "application-database": "postgres", "application-database-details": { "database": { "name": "PostgreSQL", "version": "13.21 (Debian 13.21-1.pgdg130+1)" }, "jdbc-driver": { "name": "PostgreSQL JDBC Driver", "version": "42.7.7" } } }, "system-info": { "file.encoding": "UTF-8", "java.runtime.name": "OpenJDK Runtime Environment", "java.runtime.version": "21.0.8+9-LTS", "java.vendor": "Eclipse Adoptium", "java.vendor.url": "https://adoptium.net/", "java.version": "21.0.8", "java.vm.name": "OpenJDK 64-Bit Server VM", "java.vm.version": "21.0.8+9-LTS", "os.name": "Linux", "os.version": "6.8.0-60-generic", "user.language": "en", "user.timezone": "America/Sao_Paulo" } }

{
"connection-pools": {
"db-2-oracle-dbhaustaprd": {
"numConnections": 8,
"numIdleConnections": 8,
"numBusyConnections": 0,
"minPoolSize": 1,
"maxPoolSize": 15,
"numThreadsAwaitingCheckoutDefaultUser": 0
},
"metabase-postgres-app-db": {
"numConnections": 15,
"numIdleConnections": 14,
"numBusyConnections": 1,
"minPoolSize": 1,
"maxPoolSize": 15,
"numThreadsAwaitingCheckoutDefaultUser": 0
}
}
}

Thank you guys

When adding new objects to the database I go into Admin → Database and run a manual sync. Make sure the Metabase user has access to the new objects. (This is the part I usually forget.)

This bugfix was added to 56.5 to address databases with large numbers of objects. It might be helpful for your case. It’s possible the sync is running but is taking a long time to enumerate things.

Thanks for the tip! :folded_hands:

Yesterday I double-checked the permissions as you suggested — I can even run a SELECT on the view without any issues (as shown in the screenshot) — but it still doesn’t show up in Metabase search.

Regarding updating Metabase, I’ll look into how to do that and evaluate how complex or risky it might be, since I don’t have much experience with Docker yet.

Here’s what I did today:

  • Created a table and a view in my own schema and forced a manual sync. Now I’ll wait to see if these new objects appear, since in this case there shouldn’t be any permission issues.

  • Enabled the "Rerun queries for simple explorations" and "Scanning for Filter Values" options to help with data updates.