36 ODL-52001 to ODL-52816

ODL-52001: deleting log file: {0}, size: {1} bytes

Cause: A log file was deleted because of the rules defined in the current configuration.

Action: This is an information message, no action is needed.

Level: 16

Type: NOTIFICATION

Impact: Logging

ODL-52002: invalid value for parameter {0}: {1}. Value must be greater than zero.

Cause: An invalid value was assigned to a numeric parameter that require a positive value.

Action: Use a value that is greater than zero value for the parameter.

Level: 1

Type: ERROR

Impact: Logging

ODL-52003: invalid value for parameter maxLogSize: {0}. Value must be greater than the value of maxFileSize ({1}).

Cause: The value used for the maxLogSize parameter is smaller than the value used for the maxFileSize parameter, which is not valid.

Action: Enter a value for the maxLogSize parameter that is greater than the value of the maxFileSize parameter.

Level: 1

Type: ERROR

Impact: Logging

ODL-52004: invalid encoding: {0}

Cause: The value used for encoding parameter is not valid.

Action: Enter a valid encoding value.

Level: 1

Type: ERROR

Impact: Logging

ODL-52005: invalid path: {0}. This path is already being used by another log writer instance of a different type.

Cause: There was an attempt to create a log using a path that is already being used by another log, but the two logs are of different types.

Action: Contact Oracle support services.

Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52006: Path cannot be null.

Cause: A null value was used for the log file path.

Action: Enter a non-null value for the path.

Level: 1

Type: ERROR

Impact: Logging

ODL-52007: The log path is not a directory: {0}.

Cause: The value used for the log path is not a directory. Some log types require that the log path be a directory, not a file, because the log file name is fixed.

Action: Enter a directory path instead of a file path.

Level: 1

Type: ERROR

Impact: Logging

ODL-52008: unable to create log directory: {0}

Cause: One or more directories that were used in the log path could not be created.

Action: Make sure that the process has permission to create the directories, or enter a different path. It may also be possible to create the directories manually.

Level: 1

Type: ERROR

Impact: Logging

ODL-52009: The log directory is not writable: {0}.

Cause: The process could not write to the log directory.

Action: Make sure that the process has permission to write to the log directory, or enter a different path.

Level: 1

Type: ERROR

Impact: Logging

ODL-52010: no permission to access log directory: {0}

Cause: The process could not access the log directory.

Action: Make sure that the process has permission to access the log directory, or enter a different path.

Level: 1

Type: ERROR

Impact: Logging

ODL-52011: attempting to operate on a closed LogWriter

Cause: There was an attempt to perform an operation on a log writer that is already closed.

Action: This is possible a programming error. Contact Oracle Support Services. If the problem occurs during process shut down, it is possible that some component is attempting to log a message after the logging system has already shut down.

Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52012: attempting to write to a closed LogWriter

Cause: There was an attempt to writea a message to a log writer that is already closed.

Action: This is possible a programming error. Contact Oracle Support Services. If the problem occurs during process shut down, it is possible that some component is attempting to log a message after the logging system has already shut down.

Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52013: attempting to flush a closed LogWriter.

Cause: There was an attempt to flush a log writer that is already closed.

Action: This is possible a programming error. Contact Oracle Support Services. If the problem occurs during process shut down, it is possible that some component is attempting to log a message after the logging system has already shut down.

Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52014: Maximum log size is reached.

Cause: The maximum size for the log defined in the configuration was reached and the current configuration does not enable automated removal of older log messages.

Action: Review the logging configuration. It may be necessary to increase the maxLogSize parameter, or enable a policy for the automatic removal of older messages.

Level: 1

Type: ERROR

Impact: Logging

ODL-52015: unable to delete old archived file

Cause: There was an attempt to delete an old log file, but the file could not be deleted.

Action: Check that the process has permission to delete the log file.

Level: 1

Type: ERROR

Impact: Logging

ODL-52016: failure to rotate log file: {0}

Cause: There was an attempt to rename a log file, but the operation failed.

Action: Check that the process has permission to rename files.

Level: 1

Type: ERROR

Impact: Logging

ODL-52017: out of log file names

Cause: There was an attempt to rename a log file, but there are no more names that can be used.

Action: Remove some or all of the archived files.

Level: 1

Type: ERROR

Impact: Logging

ODL-52018: unable to write to log ''{0}'': {1}

Cause: There was an error when writing messages to a log file.

Action: See the error message for the root cause.

Level: 1

Type: ERROR

Impact: Logging

ODL-52019: unable to close log ''{0}'': {1}

Cause: There was an error when closing a log file.

Action: See the error message for the root cause.

Level: 1

Type: ERROR

Impact: Logging

ODL-52020: failed to get a lock on file ''{0}'' after {1} milliseconds

Cause: A log file lock could not be acquired within the specified time period, and the log write operation has time-out.

Action: Check that other processes are not holding a lock to the log file.

Level: 1

Type: ERROR

Impact: Logging

ODL-52021: thread interrupted while waiting to lock file ''{0}''

Cause: The thread was interrupted while waiting to acquire a lock on a lock file.

Action: Check that other processes are not holding a lock to the log file.

Level: 1

Type: ERROR

Impact: Logging

ODL-52029: recursive logging detected that exceeds the recursion depth limit of {0}. The handler will not log the message.

Cause: The handler detect recursive logging calls that exceed that maximum configured recursion depth limit.

Action: Review the source code to eliminate logging calls within code that may be called while formatting a log message.

Level: 1

Type: ERROR

Impact: Logging

ODL-52030: invalid property name: {0}

Cause: An invalid property name was used in the logging configuration.

Action: Review the configuration and enter a valid property name.

Level: 1

Type: ERROR

Impact: Logging

ODL-52031: required property ''{0}'' is not found

Cause: A required property was not present in the configuration of a log handler.

Action: Review the configuration and add the required property.

Level: 1

Type: ERROR

Impact: Logging

ODL-52032: invalid format: {0}. Valid formats are: {1}.

Cause: An invalid value for the 'format' property was used in the configuration of an ODLHandler.

Action: Review the configuration and add a valid value for the format property.

Level: 1

Type: ERROR

Impact: Logging

ODL-52033: invalid value for property {0}: {1}.

Cause: An invalid value for used for an ODLHandler property.

Action: Review the configuration and add a valid value for the property.

Level: 1

Type: ERROR

Impact: Logging

ODL-52034: Configuration is invalid: {0} cannot be less than {1}.

Cause: An invalid value for used for a size property in an ODLHandler configuration.

Action: Review the configuration and make sure that the value of the 'maxFileSize' property is not greater than the value of the 'maxLogSize' property.

Level: 1

Type: ERROR

Impact: Logging

ODL-52035: failure to create ODLHandler: {0}

Cause: An ODLHandler instance could not be created.

Action: Check the error message for the root cause.

Level: 1

Type: ERROR

Impact: Logging

ODL-52036: invalid level: {0}. Check spelling and verify that the value is a valid ODL or Java level.

Cause: An invalid level was used in the configuration of a logger or handler.

Action: Review the configuration and enter a valid level.

Level: 1

Type: ERROR

Impact: Logging

ODL-52040: failure to initialize class {0}: property {1} must be defined.

Cause: A required system property was not defined.

Action: Review the process configuration and make sure that the required system property is defined.

Level: 1

Type: ERROR

Impact: Logging

ODL-52041: Use of {0} in logging configuration is deprecated; replacing it with {1}. (File: {2}).

Cause: A deprecated property was used in the logging configuration.

Action: Review the logging configuration and consider replacing the deprecated property. While the configuration may be valid, use of deprecated properties should be avoided.

Level: 1

Type: WARNING

Impact: Logging

ODL-52042: undefined property: {0}.

Cause: An undefined property was used in the logging configuration.

Action: Review the logging and process configuration and either replace the invalid property in the logging configuration, or define a value for the property.

Level: 1

Type: ERROR

Impact: Logging

ODL-52043: expecting one element of type ''{0}''

Cause: The logging configuration contained more than one XML element of a given type, when only one was expected.

Action: Review the logging configuration and remove the extra XML elements.

Level: 1

Type: ERROR

Impact: Logging

ODL-52044: cannot find handler: {0}

Cause: The logging configuration assigned a handler to one or more loggers, but the handler was not defined.

Action: Review the logging configuration and either add the missing handler, or remove any references to the handler.

Level: 1

Type: ERROR

Impact: Logging

ODL-52045: invalid class: {0}

Cause: The logging configuration defined an invalid class for a handler.

Action: Review the logging configuration and make sure that the handler class is valid. The handler class must be either a subclass of java.util.logging.Handler, or implement the oracle.core.ojdl.logging.HandlerFactory interface.

Level: 1

Type: ERROR

Impact: Logging

ODL-52046: cannot find class: {0}

Cause: The logging configuration defined a handler, filter, or error manager class, but that class could not be found.

Action: Review the logging and process configuration and make sure that the class is available in the system classpath, or that the class is visible to the classloader that loads the ODL configuration classes.

Level: 1

Type: ERROR

Impact: Logging

ODL-52047: cannot load or link class ''{0}'': {1}

Cause: The logging configuration defined a handler, filter, or error manager class, but that class could not be loaded due to a linkage error.

Action: Review the logging and process configuration and make sure that the class is available in the system classpath, or that the class is visible to the classloader that loads the ODL configuration classes, or that the correct version of the class is being used..

Level: 1

Type: ERROR

Impact: Logging

ODL-52048: Class ''{0}'' is not of expected type ''{1}''.

Cause: The logging configuration defined a handler, filter, or error manager class, but that class is not a handler, filter or error manager instance.

Action: Review the logging and process configuration and make sure that the class is of the correct type.

Level: 1

Type: ERROR

Impact: Logging

ODL-52049: cannot create instance of class ''{0}'': {1}

Cause: The logging configuration defined a handler, filter, or error manager class, but an instance of that class could not be created.

Action: Review the error message for the root cause.

Level: 1

Type: ERROR

Impact: Logging

ODL-52050: unable to process file ''{0}'', XML parse exception (line: {1}, column: {2}): {3}

Cause: The logging configuration could not be processed due to an XML error in the configuration file.

Action: Review the error message for a description of the XML error, and correct the problem in the configuration file.

Level: 1

Type: ERROR

Impact: Logging

ODL-52051: unable to process file ''{0}''; exception: {1}

Cause: The logging configuration could not be processed due to a unexpected XML parser error.

Action: Review the error message for a description of the root cause.

Level: 1

Type: ERROR

Impact: Logging

ODL-52052: unable to find resource: {0}

Cause: The logging configuration could not be processed due to a missing XML schema or DTD.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52053: unable to create handler instance using class ''{0}''; exception: {1}

Cause: The creation of a handler instance failed because the handler factory threw an exception.

Action: Review the error message for the root cause.

Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52054: The logger ''{0}'' is already defined.

Cause: There was an attempt to add a new logger to the configuration file, but the logger is already defined.

Action: Verify that the logger name is correct.

Level: 1

Type: ERROR

Impact: Logging

ODL-52055: The handler ''{0}'' is already defined.

Cause: There was an attempt to add a new handler to the configuration file, but a handler is already defined.

Action: Verify that the handler name is correct.

Level: 1

Type: ERROR

Impact: Logging

ODL-52056: The logger ''{0}'' is not defined.

Cause: There was an attempt to access a logger in the logging configuration but the logger is not defined.

Action: Verify if the logger name is correct.

Level: 1

Type: ERROR

Impact: Logging

ODL-52057: The handler ''{0}'' is not defined.

Cause: There was an attempt to access a handler in the logging configuration but the handler is not defined.

Action: Verify if the handler name is correct.

Level: 1

Type: ERROR

Impact: Logging

ODL-52058: The handler ''{0}'' cannot be removed because it is being used by logger ''{1}''.

Cause: There was an attempt to remove a handler from the logging configuration, but the handler could not be removed because it is being used by a logger.

Action: Verify that the handler name is correct, or remove the handler from all the loggers first before attempting to remove the handler.

Level: 1

Type: ERROR

Impact: Logging

ODL-52059: The logger ''{0}'' already has handler ''{1}''.

Cause: There was an attempt to add a handler to a logger but the logger already has the given handler.

Action: Verify if the logger and handler names are correct.

Level: 1

Type: ERROR

Impact: Logging

ODL-52060: The logger ''{0}'' does not have handler ''{1}''.

Cause: There was an attempt to remove a handler from a logger, but the logger does not contain the given handler.

Action: Verify if the logger and handler names are correct.

Level: 1

Type: ERROR

Impact: Logging

ODL-52061: The handler ''{0}'' does not have property ''{1}''.

Cause: There was an attempt to remove a property from a handler, but the handler does not have a property with the given name.

Action: Verify if the handler and property are correct.

Level: 1

Type: ERROR

Impact: Logging

ODL-52062: Illegal value for ''{0}'': {1}

Cause: There was an attempt to set a property for a handler or logger, but the value of the property is not valid.

Action: Verify if the handler or loggers properties are valid.

Level: 1

Type: ERROR

Impact: Logging

ODL-52063: Unable to load logging configuration from ''{0}''; exception: {1}

Cause: There was an error while loading the logging configuration file.

Action: Review the error message for the root cause.

Level: 1

Type: ERROR

Impact: Logging

ODL-52064: The handler ''{0}'' is already defined in the target logging configuration document.

Cause: There was an attempt to add a handler to a logging configuration file, but a handler with the given name already exists in the target file.

Action: Review the definition of the new handler.

Level: 1

Type: ERROR

Impact: Logging

ODL-52065: The logger ''{0}'' or a descendant is already defined in the target logging configuration document.

Cause: There was an attempt to add a logger to a logging configuration file, but the logger or one of its descendants is already defined in target logging configuration.

Action: Review the definition of the new logger.

Level: 1

Type: ERROR

Impact: Logging

ODL-52080: Reading logging configuration from ''{0}''.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Logging

ODL-52081: unable to read logging configuration from file ''{0}''; exception: {1}

Cause: There was an error reading the logging configuration from the given file.

Action: Review the error message for the root cause.

Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52082: unable to register logging runtime MBean; exception: {0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Logging

ODL-52083: unable to register log dump; exception: {0}

Cause: There was an error registering the log dump with the FMW Diagnostics Framework.

Action: Review the error message for the root cause. The system may still work, but the log dump will not be available.

Level: 1

Type: WARNING

Impact: Logging

ODL-52084: unable to initialize ODL; exception: {0}

Cause: There was an error initializing Oracle Diagnostic Logging (ODL).

Action: Review the error message for the root cause. Oracle Diagnostic Logging is not properly configured in this system.

Level: 1

Type: ERROR

Impact: Logging

ODL-52085: Reloading logging configuration from ''{0}''.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Logging

ODL-52086: unable to reload logging configuration from file ''{0}''; exception: {1}

Cause: There was an error reloading the logging configuration from the given file.

Action: Review the error message for the root cause.

Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52087: suspicious logging configuration reload. The original configuration was read from file ''{0}'', but the new configuration is being read from ''{1}''.

Cause: The logging configuration is being reloaded, but the configuration file is different from the configuration file used for the initial configuration.

Action: This is probably an error, there should only be one configuration file.

Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52088: The java.util.logging configuration was reloaded.

Cause: The java.util.logging configuration was reloaded, probably via the invocation of LogManager.readConfiguration.

Action: The java.util.logging configuration should not be reloaded programmatically, as this can override the ODL configuration.

Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52501: Unable to get OPMN connection for instance ''{0}''; check that the instance name is valid and that OPMN is running.

Cause: There was an attempt to invoke an operation on a OPMN managed target, but a connection to that target could not be created.

Action: Check the target argument and make sure that the instance and component names are valid, and that OPMN is running.

Level: 1

Type: ERROR

Impact: Logging

ODL-52502: Invalid target. The server name ''{0}'' is not a valid server name, the server is not running, or JRF is not enabled on the server.

Cause: There was an attempt to invoke an operation on a Java EE server target, but the target does not exist or is not valid for the operation.

Action: Check the target argument and make sure that the server name is correct, the server is running, and that JRF is enabled on the server.

Level: 1

Type: ERROR

Impact: Logging

ODL-52801: There is already an active trace with ID ''{0}''. Use a different trace ID or stop the active trace first before starting a new trace with the same ID.

Cause: There was an attempt to start a trace using an ID value that is already being used by another active trace.

Action: Use a different trace ID or disable the existing active trace first before starting a new one with the same ID.

Level: 1

Type: ERROR

Impact: Logging

ODL-52802: There is already an active trace for attribute ''{0}'' with value ''{1}''. The existing active trace must be disabled first before a new one can be started for the same attribute value.

Cause: There was an attempt to start a trace using an attribute value that is already used by an active trace.

Action: Use a different attribute value or disable the existing active trace first before starting a new one with the same attribute value.

Level: 1

Type: ERROR

Impact: Logging

ODL-52803: Unable to complete the start tracing operation. The operation failed on target ''{0}''; cause: {1}

Cause: The start tracing operation cannot be completed because one or more servres are unable to complete the operation.

Action: See the error message for more information on the cause of the server failure.

Level: 1

Type: ERROR

Impact: Logging

ODL-52804: The start tracing operation failed for provider ''{0}''; cause: {1}

Cause: The start tracing operation cannot be completed because a trace provider is unable to complete the operation. See the error message for more information on the cause for the provider failure.

Action: See the error message for more information on the cause of the provider failure. You may try to disable the failing provider to obtain trace data from the other trace providers.

Level: 1

Type: ERROR

Impact: Logging

ODL-52805: Unable to complete the start tracing operation. The operation failed for one or more providers and could not be rolled back. The tracing configuration may be in an inconsistent state. Disable all active traces or restart the servers to reset the selective tracing configuration.

Cause: The start tracing operation failed for one or more providers or servers but could not be rolled back on all servers or providers.

Action: The tracing system may be on an inconsistent state. Disable all active traces or restart the servers to reset the selective tracing configuration.

Level: 1

Type: ERROR

Impact: Logging

ODL-52806: The stop tracing operation failed for provider ''{0}''; cause: {1}

Cause: The stop tracing operation cannot be completed because a trace provider is unable to complete the operation. See the error message for more information on the reason for the provider failure.

Action: See the error message for more information on the cause of the provider failure.

Level: 1

Type: ERROR

Impact: Logging

ODL-52807: Unable to create incident for trace with ID ''{0}''; cause: {1}

Cause: A trace was stopped but an incident could not be created for the trace data.

Action: See the error message for more information on the root causeof the incident creation failure.

Level: 1

Type: ERROR

Impact: Logging

ODL-52808: Invalid expression: {0}

Cause: An invalid expression was passed as a parameter to the startTracing operation.

Action: Review the list of active traces and disable some of the duplicate traces.

Level: 1

Type: ERROR

Impact: Logging

ODL-52809: Multiple active traces match the current request. The request is already being traced with ID ''{0}'' and it will not be traced with ID ''{1}''.

Cause: There are multiple active traces that can be started for the current request, but the request can only be associated with one trace. One or more traces will not be started.

Action: Review the expression and check for incorrect spelling or syntax. See the documentation for details on the expression syntax.

Level: 1

Type: WARNING

Impact: Logging

ODL-52810: A new trace cannot be started because there are too many traces currently active in the system.

Cause: A new trace cannot be started because there are too many traces currently active in the system.There are multiple active traces that can be started for the current request.

Action: Wait until some of the other traces are stopped before trying to start a new one. Contact your system administrator for more information.

Level: 1

Type: ERROR

Impact: Logging

ODL-52811: A new trace cannot be started or stopped for the current HTTP session because there is no current HTTP session.

Cause: A request to start or stop tracing the current HTTP session cannot be executed because there is no HTTP session associated with the current request.

Action: The HTTP session must be already active before tracing operations can be executed for the session.

Level: 1

Type: ERROR

Impact: Logging

ODL-52812: A new trace cannot be started for the current HTTP session because the session is already being traced.

Cause: A request to start tracing the current HTTP session cannot be executed because the session is already being traced.

Action: Stop the active trace before starting a new trace for the same session.

Level: 1

Type: ERROR

Impact: Logging

ODL-52813: A request to stop tracing an HTTP request cannot be executed because the request is not being traced.

Cause: A request to stop tracing an HTTP request cannot be executed because the request is not being traced.

Action: Check if the HTTP request is being traced before trying to stop tracing.

Level: 1

Type: ERROR

Impact: Logging

ODL-52814: Unable to send notification for start tracing event. Tracing will continue on the local server, but may not be enabled on other servers. Cause: {0}

Cause: A JMX notification for a start tracing event could not be sent due to an unexpected exception.

Action: See the error message for more information on the root cause.

Level: 1

Type: WARNING

Impact: Logging

ODL-52815: Unable to send notification for stop tracing event. Tracing is stopped on the local server, but may not be stopped on other servers. Cause: {0}

Cause: A JMX notification for a stop tracing event could not be sent due to an unexpected exception.

Action: See the error message for more information on the root cause.

Level: 1

Type: WARNING

Impact: Logging

ODL-52816: Unable to propagate a {0} event; cause: {0}

Cause: A selective tracing event originating from one server could not be propagated to other servers.

Action: See the error message for more information on the root cause.

Level: 1

Type: WARNING

Impact: Logging