Skip to main content
Last updated on

SYNCED_TABLE_USER_ERROR error condition

SQLSTATE: 42000

Synced table pipeline user error.

CHANGED_PRIMARY_KEY​

The primary key columns specified for the synced table <destTableUcName> have been changed.

Specified primary key columns: (<primaryKeyColumns>). Current primary key columns: (<existingPrimaryKeyColumns>).

Changing the primary key columns of a synced table after it has been created is not supported.

To resolve this issue, either modify the synced table back to the original primary key columns, or create a new synced table and drop the existing one.

CHARACTER_NOT_IN_REPERTOIRE​

Instance: <instance>. Found invalid byte sequence in the source Delta table.

Detail: <detail>

This usually indicates the source Delta table contains characters that are not

compatible with the target database's encoding. One workaround is to convert the

source table to use BINARY TYPE, and then create a new synced table.

COLUMN_TYPE_CHANGE_NOT_SUPPORTED​

Instance: <instance>. Changing the column type is currently not supported.

Source Delta table: <srcTableName>. Destination synced table: <destTableName>.

Column: <columnName>. Existing type: <existingType>. New type: <newType>.

To resolve this issue, consider one of the following options:

  1. Perform a full refresh of the existing synced table.

  2. Create a new synced table (which will pick up the new type)

CONNECTION_ERROR​

Instance: <instance>. Connection error. Detail: <detail>.

To resolve this issue, please ensure the database instance is running, not paused or stopped.

Restart the pipeline to retry.

DATABASE_DOES_NOT_EXIST​

The destination database <databaseName> does not exist in lakebase instance <instance>. Please verify if the destination database exists.

DELTA_TRUNCATED_TRANSACTION_LOG​

Detail: <detail>.

This indicates the delta table's transaction log has been truncated due to manual deletion or the log retention policy.

To resolve this issue, perform a full refresh of the synced table.

DEPENDENT_OBJECTS_STILL_EXIST​

Instance: <instance>. Unable to drop a column because an existing

PostgreSQL object is still referring to the column. Detail: <detail>.

To resolve this issue, consider one of the following options:

  1. Add the missing column(s) back to the source table with the same data type(s) as before.

  2. Drop the dependent objects in PostgreSQL.

FOREIGN_KEY_CONSTRAINT_VIOLATION​

Instance: <instance>. Foreign key constraint violation when syncing from source table:

<srcTableName>. Detail: <detail>

Creating foreign key constraints referencing sync tables is not supported. Please

drop the foreign key constraint and retry the sync.

LOCK_TIMEOUT​

Instance: <instance>. Database: <databaseName>. The synced table pipeline could not acquire a lock within the configured timeout (<timeoutSeconds> seconds).

Detected <numBlockingTransactions> transaction(s) holding locks on the target table (max lock hold duration: <lockDurationSeconds> seconds).

User transactions are holding locks that are blocking the synced table pipeline from updating the target table.

For more information about the transactions involved in the error, check the Spark driver logs (search for '[LOCK TIMEOUT DIAGNOSTICS]').

To resolve this issue, find the connections with long-running transactions in the postgres instance using pg_stat_activity, and close those transactions (can also use pg_terminate_backend to terminate the connection if the connection isn't needed anymore).

To prevent this issue from happening in the future, consider the following options:

  1. Make sure that your application either commits or rolls back the transaction.

  2. Avoid long running transactions. Set auto_commit to on if the work in the application doesn't need to happen in a transaction.

  3. Set idle_in_transaction_session_timeout on the database to automatically terminate idle transactions.

Example: ALTER DATABASE <databaseName> SET idle_in_transaction_session_timeout = '5min';

MIS_CONFIGURED_PRIMARY_KEY​

The provided primary keys for the source Delta table: <srcTableName> are not available in the source table.

Primary keys: <primaryKeys>. Available columns: <availableColumns>. Missing primary keys: <missingPkColumns>.

To resolve this issue, consider one of the following options:

  1. Add the missing columns to the source table.

  2. Create a new synced table with the correct primary key configuration.

PERMISSION_DENIED​

Detail: <detail>.

Please verify if you have sufficient permissions.

PRIMARY_KEY_CONSTRAINT_VIOLATION​

Instance: <instance>. Duplicate rows detected based on primary key. Detail: <detail>

This likely indicates a misconfiguration of primary key columns.

Please verify that you are using the correct set of primary keys

from the source Delta table: <srcTableName>.

To resolve this issue, create a new synced table with the correct

primary key configuration.

REFRESH_WITH_FOREIGN_KEY​

Instance: <instance>. Failed to refresh synced table <destTableName> because table

<childTableName> has a foreign key constraint referencing the synced table.

Refreshing the synced table is not supported when there are foreign key constraints

referencing it. Please drop the foreign key constraint and retry the refresh.

SCHEMA_DOES_NOT_EXIST​

Detail: <detail>.

Please verify if the schema exists in Unity Catalog.

SOURCE_READ_ERROR​

Failed to read from the source table <tableName>. Please verify if the source table can be read successfully through a SELECT query.

Detail: <detail>

SPARK_JOB_CANCELLED​

Spark job is cancelled.

Detail: <detail>

TABLE_DOES_NOT_EXIST​

Detail: <detail>.

Please verify if the synced table exists in Unity Catalog.

TARGET_DATABASE_FULL​

The target database <databaseName> space is full. Not able to continue to ingest.

TOO_MANY_CONNECTIONS​

Too many open connections to the database instance: <instance>

Detail: <detail>.

Each table synchronization can use up to 16 connections to the database instance, which count toward the instance's connection limit.

To resolve this issue, try following options:

  1. Reduce the number of concurrent pipelines writing to the same database instance.

E.g., stagger the pipeline schedules.

  1. Reduce the number of concurrent connections from other workloads connecting to the same database instance.

UNTRANSLATABLE_CHARACTER​

Instance: <instance>. Found untranslatable character in the source Delta table.

Detail: <detail>

This usually indicates the source Delta table contains characters that are not

compatible with the target database's encoding. One workaround is to convert the

source table to use BINARY TYPE, and then create a new synced table.