Itgenpsr003 Linking Supabase

Questions (nl)
, ,
1

When connecting Supabase on aws-0-eu-central-1.pooler.supabase.com for AI with Invantive Cloud for replicating large numbers of financial administrations to PostgreSQL 17.6, I get the following error message:

itgenpsr003
Could not load all metadata.
One or more errors occurred.
Primary keys were found for 60 tables, but the corresponding tables were not found.
The number of 64 primary keys found must be less than the total of 2 tables and 4 views.
Check if the user can actually query tables or views in the database ‘’ .

And error code itgenpsr067.

The following tables were observed:

  • supabase_migrations.schema_migrations
  • auth.saml_relay_states
  • auth.flow_state
  • auth.saml_providers
  • auth.instances
  • auth.schema_migrations
  • auth.refresh_tokens
  • auth.users
  • auth.audit_log_entries
  • auth.sso_domains
  • auth.mfa_amr_claims
  • auth.identities
  • auth.one_time_tokens
  • auth.sessions
  • auth.mfa_challenges
  • auth.sso_providers
  • auth.mfa_factors
  • auth.oauth_consents
  • auth.oauth_authorizations
  • auth.oauth_client_states
  • auth.oauth_clients
  • auth.custom_oauth_providers
  • auth.webauthn_credentials…c.offices
  • 19x public.NAAM with its own tables
  • realtime.schema_migrations
  • realtime.subscription
2

More background on the itgenpsr003 error message can be read in:

In this case, it is not possible to read the tables using, for example, “pgAdmin 4”. For instance, a query on auth.audit_log_entries results in an error message:

ERROR:  permission denied for schema auth
LINE 1: SELECT * FROM auth.audit_log_entries
                      ^ 

SQL state: 42501
Character: 15

It is possible, however, to create a table:

create table tst(a numeric)

In Supabase, these are apparently the maximum permissions. It has previously become clear that many users do not have a PostgreSQL DBA available to configure the permissions.

In the next release of Invantive UniversalSQL, a driver attribute fail-on-missing-tables will be available for PostgreSQL, which will be disabled by default, while the current behaviour is equal to enabling this driver attribute.

3

This question was automatically closed after 1 week of inactivity. The last given answer is marked as the solution.

Please post a new question in a separate thread if the issue occurs again. In the new question, please include a link to this thread by pasting its URL into the text.