Skip to main content
Administrator Guide
Last Updated: 2026-08-07
Troubleshooting: Zero-Copy Data In

Troubleshooting: Zero-Copy Data In

Unable to Create Connection

Customers cannot create a new connection from the Prism Data Catalog.
Missing required Prism security permissions.
Verify and assign the required security domain.
Ensure the user has
Prism: Manage Connection
domain in the Prism Analytics functional area.
After the domain is assigned, log out and log back in before retrying the connection creation.

Test Connection Fails

Connection test fails when validating credentials during setup.
Incorrect OAuth credentials or misconfigured token endpoint.
Validate credentials and authentication configuration.
Confirm the Client ID, Principal, and Token Endpoint values match those provided by the external platform’s documentation.

Connection Created but No External Catalog Can Be Created

Users can create a connection but cannot create an external catalog.
Missing External Catalog Create permission.
Assign the required External Catalog security domain.
Verify the user has
Prism: External Catalog Create
domain.
Once granted, retry creating the external catalog from the Data Catalog UI.

External Catalog Creation Fails with Validation Error

Catalog creation fails with a generic validation or save error.
Invalid or unsupported namespace format.
Validate the namespace path.
Confirm the namespace exactly matches the external Iceberg catalog namespace.

External Catalog Created but Schema Sync Never Starts

Catalog is created successfully but schema sync does not initiate.
Connection misconfiguration or insufficient catalog-level permissions in the external system.
Validate external catalog access.
Ensure the identity used by the connection has sufficient permissions to list schemas and tables in the external catalog.
Once access is corrected, trigger a catalog re-sync to refresh the metadata.

External Catalog Created but Tables Are Not Visible

External catalog is created successfully, but no tables appear after schema sync.
Incorrect namespace or schema sync did not complete successfully.
Validate namespace and re-sync the catalog.
Double-check that the namespace matches the exact Iceberg namespace. If correct, manually trigger a catalog sync using the External Catalog Manage actions.

Schema Sync Fails or Times Out

Schema sync does not complete or fails intermittently.
Temporary connectivity issues or large schema size during EA.
Retry sync and limit initial scope.
Retry the schema sync after a short wait. For large catalogs, consider starting with a smaller namespace during EA to validate end-to-end functionality before expanding scope.

External Tables Visible but Cannot Be Enabled for Analysis

Tables appear in the External Tables list but the
Enable for analysis
option is unavailable.
Missing External Tables Manage permission.
Assign the External Tables Manage domain.
Ensure the user has
Prism: External Tables Manage
domain. This permission is required to edit table metadata and enable tables for analysis.

Join Fails When Creating a Derived Dataset

Join between external Iceberg tables and Workday data fails.
Data type mismatch or incompatible join keys.
Align join key data types and validate data.
Verify the join columns have compatible data types (for example, string vs numeric).
Use the External Table preview to inspect sample data and confirm key consistency before joining.

Reports Fail After Publishing Derived Dataset

Reports fail to run or return errors after dataset publication.
Dataset not fully published or upstream changes in external schema.
Republish dataset and validate schema.
Confirm the derived dataset is successfully published. If the external schema changed, re-sync the external catalog and republish the dataset before running reports again.