Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
The following critical error messages are generated by the Oracle Trace Manager.
Cause: A problem was encountered while accessing the database.
Action: Depends on additional information supplied in the error message itself.
Cause: A problem was encountered while trying to submit a job to Oracle Enterprise Manager.
Action: Contact Oracle Worldwide Customer Support.
Cause: A problem was encountered while creating/writing to the collection's input file.
Action: Contact Oracle Worldwide Customer Support.
Cause: A problem was encountered while trying to find the Oracle Trace job tcl file.
Action: Contact Oracle Worldwide Customer Support.
Cause: A problem was encountered while accessing the Oracle Enterprise Manager discovery cache.
Action: Verify that Oracle Enterprise Manager is running and that the version is compatible with the version of Oracle Trace.
Cause: A problem was encountered while trying to register the Oracle Trace active object.
Action: Verify that the Oracle Trace registry entries are correct.
Cause: The database specified by the user was not found in the Oracle Enterprise Manager discovery cache.
Action: None. This is a warning.
Cause: Database name required by user, but was not supplied.
Action: Enter a database name.
Cause: Username required by user, but was not supplied.
Action: Enter a username.
Cause: Password required by user, but was not supplied.
Action: Enter a password.
Cause: Oracle Enterprise Manager must be running.
Action: Start Oracle Enterprise Manager and restart Oracle Trace.
Cause: Error connecting to the Oracle Trace repository.
Action: Determine whether or not the problem is specific to Oracle Trace. If it is, attempt to connect to a newly created repository. If there is still a problem with the new repository, contact Oracle Worldwide Customer Support.
Cause: A problem was encountered during Oracle Enterprise Manager discovery.
Action: Verify that Oracle Enterprise Manager discovery is still functioning properly. If it is, contact Oracle Worldwide Customer Support.
Cause: A problem was encountered while communicating with Oracle Enterprise Manager via OLE. Possibly, the wrong console of Oracle Enterprise Manager console is loaded.
Action: Check that the versions of Oracle Enterprise Manager and Oracle Trace match. If they do, contact Oracle Worldwide Customer Support.
Cause: Bad versions of OLE DLL's.
Action: Reinstall product.
Cause: A problem was encountered during Oracle Trace discovery.
Action: Oracle Enterprise Manager/Oracle Trace versions are incompatible.
Cause: Prompt to stop Oracle Trace discovery.
Action: None.
Cause: Start collection failed.
Action: Retry starting the collection.
Cause: A problem was encountered while stopping a collection.
Action: Retry stopping the collection.
Cause: A problem was encountered while displaying information in the Navigator.
Action: Refresh the screen or restart the Oracle Trace Manager.
Cause: Oracle Enterprise Manager is not running but user specified administration mode on the command line.
Action: None. Only Product create/edit will be enabled for the user.
Cause: Oracle Trace was unable to find the language specific resource DLL.
Action: Assuming a correct installation, this is an internal problem. Contact Oracle Worldwide Customer Support.
Cause: Oracle Enterprise Manager discovery error.
Action: This is an internal problem. Contact Oracle Worldwide Customer Support.
Cause: At least one event set must be specified in the Collection wizard.
Action: Specify at least one event set in the Collection wizard.
Cause: A duration must be specified in the Collection wizard.
Action: Specify a duration in the Collection wizard.
Cause: If no nodes have been discovered, prompt user to perform discovery at product startup.
Action: Perform discovery to avoid getting this message again.
Cause: Only one instance of Oracle Trace can run on a client.
Action: Do not attempt to run more than one instance of Oracle Trace on the client.
Cause: Either a collection job failed during auto-format or a stand-alone format job failed.
Action: Retry the format. If it still fails, contact Oracle Worldwide Customer Support.
Cause: User is attempting to terminate the deletion of collection files.
Action: Press appropriate button.
Cause: User is attempting to terminate the deletion of a collection's formatted data.
Action: Press appropriate button.
Cause: A problem was encountered retrieving the current version from Oracle Enterprise Manager.
Action: This is an internal problem. Contact Oracle Worldwide Customer Support.
Cause: A problem was encountered attempting to read the current version from Oracle Trace Manager.
Action: This is an internal problem. Contact Oracle Worldwide Customer Support.
Cause: The database versions of Oracle Trace and Oracle Enterprise Manager are incompatible.
Action: Upgrade the Oracle Trace repository.
Cause: The Oracle Trace version is out of sync with the repository.
Action: This is an internal problem. Contact Oracle Worldwide Customer Support.
Cause: The Oracle Trace Manager was unable to insert data into the Oracle Trace repository.
Action: Save the text from the error message box and contact Oracle Worldwide Customer Support.
Cause: The Oracle Trace Manager was unable to update data into the Oracle Trace repository.
Action: Save the text from the error message box and contact Oracle Worldwide Customer Support.
Cause: The Oracle Trace Manager was unable to delete data from the Oracle Trace repository.
Action: Save the text from the error message box and contact Oracle Worldwide Customer Support.
Cause: The Oracle Trace Manager was unable to select data from the Oracle Trace repository.
Action: Save the text from the error message box and contact Oracle Worldwide Customer Support.
Cause: A collection name cannot exceed 16 characters.
Action: Modify the collection name so that it is not greater than 16 characters.
Cause: A collection name must be unique.
Action: Modify the collection name so that it is unique.
Cause: A collection output filename must not exceed 8 characters.
Action: Modify the collection output filename so it is not greater than 8 characters.
Cause: A collection output filename must be specified.
Action: Modify the collection output filename.
Cause: User is attempting to terminate the deletion of a collection.
Action: Terminate the action or continue.
Cause: A valid collection name is required.
Action: Enter a valid collection name to continue.
Cause: The user entered over 2000 characters into the description field.
Action: Truncate the description text.
Cause: One of the jobs submitted during the deletion of the collection failed.
Action: User can indicate that collection object should be deleted from repository.
Cause: Either the repository needs to be updated or the repository scripts are corrupt.
Action: Either update the repository or contact Oracle Worldwide Customer Support if the scripts are corrupt.
Cause: There may be an internal problem with the schedule control.
Action: Contact Oracle Worldwide Customer Support.
Cause: A non-alphanumeric character was used in the name.
Action: Use only alphanumeric characters in the name.
Cause: An error occurred while trying to set a node and all its children (i.e. installations and products on that node) to inactive during discovery. Most likely, a database error occurred during the database update.
Action: More information may be available from the message box about a possible database error. Either use this information to determine a course of action or contact Oracle Worldwide Customer Support.