Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
The errors in this chapter are Oracle Trace Collection Services messages including the CLI, services, formatter, and reporter.
When contacting Oracle Support Services about Oracle Trace, please have the following information available:
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.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: An invalid product ID was passed.
Action: Supply a valid product ID between 1 and 999999.
Cause: An invalid product version number was passed.
Action: Supply a product version number not greater than 11 bytes in length.
Cause: An invalid product registration ID was passed.
Action: Supply a product registration ID not greater than 256 bytes in length.
Cause: The collection of Oracle Trace data has been disabled through the use of the EPC_DISABLED environment variable.
Action: No action required.
Cause: A product version number was not specified.
Action: Specify a product version number.
Cause: The epc_init routine has already been called for the product.
Action: Check the code to verify that the EPC_INIT routine is being called only once and that the call to the EPC_INIT routine is in the correct location.
Cause: No product number argument was supplied to the Oracle Trace API routine, for example, EPC_EVENT routine.
Action: Specify a product number.
Cause: Memory allocation failed; system has run short of available memory.
Action: Try executing a similar Oracle Trace collection with fewer processes running; your system may be short of 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.
Action: Wait for currently running Oracle Trace collections to be completed before freeing up space on the *.dat files. If no Oracle Trace collections are running (and Oracle database processes are no longer attached to the files), then run the otrccref image to create new, empty .dat files, and if desired, specify larger file sizes when otrccref is run, for example, otrccref -f200 -c32 -r400.
Cause: A collection is active, but the specified instrumented product is not part of the collection.
Action: Verify the correct product version was specified for the collection.
Cause: An Oracle Trace operation (for example, cancel) was attempted for a collection that is not currently known to Oracle Trace Collection Services.
Action: Supply the name of a collection that exists.
Cause: An illegal record length was encountered on the EPC_EVENT call.
Action: Refer to the Oracle Trace User's Guide for information on valid record lengths in the epc_event call.
Cause: An invalid event number was passed.
Action: Supply a valid event number.
Cause: A 0 was specified for the event.
Action: Supply a valid event number.
Cause: A null handle argument was specified on the START_EVENT or END_EVENT call.
Action: Supply a handle address on the call.
Cause: The product is collecting, but the event is not.
Action: No action required.
Cause: The data cannot be written to the data collection file.
Action: Verify that there is enough disk space and that file protections are correct.
Cause: An unusually high contention for updating the collection data file prevents acquiring write lock on the file.
Action: Retry when fewer processes are taking part in the collection.
Cause: Typically this error is returned through Oracle Trace Manager when an underlying error value is out of range of values handled. Under unusual conditions, it may also be used to report an error for which cause could not be determined.
Action: Look for error details, if any, in the EPC_ERROR.LOG file, and find cause/action descriptions for those errors. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: An invalid context value was passed to the Oracle Trace API routine, for example, EPC_EVENT.
Action: Supply a valid context argument to the API routine calls.
Cause: There was no context passed to the Oracle Trace API routine and one was expected.
Action: Pass a context.
Cause: Context to the current thread has not been set.
Action: Set context to the current thread.
Cause: The optional registration string specified in the EPC_INIT call is a duplicate.
Action: Correct the instrumented code.
Cause: The limit of 5 products per collection was exceeded.
Action: No action required. However, you lose the connection to the oldest collection.
Cause: Oracle Trace encountered an error while attempting to open the data collection file (.dcf).
Action: Verify that collection files exist and check file protections. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Oracle Trace encountered an error while attempting to open the collection definition file (.cdf).
Action: Verify that the collection's collection definition file (.cdf) exists and check file protections. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: An invalid cross-product item number was specified, for example, in the EPC_CF_VALUE call.
Action: Supply a cross-product number from 1 through 14.
Cause: An EPC_INIT call was expected, but not found.
Action: Check the code to verify a call to EPC_INIT is made in the correct place.
Cause: The data collection file was not specified, for example, for the epc_collect call.
Action: Verify the instrumented code.
Cause: The product definition file (.fdf) was not specified, for example, for the epc_collect call.
Action: Verify the instrumented code.
Cause: The specified collection is already active.
Action: No action required.
Cause: An error was encountered while trying to read the product definition file (.fdf) specified, for example, on the EPC_COLLECT call.
Action: Verify that the product definition file exists and check file protections. Also check directory protections, definition for ORACLE_HOME, and Oracle Trace parameter settings. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: An error was encountered while trying to create the data collection file (.dcf).
Action: Check protection settings on the Oracle Trace admin/cdf directory. Also check the definition for ORACLE_HOME and Oracle Trace parameter settings. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: An error was encountered while creating the specified collection definition file (.cdf).
Action: Check protection settings on the Oracle Trace admin/cdf directory. Also check the definition for ORACLE_HOME and Oracle Trace parameter settings. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: An error was encountered while writing to the specified collection definition file (.cdf).
Action: Check that there is enough disk space and that file protections are correct. Also check directory protections, definition for ORACLE_HOME, and Oracle Trace parameter settings. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: An error was encountered while opening the product definition file.
Action: Verify that the product definition file (.fdf) exists and if so, check file protections. Also check directory protections, definition for ORACLE_HOME, and Oracle Trace parameter settings. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: A seek error was encountered in the collection definition file (.cdf).
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The operating system could not be identified.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The host name could not be identified; platform-specific call to obtain host failed.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: An invalid maximum event was specified.
Action: Supply a maximum event greater than 0 but less than 128.
Cause: The returned event flags parameter was expected but not found on the EPC_INIT call.
Action: Supply the required information on the EPC_INIT call.
Cause: This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: A file name was expected but not found, for example, an .fdf file name is required to start a collection.
Action: Supply a file name.
Cause: The PREDEFINED_EVENTFLAGS parameter was expected but a NULL pointer was passed on the EPC_INIT call.
Action: Supply the required information on the EPC_INIT call.
Cause: An invalid event key option was specified on the EPC_INIT call.
Action: Supply a valid event key option argument on the EPC_INIT call.
Cause: This feature is not yet implemented.
Action: Do not use this feature. No action required.
Cause: File I/O seek to start (or end) file during append operation failed. This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Disk space was exceeded during a file append operation, for example, while creating the collection definition file (.cdf).
Action: Increase disk space.
Cause: This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Most often this indicates that a mismatch exists between Oracle Trace Collection Services and other components (for example, database server version). Memory mapping of Oracle Trace admin .dat files can also generate errors if files are not located on a locally mounted disk device.
Action: Refer to the Oracle Trace documentation or contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This condition is used to signal the beginning of an Oracle Trace CLI job (that is, executed by the Oracle Intelligent Agent on behalf of Oracle Trace). It is not an error.
Action: No action required. For Oracle Server release 7.3.3, the error message read "Cannot allocate process record in PRO file." This often occurs in conjunction with error EPC-00084.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The EVENT_ID parameter supplied in the EPC_EVENT call is greater than the maximum previously specified on the EPC_INIT call.
Action: Supply a valid EVENT_ID.
Cause: The system may be out of disk space.
Action: Verify that the drive where ORACLE_HOME is located has enough disk space. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Oracle Trace could not get the system timestamp.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The system may be out of disk space.
Action: Verify that the drive where ORACLE_HOME is located has enough disk space. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: User may not have write access to the directory where Oracle Trace admin .dat files are to be located, for example, $ORACLE_HOME/otrace/admin; or available disk space may be insufficient.
Action: Provide access to the directory or additional free disk space. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The system may be out of disk space.
Action: Verify that the drive where ORACLE_HOME is located has enough disk space. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Oracle Trace was unable to open its admin REGID.DAT file.
Action: Verify that the file is present in the Oracle Trace admin directory and that file protections allow access. If that fails, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The registration ID string supplied is invalid (probably too long).
Action: Supply a valid registration ID string.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Oracle Trace was unable to open its admin REGID.DAT file.
Action: Verify that the file is present in the Oracle Trace admin directory and that file protections allow access. If that fails, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The collection name has already been used and currently exists in the Oracle Trace admin COLLECT.DAT file. If the collection is inactive, this record will eventually be discarded.
Action: Specify a new collection name or force clean up of Oracle Trace admin .dat files by executing the otrccref image (once all processes have detached from these files).
Cause: User may not have write access to the directory where Oracle Trace admin .dat files are to be located, for example, $ORACLE_HOME/otrace/admin; or available disk space may be insufficient; or an instrumented process may still be accessing the .dat files.
Action: Provide access to the directory or additional free disk space. Verify that no processes are currently using Oracle Trace .dat files, for example, the database. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: For Oracle Trace operations such as "start collection", a user-supplied collection name is required, but may not have been provided.
Action: Make sure a collection name has been supplied. If so, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Oracle Trace Collection Services cannot access the admin collect.dat file in the expected location, that is $ORACLE_HOME/admin.
Action: Verify that the Oracle Trace admin collect.dat file exists and check for file protection problems. Also check directory protections, definition for ORACLE_HOME, and Oracle Trace parameter settings. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This condition is used to signal the completion of an Oracle Trace CLI job (that is, executed by Oracle Intelligent Agent on behalf of Oracle Trace). It is not an error.
Action: No action required.
Cause: Used by Oracle Trace command-line interpreter (CLI); part of normal, successful Oracle Trace job output.
Action: No action required.
Cause: User-provided job ID for CLI start and stop collection functions was not supplied; else internal Oracle Trace error.
Action: If Oracle Trace CLI was executed without specifying job ID value, try operation again with the correct command-line parameters. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is a success return status for the Oracle Trace CLI "check collection" operation, assuming the specified collection exists and is active.
Action: No action required.
Cause: This is a success message.
Action: No action required.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is a success message.
Action: No action required.
Cause: Oracle Trace CLI was provided with incorrect or incomplete command verb, or no command at all.
Action: Provide complete CLI command verb, for example "start" (plus other required command-line parameters) to start a collection.
Cause: More than the maximum number of restriction records was provided as input by CLI user (maximum is currently 5).
Action: Reduce input restrictions provided as CLI parameters.
Cause: The ORACLE_HOME environment variable has not been defined and is required by the Oracle Trace CLI.
Action: Define ORACLE_HOME and rerun CLI function.
Cause: This is a success message.
Action: No action required.
Cause: This is a success message.
Action: No action required.
Cause: For Oracle database access, for example, to format Oracle Trace data, the user must supply a valid database account user name, password, and database service name to form a complete Oracle database connect string.
Action: Supply the missing connect string component.
Cause: If the regid.dat file was not accessible at collection activation, Oracle Trace could not activate the collection. This is an internal error.
Action: Verify that the regid.dat file is accessible, otherwise contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: An error occurred while translating the environment logical ORACLE_HOME.
Action: Check your ORACLE_HOME definition and that the otrace/admin directory exists and is accessible. Otherwise, see your database administrator (DBA).
Cause: An error occurred while determining the path to the Oracle Trace admin directory.
Action: Check your ORACLE_HOME definition and that the otrace/admin directory exists and is accessible. Otherwise, see your database administrator (DBA).
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The maximum file size specified when the collection was started has been exceeded.
Action: No action required. For future collections, increase the maximum file size.
Cause: Signaled by Oracle Trace CLI if an error occurred while attempting to delete a collection's .cdf 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.
Action: Verify that the file exists; fix protection if necessary. If database processes have the file held open, wait for the processes to release the files (on the next database action for each process).
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.
Action: Verify that the file exists; fix protection if necessary. If database processes have the file held open, wait for the processes to release the files (on the next database action for each process).
Cause: This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This error can occur if you provided Oracle Trace CLI with incorrect input parameters. Otherwise, this is an Oracle Trace internal error.
Action: Correct the CLI input parameters, otherwise contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The Oracle Trace CLI image otrccol does not exist in ORACLE_HOME/bin, or access to it is denied.
Action: If the image exists, set protection to allow execution. If the image does not exist, check with the person responsible for Oracle installations on that system. If you have multiple ORACLE_HOME definitions, verify that the correct ORACLE_HOME is being used. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is a success message.
Action: No action required.
Cause: This is a success message.
Action: No action required.
Cause: This message indicates that the user has explicitly stopped a collection before its scheduled completion, or the collection has been terminated due to specified maximum file size having been reached (or a full disk), or some error condition has forced the collection to stop.
Action: If the user did not stop the collection, check disk use. Check maximum file size in INIT.ORA file or Oracle Trace Manager. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is a success message.
Action: No action required.
Cause: This is a success message.
Action: No action required.
Cause: Error occurred during Oracle Trace CLI database access.
Action: See EPC_ERROR.LOG file for additional failure information and error messages. If the problem persists, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Invalid facility context argument was passed to the Oracle Trace API routine, for example, EPC_EVENT.
Action: Supply a facility context argument.
Cause: This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: An attempt was made to access collection files created by an incompatible version of Oracle Trace.
Action: Use the correct version of Oracle Trace to access the collection files.
Cause: An error occurred in setting the collection status to active in the collect.dat file. This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The maximum number of collections for this product was exceeded. The current maximum is 5 collections.
Action: Retry the collection later.
Cause: This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Error occurred while adding record for this instrumented product to the FACILITY.DAT file.
Action: Verify the existence and accessibility of the FACILITY.DAT file. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Error occurred during creation of FACILITY.DAT file by the OTRCCREF image.
Action: Verify that the Oracle Trace admin directory exists and is accessible, and that the FACILITY.DAT file is not currently in use.
Cause: This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Error occurred while opening the FACILITY.DAT file.
Action: Verify that the FACILITY.DAT file is accessible, else contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. Have the .cdf and .dat files available. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Oracle Trace could not write data to the report output file, for example, col_name*.txt.
Action: Check that there is enough disk space and that file protections are correct.
Cause: The Oracle Trace reporter could not determine the size required for the local representation of dates.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The Oracle Trace reporter encountered a seek error while looking for the first product registration ID.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The Oracle Trace reporter could not find the specified product.
Action: Contact Oracle Support Services. Have the collection definition file (.cdf) and data (.dat) files available. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The Oracle Trace reporter found an item record before an event record.
Action: Contact Oracle Support Services. Have the collection definition file (.cdf) and data (.dat) files available. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The Oracle Trace reporter could not find the event record.
Action: Contact Oracle Support Services. Have the collection definition file (.cdf) and data (.dat) files available. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: A memory allocation error has occurred.
Action: Check the use of memory in your application. If there is no problem there, Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: A memory allocation error (calloc) has occurred.
Action: Check the use of memory in your application. If there is no problem there, Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The data file could not be found, probably because it was deleted and no longer exists.
Action: No action required.
Cause: The collection definition file (.cdf) could not be found, or could not be accessed due to file protection.
Action: No action required if the .cdf file no longer exists. If the .cdf file exists, verify the file protections.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. Have the collection definition file (.cdf) and data (.dat) files available. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. Have the collection definition file (.cdf) and data (.dat) files available. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is not an error. This information is used to output arbitrary text strings.
Action: No action required.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. Have the collection definition file (.cdf) and data (.dat) files available. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. Have the collection definition file (.cdf) and data (.dat) files available. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The attempt to determine the file size failed. This is an Oracle Trace internal error.
Action: Contact Oracle Support Services. Have the .cdf and .dat files available. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Oracle Trace has encountered an error while trying to read a file.
Action: If the file protections are correct and the problem still occurs, then this is an Oracle Trace internal error. Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Oracle Trace has encountered an error while trying to write a file.
Action: If the file protections are correct and the problem still occurs, then this is an Oracle Trace internal error. Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Oracle Trace has encountered an error while trying to read a file.
Action: If the file protections are correct and the problem still occurs, then this is an Oracle Trace internal error. Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Oracle Trace could not extend the file.
Action: Check that there is sufficient disk space and that file protections are set correctly.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The data file has protection problems or is full.
Action: Correct any protection problems if necessary. Otherwise, this is an Oracle Trace internal error and you should contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace Reporter error that indicates there could be protection problems on the .dat file or that there were no processes running from which to collect data.
Action: Check the protections on the .dat file. Otherwise, no action required.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
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.
Action: If necessary, update the Oracle Trace format table definitions in the target database by running the Oracle Trace formatter SQL scripts. However, it may be necessary to use a different database and or database user account for formatted data in the situation where a newer version of Oracle Trace has already formatted data to a database or database user account. Incompatible older Oracle Trace versions will never be able to format to this same database or database user account due to format table differences. See the Oracle Trace User's Guide for the explanation about the otrcfmt image.
Cause: This error could indicate a protection problem on the message file, for example, the EPCUS.MSB file.
Action: Check that the message file protections are correct. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is an Oracle Trace internal error. It should never be returned.
Action: Contact Oracle Support Services. Have the collection definition file (.cdf) and data (.dat) files available. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: If you are running Oracle Trace CLI from the command line to start a collection, then this error indicates that required information has not been provided in the CLI input parameter file. In other cases, this is an Oracle Trace internal error and should never be returned.
Action: Correct the CLI input parameter file, if you are running the CLI in command-line mode. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This indicates that the Process report could not be created. It could be due to a disk space or protection problem.
Action: Check that there is enough disk space and that protections are set correctly. Otherwise, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The Oracle Trace Report command was incorrectly used.
Action: Resubmit the command using the correct parameters in the correct order.
Cause: The Oracle Formatter could not find the specified collection ID in the data file.
Action: Rerun the format and specify the -f option to format the entire data file.
Cause: This is an invalid format command.
Action: Reenter the format command.
Cause: An attempt was made to format a data file that contains no new data.
Action: No action required.
Cause: There are several causes for this message. It could be just an informational message and not an error message if the user canceled the Format operation.
Action: Check the EPC_ERROR.LOG for other underlying error messages, for example, failure to resolve database service name supplied to the formatter. (This could mean that the TNSNAMES.ORA file on the local node where the format code is executing does not contain an entry for the specified format database.) If the collection ID given in the error message is less than 0, then format processing probably did not get as far as accessing the format database. Retry the Format command and specify the -f parameter (that is, full rather than partial format) to reformat data that had already been formatted before the abort took place.
Cause: The Oracle Trace Format operation was stopped.
Action: No action required.
Cause: The file name specified already exists.
Action: Supply a new file name, that is, collection name.
Cause: An attempt was made to add a duplicate callback routine for the same cross-product item.
Action: Correct the code.
Cause: An attempt was made to remove a non-existent cross-product callback routine.
Action: Correct the code.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
