Skip to main content
Community Hub

Crawl and lineage issues

TL;DR

Resolve upload failures, empty extractions, and missing lineage for the Informatica PowerCenter connector

Your AI can read this via Docs MCPInstall MCP →Connect

Use these steps to resolve common upload, extraction, and lineage issues when running the Informatica PowerCenter connector workflow in Atlan.

Archive rejected during upload​

Error

Encrypted archive not supported or Invalid archive entry

Cause​

The connector rejects a .zip archive when it's password-protected or encrypted, or when it contains symbolic links or entries with absolute paths. These are blocked for security reasons.

Solution​

  1. Re-create the archive as a standard, unencrypted .zip.
  2. Make sure the archive contains only your exported files, with no symbolic links or absolute paths.
  3. Upload the new archive in the Repository XML export field and run the workflow again.

Repository export fails with permission error​

Error

Permission denied or Access denied while exporting from PowerCenter

Cause​

The account used to export repository objects lacks the required repository permissions.

Solution​

  1. Confirm the account has read permission on the objects you're exporting.
  2. Confirm the account has the Access Repository Manager privilege.
  3. Re-run the export, then repackage and upload the archive.

Repository export is invalid or fails to parse​

Error

Invalid XML or parse error while processing the repository export

Cause​

Informatica has documented issues where repository exports contain characters that break XML parsing. For example, reserved characters such as & in folder or object descriptions, or non-Unicode characters in transformation names.

Solution​

  1. Correct the problematic characters in PowerCenter and re-export the affected objects. This is the recommended fix.
  2. Alternatively, manually edit the exported XML to escape or remove the invalid characters. For example, replace a bare & with &.
  3. Repackage the corrected exports into the .zip and run the workflow again.

You don't need to add a DTD file to your upload. Atlan supplies the required powrmart.dtd automatically during extraction.

No lineage extracted​

Error

No lineage found or the workflow fails after extraction

Cause​

The workflow fails rather than publishing an empty result when the repository exports contain no resolvable data flow. This usually means the XML files are missing folder or repository declarations, or the folders don't contain mappings with resolvable sources and targets.

Solution​

  1. Confirm each XML file contains its <REPOSITORY NAME> and <FOLDER NAME> declarations.
  2. Confirm all files belong to the same repository and that no workflow folder appears in more than one file. Shared dependency folders may repeat across files.
  3. Re-export any folders that were exported incompletely, then repackage and re-upload the archive, or replace the staged copy in your object store.

Extraction fails with no workflows found​

Error

The workflow fails during staging with The repository export contains no workflow definitions in any folder, or fails early during extraction with no workflows in this snapshot or Not Generating Snapshot in the logs

Cause​

No folder in the upload contains workflow definitions, so the run either fails at staging or can't build a snapshot during extraction. This is almost always a packaging problem:

  • None of the uploaded folders contain workflows—for example, the export holds only shared or reusable objects. Folders without workflows are used for shortcut resolution but aren't crawled on their own.
  • The .zip nests archives more than one level deep. A .zip inside the uploaded archive is extracted, but anything nested deeper is skipped, so staging rejects the upload with the repository-XML zip must contain at least one .xml export.

Solution​

  1. Confirm at least one folder in the upload contains workflows. Multi-folder XML files are supported—the connector processes every folder that contains workflows and uses the shared folders for shortcut resolution.
  2. Export shared and reusable objects as dependencies of a workflow folder (using the dependent-object and shortcut export options) instead of uploading a shared folder on its own.
  3. Rebuild the archive so it contains the .xml files directly, with no nested .zip.
  4. Repackage and re-upload, then run the workflow again.

Assets appear as partial or unresolved​

Error

Lineage resolves to placeholder assets instead of your real tables

Cause​

Atlan connects PowerCenter lineage to source and target assets that already exist in the catalog. When a system hasn't been crawled, Atlan creates a partial placeholder that resolves once that system is cataloged.

Solution​

  1. Crawl and publish the source and target systems referenced by your PowerCenter mappings.
  2. Re-run the PowerCenter workflow, or wait for the placeholders to resolve automatically after the source systems are cataloged.

Missing lineage for ODBC or flat-file sources​

Error

Sources using ODBC or non-relational connections don't appear in lineage

Cause​

Repository exports don't always declare a database vendor for ODBC or non-relational (flat file, XML, VSAM) connections, so Atlan can't always determine which system the data flows to.

Solution​

  1. Confirm the affected sources use ODBC or a non-relational connection type. These may not resolve to a specific database in the current release.
  2. Contact your Atlan representative to configure a vendor mapping for the affected connection, applied through the Operator overrides field of the workflow.

See also​

Need help​

If you need assistance after trying these steps, contact Atlan support by submitting a request.