Cause: cannot scan adress from the given data stream
Action: *Define: ONS_PM_ADDRESS_ERROR
Level:
Type:
Impact: Other
ENS-00056: Connection thread create %s (%s)
Cause: The dedicated connection thread could not be created.
Action: *Define: ONS_CONN_THREAD_CREATE_ERR
Level:
Type:
Impact: Other
ENS-00057: Closing active connection %s
Cause: The active connection is being stopped.
Action: *Define: ONS_CONN_ACTIVE_CLOSE
Level:
Type:
Impact: Other
ENS-00058: Passive connection %s missing connect
Cause: In a passive connection, the first message must be a connect. This may be a malicious attack on the specified ONS port.
Action: *Define: ONS_CONN_MISSING_CONNECT
Level:
Type:
Impact: Other
ENS-00059: Local connection %s missing form factor%s
Cause: The local passive connection must contain the current form factor. This message is logged when it does not, which is caused either by an OPMN managed process started as a different user than OPMN, or an attempt is being made to issue an OPMN request as a user other than the one that started OPMN.
Action: Check if an OPMN managed process was manually started as a different user than OPMN (and stop it). Check if requests to OPMN are being issued by the wrong user. *Define: ONS_CONN_MISSING_FORMFACTOR
Level:
Type:
Impact: Other
ENS-00060: Local connection %s invalid form factor%s
Cause: The local connection contains an invalid form factor. This is caused either by an old application left running from an alternate ORACLE_HOME with the same notification-server local port as the current OPMN, or the local port was changed in opmn.xml without first shutting down OPMN.
Action: Check if an OPMN managed process was started from a different ORACLE_HOME than the current running OPMN (and stop it). Check if the notification-server local port in opmn.xml was changed without shutting OPMN down first (stop this OPMN). *Define: ONS_CONN_INVALID_FORMFACTOR
ENS-00099: XML parse: %s:\tunknown process-set %s.
Cause: An invalid process-set was specified for the dependency in opmn.xml.
Action: *Define: OPMN_NLS_MSG_00162
Level:
Type:
Impact: Other
ENS-00100: XML parse: %s:\tunknown process-type %s.
Cause: An invalid process-type was specified for the dependency in opmn.xml.
Action: *Define: OPMN_NLS_MSG_00163
Level:
Type:
Impact: Other
ENS-00101: XML parse: %s:\tunknown component %s.
Cause: An invalid component was specified for the dependency in opmn.xml.
Action: *Define: OPMN_NLS_MSG_00164
Level:
Type:
Impact: Other
ENS-00102: XML parse: %s\tunknown ias instance %s\tAssuming remote dependency.
Cause: An unknown ias instance was specified for the dependency in opmn.xml -- this dependency will be assumed to be for a managed process-set on a remote OPMN server.
Action: *Define: OPMN_NLS_MSG_00165
Level:
Type:
Impact: Other
ENS-00103: XML parse: circular managed process dependency:%s
Cause: A managed process dependency has been configured in opmn.xml that eventually leads to a dependency upon itself.
Action: *Define: OPMN_NLS_MSG_00166
Level:
Type:
Impact: Other
ENS-00104: %s: Proc %u:%u could not schedule %s (%s)
Cause: The specified job could not be scheduled for the process referenced by the given dependency for autostop or autorestart.
Action: *Define: OPMN_NLS_MSG_00167
Level:
Type:
Impact: Other
ENS-00105: XML parser init: character set initialization failed.
Cause: The XML parser failed its character set initialization.