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 following operations:
▪ select on SYS.DBA_ARGUMENTS
▪ select on SYS.DBA_COL_COMMENTS
▪ select on SYS.DBA_COLL_TYPES
▪ select on SYS.DBA_CONS_COLUMNS
▪ select on SYS.DBA_CONSTRAINTS
▪ select on SYS.DBA_DB_LINKS
▪ select on SYS.DBA_DIRECTORIES
▪ select on SYS.DBA_EXTERNAL_LOCATIONS
▪ select on SYS.DBA_EXTERNAL_TABLES
▪ select on SYS.DBA_MVIEWS
▪ select on SYS.DBA_OBJECTS
▪ select on SYS.DBA_OPBINDINGS
▪ select on SYS.DBA_SEQUENCES
▪ select on SYS.DBA_SOURCE
▪ select on SYS.DBA_SYNONYMS
▪ select on SYS.DBA_TAB_COLUMNS
▪ select on SYS.DBA_TAB_COMMENTS
▪ select on SYS.DBA_TABLES
▪ select on SYS.DBA_TRIGGERS
▪ select on SYS.DBA_TYPE_ATTRS
▪ select on SYS.DBA_USERS
▪ select on SYS.DBA_VIEWS
▪ select on SYS.NLS_SESSION_PARAMETERS
▪ select on V$PARAMETER
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 New Connection.
3Enter 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.
Type
Type of connection.
Select Oracle from the list.
4Enter properties specific to the Oracle connection:
Property
Description
Runtime Environment
The name of the runtime environment where you want to run the tasks.
Specify a Secure Agent, Hosted Agent, or serverless runtime environment.
User Name
User name for the database login.
Password
Password for the database login.
Host
Name of the machine that hosts the database server.
Port
Network port number used to connect to the database server.
Default is 1521.
Service Name
Service name or System ID (SID) that uniquely identifies the Oracle database.
Specify the SID in the following format to connect to Oracle databases:
SID:<ORACLE_SID>
Code Page
The code page of the database server.
Encryption Method
The method that the Secure Agent uses to encrypt the data exchanged between the Secure Agent and the database server.
Select No Encryption when you use Kerberos authentication to connect to Oracle.
Default is No Encryption.
Not applicable when you use the Hosted Agent or the serverless runtime environment.
Crypto Protocol Version
Cryptographic protocols to use when you enable SSL encryption.
Not applicable when you use the Hosted Agent or the serverless runtime environment.
Validate Server Certificate
Validates the certificate that is sent by the database server. If you specify the HostNameInCertificate parameter, the Secure Agent also validates the host name in the certificate.
Trust Store
The location and name of the truststore file.
Specify the following certificate path in the runtime agent machine:
The password for the keystore file required for secure communication.
Metadata Advanced Connection Properties
Additional properties for the JDBC driver to fetch the metadata.
If you specify more than one property, separate each key-value pair with a semicolon.
For example, ConnectionRetryDelay=20;ConnectionRetryCount=3
To connect to an Oracle database enabled for advanced security, you can specify the Oracle advanced security options for the JDBC driver.
For example, EncryptionLevel=required;EncryptionTypes=(AES256, RC4_40);DataIntegrityLevel=REQUIRED;DataIntegrityTypes=(MD5)
5Click Test Connection.
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.