Release 9.2.0
Part Number A96671-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle Enterprise Manager Messages Manual Release 9.2.0 Part Number A96671-01 |
|
This chapter contains probable causes and corrective actions for error messages with the following prefixes:
| Messages | Page |
|---|---|
When contacting Oracle Support Services about Oracle Trace, you must have the following information available:
The following error messages are a subset of the Oracle Trace Collection Services messages that you may see in the context of the Oracle Trace Manager. For a full listing of the Oracle Trace Collection Services messages, refer to Oracle9i Database Error Messages.
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: 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: 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 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: 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 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: None. 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: 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: 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: None.
Cause: Used by Oracle Trace command-line interpreter (CLI); part of normal, successful Oracle Trace job output.
Action: None required.
Cause: This is a success return status for the Oracle Trace CLI "check collection" operation, assuming the specified collection exists and is active.
Action: None required.
Cause: This is a success message.
Action: None 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: None required.
Cause: This is a success message.
Action: None required.
Cause: This is a success message.
Action: None 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: 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: 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, call Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: This is a success message.
Action: None required.
Cause: This is a success message.
Action: None 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: None required.
Cause: This is a success message.
Action: None 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: 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: 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. 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 Enterprise Manager Oracle Trace User's Guide for the explanation about the otrcfmt image.
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 error.
Action: Refer to the EPC_ERROR.LOG for the specific error number.
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.
The following error messages are generated by Oracle Trace Manager.
Cause: A problem was encountered while accessing the database.
Action: Depends on additional information supplied in the error message itself. Run the Oracle Trace log window or look in the Oracle Enterprise Manager Job output window for more detail.
Cause: A problem was encountered while trying to submit a job to Oracle Enterprise Manager.
Action: Verify that Oracle Enterprise Manager and Oracle Intelligent Agent are running on the target node. Also, verify that you have set the Oracle Enterprise Manager preferences for the node specified. Attempt to use Oracle Enterprise Manager to submit a test job to the node in question.
Cause: A problem was encountered while creating or writing to the collection's input file.
Action: Verify that the Oracle Enterprise Manager preferences node connection specified for the target node has permission to write to the Oracle Trace admin/cdf directory in the ORACLE_HOME. Verify that adequate free disk space is available.
Cause: A problem was encountered while trying to find the Oracle Trace job tcl file.
Action: Verify that you have file-read access to the ORACLE_HOME you are using. If you do have file-read access, run Oracle Trace Manager with the logging option and review the log information. If the information logged does not indicate the problem, save the logged text and contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
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. If necessary, restart Oracle Enterprise Manager and 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. If the entries are not correct, reinstall Oracle Trace.
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 tables.
Action: Verify that the server is running. Verify that the version of Oracle Enterprise Manager and Oracle Trace are compatible. If there is still a problem, restart both Oracle Enterprise Manager and Oracle Trace, and run Oracle Trace with the logging option. Review the log information. If the information logged does not indicate the problem, save the logged text and contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: A problem was encountered during Oracle Enterprise Manager discovery.
Action: Verify that Oracle Enterprise Manager discovery is still functioning correctly. If it is, restart both Oracle Enterprise Manager and Oracle Trace, and run Oracle Trace with the logging option. Review the log information. If the information logged does not indicate the problem, save the logged text and contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: A problem was encountered while communicating with Oracle Enterprise Manager by way of OLE. Possibly, an incompatible version of the Oracle Enterprise Manager console is loaded.
Action: Check that the versions of Oracle Enterprise Manager and Oracle Trace match. If they do, restart both Oracle Enterprise Manager and Oracle Trace, and run Oracle Trace with the logging option. Review the log information. If the information logged does not indicate the problem, save the logged text and contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Bad versions of OLE DLL's.
Action: Reinstall the Oracle Trace product.
Cause: A problem was encountered during Oracle Trace discovery.
Action: Check that the versions of Oracle Enterprise Manager and Oracle Trace match. If they do, restart both Oracle Enterprise Manager and Oracle Trace, and run Oracle Trace with the logging option. Review the log information. If the information logged does not indicate the problem, save the logged text and contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Prompt to stop Oracle Trace discovery.
Action: None.
Cause: Start collection failed. Occurs in combination with server errors.
Action: Look for additional errors in the Oracle Trace logging window and the Oracle Enterprise Manager Job output window. These errors may help identify the problems.
Cause: A problem was encountered while stopping a collection. Occurs in combination with server errors.
Action: Look for additional errors in the Oracle Trace logging window and the Oracle Enterprise Manager Job output window. These errors may help identify the problems.
Cause: A problem was encountered while displaying information in the Navigator.
Action: Refresh the screen or restart Oracle Trace Manager.
Cause: Oracle Enterprise Manager is not running but user specified administration mode on the command line.
Action: None. Only Product create or edit will be enabled for the user.
Action: Assuming a correct installation, this is an internal problem. Contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Oracle Enterprise Manager discovery error.
Action: Verify that Oracle Enterprise Manager discovery is still functioning correctly. If it is, restart both Oracle Enterprise Manager and Oracle Trace, and run Oracle Trace with the logging option. Review the log information. If the information logged does not indicate the problem, save the logged text and contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
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, prompts user to perform discovery at product startup.
Action: Perform product discovery to avoid receiving 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: Verify that valid preferred credentials were supplied for the format operation. Also, verify that a tnsnames entry for the destination node exists for the server where the collection occurred. Retry the format. If it still fails, restart both Oracle Enterprise Manager and Oracle Trace, and run Oracle Trace with the logging option. Review the Oracle Trace log information and the Oracle Enterprise Manager Job output. If the information logged does not indicate the problem, save the logged text and contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
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 while retrieving the current version from Oracle Enterprise Manager.
Action: Verify that Oracle Enterprise Manager discovery is still functioning correctly. If it is, restart both Oracle Enterprise Manager and Oracle Trace, and run Oracle Trace with the logging option. Review the log information. If the information logged does not indicate the problem, save the logged text and contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: A problem was encountered while attempting to read the current version from the Oracle Trace repository tables.
Action: Verify that the server containing your Oracle Enterprise Manager repository is working correctly. If it is, restart both Oracle Enterprise Manager and Oracle Trace, and run Oracle Trace with the logging option. Review the log information. If the information logged does not indicate the problem, save the logged text and contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: The database versions of Oracle Trace and Oracle Enterprise Manager are incompatible.
Action: Upgrade the Oracle Trace repository tables.
Cause: The Oracle Trace version is out of sync with the Oracle Enterprise Manager repository.
Action: Run the SQL command: Select * from epc_cli_version; to identify the version of the Oracle Trace repository tables. If the version of Oracle Trace is newer than the version of your Oracle Trace repository tables, upgrade the Oracle Trace repository tables. An older version of Oracle Trace will not work with a repository created or upgraded to a newer version.
Cause: Oracle Trace Manager was unable to insert data into the Oracle Trace repository tables.
Action: Verify that the server containing your Oracle Enterprise Manager repository is functioning correctly. Verify that the version of Oracle Trace you are using matches the version of your repository. If the version of Oracle Trace matches the version of the repository, restart both Oracle Enterprise Manager and Oracle Trace, and run Oracle Trace with the logging option. Review the log information. If the information logged does not indicate the problem, save the logged text and contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Oracle Trace Manager was unable to update data into the Oracle Trace repository tables.
Action: Verify that the server containing your Oracle Enterprise Manager repository is functioning correctly. Verify that the version of Oracle Trace you are using matches the version of your repository. If the version of Oracle Trace matches the version of the repository, save the text from the error message box and contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Oracle Trace Manager was unable to delete data from the Oracle Trace repository tables.
Action: Verify that the server containing your Oracle Enterprise Manager repository is functioning correctly. Verify that the version of Oracle Trace you are using matches the version of your repository. If the version of Oracle Trace matches the version of the repository, restart both Oracle Enterprise Manager and Oracle Trace, and run Oracle Trace with the logging option. Review the log information. If the information logged does not indicate the problem, save the logged text and contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: Oracle Trace Manager was unable to select data from the Oracle Trace repository tables.
Action: Verify that the server containing your Oracle Enterprise Manager repository is functioning correctly. Verify that the version of Oracle Trace you are using matches the version of your repository. If the version of Oracle Trace matches the version of the repository, restart both Oracle Enterprise Manager and Oracle Trace, and run Oracle Trace with the logging option. Review the log information. If the information logged does not indicate the problem, save the logged text and contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
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 file name must not exceed 8 characters.
Action: Modify the collection output file name so it is not greater than 8 characters.
Cause: A collection output file name must be specified.
Action: Modify the collection output file name.
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 the collection object should be deleted from the Oracle Trace repository tables.
Cause: Either the Oracle Trace repository tables need to be updated or the repository scripts are corrupt.
Action: Update the Oracle Trace repository tables. If you are still having problems, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: There may be an internal problem with the schedule control.
Action: Verify that Oracle Enterprise Manager is running. If the problem persists, restart Oracle Enterprise Manager, Oracle Intelligent Agent, and Oracle Trace. Run Oracle Trace with the logging option. Review the log information. If the information logged does not indicate the problem, save the logged text and contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
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 Oracle Trace logging window about a possible database error. Use this information to determine a course of action and restart Oracle Trace. If the problem persists, contact Oracle Support Services. See the section titled "Contacting Oracle Support Services About Oracle Trace" for additional information.
Cause: An error occurred while attempting to find an Oracle Trace user in the Oracle Trace repository user and ID table. Most likely an upgrade or create script error occurred while creating an identity for this user in the Oracle Trace repository tables.
Action: Examine the epc_cli_rep_users repository table to locate the given user. If the user is not found, drop the Oracle Trace repository tables for this user and recreate the user using the vobsh utility.
Cause: Oracle Trace did not locate a running version of the Oracle Enterprise Manager Console Bridge and attempted to instantiate one. Oracle Trace was unable to instantiate the Oracle Enterprise Console Bridge.
Action: Start the Oracle Enterprise Manage console manually and restart Oracle Trace.
Cause: The database selected from the list of databases available for formatting is specified as host:port:sid, rather than a service name. (The repository database appears as host:port:sid if the node on which it resides has not been discovered in Trace.) If the service name is not available, the long service descriptor will be sent to the Trace formatter mechanism on the collection node. Collection services for Oracle Server release 8.1.6 or later are required to handle a long service descriptor.
Action: Discover (in the Enterprise Manager console and Trace) the node on which the database resides. This causes the service name to be displayed in the list of databases available for formatting. If the release of the Oracle Server is not 8.1.6 or later, then the service name must also be defined in the TNSNAMES.ORA file under the Oracle home where the collection is being performed.
Cause: The ORACLE_TRACE_ENABLE parameter, located in the INIT.ORA file for the database which was selected as the target for this collection operation, is not set to TRUE.
Action: Edit the INIT.ORA file for the given database and set the ORACLE_TRACE_ENABLE parameter to TRUE. After modifying the INIT.ORA file, stop and restart the database.
Cause: An attempt was made to add an item to an event which already contains that item.
Action: Do not try to add the item to the event.
Cause: The user attempted to add or modify an event such that its event number is not unique within the product.
Action: Choose a different event number.
Cause: The user attempted to add or modify an item such that its item number is not unique within the product.
Action: Choose a different number.
Cause: An error occurred while writing an .fdf file during Product Create or Edit.
Action: Check that the path name is correct.
Cause: The user has removed an event set and is being warned that the corresponding .fdf file will not be automatically deleted.
Action: Remove the .fdf file manually.
Cause: An error occurred while reading an .fdf file during Product Create or Edit.
Action: The .fdf file may be corrupt; try reading another .fdf file.
Cause: Multiple .fdf files were read, but described event sets for different products.
Action: Verify that the .fdf files read in at one time during Product Edit are all for the same product.
Cause: The item definitions from two different .fdf files for the same product differ. They should be identical if all .fdf files for the product are in sync.
Action: Read in the .fdf files individually to identify the differences for the erroneous item. Correct the file containing the erroneous item before attempting to read in all the product files at once.
Cause: The event definitions from two different .fdf files for the same product differ. They should be identical if all .fdf files for the product are in sync.
Action: Read in the .fdf files individually to identify the differences for the erroneous event. Correct the file containing the erroneous event before attempting to read in all the product files at once.
Cause: The user attempted to exit a dialog box without supplying all needed information.
Action: Fill in the specified field before attempting to exit the dialog box.
Cause: The specified item number falls into a range that is not allowed for user-defined items.
Action: Choose a different item number.
Cause: The user tried to add an item with a non-unique item name; item name must be unique within a product.
Action: Use a different item name.
Cause: The user tried to add an event with a non-unique event name; event name must be unique within a product.
Action: Use a different event name.
Cause: The user tried to add an event set with a non-unique name; event set name must be unique within a product.
Action: Use a different event set name.
Cause: The user tried to create or edit an event such that it contains no items. An event must contain at least one item.
Action: Add an item to the event.
Cause: The user tried to create or edit an event set such that it contains no events. An event set must contain at least one event.
Action: Add an event to the event set.
Cause: The user tried to save a product definition file that contains no events.
Action: Must add at least one event to the product definition prior to saving.
Cause: The event set file already exists. Oracle Trace does not allow the overwriting of event set files.
Action: Save the event set to a new file by modifying the Event Set File Path or delete the existing event set file.
Cause: Failed to connect to a server with the given username and password.
Action: Verify that the username and password are correct for the server, and try again.
Cause: An error occurred while reading an .fdf file during Product Create or Edit.
Action: Verify that one of the files being edited contains the ALL Class.
Cause: Multiple .fdf files were read, and a file references an event that is missing from the ALL class.
Action: Verify that the .fdf file containing the ALL class matches the .fdf file being read.
Cause: The user tried to add an event with an invalid event name. Event names can contain any combination of characters a to z and 0 to 9. The maximum length is 15 characters.
Action: Enter a valid event name.
Cause: The user tried to add an item with an invalid item name. Item names can contain any combination of characters a to z and 0 to 9. The maximum length is 15 characters.
Action: Enter a valid name.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
