Integrations
Integrations
Breadcrumbs

JDBC Oracle


Integration model

Metadata extraction

The methods offered by the Oracle JDBC driver are used, through which schema and table definitions are accessed.

It extracts the following attributes, which must be named the same in the attribute_definition table, in the name field, for them to appear in the template.

  • physicalName and name with the same value, the name of the table

  • path with the concatenation of the catalog, schema, and table values

  • infrastructure with the selected value

  • technology with the selected value

  • zone with the selected value

Two considerations worth noting:

  • catalog: Does not support catalogs. When specifying objects in the database, the catalog field must be left blank.

  • schema: Normally, a user ID name is equivalent to the schema.


The plugin also extracts the following attributes related to the dataset_fields of the requested resource:

  • name with the value of the corresponding field

  • physicalName with the value of the corresponding field

  • defaultValue with the default value defined for the corresponding field

  • fieldDataType with the data type defined for the corresponding field

  • length with the size of the corresponding field

  • incrementalField indicating whether it is an incremental field

  • position position occupied by the corresponding field

  • precision with the precision value of the corresponding field

  • nullable indicating whether the corresponding field is nullable

  • pk indicating whether the field is a primary key

  • description with the corresponding value for the field


The attributes to be created in Anjana must have the following types:

Attribute name

Attribute type

schema

INPUT_TEXT

physicalName

INPUT_TEXT

path

INPUT_TEXT

infrastructure

SELECT

technology

SELECT

zone

SELECT

name

INPUT_TEXT

defaultValue

INPUT_TEXT

fieldDataType

INPUT_TEXT

length

INPUT_NUMBER

incrementalField

INPUT_CHECKBOX

position

INPUT_NUMBER

precision

INPUT_NUMBER

nullable

INPUT_CHECKBOX

pk

INPUT_CHECKBOX

description

ENRICHED_TEXT_AREA_INTERNATIONAL

When the creation workflow is completed and an object is governed, all available metadata for that object is sent to Tot — that is, all existing attributes of the created object.

The plugin is capable of performing metadata extraction on the element types configured for it. By default, it will attempt to extract Tables (TABLE) and Views (VIEW).

Tables with special characters in the name

Important → Using special characters such as “/” in table names is NOT recommended because extraction will not work.

Data sampling

Using the Oracle JDBC driver, a query is executed on the fields defined in the dataset, additionally replacing the values of sensitive fields with asterisks.

Active governance

An Anjana DSA containing an entity corresponding to an Oracle-native object (provided it is governed and approved) will be represented as a group created in the plugin associated as AD and as a role in the Oracle plugin. Administration of READ permissions on the corresponding tables will also be performed in the Oracle plugin.

Object editing

The plugin allows managing the activation or deactivation of non-native entities, so that when a non-native entity is activated, the corresponding permissions will be granted on the tables, and when deactivated, the permissions will be removed.

Supported versions

Support from version 19.X through 23.3.

The driver also has backward compatibility to 12.1; however, it has no official support for versions prior to 19.X, so Anjana Data does not certify the correct functioning of the plugin for those versions of Oracle.

Required credentials

Metadata extraction / data sampling

User or role with SELECT or READ permissions on the tables or views from which metadata is to be extracted or a data sample obtained. The difference is that SELECT allows locking records during sampling (if the query is configured for that).

If access to all system tables is required for governance, the predefined SELECT_CATALOG_ROLE role can be granted.

Access management

To allow management of permissions on Oracle structures, the system user included in the plugin YAML must have the following permissions:

  • CREATE ROLE to be able to create roles associated with groups.

  • DROP ANY ROLE to be able to delete the roles that were created.

  • GRANT ANY OBJECT PRIVILEGE to be able to grant and revoke READ permissions to the created roles on the tables they govern.

  • SELECT on dba_roles.

Object editing

The connection user must have the following permissions on the catalogs, schemas, and tables to be modified:

  • CREATE ROLE to be able to create roles associated with groups.

  • DROP ANY ROLE to be able to delete the roles that were created.

  • GRANT ANY OBJECT PRIVILEGE to be able to grant and revoke READ permissions to the created roles on the tables they govern.

Available ImAri

Ldap