Connect to and manage Oracle in Microsoft Purview
This article outlines how to register Oracle, and how to authenticate and interact with Oracle in Microsoft Purview. For more information about Microsoft Purview, read the introductory article.
|Metadata Extraction||Full Scan||Incremental Scan||Scoped Scan||Classification||Labeling||Access Policy||Lineage||Data Sharing||Live view|
The supported Oracle server versions are 6i to 19c. Oracle proxy server isn't supported when scanning Oracle source.
When scanning Oracle source, Microsoft Purview supports:
Extracting technical metadata including:
- Tables including the columns, foreign keys, indexes, triggers and unique constraints
- Views including the columns and triggers
- Stored procedures including the parameter dataset and result set
- Functions including the parameter dataset
- Types including the type attributes
Fetching static lineage on assets relationships among tables and views.
When setting up scan, you can choose to scan an entire Oracle server, or scope the scan to a subset of schemas matching the given name(s) or name pattern(s).
- Currently, the Oracle service name isn't captured in the metadata or hierarchy.
- When object is deleted from the data source, currently the subsequent scan won't automatically remove the corresponding asset in Microsoft Purview.
An Azure account with an active subscription. Create an account for free.
An active Microsoft Purview account.
You need Data Source Administrator and Data Reader permissions to register a source and manage it in the Microsoft Purview governance portal. For more information about permissions, see Access control in Microsoft Purview.
Set up the latest self-hosted integration runtime. For more information, see the create and configure a self-hosted integration runtime guide.
Ensure JDK 11 is installed on the machine where the self-hosted integration runtime is installed. Restart the machine after you newly install the JDK for it to take effect.
Ensure Visual C++ Redistributable (version Visual Studio 2012 Update 4 or newer) is installed on the self-hosted integration runtime machine. If you don't have this update installed, you can download it here.
Download the Oracle JDBC driver on the machine where your self-hosted integration runtime is running. Note down the folder path that you'll use to set up the scan.
The driver should be accessible by the self-hosted integration runtime. By default, self-hosted integration runtime uses local service account "NT SERVICE\DIAHostService". Make sure it has "Read and execute" and "List folder contents" permission to the driver folder.
Required permissions for scan
Microsoft Purview supports basic authentication (username and password) for scanning Oracle. The Oracle user must have read access to system tables in order to access advanced metadata.
For classification, user also needs to be the owner of the table.
If the user is not the owner of the table, the scan will run successfully and ingest metadata, but will not identify any classifications.
The user should have permission to create a session and role SELECT_CATALOG_ROLE assigned. Alternatively, the user may have SELECT permission granted for every individual system table that this connector queries metadata from:
grant create session to [user]; grant select on all_users to [user]; grant select on dba_objects to [user]; grant select on dba_tab_comments to [user]; grant select on dba_external_locations to [user]; grant select on dba_directories to [user]; grant select on dba_mviews to [user]; grant select on dba_clu_columns to [user]; grant select on dba_tab_columns to [user]; grant select on dba_col_comments to [user]; grant select on dba_constraints to [user]; grant select on dba_cons_columns to [user]; grant select on dba_indexes to [user]; grant select on dba_ind_columns to [user]; grant select on dba_procedures to [user]; grant select on dba_synonyms to [user]; grant select on dba_views to [user]; grant select on dba_source to [user]; grant select on dba_triggers to [user]; grant select on dba_arguments to [user]; grant select on dba_sequences to [user]; grant select on dba_dependencies to [user]; grant select on dba_type_attrs to [user]; grant select on V_$INSTANCE to [user]; grant select on v_$database to [user];
This section describes how to register Oracle in Microsoft Purview using the Microsoft Purview governance portal.
Steps to register
To register a new Oracle source in your data catalog, do the following:
Navigate to your Microsoft Purview account in the Microsoft Purview governance portal.
Select Data Map on the left navigation.
On Register sources, select Oracle. Select Continue.
On the Register sources (Oracle) screen, do the following:
Enter a Name that the data source will be listed within the Catalog.
Enter the Host name to connect to an Oracle source. This can either be:
- A host name used to connect to the database server. For example:
- An IP address. For example:
- A host name used to connect to the database server. For example:
Enter the Port number used to connect to the database server (1521 by default for Oracle).
Enter the Oracle service name (not Oracle UID) used to connect to the database server.
Select a collection from the list.
Finish to register the data source.
Follow the steps below to scan Oracle to automatically identify assets. For more information about scanning in general, see our introduction to scans and ingestion.
To troubleshoot any issues with scanning:
Create and run scan
To create and run a new scan, do the following:
In the Management Center, select Integration runtimes. Make sure a self-hosted integration runtime is set up. If it isn't set up, use the steps mentioned here to create a self-hosted integration runtime.
Navigate to Sources.
Select the registered Oracle source.
Select + New scan.
Provide the below details:
Name: The name of the scan
Connect via integration runtime: Select the configured self-hosted integration runtime
Credential: Select the credential to connect to your data source. Make sure to:
- Select Basic Authentication while creating a credential.
- Provide the user name used to connect to the database server in the User name input field.
- Store the user password used to connect to the database server in the secret key.
Schema: List subset of schemas to import expressed as a semicolon separated list in case-sensitive manner. For example,
schema1;schema2. All user schemas are imported if that list is empty. All system schemas (for example, SysAdmin) and objects are ignored by default.
Acceptable schema name patterns can be static names or contain wildcard %. For example:
- Start with A or
- End with B or
- Contain C or
- Equal D
Usage of NOT and special characters aren't acceptable.
Driver location: Specify the path to the JDBC driver location in your machine where self-host integration runtime is running, for example,
D:\Drivers\Oracle. It's the path to valid JAR folder location. The value must be a valid absolute file path and does not contain space. Make sure the driver is accessible by the self-hosted integration runtime, learn more from prerequisites section.
Stored procedure details: Controls the number of details imported from stored procedures:
- Signature: The name and parameters of stored procedures.
- Code, signature: The name, parameters and code of stored procedures.
- Lineage, code, signature: The name, parameters and code of stored procedures, and the data lineage derived from the code.
- None: Stored procedure details aren't included.
Maximum memory available: Maximum memory (in GB) available on customer's VM to be used by scanning processes. This is dependent on the size of Oracle source to be scanned.
As a rule of thumb, please provide 1GB memory for every 1000 tables
Select Test connection.
Use the "Test connection" button in the scan setup UI to test the connection. The "Test Connection" in self-hosted integration runtime configuration manager UI -> Diagnostics tab does not fully validate the connectivity.
Select a scan rule set for classification. You can choose between the system default, existing custom rule sets, or create a new rule set inline.
Choose your scan trigger. You can set up a schedule or ran the scan once.
Review your scan and select Save and Run.
View your scans and scan runs
To view existing scans:
- Go to the Microsoft Purview governance portal. On the left pane, select Data map.
- Select the data source. You can view a list of existing scans on that data source under Recent scans, or you can view all scans on the Scans tab.
- Select the scan that has results you want to view. The pane shows you all the previous scan runs, along with the status and metrics for each scan run.
- Select the run ID to check the scan run details.
Manage your scans
To edit, cancel, or delete a scan:
Go to the Microsoft Purview governance portal. On the left pane, select Data Map.
Select the data source. You can view a list of existing scans on that data source under Recent scans, or you can view all scans on the Scans tab.
Select the scan that you want to manage. You can then:
- Edit the scan by selecting Edit scan.
- Cancel an in-progress scan by selecting Cancel scan run.
- Delete your scan by selecting Delete scan.
- Deleting your scan does not delete catalog assets created from previous scans.
- The asset will no longer be updated with schema changes if your source table has changed and you re-scan the source table after editing the description on the Schema tab of Microsoft Purview.
Go to the asset -> lineage tab, you can see the asset relationship when applicable. Refer to the supported capabilities section on the supported Oracle lineage scenarios. For more information about lineage in general, see data lineage and lineage user guide.
Now that you've registered your source, follow the below guides to learn more about Microsoft Purview and your data.