Color scheme: Riviera
You are here: start » en » Documentation » Data integration and data access » WKL Database Gateway » Troubleshooting » A new database object can't be reached

A new database object can't be reached

A table, view, or column just created in the database is missing from the schema document; a request for it responds 404, and in Access it's missing when linking.

Environment

Every version of the service; every interface (OData, native API).

Cause

A database's resource catalog is cached (Gateway:MetadataCacheSeconds, default 300 seconds). A new object becomes reachable within this period, not immediately. A failure deliberately does not trigger a reload; otherwise a caller guessing names would force a metadata query per request. Once the period has expired, the next request responds with the previous state, and the catalog is refreshed in the background (at most one load per alias; only the very first load waits). If the refresh fails, the previous state continues to apply, and the log warns.

Resolution

  1. Wait for the period to pass, or have the catalog discarded immediately: in the administration application with Katalog neu laden (Reload catalog) or through POST /admin/v1/reload-catalog.
  2. Then relink the table in Access, or refresh the link (External Data > Linked Table Manager).

Verification

The schema document (…/$metadata) names the object; a request for it responds 200.

en/wiki/data-conectivity/database-gateway/troubleshooting/new-object-not-reachable.txt · Last modified: by Wolfgang van der Stille