Amazon RDS for Oracle lineage configuration

To import lineage metadata from Amazon RDS for Oracle, create a connection, data source definition and metadata import job.

Amazon RDS for Oracle is an Oracle relational database that runs on the Amazon Relational Database Service (RDS).

Supported versions

  • Amazon RDS for Oracle 19c, 21c

Processed metadata

The following Amazon RDS for Oracle metadata is processed and displayed on lineage:

  • PL/SQL scripts
  • Database dictionaries
  • Stored procedures
  • Functions
  • Packages
  • Triggers
  • Objects
  • Views
  • DB links
  • Exadata links

Limitations

The following limitations apply:

  • SQL*Plus scripts are not processed.
  • SQL*Loader scripts are not processed.
  • Highly dynamic SQL code that is executed by using the EXECUTE IMMEDIATE statement is not processed.
  • Synonyms are included in the data lineage visualization only if they are referenced in the SQL queries, procedures, or functions. If they are not referenced, they are not included in the visualization or the object list.

Prerequisite configuration

Before you import lineage metadata, ensure that the following prerequisites are met:

  • You must have the CONNECT and SELECT_CATALOG_ROLE privileges. An Oracle database administrator can grant these privileges.
  • A firewall access must be opened between Oracle and IBM instances. An Oracle database administrator or the network team can open the firewall.
  • If you connect to Oracle 21.1 or earlier, and you use a connection in the read-only mode, install the following patch on the Oracle instance: 30858671 - 18C DBMS_METADATA.GET_DDL FAILED WITH ORA-16000 IN READ ONLY MODE.

Creating a metadata import asset

Data source connection

To connect to the data source from which you want to import lineage metadata, you need to select a data source definition and a connection. You can create them before you start creating the metadata import, or you can create them when you create and configure the metadata import asset.

Data source definition

Select Oracle as the data source type. The Database (SID) or Service name field is required.

Connection

For connection details, see Amazon RDS for Oracle connection.

Include and exclude lists

You can include or exclude assets up to the schema level. Provide databases and schemas in the format database/schema. Each part is evaluated as a regular expression. Assets which are added later in the data source will also be included or excluded if they match the conditions specified in the lists. Example values:

  • mySchema: mySchema schema
  • mySchema[1-5]: any schema with a name that starts with mySchema and ends with a digit between 1 and 5.

External inputs

If you use external Oracle PL/SQL scripts, you can add them in a .zip file as an external input. You can organize the structure of a .zip file as subfolders that represent schemas. After the scripts are scanned, they are added under respective schemas in the selected catalog or project. The .zip file can have the following structure:

<schema_name>
   <script_name.sql>
<script_name.sql>
replace.csv

The replace.csv file contains placeholder replacements for the scripts that are added in the .zip file. For more information about the format, see Placeholder replacements.

Advanced import options

Extract extended attributes
You can extract extended attributes like primary key, unique and referential integrity constraints of columns. By default these attributes are not extracted.
Extract invalid objects
Include invalid objects in extraction.
Extraction mode
You can decide which extraction mode to run for the imported metadata. You have the following options:
  • Prefetch: use it for relational databases.
  • Parallel bulk: use it for analytical processing engines.
  • Single-thread: use it to avoid parallelism and large queries during extraction. When you select this mode, performance might be low.
Transformation logic extraction
You can enable building transformation logic descriptions from SQL code in SQL scripts.
Dynamic SQL
Enable dynamic SQL processing in DDL scripts.

Learn more