Errors From Data Adaptors

The following table explains the cause of the various error messages from data adaptors shown in Intelligent Advisor Hub.

Tip: The logging of data validation errors (OPA-VAL-001) can be turned off (for example, if the message log is being filled up with errors caused by expected end user data entry). To do this, in the Actions menu on the Message log page, select Stop logging data validation errors. To re-enable the logging, select Start logging data validation errors in the same menu.

Table 1. Description of data adaptor errors shown in the Message log in Intelligent Advisor Hub

Code

Message

Cause

OPA-VAL-001

Value provided for attribute '[Attribute Generated ID]' in policy model [model:deployment version] failed input validation restrictions - The value for attribute '[Attribute Name]' can not be later than [Date]

[Exception stack trace]

When an input fails validation restrictions. This can occur when:

  • A value has been provided that is outside the range specified for the attribute in Policy Modeling. For example, 50 when the maximum value allowed is 20. For more information on input validation, see Specify Validations On Individual Inputs.
  • A value has been provided for an attribute associated with a value list where the value provided is not in the list.

The value provided may have been input by the user or may be seeded data. When this error occurs, the user may have seen an "Invalid value" or custom message on the interview screen.

Value provided for attribute '[Attribute Generated ID]' in policy model [model:deployment version] failed input validation restrictions - The value for attribute '[Attribute Name]' should be an enumerated value.

OPA-VAL-002

Seed Data transaction error for request

'[Start Session URL]':

Rule error thrown by preseed data.

Message: [Rule Error message]

OR

Seed Data transaction error for request

'[Start Session URL]':

Rule error thrown by data passed to attribute '[Attr]' of entity '[Ent]'.

Message: [Rule Error message]

When a rule error is triggered at the start of an interview, before the first screen is rendered. Caused by loading in data from an adapter which triggers the rule error.

OPA-VAL-003

Error setting value for attribute '[Attribute Generated ID]' in policy model [Deployment Name]:[Deployment Version] - Temporal value contains bad change point dates after [Date]

java.lang.IllegalArgumentException: Temporal value contains bad change point dates after [Date]

at

[More stack trace]

A Field mapped to a policy model attribute with temporal values was given two or more change-point values which were not in chronological order by their date attribute values. Include change-point elements from earliest to latest dates.

For information on how to implement change-points, see Support Temporal Values.

OPA-VAL-004

Error setting value for attribute '[Attribute Generated ID]' in policy model [Deployment Name]:[Deployment Version]- Cannot translate object of type class [Received Type] to a [Expected Type]

java.lang.IllegalArgumentException: Cannot translate object of type class [Received Type Java Class] to a [Expected Type Java Class]

at

[More stack trace]

A Field was given a value different from the type specified in the metadata, for example, a text-val rather than a number-val. Note that all types can alternatively have an unknown-val or uncertain-val.

OPA-VAL-005

Error setting value for attribute '[Attribute Generated ID]' in policy model [Deployment Name]:[Deployment Version] - Cannot determine type of attribute to set value

A Field was given a value using an unrecognized type. If possible at all, this should only be able to happen via Oracle B2C Service.

OPA-VAL-006 Error attempting to resume session for policy mode [Policy Model Name]. Checkpoint data caused the following event to be raised: [Error Event Text] An error event rule has caused a resume session to fail.