Before you create a catalog source, ensure that you have the information required to connect to the source system.
Complete the following prerequisite tasks:
•Ensure that you have the required permissions to extract metadata and run profiles.
•If you're configuring a connection to an SSL-enabled Oracle database, specify appropriate values for the Trust Store and Key Store fields in the Oracle connection properties. The data profiling task for an SSL-enabled Oracle database might fail if either the truststore or keystore value is not specified in the connection properties.
•Configure a connection to the Oracle source system in Administrator.
•Optionally, if you want to identify pairs of similar columns and relationships between tables within a catalog source, import a relationship inference model.
Verify permissions
To extract metadata and to configure other capabilities that a catalog source might include, you need account access and permissions on the source system. The permissions required might vary depending on the capability.
Permissions to extract metadata
Ensure that you have the required permissions to enable metadata extraction.
Grant the following permissions:
•CONNECT permission for the database user account that you use to access the Oracle database.
• One of the following permissions:
- Grant a predefined SELECT_CATALOG_ROLE role
- Grant permissions that allow you to perform the SELECT operation on the following master repository tables:
▪ SNP_CONNECT
▪ SNP_CONNECT_PROP
▪ SNP_CONTEXT
▪ SNP_LANG_TECHNO
▪ SNP_LSCHEMA
▪ SNP_MTXT
▪ SNP_PSCHEMA
▪ SNP_PSCHEMA_CONT
▪ SNP_TECHNO
- Grant permissions that allow you to perform the SELECT operation on the following work repository tables:
▪ SNP_COLUMN
▪ SNP_FOLDER
▪ SNP_MAPPING
▪ SNP_MODEL
▪ SNP_PACKAGE
▪ SNP_PROJECT
▪ SNP_SCEN
▪ SNP_SCEN_FOLDER
▪ SNP_SCEN_STEP
▪ SNP_SCEN_TASK
▪ SNP_SEQ_SCEN
▪ SNP_SEQUENCE
▪ SNP_STEP
▪ SNP_TABLE
▪ SNP_TRT
▪ SNP_VAR
▪ SNP_VAR_SCEN
Permissions to run data profiles
Ensure that you have the required permissions to run profiles.
Grant SELECT permissions for tables and views that you want to profile.
Permissions to run data classification
You don't need any additional permissions to run data classification.
Permissions to run relationship discovery
You don't need any additional permissions to run relationship discovery.
Permissions to run glossary association
You don't need any additional permissions to run glossary association.
Create a connection
Before you configure the Oracle catalog source, create a connection object in Administrator.
1In Administrator, select Connections.
2Click Add Connection.
3Search for and select Oracle and then click Next.
4Enter the following connection details:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
5Enter properties specific to the Oracle connection:
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
Note: If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.
The name of the runtime environment where you want to run the tasks.
Select a Secure Agent, Hosted Agent, or serverless runtime environment.
Select a Secure Agent, Hosted Agent, serverless, or elastic runtime environment.
Oracle Subtype
The Oracle connection subtype that you can use to connect to Oracle on-premises or Oracle Autonomous Database.
Select one of the following options:
- Oracle ADB. Connects to Oracle Autonomous Database.
- Oracle On-premise. Connects to Oracle on-premises.
6Select the authentication type to connect to the Oracle source system and enter the connection properties.
You can select one of the following authentication types:
- Oracle Database authentication
- Kerberos authentication
Note: You can't configure LDAP authentication when you connect to Oracle databases.
7Click Test.
8Click Save.
Import a relationship inference model
Import a relationship inference model if you want to configure the relationship discovery capability. You can either import a predefined relationship inference model, or import a model file from your local machine.
1In Metadata Command Center, click Explore on the navigation panel.
2Expand the menu and select Relationship Inference Model. The following image shows the Explore page with the Relationship Inference Model menu:
3Select one of the following options:
- Import Predefined Content. Imports a predefined relationship inference model called Column Similarity Model v1.0.
- Import. Imports the predefined relationship inference model from your local machine. Select this if you previously imported predefined content into your local machine and the inference model is stored on the machine.
To import a file, click Choose File in the Import Relationship Inference Model window and navigate to the model file on your local machine. You can also drag and drop the file.
The imported models appear in the list of relationship inference models on the Relationship Discovery tab.
