Create an Oracle metadata collector
Create a collector to import metadata from Oracle.
Before you begin
Before you begin, verify the following:
- A MID Server is setup for the collectors. For more information, see MID Server for metadata collectors.
- All per-requisite tasks are completed. For more information, see Prepare to run the Oracle collector.
- Role required: connection-admin
Procedure
Navigate to All > Workflow Data Fabric > Workflow Data Fabric Home.
Select the Connect Hub
Connect Hub icon icon in the left sidebar.
Select Create > Metadata collector.
From the System list, select Oracle.
From the Connection type list, select one of the following:
Select New connection to configure a new connection.
Select Existing connection to reuse an existing connection and select an existing connection from the Connections list.
The configuration form is filled with details from the existing connection. The name is appended with the word Copy and sensitive details like password aren't copied.
Complete the form.
Field Description Connection name Unique identifier for the connection. This field can't be modified once the connection is established. Short description Purpose and details of the connection. Configure the authentication options.
Field Description Username Username to use to connect to the database. Password Password of the databsase user. Select from Collect all schemas or Specify which schema to collect to configure the schema collection options.
Field Description Collect all schemas Collect all schemas Catalog all schemas to which the user has access. Exclude Schema Name or regular expression of the database schema to be excluded. Include Information Schema Include the database's Information Schema in catalog collection. Specify which schema to collect Specify which schema to collect Catalog only the specified schemas. Schema Name of the database schema to catalog. Configure the connection information.
| Field | Description |
|---|---|
| Server | Hostname of the database server to connect to. |
| Server port | Port of the database server \(if not the default\). |
| Database | Name of the database to connect to. Specify multiple databases by adding one value per line. If not specified, the collector harvests metadata from all databases. |
| Excluded database | Name or regular expression indicating databases not to catalog when the Database field is empty.Note: This parameter is ignored if the Database field is specified. |
- Configure the statistics and sampling options.
| Field | Description |
|---|---|
| Enable column statistics collection | Enable harvesting of column statistics (that is, data profiling).Note: Enabling profiling can increase the collector’s runtime, as the collector must read table data to generate profiling metadata. |
| Target sample size for column statistics | Number of rows sampled for computation of column statistics and string-value histograms. For example, to sample 1000 rows, set the parameter as: 1000.Default: 100000 |
| Disable Lineage collection | Skip harvesting of intra-database lineage metadata. |
| Disable Extended Metadata collection | Skip harvesting of extended metadata for data asset types such as database, schema, table, columns functions, stored procedures, user defined types, synonyms. Basic metadata for these data asset types will still be harvested. |
Configure the harvesting scope and limits options.
Field Description Database is an Oracle SID Indicate that the database is actually an Oracle SID. Oracle JDBC Connection Timezone Specify whether the default timezone of JVM should be used as the Oracle JDBC connection timezone. Enable Sample String Values collection Enable harvesting of sample values and histograms for columns containing string data. Exclude system functions Exclude system functions from metadata collection. Configure the connection and reliability options.
| Field | Description |
|---|---|
| Server environment | Friendly name for the environment in which your database server runs when the server name is localhost. Helps differentiate it from other environments. |
| Database ID | Unique identifier for this database. Used to generate the database ID when the database name is not sufficiently unique. |
| Use Oracle Autonomous Database | Option to connect to an Autonomous Database.When this option is enabled: - Enter the service name as the value for the Database parameter. For example, g0404\_ktest\_high.adb.oraclecloud.com - Enter the host name as the value for the Server parameter. For example, adb.us-chicago-1.oraclecloud.com |
| Oracle Autonomous Database Connection String | The connection string for an Autonomous Database. The connection string should be in the format: jdbc:oracle:thin:@<host>:<port>/<service_name> or jdbc:oracle:thin:@(address=(protocol=tcps)(port=<port>) (host:<host>))(connect_data=(service_name=<service_name>))(security=(ssl_server_dn_match=yes))).Note: The collector connects to the Oracle Cloud instance using the value in the Oracle Autonomous Database Connection String field. However, the server, port, and database parameters are still required—they are used for IRI coining and to uniquely identify the database data assets within your catalog. |
| JDBC properties | JDBC driver properties to pass through to driver connection. |
| SQL parsing timeout | Timeout in seconds for SQL parsing during lineage collection. Default: 60 |
- Select Save.
Result
The metadata collector is created and appears on the Connectors page with a Configured status. It is now ready to connect to the source system and harvest metadata.
What to do next
After creating the collector, you can perform any of the following tasks:
- Run the collector manually to harvest metadata immediately. See Run metadata collectors manually.
- Automate metadata collection by scheduling regular collector runs. See Schedule metadata collector runs.
- Monitor execution status and troubleshoot issues by viewing the runtime logs. See View runtime logs for collector runs.
- Discover and evaluate the harvested data assets in the Data Catalog. See Governing the Data Catalog.
Parent Topic:Oracle metadata collector