Property
Description
Name
Name of the physical schema, as it appears in the graphic interface. It is calculated automatically.
(Schema)
Name of the schema in the data server. Schema, owner, or library where the required data is stored.
Caution: Oracle Data Integrator lists all the schemas present in the data server. Sometimes, Oracle Data Integrator cannot draw up this list. In this case, you should enter the schema name, respecting the case.
(Work schema)
For some data validation or transformation operations, Oracle Data Integrator may require work objects to be created. Indicate the schema you want to create these objects in.
Caution: Oracle Data Integrator lists all the schemas present in the data server. Sometimes, Oracle Data Integrator cannot draw up this list. In this case, you should enter the schema name, respecting the case.
Note: It is preferable to create a specific schema dedicated to any Work tables. By creating a schema named "SAS" or "ODI" in all your data servers, you ensure that all Oracle Data Integrator activity remains totally independent from your applications.
Default
If this box is checked, then the physical schema will be the data server
default schema, when no schema has been specified. Only one physical schema
can be marked by default. The default schema
of each data server is indicated with this icon:
Work tables prefixes
This section details the work table prefixes that Oracle Data Integrator is likely to create in the work schema of this physical schema.
Errors
Prefix used to create the tables that contain erroneous data. These tables are created and/or updated during a data quality control and can be consulted from the graphic interface.
Loading
Prefix used to create the objects (tables, views, files, etc) that allow data loading between two data servers.
Integration
Prefix used to create the objects (tables, files, etc) dedicated to data integration during execution of an interface.
Journalizing Elements Prefixes
This section details the prefixes that Data Integrator is likely to use to create elements for journalizing in this schema.
Tables
Prefix used to create the journalizing tables (containing the changes indications.)
Views
Prefix user to create the views linking journalizing tables and the data tables.
Triggers
Prefix used to create triggers on the data stables enabling to update the journalizing tables.
Naming rules
This section shows how to locate and name (term) the data containers for this technology.
Local object mask
The local object mask shows how to name an object in the physical schema, when you are connected to the data server on which the object is based.
For example, for Oracle, you should indicate %SCHEMA.%OBJECT to symbolize the syntax "SCOTT.EMP" giving access to the table EMP belonging to the user SCOTT.
In Oracle Data Integrator, the tags available for this mask are:
%CATALOG to symbolize the catalog name (property of the physical schema),
%SCHEMA to symbolize the schema name (property of the physical schema),
%OBJECT to symbolize the datastore name.
Caution: These tags are case-sensitive.
Remote object mask
The remote object mask shows how to name an object in the physical schema, when you are connected to a different data server from the one this object is based on.
For example, for Oracle, you should indicate %SCHEMA.%OBJECT@DSERVER to symbolize the syntax SCOTT.EMP@NYORK allowing access to the EMP table of the user SCOTT of the instance (remote data server) NYORK.
The tags available for this mask are the same as for local objects, to which must be added %DSERVER representing the name of the data server (property of the connection).