Data queryable but schema & table not displaying in Data Model or Browse Data

Get Help
1

(New user; first post.)

We added a new schema to our Postgres database, and – after a database schema sync – I can now query the table with Write SQL. However, the schema and table don’t yet appear in the Data Model or under Browse Data. The sync ran >13 hours ago.

Is this delay expected? Do I need to take an additional step to get the schema & table to appear in the data model/browser?

{
  "browser-info": {
    "language": "en-US",
    "platform": "MacIntel",
    "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.183 Safari/537.36",
    "vendor": "Google Inc."
  },
  "system-info": {
    "file.encoding": "UTF-8",
    "java.runtime.name": "OpenJDK Runtime Environment",
    "java.runtime.version": "11.0.8+10",
    "java.vendor": "AdoptOpenJDK",
    "java.vendor.url": "https://adoptopenjdk.net/",
    "java.version": "11.0.8",
    "java.vm.name": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "11.0.8+10",
    "os.name": "Linux",
    "os.version": "4.14.192-147.314.amzn2.x86_64",
    "user.language": "en",
    "user.timezone": "GMT"
  },
  "metabase-info": {
    "databases": [
      "postgres",
      "redshift",
      "h2"
    ],
    "hosting-env": "elastic-beanstalk",
    "application-database": "postgres",
    "application-database-details": {
      "database": {
        "name": "PostgreSQL",
        "version": "12.3"
      },
      "jdbc-driver": {
        "name": "PostgreSQL JDBC Driver",
        "version": "42.2.8"
      }
    },
    "run-mode": "prod",
    "version": {
      "date": "2020-08-17",
      "tag": "v0.36.4",
      "branch": "release-0.36.x",
      "hash": "196c1f6"
    },
    "settings": {
      "report-timezone": null
    }
  }
}
2

Hi @ljhopkins2
Check the log for errors during the sync process - Admin > Troubleshooting > Logs.
Depending on your browser cache, you might have to refresh the page to see newly synced information.
There has been a lot of optimizations and fixes to the sync/scan process in the latest release 0.37.2

3

Thank you @flamber. My issue seems to have been related to browser caching and how I was logging in to Metabase. We have LDAP authentication set up, but I was using a password I’d set up using password recovery. Once I logged in using LDAP, the schema showed up as expected.

4

@ljhopkins2 Perfect. Please upvote this issue by clicking :+1: on the first post:
https://github.com/metabase/metabase/issues/5129

1 Like