Connecting to Oracle

DataVeil supports connections to Oracle 10g and later. DataVeil uses JDBC for connectivity.

The form displayed in the Connection window for Oracle connections is shown below:


NOTE: DataVeil attempts to present a user interface in a database-agnostic manner. Consequently, there can be some ambiguity with terminology used. For example, DataVeil's use of the term "database" generally corresponds to what is generally referred to in Oracle as a "schema" (keep this in mind when reading DataVeil log messages.) In some specific cases, such as in the Oracle-specific connection form shown above, the Oracle term "schema" is used.

In the example shown above, the schema (owner) name is "KONA" and the username is "ref001". The schema name should be in uppercase.

It is important to realize that if 'Schema Name' is not recognized by Oracle or if the Username does not have access permissions, then Oracle will still accept the connection. In such a situation, DataVeil shall provide a list of all schema names accessible to Username. You can either select an available schema name from the list or cancel the connection attempt.



Please check with your DBA to ensure that your Username has the required access and permissions. In order to Run DataVeil masking projects, it is recommended that the Username have broad DBA-level permissions or at least be the owner of the schema (assuming the owner has all required privileges on all objects withing the schema). DataVeil needs to create and drop tables, indexes, triggers and constraints. Other tasks such as refreshing materialized views, querying DDL using DDMS_METADATA and compiling the schema are also performed.

Other execution parameters that apply to this connection, such as masking batch sizes and the maximum number of parallel JDBC connections (threads), can be specified in Execution Settings.