Enterprise Data Catalog Scanner Configuration Guide > Configuring Database Management Resources > Oracle
  

Oracle

Configure an Oracle resource to extract metadata from Oracle databases.

Objects Extracted

Enterprise Data Catalog extracts metadata of the following schema objects from an Oracle resource:

Permissions to Configure the Resource

You must configure the CONNECT and SELECT_CATALOG_ROLE permissions for the database user account that you use to access the Oracle database.

Resource Connection Properties

The following table describes the properties for the Oracle resource type:
Property
Description
User
Name of the user account that connects to the Oracle database.
Password
Password for the user account that connects to the Oracle database.
Host
Fully qualified host name of the machine where the Oracle database is hosted.
Port
Port number for the Oracle database engine service.
Service
Unique identifier or system identifier for the Oracle database server.
The following table describes the Additional and Advanced properties for source metadata settings on the Metadata Load Settings tab:
Property
Description
Enable Source Metadata
Select to extract metadata from the data source.
Import system objects
Specifies the system objects to import.
The default value is True or False whatever the case might be.
Schema
Specifies a list of semicolon-separated database schema.
Source Metadata Filter
You can include or exclude tables and views from the resource run. Use semicolons (;) to separate the table names and view names.
For more information about the filter field, see Source Metadata and Data Profile Filter.
Import stored procedures
Specifies the stored procedures to import.
The default value is True or False whatever the case might be.
Import Private and Public Synonyms
Specifies private and public synonyms to import. Select one of the following values:
  • - True. Select this check box to import private and public synonyms.
  • - False. Clear this check box if you do not want to import the private and public synonyms.
The default value is False.
Case Sensitive
Specifies that the resource is configured for case insensitivity. Select one of the following values:
  • - True. Select this check box to specify that the resource is configured as case sensitive.
  • - False. Clear this check box to specify that the resource is configured as case insensitive.
The default value is False.
Import Database Name
Extracts the database name of the data source from the v$database variable. Enable the option when you want to extract metadata from an Oracle Real Application Clusters (Oracle RAC) data source.
Memory
Specify the memory value required to run a scanner job.
Specify one of the following memory values:
  • - Low
  • - Medium
  • - High
Note: For more information about the memory values, see the Tuning Enterprise Data Catalog Performance article on How To-Library Articles tab in the Informatica Doc Portal
JVM Options
JVM parameters that you can set to configure scanner container. Use the following arguments to configure the parameters:
  • - -Dscannerloglevel=<DEBUG/INFO/ERROR>. Changes the log level of scanner to values, such as DEBUG, ERROR, or INFO. Default value is INFO.
  • - -Dscanner.container.core=<No. of core>. Increases the core for the scanner container. The value should be a number.
  • - -Dscanner.yarn.app.environment=<key=value>. Key pair value that you need to set in the Yarn environment. Use a comma to separate the key pair value.
  • - -Dscanner.pmem.enabled.container.memory.jvm.memory.ratio=<1.0/2.0>. Increases the scanner container memory when pmem is enabled. Default value is 1.
  • - -DskipExternalDatabaseObjects=true. Excludes all external objects such as schema, table, database and view.
Track Data Source Changes
View metadata source change notifications in Enterprise Data Catalog.
You can enable data discovery for an Oracle resource. For more information about enabling data discovery, see the Enable Data Discovery topic.
You can enable composite data domain discovery for an Oracle resource. For more information about enabling composite data domain discovery, see the Composite Data Domain Discovery topic.