51 ORAMED-01001 to ORAMED-09001

ORAMED-01001: Error occurred while assigning to target "{0}" using expression "{1}".

Cause: Error occurred while assigning to target "{0}" using expression "{1}".

Action: Check if source message has right values or source expression is valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01002: Metadata Error occurred while assigning to target "{0}" using invalid expression "{1}".

Cause: Metadata Error occurred while assigning to target "{0}" using invalid expression "{1}".

Action: Fix the expression.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01101: Error evaluating filter expression.

Cause: Error evaluating filter expression.

Action: Fix the filter expression.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01102: Invalid filter expression "{0}"

Cause: Invalid filter expression "{0}"

Action: Fix the filter expression.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01201: Error occurred while transforming payload.

Cause: Error occurred while transforming payload.

Action: Review the XSL or source payload. Either the XSL defined does not match with the payload or payload is invalid.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01202: Fatal error occurred while transforming payload using XSL "{0}" for target part "{1}"

Cause: Fatal error occurred while transforming payload using XSL "{0}" for target part "{1}"

Action: Review the XSL for any syntax error.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01203: No part exist with name "{0}" in source message.

Cause: No part exist with name "{0}" in source message.

Action: Review the transformation definition in mplan.Contact Oracle Support if the error cannot be fixed.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01301: Schematron validation fails with error {0}

Cause: Schematron validation fails with error {0}

Action: Fix the payload.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01302: Response payload for operation "{0}" is invalid.

Cause: Response payload for operation "{0}" is invalid.

Action: Response received by Mediator was either invalid or null. Verify if the service being invoked by Mediator is functioning properly. You can also try invoking the service directly and see if it sends back proper response.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01303: XSD schema validation fails with error {0}

Cause: XSD schema validation fails with error {0}

Action: Fix payload and resubmit.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01304: Schematron validation failure.

Cause: Schematron validation failure.

Action: Fix payload or schematron definition and resubmit.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01305: Group Id validation failure.

Cause: Group Id validation failure.

Action: Group Id is empty. Fix payload and resubmit.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01306: Sequence Id validation failure.

Cause: Sequence Id validation failure.

Action: Sequence Id is empty. Fix payload and resubmit.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01351: Unable to execute "{0}" method on callout instance of "{1}"

Cause: Unable to execute "{0}" method on callout instance of "{1}"

Action: Check server log for any exceptions. Check if there is an issue in implementation of Java callout class.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01360: Wrong source message type. Neither a NormalizedMessage nor a BusinessEvent, message type class :{1}

Cause: Wrong source message type. Neither a NormalizedMessage nor a BusinessEvent, message type class :{1}

Action: Contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01361: Mediator does not support the Resequencing strategy."{0}"

Cause: Mediator does not support the Resequencing strategy."{0}"

Action: Contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01362: Unexpected runtime error occured while processing the message.

Cause: Unexpected runtime error occured while processing the message.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02001: This error occurs because of invalid filter expression "{0}". Reason : {1}

Cause: This error occurs because of invalid filter expression "{0}". Reason : {1}

Action: Review the filter expression and check for possible syntax errors in the filter expression.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02002: Invalid filter metadata. Reason : {0}

Cause: Invalid filter metadata. Reason : {0}

Action: Fix the filter condition metadata.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02051: Invalid callout implementation "{0}".

Cause: Invalid callout implementation "{0}".

Action: Fix the callout implementation.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02101: Cannot load XSL transform into the cache for XSL or XSLT "{0}" Reason : {1}

Cause: Cannot load XSL transform into the cache for XSL or XSLT "{0}" Reason : {1}

Action: Check XSL file for any syntax error and fix the same.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02102: Invalid part type "{0}".

Cause: Invalid part type "{0}".

Action: Provide right parttype.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02103: Invalid assign expression "{0}".

Cause: Invalid assign expression "{0}".

Action: Check assign xpath expression for any syntax error. If there are any syntax error, correct the xpath expression.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02201: Could not load schema document into the cache for XSD "{0}". Reason : {1}

Cause: Could not load schema document into the cache for XSD "{0}". Reason : {1}

Action: Check the XSD schema for any syntax error and fix the same.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02202: Invalid part name in metadata for schematron validator "{0}"

Cause: Invalid part name in metadata for schematron validator "{0}"

Action: Fix the schematron metadata.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02203: Could not load schematron file {0}

Cause: Could not load schematron file {0}

Action: Provide the correct schematron document.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02204: Could not load wsdl interface for message with component dn "{0}".

Cause: Could not load wsdl interface for message with component dn "{0}".

Action: Fix the component to point to valid wsdl.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02205: Schematron document for schematron file {0} is invalid.

Cause: Schematron document for schematron file {0} is invalid.

Action: Fix the schematron document.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02206: Could not create XSD validator for schema with target namespace "{0}" for message {1}

Cause: Could not create XSD validator for schema with target namespace "{0}" for message {1}

Action: Check XML schema for any syntax error.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02301: Could not load mediator mplan information. Reason : {0}

Cause: Could not load mediator mplan information. Reason : {0}

Action: Check your mediator mplan for any syntax error.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02302: Could not load metadata manager. Reason : {0}.

Cause: Could not load metadata manager. Reason : {0}.

Action: Check your composite configuration.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02303: Composite reference {0} not found for operation {1}

Cause: Composite reference {0} not found for operation {1}

Action: Check your composite.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02304: Could not load mediator mplan for componentDN "{0}" . It may be undeployed.

Cause: Could not load mediator mplan for componentDN "{0}" . It may be undeployed.

Action: Using SOA Enterprise Manager, check if composite is deployed. If the composite is not deployed, you can try deploying the composite again.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02305: Could not find mediator case for case name "{0}" . Mediator component may be redeployed with different case names

Cause: Could not find mediator case for case name "{0}" . Mediator component may be redeployed with different case names

Action: This message will be errored out. Fix the mplan by adding the right case and then recover it through error hospital.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02401: Got invalid response from decision service : {0}

Cause: Got invalid response from decision service : {0}

Action: Ensure that the decision service used by the mediator is configured properly.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02402: Could not invoke decision service : {0}

Cause: Could not invoke decision service : {0}

Action: Ensure that the decision service used by the mediator is configured properly.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02403: Dynamic mplan returned by decision service : is invalid. Mplan returned by decision service : {0}

Cause: Dynamic mplan returned by decision service : is invalid. Mplan returned by decision service : {0}

Action: Ensure that the decision service used by the mediator is configured properly.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03001: Unable to lock Resequencer Groups for containerId "{0}" and timestamp "{1}"

Cause: Unable to lock Resequencer Groups for containerId "{0}" and timestamp "{1}"

Action: Unable to lock Resequencer Groups. check your Database connection

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03002: Unable to retreive locked Resequencer Groups for containerId "{0}" and timestamp "{1}"

Cause: Unable to retreive locked Resequencer Groups for containerId "{0}" and timestamp "{1}"

Action: Unable to retreive lock Resequencer Groups. check your Database connection

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03003: Unable to store locked Resequencer Group."{0}"

Cause: Unable to store locked Resequencer Group."{0}"

Action: Unable to store Resequencer Group. check your Database connection or check data

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03004: Unable to store locked Resequencer Message."{0}"

Cause: Unable to store locked Resequencer Message."{0}"

Action: Unable to store Resequencer Message. check your Database connection or check data

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03005: Unable to unlock Resequencer Groups for containerId "{0}" and timestamp "{1}"

Cause: Unable to unlock Resequencer Groups for containerId "{0}" and timestamp "{1}"

Action: Unable to unlock Resequencer Groups. check your Database connection

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03101: Unable to get subscriptions for message "{0}"

Cause: Unable to get subscriptions for message "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03102: Error creating cache for cache policy "{0}". Reason : {1}

Cause: Error creating cache for cache policy "{0}". Reason : {1}

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03103: Cannot load Cache entry with NULL or EMPTY key.

Cause: Cannot load Cache entry with NULL or EMPTY key.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03104: Do not cache RuntimeESBSystem object for NULL or EMPTY system GUID.

Cause: Do not cache RuntimeESBSystem object for NULL or EMPTY system GUID.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03105: Could not read WSDL Definition for WSDL with NULL or EMPTY file name.

Cause: Could not read WSDL Definition for WSDL with NULL or EMPTY file name.

Action: The WSDL file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03106: Do not cache WSDL Definition for NULL or EMPTY WSDL file name.

Cause: Do not cache WSDL Definition for NULL or EMPTY WSDL file name.

Action: The WSDL file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03107: Could not read Schema Document for XSD with NULL or EMPTY file name.

Cause: Could not read Schema Document for XSD with NULL or EMPTY file name.

Action: The XSD schema file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03108: Do not cache Schema Document for NULL or EMPTY XSD file name.

Cause: Do not cache Schema Document for NULL or EMPTY XSD file name.

Action: The XSD schema file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03109: Could not read parsed filter expression for NULL or EMPTY expression.

Cause: Could not read parsed filter expression for NULL or EMPTY expression.

Action: The filter expression is null or empty. Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03110: Information to process an incoming callback message is not available.

Cause: Information to process an incoming callback message is not available.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03201: Retry of deferred message failed.

Cause: Retry of deferred message failed.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03202: Retry of callback message failed.

Cause: Retry of callback message failed.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03203: Retry of timeout message failed.

Cause: Retry of timeout message failed.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03301: Unexpected exception in case execution "{0}"

Cause: Unexpected exception in case execution "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03302: Unexpected exception in oneway operation "{0}" on reference "{1}".

Cause: Unexpected exception in oneway operation "{0}" on reference "{1}".

Action: Check whether the reference service is properly configured and running or look at exception for analysing the reason or contact oracle support.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03303: Unexpected exception in request response operation "{0}" on reference "{1}".

Cause: Unexpected exception in request response operation "{0}" on reference "{1}".

Action: Check whether the reference service is properly configured and running or look at exception for analysing the reason or contact oracle support.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03304: Unexpected exception in async request execution "{0}"

Cause: Unexpected exception in async request execution "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03401: Context lookup failed "{0}"

Cause: Context lookup failed "{0}"

Action: Make sure the topic is mapped to a jndi tree.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03402: Error creating "{0}"

Cause: Error creating "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03403: Subscriber not exist for system "{0}"

Cause: Subscriber not exist for system "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03405: Error converting field "{0}"

Cause: Error converting field "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03406: Publisher not exist for system "{0}"

Cause: Publisher not exist for system "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03408: Unable to store deferred message "{0}"

Cause: Unable to store deferred message "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03409: Invalid, premature, or already-handled callback message. No correlation found for message with conversation id "{0}"

Cause: Invalid, premature, or already-handled callback message. No correlation found for message with conversation id "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03501: Unable to start transaction; transaction status is "{0}"

Cause: Unable to start transaction; transaction status is "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03502: Unable to resume transaction

Cause: Unable to resume transaction

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03503: Unable to commit transaction; transaction status is "{0}"

Cause: Unable to commit transaction; transaction status is "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03504: Unable to rollback transaction; transaction status is "{0}"

Cause: Unable to rollback transaction; transaction status is "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03505: "{0}" object not found in jndi tree

Cause: "{0}" object not found in jndi tree

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03506: Unable to get transaction status

Cause: Unable to get transaction status

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03507: Unable to set rollback only for transaction; transaction status is "{0}"

Cause: Unable to set rollback only for transaction; transaction status is "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03508: one of the routing rule executions resulted a transaction rollback.

Cause: one of the routing rule executions resulted a transaction rollback.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03509: Unable to suspend transaction.

Cause: Unable to suspend transaction.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03510: Error obtaining Transaction Manager.

Cause: Error obtaining Transaction Manager.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03601: Unable to create transformer due to: "{0}"

Cause: Unable to create transformer due to: "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03602: Unable to create document.

Cause: Unable to create document.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03603: Unable to register base function "{0}" for "{1}"

Cause: Unable to register base function "{0}" for "{1}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03651: Unable to create callout instance for "{0}"

Cause: Unable to create callout instance for "{0}"

Action: Make sure your callout configuration is proper.Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03652: Unable to execute "{0}" method on callout instance of "{1}"

Cause: Unable to execute "{0}" method on callout instance of "{1}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03802: Unable to create initial context.

Cause: Unable to create initial context.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03803: Unable to initialize Container Id Manager.

Cause: Unable to initialize Container Id Manager.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04001: Error executing service due to server down "{0}". Reason : {1}

Cause: Error executing service due to server down "{0}". Reason : {1}

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04101: Error receiving DB message.

Cause: Error receiving DB message.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04102: Error publishing DB message.

Cause: Error publishing DB message.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.

Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-09001: Parameter name contains "{0}" qname "{1}"

Cause: Parameter name contains "{0}" qname "{1}"

Action: Verify Name-Value parameters to be of the form 'name1=value1 name2=value2' with value not having any spaces.

Level: 1

Type: ERROR

Impact: Programmatic