Skip Headers
Oracle® Fusion Middleware Error Messages Reference
11g Release 1 (11.1.1.5.0)

Part Number E10113-08
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

29 DMS-50700 to DMS-58070

DMS-50700: initialization error
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: ERROR

Impact: Configuration

DMS-50701: security error
Cause: (See message)
Action: Review the exception chain in log files for the cause and make sure that the appropriate permission has been granted.

Level: 1

Type: ERROR

Impact: Security

DMS-50702: The DMS Java class "{0}" could not be found.
Cause: (See message)
Action: Review the classpath of the application and ensure that the class is available in a jar file or directory listed therein.

Level: 1

Type: ERROR

Impact: Configuration

DMS-50703: The LogWriter name "{0}" is reserved.
Cause: (See message)
Action: Use a different name.

Level: 1

Type: ERROR

Impact: Logging

DMS-50704: unable to create a new LogWriter: {0}
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: ERROR

Impact: Logging

DMS-50705: attempting to create a concrete LogWriter instance with an invalid class ({0})
Cause: (See message)
Action: Correct the declaration for the LogWriter to use a valid class.

Level: 1

Type: ERROR

Impact: Logging

DMS-50706: invalid configuration property: name = "{0}", value = "{1}"
Cause: (See message)
Action: Remove the property or correct its name or value to comply with the set of supported property names. If the property value is at fault then reviewing the base exception may provide more information on the manner of the fault (e.g. missing class, invalid directory name).

Level: 1

Type: WARNING

Impact: Configuration

DMS-50707: unable to load configuration file "{0}"
Cause: (See message)
Action: Review the exception chain in log files for the cause and make sure that the configuration file exists and the permissions on the file permit it to be read.

Level: 1

Type: ERROR

Impact: Configuration

DMS-50708: unable to parse metric rule document
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: WARNING

Impact: Configuration

DMS-50709: The metric rule resource {0} could not be read. Aggregation is off.
Cause: (See message)
Action: Check that the resource is available and if necessary correct the content of the classpath.

Level: 1

Type: WARNING

Impact: Files

DMS-50710: duplicated table "{1}" in metric table "{0}"
Cause: (See message)
Action: Remove the <Union> or <Select> table from the metric table (it is already in use therein).

Level: 1

Type: WARNING

Impact: Other

DMS-50711: Value "{1}" is invalid for attribute "{0}".
Cause: (See message)
Action: Review the documentation for the correct use of the specific attribute.

Level: 1

Type: WARNING

Impact: Other

DMS-50713: invalid metric rule syntax
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to the metric rule documentation.

Level: 1

Type: WARNING

Impact: Other

DMS-50714: no DMS Archiver found
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: ERROR

Impact: Configuration

DMS-50715: no ONS found
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: ERROR

Impact: Configuration

DMS-50716: unable to create DMS ONS RPC server
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: WARNING

Impact: Other

DMS-50717: unable to create DMS Publisher "{0}"
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: WARNING

Impact: Other

DMS-50719: unable to connect to the server and retrieve metrics at "{0}"
Cause: (See message)
Action: Review the exception chain in log files for the cause and make sure that the server starts up.

Level: 1

Type: WARNING

Impact: Requests/Responses

DMS-50720: unable to retrieve DMS metrics
Cause: The HTTP server failed to handle the metric request.
Action: Make sure the HTTP server is able to handle metric requests.

Level: 1

Type: WARNING

Impact: Other

DMS-50722: unable to parse DMS metric document
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: WARNING

Impact: Other

DMS-50723: The reference to table {0} for aggregating DMS metrics is invalid.
Cause: Columns from tables created by select and union elements are not valid in this context.
Action: Correct the aggregation statement in the metric rules.

Level: 1

Type: WARNING

Impact: Other

DMS-50725: unable to bind to port "{0}"
Cause: (See message)
Action: Review the exception chain in log files for the cause and make sure port is free.

Level: 1

Type: ERROR

Impact: Ports

DMS-50726: The metric configuration resource {0} could not be read.
Cause: (See message)
Action: Check that the resource is available and if necessary correct the content of the classpath.

Level: 1

Type: ERROR

Impact: Configuration

DMS-50727: invalid metric configuration syntax
Cause: (See message)
Action: Refer to XML schema "metric_config.xsd" and correct the configuration.

Level: 1

Type: ERROR

Impact: Configuration

DMS-50728: No writable metric repository directory "{0}" is available. The default metric archiving is off.
Cause: (See message)
Action: Make sure that a writable metric repository exists.

Level: 1

Type: WARNING

Impact: Files

DMS-50730: The repository directory "{0}" is not readable.
Cause: (See message)
Action: Make sure that a readable metric repository exists.

Level: 1

Type: WARNING

Impact: Files

DMS-50731: invalid value type "{0}" for column "{1}"
Cause: (See message)
Action: Refer to the metric rule documentation for valid value types.

Level: 1

Type: WARNING

Impact: Configuration

DMS-50732: invalid value type for "Concat" operation: should be string
Cause: (See message)
Action: Refer to the metric rule documentation for valid value types.

Level: 1

Type: WARNING

Impact: Configuration

DMS-50733: Arithmetic expression cannot be string type.
Cause: (See message)
Action: Refer to the metric rule documentation for details of defining metrics.

Level: 1

Type: WARNING

Impact: Configuration

DMS-50734: missing value type for column <{0} Name="{1}">
Cause: (See message)
Action: Refer to the metric rule documentation and add an explicit value type to the column.

Level: 1

Type: WARNING

Impact: Configuration

DMS-50735: invalid system function <Function Name="{0}">
Cause: (See message)
Action: Refer to the metric rule documentation for a list of valid system functions.

Level: 1

Type: WARNING

Impact: Configuration

DMS-50736: missing an argument in <Expression> for column "{0}"
Cause: (See message)
Action: Refer to the metric rule documentation and add an argument for the expresstion.

Level: 1

Type: WARNING

Impact: Configuration

DMS-50737: circular dependency found on aggregated metric tables {0}
Cause: (See message)
Action: Remove circular dependency among aggregated tables.

Level: 1

Type: WARNING

Impact: Configuration

DMS-50738: invalid operation "{0}"
Cause: (See message)
Action: Refer to the metric rule documentation for a list of valid operations.

Level: 1

Type: WARNING

Impact: Configuration

DMS-50742: Exception occurred while performing individual refresh operation for metric "{0}".
Cause: (See message)
Action: Refer to log files for the cause and, if possible, correct the problem.

Level: 1

Type: WARNING

Impact: Configuration

DMS-50743: Exception occurred while performing group refresh operation for metric "{0}". This failed refresh may have affected other metrics too.
Cause: (See message)
Action: Refer to log files for the cause and, if possible, correct the problem.

Level: 1

Type: WARNING

Impact: Configuration

DMS-50744: illegal argument values passed to method: {0}
Cause: This is in internal error: a set of arguments have been passed to a method within the DMS component that are not appropriate for that method. This state should not have occurred and is indicative of a series of conditions that were not anticipated during development.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

DMS-50745: illegal program state detected: {0}
Cause: This is in internal error: a program state has been detected within the DMS component that is unexpected or contradictory.
Action: Refer to log files for the cause and, if possible, correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

DMS-50747: attempt to read an older metric rule document "{0}"
Cause: Metric rule document "{0}" was older than the one currently used in the system.
Action: Make sure the version of the metric rules is equal to or higher than the one currently used in the system.

Level: 1

Type: WARNING

Impact: Configuration

DMS-50748: attempt to read an metric rule document "{0}" that is equal to or older than the one currently used in the system
Cause: The version of the metric rule document "{0}" was equal to or older than the one currently used in the system.
Action: Make sure the version of the metric rules is higher than the one currently used in the system.

Level: 1

Type: WARNING

Impact: Configuration

DMS-50749: OPMN is down.
Cause: (See message)
Action: Start OPMN.

Level: 1

Type: WARNING

Impact: Requests/Responses

DMS-50750: Metric parameter is null.
Cause: (See message)
Action: Pass in a non-null metric.

Level: 1

Type: WARNING

Impact: Data

DMS-50751: Metric "{0}" passed in does not belong to "{1}".
Cause: (See message)
Action: Pass in an appropriate metric.

Level: 1

Type: WARNING

Impact: Data

DMS-50752: One of the parameters for "{0}" is null or empty: {1}
Cause: (See message)
Action: Do not pass in null or empty parameters.

Level: 1

Type: WARNING

Impact: Data

DMS-50753: wrong value type
Cause: (See message)
Action: Pass in value with appropriate type.

Level: 1

Type: WARNING

Impact: Data

DMS-50754: One of the parameters for "{0}" has unexpected value "{1}".
Cause: (See message)
Action: Pass in correct values.

Level: 1

Type: WARNING

Impact: Data

DMS-50755: server unavailable: {0}
Cause: (See message)
Action: Specify valid server or cluster names.

Level: 1

Type: WARNING

Impact: Data

DMS-50903: Metric aggregation is off due to errors.
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50904: unable to parse metric rule document: {0}
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50907: Metric table "{0}" will not be built due to exception.
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50908: Name attribute is invalid in <ColumnDef> for metric table "{0}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50909: duplicated <ColumnDef Name="{1}"> for metric table "{0}"
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50910: Type attribute is invalid in <ColumnDef Name="{1}"> for metric table "{0}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50915: wrong value type "{2}" for column "{1}" in metric table "{0}". Expect value type "{3}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50916: Column "{0}" is missing in table "{1}" for metric table "{2}".
Cause: (See message)
Action: Make sure to match <ColumnDef> with <Column>.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50917: Name attribute is empty in <ColumnGroup>.
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50918: Type attribute is invalid in <ColumnGroup Name="{1}">.
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50919: empty group member in <ColumnGroup Name="{1}">
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50920: Attribute "{3}" of <{0}> is invalid in table "{1}" for metric table "{2}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50921: Column "{0}" is not defined in table "{1}" for metric table "{2}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50922: Attribute "{4}" of <{3} Name="{0}"> is invalid in table "{1}" for metric table "{2}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50923: Number of arguments for column "{3}" in <Expression> is "{0}" in table "{1}" for metric table "{2}", which is less that expected.
Cause: (See message)
Action: Make sure to have at least two arguments.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50924: Arguments for column "{2}" in <Expression> are missing in table "{0}" for metric table "{1}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50925: unexpected <Aggregation> in <Where> in table "{0}" for metric table "{1}"
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50926: Metric table "{2}" should not reference column "{0}" defined in table "{1}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50927: duplicated <{0}> in table "{1}" for metric table "{2}"
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50928: missing <{0}> in table "{1}" for metric table "{2}"
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50929: unexpected <{0}> in <Union Name="{1}"> for metric table "{2}"
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50930: unable to resolve column "{2}" in table "{0}" for metric table "{1}"
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50932: The value of attribute "{0}", "{1}", is less then the minimum "{2}".
Cause: (See message)
Action: Review the documentation for the correct use of the specific attribute and give a valid value.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50933: unable to convert the value of attribute "{0}", "{1}", to a number
Cause: (See message)
Action: Review the documentation for the correct use of the specific attribute and give a valid value.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50934: Sampling is not enabled for metric table "{0}".
Cause: (See message)
Action: Refer to log files for the cause and, if possible, correct the problem.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50935: unable to convert value "{0}" to a number
Cause: (See message)
Action: Refer to log files for the cause and, if possible, correct the problem.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50938: duplicated <{3} Name="{0}"> in table "{1}" for metric table "{2}"
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50940: The value of Attribute "Name" for <OrderBy> fails to match one of column names in table "{0}" for metric table "{1}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50941: unable to convert the value of <RowRetained>, "{0}", in table "{1}" to a number for metric table "{2}"
Cause: (See message)
Action: Review the documentation for the correct use of the specific element and give a valid value.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50942: Only two tables can be referred to in outer join in table "{0}" for metric table "{1}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50945: missing <And>, <Or>, <Not>, or <Condition> in table "{0}" for metric table "{1}"
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50946: invalid <{0}> in table "{1}" for metric table "{2}"
Cause: (See message)
Action: Specify one of <And>, <Or>, <Not>, or <Condition>.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50947: Number of arguments for condition is "{0}" in table "{1}" for metric table "{2}", which is less that expected.
Cause: (See message)
Action: Make sure to have at least two arguments.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50948: missing condition argument in table "{0}" for metric table "{1}"
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50949: <Null> is not valid when operator is "{0}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50950: Exception occurred while retrieving metrics from metric repository.
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50951: wrong number of tokens in auto aggregation table name "{0}"
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50952: invalid auto aggregation table name "{0}"
Cause: (See message)
Action: Make sure that auto aggregation table names follow the patterns of <prefix>/<opcode>//<table_name> or <prefix>/<opcode>/groupby/<column_name1>/.../<column_nameN>//<table_name>.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50953: invalid aggregation operation "{1}" in auto aggregation table name "{0}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50955: invalid metric prefetch interval "{0}"
Cause: (See message)
Action: Make sure to give a valid value for the metric prefetch interval in seconds.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50956: invalid metric prefetch removal cycle "{0}"
Cause: (See message)
Action: Make sure to give a valid value for the metric prefetch removal cycle.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50957: Value of column "{1}" in table "{0}" is not a number.
Cause: (See message)
Action: Review the documentation for the correct use of the specific element and make sure to give valid value.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50960: Column <{2}> should not be type "{3}" in table "{0}" for metric table "{1}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50961: Operation "{2}" should be type "{3}" in table "{0}" for metric table "{1}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50962: Arithmetic expression should not be String type in table "{0}" for metric table "{1}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50963: Column "{0}" expects a number.
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50964: Column <{2} Name="{3}"> is missing value type in table "{0}" for metric table "{1}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50965: <Function Name="{0}"> has invalid function name in table "{1}" for metric table "{2}".
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50966: Metric table "{0}" has no key column. It will not be collected.
Cause: (See message)
Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50973: Caught Exception.
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50976: The use of one or more of the following deprecated properties [{0}] has been detected.
Cause: (See message)
Action: Cease use of the deprecated properties and use one or more of these properties [{1}] instead.

Level: 1

Type: WARNING

Impact: Configuration

DMS-50977: a potentially conflicting use of properties. The use of one or more of the following deprecated properties [{0}] has been detected.
Cause: (See message)
Action: Cease use of the deprecated properties and use one or more of these properties [{1}] instead. The deprecated properties will be ignored.

Level: 1

Type: WARNING

Impact: Configuration

DMS-50978: Exception occurred while registering metric rules "{0}"
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50980: Exception occurred while looking up runtime mbean server by JNDI name "{0}".
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50981: Exception occurred while reading metric rules "{0}".
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50983: Exception occurred while reading metric configuration file "{0}".
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50985: Exception occurred while retrieving metrics from address "{0}" with query string "{1}".
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50989: Exception occurred while retrieving metrics from address "{0}".
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50990: Unable to register MBean "{0}"
Cause: (See message)
Action: Review the exception chain in log files for the cause and correct the specific problem.

Level: 1

Type: NOTIFICATION

Impact: Other

DMS-57003: Failed to process the wrapped DMS execution context {0} sent by {1} (user-agent: {2}) when requesting the resource {3}.
Cause: By scrutinizing the incoming HTTP request DMS has attempted to detect and, if appropriate, make use of a wrapped execution context. That process has failed. This should not affect the processing of the servlet handling the request, but the ability to correlate the processing of this request with others to which it may related will have been adversely affected. A DMS execution context is an object that contains context information about the piece of work being performed at a particular moment in time. The type of context information carried by the DMS execution context may include the URL of the http request, the unique correlation key (ECID) assigned to that piece of work, etc - information that is useful for tracking requests though the system. The execution context does not carry user names, passwords or general application parameters. The DMS execution context should not be confused with application specific context objects, such as ADF-context or Faces-context, which are vital to the accurate execution of the application concerned.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

DMS-57004: Failed to initialize the DMS trace to be associated with DMS execution context {0}, that itself is associated with a request of resource {1}.
Cause: A problem has occurred in the initialization of the trace system for this request. This should not affect the processing of the servlet handling the request but will be a problem if the trace (aggregate, debug or triggered) data was of value to the system's administrator.
Action: If the trace of this request was important, and has been affected by this error, then contact Oracle Support Services

Level: 1

Type: WARNING

Impact: Other

DMS-57005: Failed to terminate the DMS trace associated with DMS execution context {0}, that itself is associated with a request of resource {1}.
Cause: A problem has occurred in the finalization of the trace system for this request. This should not affect the processing of the servlet handling the request but will be a problem if the trace (aggregate, debug or triggered) data was of value to the system's administrator.
Action: If the trace of this request was important, and has been affected by this error, then contact Oracle Support Services

Level: 1

Type: WARNING

Impact: Other

DMS-57006: Failed to deactivate the DMS execution context, {0}, associated with a request of resource {1}.
Cause: A problem has occurred in the termination of the DMS execution context in place during the processing of the HTTP request. This should not affect the servlet handling the request, but may result in an invalid execution context being in place for the processing of future requests and possibly prevent accurate trace data from being gathered.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

DMS-57007: Failed to url-decode a wrapped execution context ({0}) due to a problem in the decoding process itself: {1}
Cause: A problem has occurred while trying to url-decode a wrapped execution context found as a url-parameter. The consequence is that the execution context being passed from client to server can not be used. A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.
Action: Determine if there is any code in the system that integrates with the Oracle DMS Context API (java package oracle.dms.context) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code, and if necessary contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

DMS-57008: The execution context put in place at the start of the request, {0}, is not the execution context in place at the end of the request, {1}. The request is as follows: {2}
Cause: When enabled to do so DMS associates an execution context with the resources (typically a thread) assigned to process an incoming request. In this case the context that DMS assigned at the start of the processing is not the one in place at the end of the processing. At some point during the processing the context has been changed. This could result in the loss of the ability to correlate the work performed across the complete request lifecycle for this request. A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.
Action: Determine if there is any code in the system that integrates with the Oracle DMS Context API (java package oracle.dms.context) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code, and if necessary contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

DMS-57009: An error prevented selection of an appropriate execution context implementation for this environment - the feature will be disabled.
Cause: At the point of initialization DMS needs to determine the environment in which it is operating in order to select the most appropriate implementation of the execution context feature. An unexpected error has occurred during that process. The DMS execution context feature will be disabled.
Action: Review the error to see if it can be resolved and then restart the server.

Level: 1

Type: ERROR

Impact: Other

DMS-58002: Could not create trace output directory ({0}) - Disabling {1} traces.
Cause: An attempt to create a file system directory, into which trace files were to be written, has failed. Consequently no trace information can be saved and therefore, to save unnecessary burden on the system, trace information will not be collected.
Action: Check that the system user that owns the process has permissions to create such a directory. Check that the system has sufficient disk space to create a new directory.

Level: 1

Type: WARNING

Impact: Files

DMS-58005: ignoring exception: {0}
Cause: An unanticipated problem has occurred for which the runtime code can not take automatic remedial action.
Action: Refer to the base exception to see if there is a problem with the system that can be addressed (e.g. run low in disk space, run out of memory, etc).

Level: 1

Type: WARNING

Impact: Other

DMS-58006: Problem encountered while removing old files from trace output directories.
Cause: DMS was attempting to remove old files from the trace output directories but for some reason (see base exception) has failed.
Action: The system is unlikely to fail as a consequence of this error, but disk space will be used that would otherwise have been released. Refer to the base exception to see if the problem can be addressed, and consider deleting unrequired files manually (DMS no longer needs these old files so any or all of them can be removed).

Level: 1

Type: WARNING

Impact: Files

DMS-58007: Problem encountered when closing file and associated streams.
Cause: As part of the termination of a normal read or write operation on a file the file could not be closed.
Action: If a file can not be properly closed then the operating system's file-handle associated with that file may not be properly released. An operating system can manage only a finite number of file-handles and if they are not released then new file-handles can not be created. One consequence of a depletion of file-handles is that file input/outpt on the machine concerned may be forced to come to a stop. It is more likely, however, that this is a one-off problem and that Java will tidy up the file-handle internally. This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs.

Level: 1

Type: WARNING

Impact: Files

DMS-58008: error writing trace data to disk
Cause: DMS has failed to create or use the objects required to write trace output to disk. The output intended to be written will be discarded.
Action: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs.

Level: 1

Type: WARNING

Impact: Other

DMS-58013: Problem encountered aggregating trace: {0}.
Cause: DMS has failed to perform the aggregation process on the trace data collected during the handling of this particular task or servlet request. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.
Action: Review exception details and the log for any seemingly related messages. If the problem has come from the JVM itself: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs. Otherwise the problem is with the code written to run on the JVM: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.

Level: 1

Type: WARNING

Impact: Other

DMS-58014: Failed to handle REQUEST_BEGIN for {0}. The trace will not be aggregated.
Cause: DMS did not find the trace event that marks the start of the series of trace events to be associated with an HTTP request. Without that particular trace event DMS can not be sure that the set of collected trace events will accurately represent the actions performed during that HTTP request and consequently will not process them further. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.
Action: Review exception details and the log for any seemingly related messages. If the problem has come from the JVM itself: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs. Otherwise the problem is with the code written to run on the JVM: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.

Level: 1

Type: WARNING

Impact: Other

DMS-58015: Can not get the current task's execution context and therefore the trace events that occurred during this task's lifecycle can not be used to contribute to the aggregate trace associated with the task's URL.
Cause: In order to perform the process of trace aggregation for a completed task the execution context for that task is required. In this case the execution context could not be found; without the execution context object the trace aggregation process can not be performed. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.
Action: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.

Level: 1

Type: WARNING

Impact: Other

DMS-58016: Can not get the URI associated with the current thread's recent activities.
Cause: In order to perform the process of trace aggregation for a completed task the URI associated with that task is required. In this case the URI could not be found; without the URI the trace information collected cannot be aggregated. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.
Action: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.

Level: 1

Type: WARNING

Impact: Other

DMS-58017: The maximum number of allowed aggregates has already been reached. Traces referring to URLs not already being aggregated will not contribute to aggregate information.
Cause: In order to prevent too much memory being consumed by the DMS trace system the current request will not be added to the aggregate trace set because the maximum number of URIs for which trace data will be aggregated has already been reached. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI.
Action: If aggregate trace information is not required for this request there is no action required. Otherwise please review the value of the system property oracle.dms.trace.maxAggregates.

Level: 1

Type: WARNING

Impact: Other

DMS-58018: Cannot delete old trace file: {0}.
Cause: An attempt to delete a file system file has failed (the deletion attempt was intended to keep files organized and their number manageable). The system is unlikely to fail as a consequence of this error, but disk space will be used that would otherwise have been released.
Action: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs.

Level: 1

Type: WARNING

Impact: Files

DMS-58019: Cannot generate aggregate trace data because the trace system failed initialization.
Cause: (See message)
Action: Review the log files for reports of other problems relating to initialization failure. Where possible correct those other problems and restart the system. Failure of the trace subsystem should not affect the ability of the system to execute, but will prevent traces from being produced.

Level: 1

Type: WARNING

Impact: Other

DMS-58020: failure writing DMS configuration file {0}
Cause: An error occurred attempting to save the DMS configuration file.
Action: Check that the process has permission to write the configuration file. Review log files for more information on this issue.

Level: 1

Type: WARNING

Impact: Files

DMS-58021: failure loading DMS configuration file {0}
Cause: An error occurred attempting to load the DMS configuration file.
Action: Check that the process has permission to read the configuration file, and the file exists. Review log files for more information on this issue.

Level: 1

Type: WARNING

Impact: Files

DMS-58022: failure registering DMS configuration MBean {0}
Cause: An error occurred attempting to register the DMS configuration MBean.
Action: Check that the J2EE container is up. Review log files for more information.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58023: There has been a failure activating the DMS configuration. Failed to close the event configuration file for server "{0}".
Cause: An error occurred attempting to activate the DMS configuration.
Action: Review the log files for more information.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58024: cannot create a condition for filter {0}
Cause: A condition could not be created for the condition filter at runtime.
Action: Check that the filter has been configured correctly.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58025: cannot instantiate class {0} for destination with id = {1}
Cause: A Destination could not be created at runtime.
Action: Check that the Destination has been configured correctly.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58026: cannot not set property {0} on an instance of class {1} for destination with id = {2}
Cause: The configuration of a destination specified one or more properties to be set on the destination before the destination was used. A problem was encountered trying to set the property listed in the message the precise details of which are also shown in the message.
Action: Verify that the property exists on the class being instantiated as the destination, and that the value is legal for that property.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58028: will not associate filter {0} and destination {1} - one or both are null or have null IDs.
Cause: (See message)
Action: Check the configuration of the filter and destination, and search the log file for other messages that may report problems creating instances of the filter or destination.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58033: Can not associate a destination, id={0}, with a filter, id={1} if the filter declares that it will not pass any events.
Cause: An instance of a filter should declare the set of event types in which it has an interest. In this particular case the set is empty and thus the filter is apparently interested in no events at all. Such a filter serves no sensible purpose and therefore will be ignored.
Action: Check the log file for other error relating to this filter to see if there were problems in its construction. Also verify the configuration of the filter and its associated destination (some filters are created implicitly to cooperate with a destination, so the configuration may only specify details of the destination).

Level: 1

Type: WARNING

Impact: Configuration

DMS-58035: The required JRockit Flight Recorder classes can not be found. The JFRDestination can not function without them.
Cause: The JRockit Flight Recorder classes are only available on Oracle JRockit.
Action: Check that the system is running using JRockit or disable the JFRDestination declared within dms_config.xml

Level: 1

Type: WARNING

Impact: Other

DMS-58040: The JRockit FlightRecorder class is declaring that it is not the JRockit native implementation and thus DMS can not use it.
Cause: DMS only makes use of the JRockit FlightRecorder implementation that is native to JRockit. The FlightRecorder class available to DMS is apparently not a native implementation and will therefore not be used by DMS.
Action: This situation will not affect the runtime operation of the system, but in order to avoid the message being reported again either switch to using the JRockit JVM or remove eventRoutes from dms_config.xml that involve the JFRDestination.

Level: 1

Type: WARNING

Impact: Other

DMS-58041: The JRockit FlightRecorder class is declaring that it is not active and so DMS can not use it.
Cause: DMS can only make use of the JRockit FlightRecorder class if it is active. The FlightRecorder class is declaring that it is not active and therefore DMS will not make use of it.
Action: This situation will not affect the runtime operation of the system, but in order to avoid the message being reported again either switch to using the JRockit JVM or remove eventRoutes from dms_config.xml that involve the JFRDestination.

Level: 1

Type: WARNING

Impact: Other

DMS-58042: The DMS configuration file is invalid, and may not be viewed. No updates are allowed until the file has been fixed manually.
Cause: The DMS configuration file is invalid. No updates are allowed until the file has been fixed.
Action: Review the log files for more information, and correct the problem in the configuration file

Level: 1

Type: WARNING

Impact: Configuration

DMS-58045: DMS classic tracing will not be performed because the DMS context manager is disabled.
Cause: The classic trace features of DMS are dependent upon the DMS context manager being enabled. The DMS context manager is not enabled, and therefore the classic trace features can not operate.
Action: Review the java startup parameters to see if the DMS context manager has been disabled (check for properties with a prefix of 'oracle.dms.context')

Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-58055: A failure has occurred updating the condition. Context value "{0}" is not of type "{1}".
Cause: An attempt was made to specify a data type that is not legal for the existing context value.
Action: Execute the command again, using a different data type.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58056: Unable to create an event element.
Cause: There has been a problem parsing the element from the configuration.
Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58057: There has been an error during activation.
Cause: There has been a problem activating the current configuration in the JVM.
Action: Review the cause(s) and action(s) of the nested error(s).

Level: 1

Type: ERROR

Impact: Configuration

DMS-58058: A failure has occurred parsing condition "{0}" when adding filter "{1}"
Cause: There has been a problem with the filter condition.
Action: Correct the syntax for the condition.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58059: An event route exists using destinationID="{0}" and filter(s) "{1}". The destination cannot be removed.
Cause: An event route already exists using destinationID="{0}".
Action: Remove the event route(s) first, before removing the destination.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58060: An event route exists using filterID="{0}" and destination(s) "{1}". The filter cannot be removed.
Cause: An event route already exists using filterID="{0}".
Action: Remove the event route(s) first, before removing the filter.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58061: The class name "{0}" in destination "{1}" does not exist.
Cause: A class name has been specified for the destination, but the class cannot be found.
Action: Check the class name is spelled correctly.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58062: The mandatory property "{0}" is not present in destination "{1}" for class "{2}".
Cause: The destination expected a mandatory property, but that property was not specified.
Action: Execute the command again, specifying the mandatory property, or change the destination class.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58063: The class "{0}", used by destination "{1}", implements FilterProvider. Instances of "{0}" need not, and cannot be associated with user defined filters.
Cause: The class specified may not be used with a user defined filter.
Action: Specify a different class name in the destination.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58064: The DMS event configuration document has failed to parse. The configuration is null.
Cause: There has been a problem generating the configuration from the configuration file.
Action: Check the dms_config.xml configuration file exists, has the correct permissions, and valid XML syntax. Consider reverting to a backup of the configuration file.

Level: 1

Type: ERROR

Impact: Configuration

DMS-58065: Either no condition, or no element, or no document has been passed to buildConditionElement(). Condition="{0}", Element="{1}".
Cause: There has been a problem extracting the condition from the filter.
Action: Check the condition, element and document passed to buildConditionElement are not null.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58066: A null DMS configuration cannot be saved.
Cause: The configuration was null when attempting to activate it in the runtime.
Action: Review the server log, and check the server started successfully.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58067: There are invalid arguments; filter ID="{0}". Check the id, event types and condition are valid for server "{1}".
Cause: One or more of the arguments passed are invalid, or have not been specified where required.
Action: Examine the syntax used for the command, identify the issue, and try again using the correct syntax.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58068: No runtime configuration exists.
Cause: A problem occurred loading the runtime configuration from the dms_config.xml configuration file
Action: Review the server log, and check the server started successfully.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58069: The configuration is invalid for server "{0}".
Cause: An invalid configuration has been detected.
Action: The dms_config.xml configuration file must be corrected manually before configuration changes are allowed.

Level: 1

Type: WARNING

Impact: Configuration

DMS-58070: The destination "{0}" is only valid on the Weblogic platform using the Oracle Corporation (JRocket) VM. The actual platform is "{1}" and VM is "{2}".
Cause: Either the platform is not Weblogic, or the VM is not the Oracle Corporation (JRocket) VM, or both.
Action: No action is required. The destination will be ignored and may be removed from the configuration file during the next update.

Level: 1

Type: WARNING

Impact: Configuration