FAQ > Ensuring DMExpress Uses Fast Load into Oracle Target Tables

Ensuring DMExpress Uses Fast Load into Oracle Target Tables

Article #: Product: Version:

Summary

DMExpress uses two methods to load data into an Oracle database target table:

DMExpress dynamically selects either the fast load or regular load method to load the data into an Oracle target database table. DMExpress uses fast load whenever possible to get optimal performance. In cases where DMExpress cannot use fast load, DMExpress continues with regular load and issues a warning message that provides information on why fast load cannot be used.

Symptom

The following warning message is issued when fast load cannot be used:

(DOPRFNOP) performance of writing to target database "<text>" table "<text>" was not optimal

This message is followed by one of the following warning messages, which explain why fast load cannot be used:

(INDXNOFL) there are unique index(es) on the table

(NOUNQIDX) information about unique index(es) on the table could not be retrieved

(TRIGGERS) there are triggers on the table

(CONSTRTS) there are referential or check constraints on the table

(CMTORARE) you have specified a number of records for the commit interval

Resolution

In cases where DMExpress cannot use fast load, DMExpress continues with regular load. Provided the integrity of the database is not compromised, consider the following actions to ensure that DMExpress uses fast load.

Additional Information

For additional details on the DMExpress warning messages when fast load cannot be used, refer to the DMExpress Help.

For more information on direct path load and conventional path load, refer to Oracle's documentation.

Last updated: