This section shows how to locate and name the data
containers for this technology.
File Shows
if this technology is based on the use of files.
Using "Data server"
Shows that the technology uses a data server whose name can
be used to name objects. If the check box is selected, the term used to
describe the data servers for the technology must be specified.
For example, in Oracle technology, the data server is
accessed by an Instance/DBLink.
Using "Catalog" Shows
that the technology uses a catalog to name its datastores. If the check box is
selected, the term used to describe the catalog concept in the technology must
be specified. For example, Microsoft SQL Server uses a catalog named Database,
IBM AS/400 uses a catalog named Library, Oracle does not use any catalog.
Using "Schema" Shows
that the technology uses a schema to name its datastores. If the box is
selected, the term used to describe the schema concept in the technology must
be specified.
For example, Microsoft SQL Server uses a schema named Owner,
Oracle uses a schema named Schema/User, Microsoft Access does not use schema.
Character Encoding
Shows the character encoding to be used while reading and
writing data.
Local object mask
Defines how an object is named 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
EMP table 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
Defines how an object is named when you are connected to a
different data server from the one on which the object is based. 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 NYORK (remote data server).
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).
Partition Mask
Shows how to name a partition in a SELECT statement. This field
in enabled only when partitions are selected. 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.
%PARTITION
to symbolize a partition name.
For example: %SCHEMA.%OBJECT PARTITION(%PARTITION)
Sub-Partition Mask
Sub-Partition Mask shows how to name a sub-partition in a
SELECT statement. This field in enabled only when Sub-Partitions is selected in
Partitioning Support.
In Oracle Data Integrator, the tags available for this mask
are the same as for the Partition mask.
For example: %SCHEMA.%OBJECT SUBPARTITION(%PARTITION)
Supports Native Sequences Technology's
capacity to support native sequences. If this option is selected, you need to
provide at least a value for the Local Sequence Mask.
Local Sequence Mask Shows
the SQL code to use when accessing a native sequence that is on the current
(local) data server.
For example: %SCHEMA.%OBJECT.nextval
Remote Sequence Mask Shows the SQL code to use when
accessing a native sequence that is on the remote data server.
For example: %SCHEMA.%OBJECT.nextval@%DSERVER
No comments:
Post a Comment