Description:
EPC-00001: invalid event flags passed
Cause:
This is an Oracle Trace internal error; if it is returned it may indicate that some lower level routine has returned a status of 1 which the Oracle Trace code has not handled.
Description:
EPC-00063: error reading product definition file
Cause:
An error was encountered while trying to read the product definition file (.fdf) specified, for example, on the EPC_COLLECT call.
Description:
EPC-00100: error finding free slot for new registration ID detail record
Cause:
The system may be out of disk space.
Description:
EPC-00155: maximum number of restrictions exceeded
Cause:
More than the maximum number of restriction records was provided as input by CLI user (maximum is currently 5).
Description:
EPC-00195: error finding next product record in facility.dat file
Cause:
This is an Oracle Trace internal error.
Description:
EPC-00309: error parsing SQL statement
Cause:
This error is typically seen during the format of Oracle Trace data into a database. This error indicates that format tables may not exist in the database or current format table definitions are out of sync with an Oracle Trace image trying to perform the format operation. Oracle Trace releases 7.3.4 and 8.0.4 (and higher) are able to create and update metadata describing format tables automatically but older versions do not have this ability.
Description:
EPC-00030: collection not found
Cause:
An Oracle Trace operation (for example, cancel) was attempted for a collection that is not currently known to Oracle Trace Collection Services.
Description:
EPC-00075: file name required
Cause:
A file name was expected but not found, for example, an .fdf file name is required to start a collection.
Description:
EPC-00113: error during addition of new collection record
Cause:
This is an Oracle Trace internal error. It should never be returned.
Description:
EPC-00170: error deleting collection data file
Cause:
Signaled by Oracle Trace CLI if an error occurred while attempting to delete a collection’s .dat file, most likely caused by file not existing (that is, already deleted), or file protection; or file may still be held by one or more processes that took part in the Oracle Trace collection, that is database processes.