Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Metadata access control
  3. Data profiling
  4. Data quality
  5. Data observability
  6. Data classification
  7. Stakeholder propagation in a catalog source
  8. Relationship discovery
  9. Glossary association
  10. Lineage discovery
  11. Autonomous Enrichment
  12. Lookup tables
  13. Connections
  14. Link catalog sources to generate lineage
  15. Asset customization
  16. Custom layouts
  17. Prefix values for asset reference IDs
  18. Workflows
  19. IDMC metadata
  20. Notifications
  21. Usage analytics
  22. Jobs
  23. Upgrade an organization to the latest version
  24. Informatica Resources

Administration

Administration

Types of connection scans

Types of connection scans

Depending on the accuracy and detail of the lineage required, you can choose to run connectionless or connection-aware scans.
Connectionless scan
Connectionless scans are performed without connection assignment to external source systems. They generate incomplete or inaccurate lineage based on predictions of what the repository might be, instead of actual details that a connection to the databases provides. You run connectionless scans to identify preliminary configuration issues.
Connection-aware scan
Connection-aware scans retrieve the exact database information from external source systems into the catalog. This external database information is then used to derive complete and accurate column-level lineage for external source systems that include stored procedures and select* SQL statements. For example, you can extract metadata with an Informatica Intelligent Cloud Services catalog source that connects to an external Oracle source system to generate complete lineage.
To run connection-aware scans, perform the following tasks:
  1. If you created catalog sources before the April 2023 release, purge the catalog sources.
  2. Create the catalog source, and run the catalog source job.
  3. Assign connections or database schemas to the respective catalog sources.
    For example, if you have connections to a source Oracle database and a target Teradata Data Warehouse, assign both source and target connections to the catalog sources that represent the databases.
    If you do not assign a connection to the catalog source, then the catalog source is a referenced catalog source.
  4. Run the catalog source job again.
After you perform connection assignment, when you run the scan again,
Metadata Command Center
passes the actual connection names and database information of the source and target objects that is used to display complete column-level lineage for the catalog source in
Data Governance and Catalog
.
If you assign multiple catalog sources that use the same connection or endpoint, then
Metadata Command Center
uses the connection-aware approach to fetch the database information of the assigned catalog sources. If you assign multiple catalog sources that use different connections or endpoints, then
Metadata Command Center
switches back to the connectionless approach.
If you find reference objects that are not assigned to endpoint objects after a connection-aware scan, choose Delete in the Metadata Change Option when you run the next full scan. This deletes objects that are not included in the scan. If the unassigned reference objects are not included in the scan, they get deleted. You can then run subsequent full or incremental scans without the Delete option.

0 COMMENTS

We’d like to hear from you!