/
/ Copyright © 1994, 1998,  Oracle Corporation.  All rights reserved.
/
/ The Programs (which include both the software and documentation)
/ contain proprietary information of Oracle Corporation; they are 
/ provided under a license agreement containing restrictions on use 
/ and disclosure and are also protected by copyright, patent and 
/ other intellectual and industrial property laws. Reverse 
/ engineering, disassembly or decompilation of the Programs is 
/ prohibited.
/
/ The information contained in this document is subject to change 
/ without notice. If you find any problems in the documentation, 
/ please report them to us in writing. Oracle Corporation does not 
/ warrant that this document is error free. Except as may be 
/ expressly permitted in your license agreement for these Programs, 
/ no part of these Programs may be reproduced or transmitted in any 
/ form or by any means, electronic or mechanical, for any purpose, 
/ without the express written permission of Oracle Corporation.
/
/ If the Programs are delivered to the US Government or anyone 
/ licensing or using the Programs on behalf of the US Government, 
/ the following notice is applicable:
/
/ RESTRICTED RIGHTS NOTICE
/
/ Programs delivered subject to the DOD FAR Supplement are 
/ ’commercial computer software’ and use, duplication and disclosure 
/ of the Programs including documentation, shall be subject to the 
/ licensing restrictions set forth in the applicable Oracle license 
/ agreement. Otherwise, Programs delivered subject to the Federal 
/ Acquisition Regulations are ’restricted computer software’ and use, 
/ duplication and disclosure of the Programs shall be subject to the 
/ restrictions in FAR 52.227-19, Commercial Computer Software - 
/ Restricted Rights (June, 1987). Oracle Corporation, 500 Oracle 
/ Parkway, Redwood City, CA 94065.
/
/ The Programs are not intended for use in any nuclear, aviation, 
/ mass transit, medical, or other inherently dangerous applications. 
/ It shall be the licensee’s responsibility to take all appropriate 
/ fail-safe, back up, redundancy and other measures to ensure the 
/ safe use of such applications if the Programs are used for such 
/ purposes, and Oracle disclaims liability for any damages caused 
/ by such use of the Programs.
/ 
/ Oracle is a registered trademark of Oracle Corporation. All other 
/ company or product names mentioned are used for identification 
/ purposes only and may be trademarks of their respective owners.
/                                                                             
/ 
/  File		 : epcus.msg 
/  Product	 : otrace
/  Facility	 : tra
/ 
/  Language      : American
/  Character set : US7ASCII
/
/  Abstract:       Contains error strings, prompts,  and constants   
/ 	           to be used by apptrace application.  
/
/
/  Note to Doc Writer: In September 1998 all messages were checked 
/  to see if they were still being used as of Oracle Server release 
/  8.1.5. If the messages were no longer being used, they were no 
/  longer being documented. All messages that are documented are 
/  marked as such and in which manual(s) they are located. All 
/  other messages are leftovers from other releases of Oracle 
/  Trace Collection Services.
/
/
/  History:	   
/
/  jmcdonal       27-Jan-1999 - For 806: add otrcfmt -p option to 343
/  jgosseli       01-Oct-1998 - Corrected copyright information 
/                               and edited messages.
/  jmcdonal       06-Mar-1998 - Add required NLS + UI comments
/  xxu            21-Nov-1997 - add one more flag -d for otrcrep usage
/  xxu            22-Oct-1997 - Add reg/unreg callback errors
/  mjlamber       31-May-1996 - Add cmd-line parm to otrcrep
/  C. Mrozienski  18-Apr-1996 - move catalog errors here
/  C. Mrozienski  17-Apr-1996 - add load resource dll error
/  E.Brown        24-Jan-1996 - add File Exist error 	
/  C. Mrozienski  02-Dec-1995 - add EPCESVR* error text
/  C. Mrozienski  26-Nov-1995 - Add epc_s_forafpath error text
/  G Lavash       11-oct-1195 - sched messages
/  C. Mrozienski   6-Oct-1995 - Add new EPCESD* errors for epcsdirf.c
/  J.McDonald	   1-Sep-1995 - Add new PRO file errors for epcpro.c
/  J.McDonald	  30-Aug-1995 - Add new COL file errors for epccol.c
/  J.McDonald	  21-Aug-1995 - Add new Reg ID errors for epcrid.c
/  G. Lava        07-Apr-1995   reporter errors
/  C. Mrozienski  17-Mar-1995 - Added epc_s_badminute & epc_s_badhour
/  E.Simart	  31-Jan-1995 - Replaced OSF Version by OS version
/  ebrown	  20-Jan-1995 - Creation 
/ 
/ 
/ 
/===========================================================================================================
/0001 .. 0199
/===========================================================================================================

1,0,"invalid event flags passed" 
// *Comment: mnemonic: epc_s_badevntflgs
// Message documented only in Server Error Messages manual
//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 Worldwide Customer Support.

2,0,"invalid product ID passed"
// *Comment: mnemonic: epc_s_badfac
// Message documented only in Server Error Messages manual
//Cause:  An invalid product ID was passed.
//Action:  Supply a valid product ID between 1 and 999999.

3,0,"invalid product version passed"
// *Comment: mnemonic: epc_s_badfacver
// Message documented only in Server Error Messages manual
//Cause:  An invalid product version number was passed.
//Action:  Supply a product version number not greater than 11 
//bytes in length.

4,0,"invalid product registration ID passed"
// *Comment: mnemonic: epc_s_badregid
// Message documented only in Server Error Messages manual
//Cause:  An invalid product registration ID was passed.
//Action:  Supply a product registration ID not greater than 256 
//bytes in length.

// NLS_DO_NOT_TRANSLATE [5,5]

5,0,"invalid vendor ID passed"
// *Comment: mnemonic: epc_s_badvendor
// Message not used in Oracle Trace Collection Services release 8.1.5

6,0,"collection has been disabled"
// *Comment: mnemonic: epc_s_disabled
// Message documented only in Server Error Messages manual
//Cause:  The collection of Oracle Trace data has been disabled 
//through the use of the EPC_DISABLED environment variable.
//Action:  No action required.

7,0,"product version required"
// *Comment: mnemonic: epc_s_facverreq
// Message documented only in Server Error Messages manual
//Cause:  A product version number was not specified.
//Action:  Specify a product version number.

8,0,"epc_init routine called twice for this product"
// *Comment: mnemonic: epc_s_init2
// Message documented only in Server Error Messages manual
//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.

// NLS_DO_NOT_TRANSLATE [9,13]

9,0,"no data capture file exists"
// *Comment: mnemonic: epc_s_nodcfexists
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  There is no data file for the collection.
//Action:  No action required.

10,0,"no registrar process exists on this node"
// * Comment: mnemonic: epc_s_noregexists
// Message not used in Oracle Trace Collection Services release 8.1.5

11,0,"Oracle Trace software not installed"
// * Comment: mnemonic: epc_c_notinstall
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  The Oracle Trace software is not installed.
//Action:  Install the Oracle Trace software.

12,0,"registrar is not responding within time set by EPC_BE_REGTIMEOUT variable"
// * Comment: mnemonic: epc_s_regtimeout
// Message not used in Oracle Trace Collection Services release 8.1.5

13,0,"no message list"
// * Comment: mnemonic: epc_s_nomsglist
// Message not used in Oracle Trace Collection Services release 8.1.5

14,0,"no product number specified"  
// * Comment: mnemonic: epc_s_nofac
// Message documented only in Server Error Messages manual
//Cause: No product number argument was supplied to the Oracle Trace
//API routine, for example, epc_event routine.
//Action: Specify a product number.

15,0,"not enough memory"
// * Comment: mnemonic: epc_s_noheap
// Message documented only in Server Error Messages manual
//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.

// NLS_DO_NOT_TRANSLATE [16,19]

16,0,"invalid minimum event" 
// * Comment: mnemonic: epc_s_badminevent
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  The event number is less than the minimum event specified
//in the product definition file (.fdf).
//Action:  Specify a valid minimum event number.

17,0,"invalid maximum event" 
// * Comment: mnemonic: epc_s_badmaxevent
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  The event number is greater than the maximum event specified
//in the product definition file (.fdf).
//Action:  Specify a valid maximum event number.

18,0,"product added to the list"
// * Comment: mnemonic: epc_s_facadded
// Message not used in Oracle Trace Collection Services release 8.1.5

19,0,"Oracle Trace cannot attach to shared memory" 
// * Comment: mnemonic: epc_s_badattach
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  Oracle Trace could not attach to shared memory.
//Action:  Contact Oracle Worldwide Customer Support. 

20,0,"Oracle Trace cannot access memory" 
// *Comment: mnemonic: epc_s_badget
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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.
	
// NLS_DO_NOT_TRANSLATE [21,22]

21,0,"Oracle Trace cannot open semaphore"
// *Comment: mnemonic: epc_s_badopen
// Message not used in Oracle Trace Collection Services release 8.1.5

22,0,"product found in registrar's product block list" 
// *Comment: mnemonic: epc_s_facfound
// Message not used in Oracle Trace Collection Services release 8.1.5

23,0,"product not collecting data" 
// *Comment: mnemonic: epc_s_facnotcol
// Message documented only in Server Error Messages manual
//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. 

// NLS_DO_NOT_TRANSLATE [24,29]

24,0,"Oracle Trace cannot detach from shared memory" 
// *Comment: mnemonic: epc_s_baddettach
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  Oracle Trace cannot detach from the shared memory.
//Action:  Contact Oracle Worldwide Customer Support. 

25,0,"Oracle Trace cannot release semaphore" 
// *Comment: mnemonic: epc_s_badclose
// Message not used in Oracle Trace Collection Services release 8.1.5

26,0,"collection list found for given product number"
// *Comment: mnemonic: epc_s_colfound
// Message not used in Oracle Trace Collection Services release 8.1.5

27,0,"metric found in registrar's product block list"
// *Comment: mnemonic: epc_s_metricfound
// Message not used in Oracle Trace Collection Services release 8.1.5

28,0,"metric not found in registrar's product block list"
// *Comment: mnemonic: epc_s_metricnotfound 
// Message not used in Oracle Trace Collection Services release 8.1.5

29,0,"product not found in product block list process"
// *Comment: mnemonic: epc_s_facnotfound
// Message not used in Oracle Trace Collection Services release 8.1.5

30,0,"collection not found" 
// *Comment: mnemonic: epc_s_colnotfound
// Message documented only in Server Error Messages manual
//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.

// NLS_DO_NOT_TRANSLATE [31,34]

31,0,"collection added to collection block"
// *Comment: mnemonic: epc_s_coladded
// Message not used in Oracle Trace Collection Services release 8.1.5

32,0,"data capture file exists"
// *Comment: mnemonic: epc_s_dcfexists
// Message not used in Oracle Trace Collection Services release 8.1.5

33,0,"global mutex created for data collection file"
// *Comment: mnemonic: epc_s_mutex_init
// Message not used in Oracle Trace Collection Services release 8.1.5

34,0,"error while creating mutex"
// *Comment: mnemonic: epc_s_mutex_initerror
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error.
//Action:  Contact Oracle Worldwide Customer Support.

35,0,"illegal record length"
// *Comment: mnemonic: epc_s_illbuflen
// Message documented only in Server Error Messages manual
//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. 

36,0,"invalid event passed" 
// *Comment: mnemonic: epc_s_badevnt
// Message documented only in Server Error Messages manual
//Cause:  An invalid event number was passed.
//Action:  Supply a valid event number. 

37,0,"invalid event number" 
// *Comment: mnemonic: epc_s_noevnt
// Message documented only in Server Error Messages manual
//Cause:  A 0 was specified for the event.
//Action:  Supply a valid event number. 

38,0,"no handle specified"
// *Comment: mnemonic: epc_s_nohandl
// Message documented only in Server Error Messages manual
//Cause:  A null handle argument was specified on the start_event or 
//end_event call.
//Action:  Supply a handle address on the call.

39,0,"event specified not collecting data"
// *Comment: mnemonic: epc_s_evntnotcol
// Message documented only in Server Error Messages manual
//Cause:  The product is collecting data, but the event is not.
//Action:  No action required.

40,0,"error writing to data collection file"
// *Comment: mnemonic: epc_s_writdcf
// Message documented only in Server Error Messages manual
//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.

// NLS_DO_NOT_TRANSLATE [41,42]

41,0,"error creating thread"
// *Comment: mnemonic: epc_s_badthdcreate
// Message not used in Oracle Trace Collection Services release 8.1.5

42,0,"error detaching thread"
// *Comment: mnemonic: epc_s_badthddetach
// Message not used in Oracle Trace Collection Services release 8.1.5

43,0,"error obtaining data file lock"
// *Comment: mnemonic: epc_s_mutexlck_error
// Message documented only in Server Error Messages manual
//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. 

// NLS_DO_NOT_TRANSLATE [44,45]

44,0,"error unlocking mutex"
// *Comment: mnemonic: epc_s_mutexunlck_error
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error.
//Action:  Contact Oracle Worldwide Customer Support. 

45,0,"item is not collecting data" 
// *Comment: mnemonic: epc_s_itmnotcol
// Message not used in Oracle Trace Collection Services release 8.1.5

// UI [46,46]
46,0,"general error message"
// *Comment: mnemonic: epc_s_fail
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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 Worldwide Customer Support. 

47,0,"invalid context value passed" 
// *Comment: mnemonic: epc_s_badthread
// Message documented only in Server Error Messages manual
//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.

48,0,"no context passed; one is expected"
// *Comment: mnemonic: epc_s_nothread
// Message documented only in Server Error Messages manual
//Cause:  There was no context passed to the Oracle Trace
//API routine and one was expected.
//Action:  Pass a context.

49,0,"thread_id is not current thread"
// *Comment: mnemonic: epc_s_thread_not_cur
// Message documented only in Server Error Messages manual
//Cause:  Context to the current thread has not been set.
//Action:  Set context to the current thread.

// NLS_DO_NOT_TRANSLATE [50,52]

50,0,"invalid event record argument passed"
// *Comment: mnemonic: epc_s_badevntrec
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  An invalid event record argument was passed.
//Action:  Check the code and correct the argument value.

51,0,"registration ID does not exist"
// *Comment: mnemonic: epc_s_regid_notexists
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  An epc_remove_reg_id call was made for a registration ID 
//(regid) that does not exist. 
//Action:  Supply a valid registration ID.

52,0,"registration ID limit exceeded" 
// *Comment: mnemonic: epc_s_regid_limit_exd
// Message not used in Oracle Trace Collection Services release 8.1.5

53,0,"registration ID already exists"
// *Comment: mnemonic: epc_s_regid_exists
// Message documented only in Server Error Messages manual
//Cause:  The optional registration string specified in the epc_init 
//call is a duplicate.
//Action:  Correct the instrumented code.

54,0,"product limit exceeded"
// *Comment: mnemonic: epc_s_fac_limit_exd
// Message documented only in Server Error Messages manual
//Cause:  The limit of 5 products per collection was exceeded.
//Action:  No action required. However, you lose the connection to 
//the oldest collection.

55,0,"error opening data collection file"
// *Comment: mnemonic: epc_s_opedcf
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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 Worldwide Customer Support. 

56,0,"error opening collection definition file" 
// *Comment: mnemonic: epc_s_opecdf
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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 Worldwide Customer Support.

57,0,"invalid cross-product item number"
// *Comment: mnemonic: epc_s_badcfitem
// Message documented only in Server Error Messages manual
//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.

58,0,"epc_init call required"
// *Comment: mnemonic: epc_s_initreq
// Message documented only in Server Error Messages manual
//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.

// NLS_DO_NOT_TRANSLATE [59,59]

59,0,"event flags parameter required"
// *Comment: mnemonic: epc_s_eflgsreq
// Message not used in Oracle Trace Collection Services release 8.1.5

60,0,"data collection file required"
// *Comment: mnemonic: epc_s_datafilereq
// Message documented only in Server Error Messages manual
//Cause: The data collection file was not specified, for example, 
//for the epc_collect call.
//Action: Verify the instrumented code.

61,0,"product definition file required"
// *Comment: mnemonic: epc_s_fdffilereq
// Message documented only in Server Error Messages manual
//Cause: The product definition file (.fdf) was not specified, 
//for example, for the epc_collect call.
//Action: Verify the instrumented code.

62,0,"collection already active"
// *Comment: mnemonic: epc_s_colactive
// Message documented only in Server Error Messages manual
//Cause:  The specified collection is already active.
//Action:  No action required.

63,0,"error reading product definition file"
// *Comment: mnemonic: epc_s_fdfrderr
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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 Worldwide Customer Support.

64,0,"error creating data collection file"
// *Comment: mnemonic: epc_s_credcf
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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 Worldwide 
//Customer Support.

65,0,"error creating collection definition file"
// *Comment: mnemonic: epc_s_crecdf
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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 Worldwide 
//Customer Support. 

66,0,"error writing collection definition file"
// *Comment: mnemonic: epc_s_wrtcdf
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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 Worldwide Customer Support.

67,0,"error opening product definition file"
// *Comment: mnemonic: epc_s_opefdf
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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 Worldwide Customer Support.

68,0,"seek error in collection definition file"
// *Comment: mnemonic: epc_s_cdfseek
// Message documented only in Server Error Messages manual
//Cause:  A seek error was encountered in the collection 
//definition file (.cdf). 
//Action:  Contact Oracle Worldwide Customer Support.

69,0,"error obtaining platform/system information, e.g., OS name and version"
// *Comment: mnemonic: epc_s_ogetmach
// Message documented only in Server Error Messages manual
//Cause:  The operating system could not be identified.
//Action:  Contact Oracle Worldwide Customer Support. 

70,0,"get host name error; host cannot be identified "
// *Comment: mnemonic: epc_s_ogethost
// Message documented only in Server Error Messages manual
//Cause:  The host name could not be identified; platform-specific
//call to obtain host failed.
//Action:  Contact Oracle Worldwide Customer Support. 

71,0,"invalid maximum event specified"
// *Comment: mnemonic: epc_s_maxevent
// Message documented only in Server Error Messages manual
//Cause:  An invalid maximum event was specified.
//Action:  Supply a maximum event greater than 0 but less than 128.

72,0,"returned_eflags parameter required "
// *Comment: mnemonic: epc_s_ret_eflagsreq
// Message documented only in Server Error Messages manual
//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.

73,0,"invalid offset value specified"
// *Comment: mnemonic: epc_s_badoffset
// Message documented only in Server Error Messages manual
//Cause: This is an Oracle Trace internal error.
//Action:  Contact Oracle Worldwide Customer Support.

// NLS_DO_NOT_TRANSLATE [74,74]

74,0,"shared memory ID or file name required"
// *Comment: mnemonic: epc_s_shmemreq
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  A shared memory ID or file name was expected but not 
//found on the epc_init call.
//Action:  Supply the required information on the epc_init call.

75,0,"file name required"
// *Comment: mnemonic: epc_s_filnamreq
// Message documented only in Server Error Messages manual
//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.

76,0,"predefined_eventflags parameter required on epc_init call"
// *Comment: mnemonic: epc_s_preeflagsreq
// Message documented only in Server Error Messages manual
//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.

77,0,"invalid event key option value specified on epc_init call"
// *Comment: mnemonic: epc_s_badoption
// Message documented only in Server Error Messages manual
//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.

78,0,"feature not yet implemented "
// *Comment: mnemonic: epc_s_not_impl
// Message documented only in Server Error Messages manual
//Cause:  This feature is not yet implemented.
//Action:  Do not use this feature. No action required.

// NLS_DO_NOT_TRANSLATE [79,79]

79,0,"file append failed"
// *Comment: mnemonic: epc_s_appendfail
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  Disk space exceeded while creating the collection 
//definition file (.cdf).
//Action:  Increase disk space.

80,0,"file append seek failed"
// *Comment: mnemonic: epc_s_appendseek
// Message documented only in Server Error Messages manual
//Cause: File I/O seek to start (or end) file during append 
//operation failed. This is an Oracle Trace internal error.
//Action: Contact Oracle Worldwide Customer Support.

81,0,"append write failed"
// *Comment: mnemonic: epc_s_appendwrt
// Message documented only in Server Error Messages manual
//Cause:  Disk space was exceeded during a file append
//operation, for example, while creating the collection 
//definition file (.cdf).
//Action:  Increase disk space.
	
82,0,"append read failed"
// *Comment: mnemonic: epc_s_appendrd
// Message documented only in Server Error Messages manual
//Cause: This is an Oracle Trace internal error.
//Action: Contact Oracle Worldwide Customer Support.

83,0,"error creating product definition file"
// *Comment: mnemonic: epc_s_crefdf
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should 
//never be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

84,0,"file memory mapping failed"
// *Comment: mnemonic: epc_s_memmap
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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 Worldwide Customer Support. 

85,0,"memory unmapping failed"
// *Comment: mnemonic: epc_s_unmap
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

86,0,"memory mapping required before memory unmapping"
// *Comment: mnemonic: epc_s_mmapreq
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

// UI [87,87]
87,0,"beginning CLI job"
// *Comment: mnemonic: epc_s_begclijob
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
// Message not used in Oracle Trace Collection Services release 8.1.5
// but it is used in Oracle Trace Tcl scripts.
//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.

88,0,"call to string formatting package failed" 
// *Comment: mnemonic: epc_s_lsffail
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never be 
//returned.
//Action:  Contact Oracle Worldwide Customer Support. 

89,0,"value of event_id exceeds epc_init max_event"
// *Comment: mnemonic: epc_s_excdmaxeve
// Message documented only in Server Error Messages manual
//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.

90,0,"error writing version record"
// *Comment: mnemonic: epc_s_wrtver
// Message documented only in Server Error Messages manual
//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 Worldwide 
//Customer Support. 

// NLS_DO_NOT_TRANSLATE [91,93]

91,0,"invalid number of minutes: 0 to 59 required"
// *Comment: mnemonic: epc_s_badminute
// Message not used in Oracle Trace Collection Services release 8.1.5

92,0,"invalid number of hours: 0 to 23 required"
// *Comment: mnemonic: epc_s_badhour
// Message not used in Oracle Trace Collection Services release 8.1.5

93,0,"internal error: invalid argument"
// *Comment: mnemonic: epc_s_interrarg
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

94,0,"system timestamp call failed"
// *Comment: mnemonic: epc_s_timefail
// Message documented only in Server Error Messages manual
//Cause:  Oracle Trace could not get the system timestamp.
//Action:  Contact Oracle Worldwide Customer Support.

95,0,"error adding new registration ID record"
// *Comment: mnemonic: epc_s_add_regid
// Message documented only in Server Error Messages manual
//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 Worldwide 
//Customer Support. 

96,0,"error closing registration ID file"
// *Comment: mnemonic: epc_s_clo_regid
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

97,0,"error creating new registration ID file"
// *Comment: mnemonic: epc_s_cre_regid
// Message documented only in Server Error Messages manual
//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 Worldwide Customer Support.

98,0,"error deleting registration ID record"
// *Comment: mnemonic: epc_s_del_regid
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

99,0,"error deleting registration ID detail record"
// *Comment: mnemonic: epc_s_del_regid_det
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

100,0,"error finding free slot for new registration ID detail record"
// * Comment: mnemonic: epc_s_find_free_slot
// Message documented only in Server Error Messages manual
//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 Worldwide 
//Customer Support. 

101,0,"error finding primary registration ID record for specified process"
// * Comment: mnemonic: epc_s_find_regid_fac
// Message documented only in Server Error Messages manual
//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 Worldwide Customer Support.

// NLS_DO_NOT_TRANSLATE [102,102]

102,0,"error fetching registration ID data for specified process"
// * Comment: mnemonic: epc_s_get_regid
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

103,0,"invalid registration ID context"
// * Comment: mnemonic: epc_s_inv_regid_cxt
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

104,0,"invalid or inconsistent registration ID data"
// * Comment: mnemonic: epc_s_inv_regid_data
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

105,0,"invalid registration ID string, e.g. too long"
// * Comment: mnemonic: epc_s_inv_regid_str
// Message documented only in Server Error Messages manual
//Cause:  The registration ID string supplied is invalid (probably 
//too long).
//Action:  Supply a valid registration ID string.

106,0,"error finding next registration ID record"
// * Comment: mnemonic: epc_s_next_regid
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 	

107,0,"error finding next registration ID detail record"
// * Comment: mnemonic: epc_s_next_regid_det
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

108,0,"error opening registration ID file"
// * Comment: mnemonic: epc_s_ope_regid
// Message documented only in Server Error Messages manual
//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 Worldwide Customer Support.

109,0,"error reading registration ID record"
// * Comment: mnemonic: epc_s_read_regid
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

110,0,"error reading registration ID file header"
// * Comment: mnemonic: epc_s_read_regid_hdr
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

// NLS_DO_NOT_TRANSLATE [111,111]

111,0,"registration ID environment variable not defined"
// * Comment: mnemonic: epc_s_regid_env
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 
	
112,0,"error setting file extend_count parameter"
// * Comment: mnemonic: epc_s_set_regid_ext
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

113,0,"error during addition of new collection record"
// * Comment: mnemonic: epc_s_add_col
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

114,0,"error during close of collection file"
// * Comment: mnemonic: epc_s_clo_col
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

// NLS_DO_NOT_TRANSLATE [115,115]

115,0,"invalid or missing collect.dat file environment variable"
// * Comment: mnemonic: epc_s_col_env
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

116,0,"collection already exists in collect.dat file"
// * Comment: mnemonic: epc_s_col_exists
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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).

117,0,"error creating collect.dat file"
// * Comment: mnemonic: epc_s_cre_col
// Message documented only in Server Error Messages manual
//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 Worldwide Customer Support. 

118,0,"error deleting collect.dat record"
// * Comment: mnemonic: epc_s_del_col
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

119,0,"error finding specified collect.dat record"
// * Comment: mnemonic: epc_s_find_col
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

120,0,"invalid or undefined collect.dat context"
// * Comment: mnemonic: epc_s_inv_col_cxt
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

121,0,"invalid or undefined collection name"
// * Comment: mnemonic: epc_s_inv_col_name
// Message documented only in Server Error Messages manual
//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 Worldwide Customer Support.
	
122,0,"error getting next collect.dat record"
// * Comment: mnemonic: epc_s_next_col
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

123,0,"error during opening of collect.dat file"
// * Comment: mnemonic: epc_s_ope_col
// Message documented only in Server Error Messages manual
//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  
//Worldwide Customer Support.

124,0,"error reading collect.dat record"
// * Comment: mnemonic: epc_s_read_col
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

125,0,"error reading collect.dat file header"
// * Comment: mnemonic: epc_s_read_col_hdr
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

126,0,"error setting collect.dat extend_count"
// * Comment: mnemonic: epc_s_set_col_ext
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 
	
// NLS_DO_NOT_TRANSLATE [127,132]

127,0,"product event flag parameter update error"
// * Comment: mnemonic: epc_s_upd_fac_ef
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

128,0,"process event flag parameter update error"
// * Comment: mnemonic: epc_s_upd_pro_ef
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. Most often this 
//indicates that a mismatch exists between Oracle Trace Collection 
//Services and other components (for example, database server 
//version).
//Action:  Contact Oracle Worldwide Customer Support.

129,0,"error adding PRO record"
// * Comment: mnemonic: epc_s_pro_add
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

130,0,"error closing PRO file"
// * Comment: mnemonic: epc_s_pro_clo
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

131,0,"error creating PRO file"
// * Comment: mnemonic: epc_s_pro_cre
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  User may not have access to the directory where the 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 disk space.
//Otherwise, contact Oracle Worldwide Customer Support. 
	
132,0,"error in deleting or freeing of PRO record"
// * Comment: mnemonic: epc_s_pro_del
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

// UI [133,133]
133,0,"completed CLI job"
// * Comment: mnemonic: epc_s_comclijob
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
// Message not used in Oracle Trace Collection Services release 8.1.5
// but it is used in Oracle Trace Tcl scripts.
//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.


// NLS_DO_NOT_TRANSLATE [134,145]

134,0,"error adding PRO_REGID to PRO_FAC"
// * Comment: mnemonic: epc_s_pro_fac_add_regid
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

135,0,"error deleting PRO_REGID"
// * Comment: mnemonic: epc_s_pro_fac_del_regid
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

136,0,"get registrar PID from PRO failed"
// * Comment: mnemonic: epc_s_pro_get_regpid
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 
	
137,0,"invalid or undefined PRO file context"
// * Comment: mnemonic: epc_s_pro_inv_cxt
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

138,0,"fetch of next PRO record failed"
// * Comment: mnemonic: epc_s_pro_next
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

139,0,"error opening process.dat file"
// * Comment: mnemonic: epc_s_pro_ope
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  Oracle Trace Collection Services cannot access admin 
//process.dat file in the //expected location, that is, 
//$ORACLE_HOME/admin.
//Action:  Verify that the Oracle Trace admin process.dat file 
//exists and check for file protection problems. If you have 
//multiple ORACLE_HOME definitions, verify that the correct 
//ORACLE_HOME is being used. If the problem persists, contact 
//Oracle Worldwide Customer Support. 

140,0,"read of PRO file record failed"
// * Comment: mnemonic: epc_s_pro_read
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

141,0,"error during read (map) of PRO hdr"
// * Comment: mnemonic: epc_s_pro_read_hdr
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This may indicate a problem with the memory mapped Oracle 
//Trace admin .dat files due to their location on disks which are 
//not locally mounted. Otherwise this is an Oracle Trace internal 
//error and should never be returned.
//Action:  Check the disk device where the Oracle Trace admin .dat 
//files are located. Otherwise, contact Oracle Worldwide Customer 
//Support.
	
142,0,"set of PRO file extend_count failed"
// * Comment: mnemonic: epc_s_pro_set_ext
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

143,0,"update of PRO record failed"
// * Comment: mnemonic: epc_s_pro_upd
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

144,0,"error updating registrar PID in PRO"
// * Comment: mnemonic: epc_s_pro_upd_regpid
// Message not used in Oracle Trace Collection Services release 8.1.5

145,0,"error stopping collection"
// * Comment: mnemonic: epc_s_stop_col
// Message not used in Oracle Trace Collection Services release 8.1.5

// NLS_DO_NOT_TRANSLATE [146,146] 

146,0," "
// * Comment: mnemonic: epc_s_clisuccess
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//Cause: Used by Oracle Trace command-line interpreter (CLI); part of 
//normal, successful Oracle Trace job output. 
//Action: None required.

147,0,"job ID not specified"
// * Comment: mnemonic: epc_s_nojobid
// Message documented only in Server Error Messages manual
//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 the operation again with the correct 
//command-line parameters. Otherwise, contact Oracle 
//Worldwide Customer Support. 

// UI [148,151]

148,0,"collection status is: active"
// * Comment: mnemonic: epc_s_colstatact
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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.

149,0,"collection status is: not active"
// * Comment: mnemonic: epc_s_colstatnotact
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//Cause:  This is a success message. 
//Action:  None required.

150,0,"collection status is: undefined"
// * Comment: mnemonic: epc_s_colstatundef
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//Cause: This is an Oracle Trace internal error. It should never
//be returned.
//Action: Contact Oracle Worldwide Customer Support.

151,0,"deleted collection definition and data collection files"
// * Comment: mnemonic: epc_s_delcolfil
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//Cause:  This is a success message.
//Action:  None required.
	
// NLS_DO_NOT_TRANSLATE [152,152]

152,0,"error opening input parameter file"
// * Comment: mnemonic: epc_s_opeparfil
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  May be due to a parameter file required by Oracle Trace CLI 
//not having been provided by the user. For NT Oracle Trace 
//Collection Services release 7.3.3 specifically, more common use of 
//this condition value is to indicate successful completion of an 
//Oracle Enterprise Manager job run by the Oracle Intelligent Agent 
//on behalf of Oracle Trace.
//Action:  If the missing parameter file can be provided, then do so. 
//Ignore this message if it is seen in the context of a job 
//completion in details of NT 7.3.3 Oracle Trace Collection Services 
//job, as seen through Oracle Trace Manager.

153,0,"invalid or ambiguous CLI command specified"
// * Comment: mnemonic: epc_s_invclicom
// Message documented only in Server Error Messages manual
//Cause:  Oracle Trace CLI was provided with an 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.

// NLS_DO_NOT_TRANSLATE [154,154]

154,0,"invalid or missing restriction"
// * Comment: mnemonic: epc_s_invprores
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  The CLI found the input restriction record with either 
//missing or otherwise invalid value. For NT Oracle Trace Collection 
//Services release 7.3.3 specifically, more common use of this 
//condition value is to indicate successful start of an Oracle 
//Enterprise Manager job run by the Oracle Intelligent Agent 
//on behalf of Oracle Trace.
//Action:  If restriction input is to be used with CLI, make 
//sure it is complete. Ignore this message if it is seen in 
//the context of a job start up in details of NT 7.3.3 Oracle
//Trace Collection Services job, as seen through Oracle 
//Trace Manager.

155,0,"maximum number of restrictions exceeded"
// * Comment: mnemonic: epc_s_res_limit_exd
// Message documented only in Server Error Messages manual
//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. 

156,0,"ORACLE_HOME parameter not supplied"
// * Comment: mnemonic: epc_s_nohompar
// Message not used in Oracle Trace Collection Services release 8.1.5
// but it is used in Oracle Trace Tcl scripts.
//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.

// UI [157,158]

157,0,"collection started "
// * Comment: mnemonic: epc_s_started
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//Cause:  This is a success message.
//Action:  None required.

158,0,"collection completed "
// * Comment: mnemonic: epc_s_stopped
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//Cause:  This is a success message.
//Action:  None required.

159,0,"User name or password (or service name) not supplied"
// * Comment: mnemonic: epc_s_invconstr
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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.

160,0,"error activating collection"
// * Comment: mnemonic: epc_s_scolact
// Message documented only in Server Error Messages manual
//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 Worldwide Customer Support. 

// NLS_DO_NOT_TRANSLATE [161,162]

161,0,"error modifying collection definition file"
// * Comment: mnemonic: epc_s_scolmod
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  An error occurred while activating the collection. This is 
//an internal error.
//Action:  Contact Oracle Worldwide Customer Support. 
	
162,0,"error with product definition file in active collection"
// * Comment: mnemonic: epc_s_scolfdf
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  An error occurred while activating the collection.
//Action:  Contact Oracle Worldwide Customer Support.

163,0,"error translating ORACLE_HOME"
// * Comment: mnemonic: epc_s_orahome
// Message documented only in Server Error Messages manual
//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).

164,0,"error in product admin directory name translation"
// * Comment: mnemonic: epc_s_fadmindir
// Message documented only in Server Error Messages manual
//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).

// NLS_DO_NOT_TRANSLATE [165,165]

165,0,"error in product directory name translation"
// * Comment: mnemonic: epc_s_fproddir
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  An error occurred while translating the environment 
//logical ORACLE_HOME.
//Action:  Check your ORACLE_HOME definition or see your 
//database administrator (DBA).

166,0,"error canceling collection"
// * Comment: mnemonic: epc_s_colcan
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should 
//never be returned.
//Action:  Contact Oracle Worldwide Customer Support.
	
167,0,"collection file reached limit"
// * Comment: mnemonic: epc_s_colfull
// Message documented only in Server Error Messages manual
//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.

// NLS_DO_NOT_TRANSLATE [168,168]

168,0,"error acquiring file path from ORACLE_HOME"
// * Comment: mnemonic: epc_s_forafpath
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  An error occurred while translating the environment 
//logical ORACLE_HOME.
//Action:  Check your ORACLE_HOME definition or see your 
//database administrator (DBA).

// UI [169,170]

169,0,"error deleting collection definition file"
// * Comment: mnemonic: epc_s_delcdf
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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).

170,0,"error deleting collection data file"
// * Comment: mnemonic: epc_s_deldat
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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).

// NLS_DO_NOT_TRANSLATE [171,171]

171,0,"Tcl scan error"
// * Comment: mnemonic: epc_s_tclscan
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  Oracle Trace CLI error occurred scanning an input parameter.
//This is an internal error that should not be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

172,0,"parameter parsing error"
// * Comment: mnemonic: epc_s_lrmfail
// Message documented only in Server Error Messages manual
//Cause: This is an Oracle Trace internal error.
//Action: Contact Oracle Worldwide Customer Support.

173,0,"command-line argument list parse failed"
// * Comment: mnemonic: epc_s_lrmpaa
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//Cause: This is an Oracle Trace internal error.
//Action: Contact Oracle Worldwide Customer Support.

174,0,"input parameter file parse failed"
// * Comment: mnemonic: epc_s_lrmpfi
// Message documented only in Server Error Messages manual
//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 Worldwide Customer Support.


// UI [175,177]

175,0,"Oracle Trace CLI otrccol image not found or not executable"
// * Comment: mnemonic: epc_s_nocliexe
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
// Message not used in Oracle Trace Collection Services release 8.1.5
// but it is used in Oracle Trace Tcl scripts.
//Cause:  The Oracle Trace CLI image otrccol does not exist in 
//ORACLE_HOME/bin, or access to the image 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 Worldwide Customer Support. 

176,0,"format completed"
// * Comment: mnemonic: epc_s_fmtdone
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//Cause:  This is a success message.
//Action:  None required.

177,0,"format started"
// * Comment: mnemonic: epc_s_fmtstart
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
// Message not used in Oracle Trace Collection Services release 8.1.5
// but it is used in Oracle Trace Tcl scripts.
//Cause:  This is a success message.
//Action:  None required.

// NLS_DO_NOT_TRANSLATE [178,178]

178,0,"Tcl job name not specified"
// * Comment: mnemonic: epc_s_notcljob
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal message. It should never
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

// UI [179,182]

179,0,"collection stopped by user action or maximum file size (or error)"
// * Comment: mnemonic: epc_s_errstop
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
// Message not used in Oracle Trace Collection Services release 8.1.5
// but it is used in Oracle Trace Tcl scripts.
//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 the init.ora file or Oracle Trace Manager.
//Otherwise, contact Oracle Worldwide Customer Support. 

180,0,"deletion of formatted data started"
// * Comment: mnemonic: epc_s_delfmtstart
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
// Message not used in Oracle Trace Collection Services release 8.1.5
// but it is used in Oracle Trace Tcl scripts.
//Cause:  This is a success message.
//Action:  None required.
	
181,0,"deletion of formatted data completed"
// * Comment: mnemonic: epc_s_delfmtdone
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//Cause:  This is a success message.
//Action:  None required.

182,0,"OCI database access error occurred"
// * Comment: mnemonic: epc_s_ocierr
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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 
//Worldwide Customer Support. 

183,0,"invalid epcfctx parameter"
// * Comment: mnemonic: epc_s_epcfctx
// Message documented only in Server Error Messages manual
//Cause: Invalid facility context argument was passed to the Oracle 
//Trace API routine, for example, epc_event.
//Action: Supply a facility context argument.

184,0,"invalid collection definition file pointer"
// * Comment: mnemonic: epc_s_cdfinvalid
// Message documented only in Server Error Messages manual
//Cause: This is an Oracle Trace internal error.
//Action: Contact Oracle Worldwide Customer Support.

185,0,"file version not current Oracle Trace version"
// * Comment: mnemonic: epc_s_filever
// Message documented only in Server Error Messages manual
//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.

186,0,"error starting collection"
// * Comment: mnemonic: epc_s_colstart
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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 Worldwide Customer Support.

189,0,"active collection limit exceeded"
// * Comment: mnemonic: epc_s_collmtexcd
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//Cause: The maximum number of collections for this product was 
//exceeded. The current maximum is 5 collections.
//Action: Retry the collection later.

190,0,"invalid facility.dat file context; internal error"
// * Comment: mnemonic: epc_s_fac_inv_cxt
// Message documented only in Server Error Messages manual
//Cause: This is an Oracle Trace internal error.
//Action: Contact Oracle Worldwide Customer Support.

191,0,"error adding product record to facility.dat file"
// * Comment: mnemonic: epc_s_fac_add
// Message documented only in Server Error Messages manual
//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 Worldwide Customer
//Support.

192,0,"error creating facility.dat file"
// * Comment: mnemonic: epc_s_fac_cre
// Message documented only in Server Error Messages manual
//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.

193,0,"error setting file extent in the facility.dat file"
// * Comment: mnemonic: epc_s_fac_set_ext
// Message documented only in Server Error Messages manual
//Cause: This is an Oracle Trace internal error.
//Action: Contact Oracle Worldwide Customer Support.

194,0,"error updating product record in facility.dat file"
// * Comment: mnemonic: epc_s_fac_upd
// Message documented only in Server Error Messages manual
//Cause: This is an Oracle Trace internal error.
//Action: Contact Oracle Worldwide Customer Support.

195,0,"error finding next product record in facility.dat file"
// * Comment: mnemonic: epc_s_fac_next
// Message documented only in Server Error Messages manual
//Cause: This is an Oracle Trace internal error.
//Action: Contact Oracle Worldwide Customer Support.

196,0,"error reading header record from facility.dat file"
// * Comment: mnemonic: epc_s_fac_read_hdr
// Message documented only in Server Error Messages manual
//Cause: This is an Oracle Trace internal error.
//Action: Contact Oracle Worldwide Customer Support.

197,0,"error reading from facility.dat file"
// * Comment: mnemonic: epc_s_fac_read
// Message documented only in Server Error Messages manual
//Cause: This is an Oracle Trace internal error.
//Action: Contact Oracle Worldwide Customer Support.

198,0,"error deleting product record from facility.dat file"
// * Comment: mnemonic: epc_s_fac_del
// Message documented only in Server Error Messages manual
//Cause: This is an Oracle Trace internal error.
//Action: Contact Oracle Worldwide Customer Support.

199,0,"error closing facility.dat file"
// * Comment: mnemonic: epc_s_fac_clo
// Message documented only in Server Error Messages manual
//Cause: This is an Oracle Trace internal error.
//Action: Contact Oracle Worldwide Customer Support.

200,0,"error opening facility.dat file"
// * Comment: mnemonic: epc_s_fac_ope
// Message documented only in Server Error Messages manual
//Cause: Error occurred while opening the facility.dat file.
//Action: Verify that the facility.dat file is accessible, else
//contact Oracle Worldwide Customer Support.

/
/
/===========================================================================================================
/0200 .. 0399
/===========================================================================================================
//0201 through 0219 are headers; no documentation needed
//0221 through 0223 are headers; no documentation needed
//0231 through 0232 are headers; no documentation needed

201,0,"Page"
// * Comment: mnemonic: EPC__PAGE

202,0,"Oracle Trace Detail Report"
// * Comment: mnemonic: EPC__FACDEF_STITLE

// NLS_DO_NOT_TRANSLATE [203,203] 

203,0,"%d-%b-%Y %H:%M"
// * Comment: mnemonic: EPC__SUP_DATE_FORMAT

204,0,"Date Disabled"
// * Comment: mnemonic: EPC__RPQU_DATE_DISABLED

// NLS_DO_NOT_TRANSLATE [205,206] 

205,0,"Oracle Trace"
// * Comment: mnemonic: EPC__PRODUCT_NAME

206,0,"V XXX"
// Message not used in Oracle Trace Collection Services release 8.1.5

207,0,"Event:"
// * Comment: mnemonic: EPC__RPQU_EVENT

208,0,"Product:" 
// * Comment: mnemonic: EPC__RPQU_FACILITY

209,0,"Version:"
// * Comment: mnemonic: EPC__RPQU_VERSION

210,0,"Collection:"
// * Comment: mnemonic: EPCREPCOLLECTION

// NLS_DO_NOT_TRANSLATE [211,211] 

211,0,"Epid" 
// * Comment: mnemonic: EPCREPEPID

212,0,"User Name"
// * Comment: mnemonic: EPCREPUNAME

213,0,"CPU Type"
// * Comment: mnemonic: EPCREPCPU

214,0,"OS Version"
// * Comment: mnemonic: EPCREPOSFVER

215,0,"Node Name"
// * Comment: mnemonic: EPCREPNODENAME

216,0,"Timestamp"
// * Comment: mnemonic: EPCREPTIME

// NLS_DO_NOT_TRANSLATE [217,217] 

217,0,"%d-%b-%Y %X"
// * Comment: mnemonic: EPCREPTIME_FORMAT

218,0,"Prod Num" 
// * Comment: mnemonic: EPCREPFACILITY

219,0,"Version"
// * Comment: mnemonic: EPCREPVERSION

220,0,"Could not find item"
// * Comment: mnemonic: EPCREPITMNTFND
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. Have the 
//collection definition file (.cdf) 
//and data (*.dat) files available.

221,0,"Registration ID"
// * Comment: mnemonic: EPCREPREGID

222,0,"Start Timestamp"
// * Comment: mnemonic: EPCREPSTIME

223,0,"End Timestamp"
// * Comment: mnemonic: EPCREPETIME

224,0,"error writing to a report file"
// * Comment: mnemonic: EPCREPERRPUT
// Message documented only in Server Error Messages manual
//Cause:  Oracle Trace could not write data to a report output file, 
//for example, <col_name>*.txt.
//Action:  Check that there is enough disk space and that file 
//protections are correct.
	
// NLS_DO_NOT_TRANSLATE [225,225]

225,0,"time() error"
// * Comment: mnemonic: EPCREPERRTIME
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  The Oracle Trace reporter could not get the time from 
//the system.
//Action:  Contact Oracle Worldwide Customer Support. 

226,0,"localtime() error"
// * Comment: mnemonic: EPCREPERRLOCALTIME
// Message documented only in Server Error Messages manual
//Cause:  The Oracle Trace reporter could not determine the size
//required for the local representation of dates.
//Action:  Contact Oracle Worldwide Customer Support. 

227,0,"seek error trying to find first product registration ID"
// * Comment: mnemonic: EPCREPFACREGID_NF
// Message documented only in Server Error Messages manual
//Cause:  The Oracle Trace reporter encountered a seek error while 
//looking for the first product registration ID.
//Action:  Contact Oracle Worldwide Customer Support. 

228,0,"could not find matching product"
// * Comment: mnemonic: EPCREPFAC_NF
// Message documented only in Server Error Messages manual
//Cause:  The Oracle Trace reporter could not find the specified 
//product.
//Action:  Contact Oracle Worldwide Customer Support. Have the 
//collection definition file (.cdf)  
//and data (*.dat) files available.

229,0,"event item record found before event record"
// * Comment: mnemonic: EPCREPERR_ADDEITE
// Message documented only in Server Error Messages manual
//Cause:  The Oracle Trace reporter found an item record before an 
//event record.
//Action:  Contact Oracle Worldwide Customer Support. Have the 
//collection definition file (.cdf) 
//and data (*.dat) files available.

230,0,"event record not found"
// * Comment: mnemonic: EPCREPEVE_NF
// Message documented only in Server Error Messages manual
//Cause:  The Oracle Trace reporter could not find the event record.
//Action:  Contact Oracle Worldwide Customer Support. Have the 
//collection definition file (.cdf) 
//and data (*.dat) files available. 

231,0,"Unmatched Start Records"
// * Comment: mnemonic: EPCREPSTART_ORPH

232,0,"Unmatched END Records"
// * Comment: mnemonic: EPCREPEND_ORPH

233,0,"error allocating %s in %s."
// * Comment: mnemonic: EPC__MEM_MALLOC
// Message documented only in Server Error Messages manual
//Cause:  A memory allocation error occurred. 
//Action:  Check the use of memory in your application. If there is 
//no problem there, contact Oracle Worldwide Customer Support. 
	
234,0,"could not allocate memory."
// * Comment: mnemonic: EPC__MEM_CALLOC
// Message documented only in Server Error Messages manual
//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 Worldwide Customer Support.

235,0,"data collection file %s.dat not found" 
// * Comment: mnemonic: EPCDCF_FNF
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//Cause:  The data file could not be found, probably because it was 
//deleted and no longer exists.
//Action:  No action required.

236,0,"collection definition file %s not found" 
// * Comment: mnemonic: EPCCDFFNF
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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.

237,0,"unknown record in collection definition file"  
// * Comment: mnemonic: EPCCDFRNK
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. Have the 
//collection definition file (.cdf) 
//and data (*.dat) files available. 

238,0,"error reading collection definition file"
// * Comment: mnemonic: EPCCDFERF
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. Have the 
//collection definition file (.cdf) 
//and data (*.dat) files available. 

// NLS_DO_NOT_TRANSLATE [239,239] 

239,0,"%s"
// * Comment: mnemonic: EPC__ERR_HUH
// Message documented only in Server Error Messages manual
//Cause: This is not an error. This information is used to output
//arbitrary text strings.
//Action: None required.

240,0,"invalid justification in insert field"
// * Comment: mnemonic: EPCLBJUST
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. Have the 
//collection definition file (.cdf) 
//and data (*.dat) files available. 

241,0,"consistency error in insert field"
// * Comment: mnemonic: EPCLBINSB
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. Have the 
//collection definition file (.cdf) 
//and data (*.dat) files available. 	

// NLS_DO_NOT_TRANSLATE [242,255]

242,0,"cannot open file %s"
// * Comment: mnemonic: EPC__OPEN
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  The file specified cannot be opened.
//Action:  Check that the file protections are correct.

243,0,"cannot create file %s"
// * Comment: mnemonic: EPC__CREATE
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  The file specified cannot be created.
//Action:  Check that the directory protections are correct.

244,0,"environment variable %s not found"
// * Comment: mnemonic: EPC__ENV_NF
// Message not used in Oracle Trace Collection Services release 8.1.5

245,0,"map error in %s"
// * Comment: mnemonic: EPC__MAP
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

246,0,"error updating event flags variable"
// * Comment: mnemonic: EPC__EVNTFLG_UPD
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

247,0,"error reading .fdf file"
// * Comment: mnemonic: EPCFDFERF
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

248,0,"unknown record in collection definition file"  
// * Comment: mnemonic: EPCFDFRNK
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. Have 
//the collection definition (.cdf) file available.

249,0,"history output is buffered"
// * Comment: mnemonic: EPC__HIST_BUF
// Message not used in Oracle Trace Collection Services release 8.1.5

250,0,"history write failed"
// * Comment: mnemonic: EPC__HIST_WRT
// Message not used in Oracle Trace Collection Services release 8.1.5

251,0,"append seek operation failed"
// * Comment: mnemonic: EPC__IO_APPSEEK
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

252,0,"append read failed"
// * Comment: mnemonic: EPC__IO_APPREAD
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  Oracle Trace encountered an error reading a file during an 
//FDF append operation.
//Action:  Check that the protections are correct for the 
//product definition file (.fdf) 
//specified when the collection was activated.

253,0,"append write failed"
// * Comment: mnemonic: EPC__IO_APPWRT
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  Oracle Trace encountered an error writing to a file during 
//an FDF append operation.
//Action:  Check that the protections are correct for the 
//product definition file (.fdf) 
//specified when the collection was activated. If that is not 
//the problem; check that there is sufficient disk space.

254,0,"error clearing file flag"
// * Comment: mnemonic: EPC__IO_CLR
// Message not used in Oracle Trace Collection Services release 8.1.5

255,0,"error setting file flag"
// * Comment: mnemonic: EPC__IO_SET
// Message not used in Oracle Trace Collection Services release 8.1.5

256,0,"error checking file status"
// * Comment: mnemonic: EPC__IO_STAT
// Message documented only in Server Error Messages manual
//Cause: The attempt to determine the file size failed. This is an
//Oracle Trace internal error.
//Action: Contact Oracle Worldwide Customer Support.

257,0,"read error"
// * Comment: mnemonic: EPC__IO_READ
// Message documented only in Server Error Messages manual
//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 
//Worldwide Customer Support.

258,0,"write error in %s"
// * Comment: mnemonic: EPC__IO_WRT
// Message documented only in Server Error Messages manual
//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 Worldwide Customer Support.

259,0,"seek error in %s"
// * Comment: mnemonic: EPC__IO_SEEK
// Message documented only in Server Error Messages manual
//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 
//Worldwide Customer Support.

260,0,"error extending file"
// * Comment: mnemonic: EPC__IO_EXTEND
// Message documented only in Server Error Messages manual
//Cause:  Oracle Trace could not extend the file.
//Action:  Check that there is sufficient disk space and that file 
//protections are set correctly.
	
261,0,"map read error in %s"
// * Comment: mnemonic: EPC__IO_MAPRD
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.
	
// NLS_DO_NOT_TRANSLATE [262,296]

262,0,"map write error in %s"
// * Comment: mnemonic: EPC__IO_MAPWRT
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

263,0,"map lock error"
// * Comment: mnemonic: EPC__IO_MAPLCK
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

264,0,"invalid file pointer"
// * Comment: mnemonic: EPC__IO_BADFP
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

265,0,"thread error number: %d, occurred in collection %s"
// * Comment: mnemonic: EPC__THREAD_ERR
// Message not used in Oracle Trace Collection Services release 8.1.5

266,0,"error unlocking mutex in collection %s"
// * Comment: mnemonic: EPC__MUTEXUNLCK
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

267,0,"flush error number :%d, occurred in collection %s"
// * Comment: mnemonic: EPC__FLUSH_ERR
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

268,0,"error acquiring lock"
// * Comment: mnemonic: EPC__LOCK
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

269,0,"error testing lock"
// * Comment: mnemonic: EPC__LOCK_TST
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

270,0,"error unmapping file in %s"
// * Comment: mnemonic: EPC__IO_UNMAP
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

271,0,"error updating %s file"
// * Comment: mnemonic: EPC__REG_UPD
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

272,0,"error creating communication message queue"
// * Comment: mnemonic: EPC__REG_QUEUE
// Message not used in Oracle Trace Collection Services release 8.1.5

273,0,"unknown message type %d received by registrar"
// * Comment: mnemonic: EPC__REG_UNKMSG
// Message not used in Oracle Trace Collection Services release 8.1.5

274,0,"process with process identifier %d incurred an error"
// * Comment: mnemonic: EPC__REG_PROERR
// Message not used in Oracle Trace Collection Services release 8.1.5

275,0,"communication message queue already exists"
// * Comment: mnemonic: EPC__RGMSG_EXISTS
// Message not used in Oracle Trace Collection Services release 8.1.5

276,0,"error creating communication message queue"
// * Comment: mnemonic: EPC__RGMSG_CREATE
// Message not used in Oracle Trace Collection Services release 8.1.5

277,0,"error destroying communication message queue"
// * Comment: mnemonic: EPC__RGMSG_DESTROY
// Message not used in Oracle Trace Collection Services release 8.1.5

278,0,"error opening communication message queue"
// * Comment: mnemonic: EPC__RGMSG_OPEN
// Message not used in Oracle Trace Collection Services release 8.1.5

279,0,"error reading communication message queue"
// * Comment: mnemonic: EPC__RGMSG_READ
// Message not used in Oracle Trace Collection Services release 8.1.5

280,0,"error sending message"
// * Comment: mnemonic: EPC__RGMSG_SEND
// Message not used in Oracle Trace Collection Services release 8.1.5

281,0,"logic error in %s"
// * Comment: mnemonic: EPC__SCHED_ERR 
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

282,0,"error accessing collection file in %s"
// * Comment: mnemonic: EPC__RGSCHED_COL
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This error could indicate a potential protection problem 
//on the collect.dat file. If the protections are correct, then 
//this is an Oracle Trace internal error. 
//Action:  Contact Oracle Worldwide Customer Support.

// UI [283,283]

283,0,"error starting collection %s"
// * Comment: mnemonic: EPC__RGSCHED_START
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This error could indicate a protection problem on the 
//collection definition file (.cdf) and product definition file 
//(.fdf).
//Action:  There should be other error messages displayed along with 
//this message. Take the actions indicated for those messages.
	
284,0,"error in product definition file"
// * Comment: mnemonic: EPC__RGSCHED_FDF
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. Have the 
//.fdf file available.

285,0,"error in product definition file; file is empty"
// * Comment: mnemonic: EPC__RGSCHED_FDFEMP
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This error could be due to the product definition 
//file (.fdf) file having been edited or corrupted in some way. 
//Action:  Get another copy of the product definition file from
//another node or copy the file from the installation disk.
	
286,0,"error appending FDF and CDF files for collection %s" 
// * Comment: mnemonic: EPC__RGSCHED_APP2
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. Have 
//the product definition file (.fdf) and 
//collection definition file (.cdf) available.

287,0,"unexpected record found in product definition file processing"
// * Comment: mnemonic: EPC__RGSCHED_UNXFDF
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. Have 
//the product definition file (.fdf) available.

288,0,"process file empty"
// * Comment: mnemonic: EPC__RGSCHED_PROEMP
// Message not used in Oracle Trace Collection Services release 8.1.5

289,0,"error sending start message to process %d"
// * Comment: mnemonic: EPC__RGSCHED_PROSEND
// Message not used in Oracle Trace Collection Services release 8.1.5

290,0,"gethostname call failed"
// * Comment: mnemonic: EPC__GETHOSTNAME
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

291,0,"unable to find free space for process record"
// * Comment: mnemonic: EPCPRO_FIND
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

292,0,"pthread_cond_init call failed in %s"
// * Comment: mnemonic: EPC__CONDINIT
// Message not used in Oracle Trace Collection Services release 8.1.5

293,0,"pthread_mutex_init call failed in %s"
// * Comment: mnemonic: EPC__MUTEXINIT
// Message not used in Oracle Trace Collection Services release 8.1.5

294,0,"pthread_create call failed in %s"
// * Comment: mnemonic: 
// Message not used in Oracle Trace Collection Services release 8.1.5

295,0,"registration limit exceeded for product %d"
// * Comment: mnemonic: 
// Message not used in Oracle Trace Collection Services release 8.1.5

296,0,"user name system call failed"
// * Comment: mnemonic: EPC__UNAME
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. 

297,0,"error writing to data collection file %s"
// * Comment: mnemonic: EPC__WRITDCF
// Message documented only in Server Error Messages manual
//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 Worldwide Customer Support.

// NLS_DO_NOT_TRANSLATE [298,305]

298,0,"error locking mutex in %s"
// * Comment: mnemonic: EPC__MUTEXLCK
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

299,0,"offset %d does not match an active collection"
// * Comment: mnemonic: EPCCOLNOTFOUND
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

300,0,"collection %s does not match an active collection"
// * Comment: mnemonic: EPCCOLNOTFOUNDA
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  The collection cannot be stopped because it does not exist.
//Action:  No action required.
	
301,0,"collection %s found but not active"
// * Comment: mnemonic: EPCCOLNOTACTIVE
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  The collection has already been stopped.
//Action:  No action required.
	
302,0,"Error calling pthread_cond_signal in %s"
// * Comment: mnemonic: EPC__CONDSIG
// Message not used in Oracle Trace Collection Services release 8.1.5

303,0,"pthread_delay_np call failed"
// * Comment: mnemonic: EPC__THDDELAYNP
// Message not used in Oracle Trace Collection Services release 8.1.5

304,0,"error writing history"
// * Comment: mnemonic: EPC__HST_WRT
// Message not used in Oracle Trace Collection Services release 8.1.5

305,0,"error finding free collection entry"
// * Comment: mnemonic: EPCCOLFILFULL
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

306,0,"no data to report from file %s"
// * Comment: mnemonic: EPCREPNOTEXT
// Message documented only in Server Error Messages manual
//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.
	
307,0,"error during Oracle commit"
// * Comment: mnemonic: EPCFMTCOMMIT_ERR
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

308,0,"error executing Oracle statement"
// * Comment: mnemonic: EPCFMTORACLE_ERR 
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

309,0,"error parsing %s"
// * Comment: mnemonic: EPCFMTORASQL_ERR
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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.

310,0,"error opening message file"
// * Comment: mnemonic: EPCERRMSB
// Message documented only in Server Error Messages manual
//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 Worldwide Customer Support.

// NLS_DO_NOT_TRANSLATE [311,313]

311,0,"error creating epc_pro process file" 
// * Comment: mnemonic: EPCCREPROCESS
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  The user may not have access to the directory where the 
//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 provide additional 
//free disk space. Otherwise, contact Oracle Worldwide 
//Customer Support.

312,0,"error creating epc_sched schedule file"
// * Comment: mnemonic: EPCCRESCHEDULE
// Message not used in Oracle Trace Collection Services release 8.1.5

313,0,"error creating epc_col collection file"
// * Comment: mnemonic: EPCCRECOLLECTION
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  The user may not have access to the directory where the 
//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 provide additional 
//free disk space, or contact Oracle Worldwide Customer Support.

314,0,"error reading body of data collection file"
// * Comment: mnemonic: EPCREADDCF
// Message documented only in Server Error Messages manual
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. Have the 
//collection definition file (.cdf) and data (*.dat) files available. 

// NLS_DO_NOT_TRANSLATE [315,318]

315,0,"error creating start handle record"
// * Comment: mnemonic: EPCCRESTARTHDL
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This error indicates a problem with Reporter memory.
//Action:  Contact Oracle Worldwide Customer Support. Have the 
//collection definition file (.cdf) and data (*.dat) files available. 

316,0,"error finding process record"
// * Comment: mnemonic: EPCFINDPROCREC
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should 
//never be returned.
//Action:  Contact Oracle Worldwide Customer Support. Have the 
//collection definition file (.cdf) and data (*.dat) files available. 
 
317,0,"string too long"
// * Comment: mnemonic: EPCSTRTOOLONG
// Message not used in Oracle Trace Collection Services release 8.1.5

318,0,"error creating data file %s"
// * Comment: mnemonic: EPCCREDATAFILE
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This error could indicate a disk space problem.
//Action:  Check that there is enough disk space. Otherwise, 
//contact Oracle Worldwide Customer Support.

319,0,"missing required schedule collection user information"
// * Comment: mnemonic: EPCMISSCHEDINFO
// Message documented only in Server Error Messages manual
//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 Worldwide 
//Customer Support.
	
// NLS_DO_NOT_TRANSLATE [320,321]

320,0,"error finding free schedule record"
// * Comment: mnemonic: EPCFINDSCHEDREC
// Message not used in Oracle Trace Collection Services release 8.1.5

321,0,"collection will not start until registrar is running"
// * Comment: mnemonic: EPCCOLLSTART
// Message not used in Oracle Trace Collection Services release 8.1.5

322,0,"error creating process report file"
// * Comment: mnemonic: EPCREPPRO_ERR
// Message documented only in Server Error Messages manual
//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 Worldwide Customer 
//Support.

// NLS_DO_NOT_TRANSLATE [323,323]

323,0,"process record not found to match product registration record"
// * Comment: mnemonic: EPCREPREGPRO
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support. Have the 
//collection definition file and data (*.dat) files available.

// NLS_DO_NOT_TRANSLATE [324,329]

324,0,"Placeholder"
325,0,"Placeholder"
326,0,"Placeholder"
327,0,"Placeholder"
328,0,"Placeholder"
329,0,"Placeholder"

// NLS_DO_NOT_TRANSLATE [330,336]

330,0,"invalid search directory arguments"
// * Comment: mnemonic: EPCESDIA_INVARGS_ERR
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

331,0,"error opening product definition directory file"
// * Comment: mnemonic: EPCESDOD_OPENDIR_ERR
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This error could be due to protection problems on the 
//otrace/admin/fdf directory or filespec. 
//Action:  If the protections are correct and the problem still 
//exists, contact Oracle Worldwide Customer Support.

332,0,"error allocating memory for product information record"
// * Comment: mnemonic: EPCESDFA_FINFOALLOC_ERR
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

333,0,"error reading product definition directory file" 
// * Comment: mnemonic: EPCESDRD_READDIR_ERR
// Message not used in Oracle Trace Collection Services release 8.1.5

334,0,"error allocating memory for list of product information pointers"
// * Comment: mnemonic: EPCESDLA_LISTALLOC_ERR
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

335,0,"error allocating memory for product definition file record"
// * Comment: mnemonic: EPCESDDA_FDFALLOC_ERR
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

336,0,"requested product definition directory entry not found" 
// * Comment: mnemonic: EPCESDNM_NOMATCH_ERR
// Message not used in Oracle Trace Collection Services release 8.1.5

337,0,"usage:  %s [-w[wid] -l[len] -P -p[pid] -h -a -d] input_file [output_dir]"
// * Comment: mnemonic: EPCREPUSAGE
// Message documented only in Server Error Messages manual
//Cause:  The Oracle Trace Report command was incorrectly used.
//Action:  Resubmit the command using the correct parameters in 
//the correct order.
	
// NLS_DO_NOT_TRANSLATE [338,341]

338,0,"error deleting unused process record: offset %d"
// * Comment: mnemonic: EPCPRODELERR
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never 
//be returned.
//Action:  Contact Oracle Worldwide Customer Support.

339,0,"error deleting unused collection: offset %d"
// * Comment: mnemonic: EPCCOLDELERR
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  This is an Oracle Trace internal error. It should never be 
//returned.
//Action:  Contact Oracle Worldwide Customer Support.

340,0,"invalid remote procedure call context"
// * Comment: mnemonic: EPCN_INV_CCX
// Message not used in Oracle Trace Collection Services release 8.1.5

341,0,"invalid remote procedure call service context"
// * Comment: mnemonic: EPCN_INV_SCX
// Message not used in Oracle Trace Collection Services release 8.1.5

342,0,"ID for collection %s not found in database; rerun with -f option"
// * Comment: mnemonic: EPCFMTNOCOL
// Message documented only in Server Error Messages manual
//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.
	
343,0,"usage:  %s [-f] [-p] [-c#] cdf_file [username [password [service]]]"
// * Comment: mnemonic: EPCFMTUSAGE
// Message documented only in Server Error Messages manual
//Cause: An invalid format command.
//Action: Reenter the format command.

// UI [344,344]

344,0,"no new data to format; exiting"
// * Comment: mnemonic: EPCFMTNONEWDATA
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//Cause:  An attempt was made to format a data file that contains 
//no new data.
//Action:  No action required.
	
// NLS_DO_NOT_TRANSLATE [345,349]

345,0,"error adding Oracle7 ALL class FDF to fdfdir.dat file"
// * Comment: mnemonic: EPCESVRAAO_FDFERR
// Message not used in Oracle Trace Collection Services release 8.1.5

346,0,"error adding Oracle7 Expert class FDF to fdfdir.dat file"
// * Comment: mnemonic: EPCESVRAEO_FDFERR
// Message not used in Oracle Trace Collection Services release 8.1.5

347,0,"error adding SQL*Net ALL class FDF to fdfdir.dat file"
// * Comment: mnemonic: EPCESVRAAS_FDFERR
// Message not used in Oracle Trace Collection Services release 8.1.5

348,0,"error adding ATM ALL class FDF to fdfdir.dat file"
// * Comment: mnemonic: EPCESVRAAA_FDFERR
// Message not used in Oracle Trace Collection Services release 8.1.5

// UI [349,352]

349,0,"error starting or stopping Oracle7 database collection"
// * Comment: mnemonic: EPCESVR_ORADBERR
// Message documented only in OEM Messages manual
// Message not used in Oracle Trace Collection Services release 8.1.5
//Cause:  There are several causes for this error.
//Action:  Refer to the EPC_ERROR.LOG for the specific error number.

350,0,"aborting format of collection_id %d; delete from database and reformat"
// * Comment: mnemonic: EPCFMTABORT_ERR
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//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 file 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.

351,0,"format canceled by user"
// * Comment: mnemonic: EPCFMTCANCEL_ERR
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//Cause:  The Oracle Trace Format operation was stopped.
//Action:  No action required.
	
352,0,"file already exists; select a new name"
// * Comment: mnemonic: EPCFILEEXISTS
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
//Cause:  The file name specified already exists.
//Action:  Supply a new file name, that is, collection name.

// NLS_DO_NOT_TRANSLATE [353,353] 

353,0,"unable to load resource DLL"
// * Comment: mnemonic: EPCLOADRESDLL
// Message not used in Oracle Trace Collection Services release 8.1.5

// NLS_DO_NOT_TRANSLATE [354,356] 

354,0,"NEXT ERROR GOES HERE"

355,0,"error deleting regitration ID record from product"
// * Comment: mnemonic: epc_s_fac_del_regid
// Message not used in Oracle Trace Collection Services release 8.1.5

356,0,"incompatible api version"
// * Comment: mnemonic: epc_s_apiver
// Message not used in Oracle Trace Collection Services release 8.1.5

357,0,"tried to add a duplicate callback routine for same cross-product item"
// * Comment: mnemonic: epc_s_reg_cb_duplicate
// Message documented only in Server Error Messages manual
//Cause: An attempt was made to add a duplicate callback routine for 
//the same cross-product item.
//Action: Correct the code.

358,0,"tried to remove a non-existent cross-product callback routine"
// * Comment: mnemonic: epc_s_unreg_cb_nonexist
// Message documented only in Server Error Messages manual
//Cause: An attempt was made to remove a non-existent 
//cross-product callback routine.
//Action: Correct the code.

// NLS_DO_NOT_TRANSLATE [399,400] 

399,0,"This is an MSB test data1=%s data2=%s data3=%d data4=%c data5=%x data6=%u"
/399 There is no message with this number. 

/===========================================================================================================
/0400 .. 0499
/===========================================================================================================
0400,0,"Placeholder"
/===========================================================================================================
/0500 .. 0599
/===========================================================================================================

// NLS_DO_NOT_TRANSLATE [501,516] 

501,0,"database operation resulted in an error"
// * Comment: mnemonic: EPCCATALOG_ERROR
// Message not used in Oracle Trace Collection Services release 8.1.5

502,0,"database fetch operation returned no data"
// * Comment: mnemonic: EPCCATALOG_EOF
// Message not used in Oracle Trace Collection Services release 8.1.5

503,0,"database cannot be accessed"
// * Comment: mnemonic: EPCCATALOG_NO_DB_ACCESS
// Message not used in Oracle Trace Collection Services release 8.1.5

// UI [504,504]

504,0,"collection names must be unique"
// * Comment: mnemonic: EPCCATALOG_DUP_COLL_NM
// Message not used in Oracle Trace Collection Services release 8.1.5

505,0,"collection definition file specifications must be unique"
// * Comment: mnemonic: EPCCATALOG_DUP_CDF
// Message not used in Oracle Trace Collection Services release 8.1.5

506,0,"collection data cannot be found in specified database"
// * Comment: mnemonic: EPCCATALOG_FMT_COLL_NOT_FOUND
// Message not used in Oracle Trace Collection Services release 8.1.5

507,0,"ID value could not be returned for collection entry %s"
// * Comment: mnemonic: EPCCATALOG_NO_ID_STR
// Message not used in Oracle Trace Collection Services release 8.1.5

508,0,"network error or server database not available"
// * Comment: mnemonic: EPCCATALOG_NO_DB_STR
// Message not used in Oracle Trace Collection Services release 8.1.5

509,0,"Oracle not available."
// * Comment: mnemonic: EPCCATALOG_ORA_NOT_AVAIL_STR
// Message not used in Oracle Trace Collection Services release 8.1.5

510,0,"no collection summary entries found"
// * Comment: mnemonic: EPCCATALOG_NO_COLL_SUM_STR
// Message not used in Oracle Trace Collection Services release 8.1.5

// UI [511,511]

511,0,"invalid Oracle user name or password; logon denied"
// * Comment: mnemonic: EPCCATALOG_LOGON_DENIED
// Message documented in both Server Error Messages manual 
// and OEM Messages manual
// Message not used in Oracle Trace Collection Services release 8.1.5

512,0,"no formatted data found for collection %s"
// * Comment: mnemonic: EPCCATALOG_NO_FMT_FOUND
// Message not used in Oracle Trace Collection Services release 8.1.5

513,0,"catalog entry not found for collection ID %s"
// * Comment: mnemonic: EPCCATALOG_COLL_NOT_FOUND
// Message not used in Oracle Trace Collection Services release 8.1.5

514,0,"in-memory catalog information is not consistent with database"
// * Comment: mnemonic: EPCCATALOG_INCONSISTENT
// Message not used in Oracle Trace Collection Services release 8.1.5

515,0,"specified summary entry not found"
// * Comment: mnemonic: EPCCATALOG_SUMMARY_NOT_FOUND
// Message not used in Oracle Trace Collection Services release 8.1.5

516,0,"data could not be deleted from formatter event tables"
// * Comment: mnemonic: EPCCATALOG_NO_EVENT_DEL
// Message not used in Oracle Trace Collection Services release 8.1.5

// NLS_DO_NOT_TRANSLATE [517,517] 

517,0,"NEXT CATALOG ERROR GOES HERE"
// * Comment: mnemonic: 
//Cause:
//Action:

/
/
/
