- Queries used by Oracle Data Integrator to perform specific tasks. These queries are technology-specific.
The SQL query for PKs, AKs, FKs, and Indexes is defined by
the following parameters:
CATALOG (if
supported by technology)
SCHEMA (if
supported by technology)
TABLE
The SQL query for native sequences is defined with CATALOG
and SCHEMA.
Current Date
Query that can be sent at anytime to a data server of this technology to
return the current date and time of the server. This query is used internally
to recover connections.
Reverse-Engineer PKs
Query used by Common Format Designer to compare the data
model with the metadata from the data server. This query retrieves primary key
definitions. Note that this query is not used for standard or customized reverse-engineering.
This query should return a record set (one row per primary key column) that
contains the following VARCHAR fields:
PK_NAME: Name of the primary key.
COLUMN_NAME: Name of the primary key column.
The record set should be ordered by PK_NAME and by the
position of COLUMN_NAME in the primary key.
Reverse-Engineer AKs
Query is used by Common Format Designer to compare the data
model with the metadata from the data server. This query is not used for
standard or customized reverse-engineering. This query retrieves alternate key
definitions. This query should return a record set (one row per alternate key
column) that contains the following VARCHAR fields:
AK_NAME: Name of the alternate key.
COLUMN_NAME: Name of the alternate key column.
The record set should be ordered by AK_NAME and by the position of COLUMN_NAME in the alternate key.
Reverse-Engineer FKs
Query is used by Common Format Designer to compare the data
model with the metadata from the data server. This query is not used for
standard or customized reverse-engineering. This query retrieves foreign key
definitions. This query should return a record set (one row per foreign key
column) containing the following VARCHAR fields:
FK_NAME: Name of the foreign key.
COLUMN_NAME: Name of the foreign key column.
The record set should be ordered by FK_NAME and by the
position of COLUMN_NAME in the foreign key.
Reverse-Engineer Indexes
Query is used by Common Format Designer to compare the data
model with the metadata from the data server. This query is not used for
standard or customized reverse-engineering. This query reverse-engineers
indexes. This query should return a record set (one row per index column)
containing the following VARCHAR fields:
INDEX_NAME: Name of the index.
COLUMN_NAME: Name of the index column.
The record set should be ordered by INDEX_NAME and by the
position of COLUMN_NAME in the index.
Reverse-Engineer Check Constraints
Query is used by Common Format Designer to compare the data
model with the metadata from the data server. This query is not used for
standard or customized reverse-engineering. This query reverse-engineers check
constraints. This query should return a record set (one row per check
constraint) containing the following VARCHAR fields:
CHECK_NAME: Name
of the check constraint.
CHECK_TXT: SQL
statement of the constraint.
CHECK_STATUS:
Status of the check constraint - '1' for enabled, '0' for disabled.
CHECK_DESC:
Description of the check constraint.
Reverse-Engineer Native Sequences
Query used to retrieve definitions for the native sequences.
This query should return a record set (one row per native sequence) that
contains the following VARCHAR field:
SEQUENCE_NAME: Name of the native sequence.
The record set should be ordered by SEQUENCE_NAME.
Sequence Next Value In Non-binded Mode
No comments:
Post a Comment