If error conditions are detected in the Access Definition
or the Extract Request when the Extract is run, processing stops and
an error message is displayed. For example, errors can occur if changes
have been made to the tables since the Access Definition was created.
Error messages, such as those listed below,
appear in the message bar of the Extract Request Editor:
- Duplicate Table Entries
- A single table is listed in the Access Definition
twice. You cannot specify a table and one or more views or aliases
of that table, or specify more than one view or alias of a table.
- No Valid Table
- No valid table is specified. The list of tables
in the Access Definition does not include any valid tables. These
tables may have been dropped from the database.
- Invalid WHERE Clause
- An SQL WHERE Clause is invalid. Selection criteria
for one or more tables are invalid. (For example, a column used in
an SQL WHERE Clause has been dropped from the table.)
- Invalid Start Table
- The Start Table is invalid. This can occur when
the table is dropped or the Creator ID changed. The table is then
marked as Unknown and cannot be used as the
Start Table.
- Missing Primary Keys
- A child table that has multiple parents does not
have a primary key. The primary key is required when the child table
is related to multiple parents to ensure that multiple copies of a
row are not extracted.
A parent table does not have
a primary key. Relationships defined in the Optim™ Directory are not required to include
a primary key for the parent table. However, a primary key is required
to enable tracking of outstanding parent rows.
- Improper Authorization
- The person requesting the extract is not authorized
to access data from a table included in the Access Definition.