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.
admin ORADB-EPC
Description:
EPC-00002: invalid product ID passed
Cause:
An invalid product ID was passed.
admin ORADB-EPC
Description:
EPC-00003: invalid product version passed
Cause:
An invalid product version number was passed.
admin ORADB-EPC
Description:
EPC-00004: invalid product registration ID
Cause:
An invalid product registration ID was passed.
admin ORADB-EPC
Description:
EPC-00006: collection has been disabled
Cause:
The collection of Oracle Trace data has been disabled through the use of the EPC_DISABLED environment variable.
admin ORADB-EPC
Description:
EPC-00007: product version required
Cause:
A product version number was not specified.
admin ORADB-EPC
Description:
EPC-00008: epc_init routine called twice for this product
Cause:
The epc_init routine has already been called for the product.
admin ORADB-EPC
Description:
EPC-00014: no product number specified
Cause:
No product number argument was supplied to the Oracle Trace API routine, for example, EPC_EVENT routine.
admin ORADB-EPC
Description:
EPC-00015: not enough memory
Cause:
Memory allocation failed; system has run short of available memory.
admin ORADB-EPC
Description:
EPC-00020: Oracle Trace cannot access memory
Cause:
This error indicates that Oracle Trace is unable to extend the size of one of its memory mapped administrative .dat files, when the file has become full. This is only a Windows NT issue. On other platforms, the files are extended as needed with no user action needed.
admin ORADB-EPC