Oracle Errors

This page is accessed via Configuration and Administration > Power Data > General > Oracle Errors.

Use this page to configure tracking and translating of Oracle errors into end-user messages.

When Oracle Transportation Management catches a SqlException it:

• Retrieves the error code.
• Determines if the error is due to a constraint (primary, foreign or check). If so, Oracle Transportation Management parses the constraint name.
• Looks up cause/solution translation IDs from the ORACLE_ERROR table based on the error and possible constraint.
• If found, adds a compound cause to the exception.

• Note: The cause/solution messages within ORACLE_ERROR do not support context parameters. OTM does not support parsing the original SQL to retrieve bind parameters. The SQL statement and Oracle error code are always available as a nested cause of the error, providing context information for support or advanced users.

Oracle Errors provide user-friendly descriptions of Oracle ORA errors. In the Constraint field, you can enter any text if the errors do not involve constraints. For errors that involve constraint failures, each constraint can map to a user-defined translatable message. The constraint field is the Oracle constraint name (e.g. FK_OR_ASSIGID) for these errors.

As an example, assume a user tries to delete an itinerary that is on an existing shipment. The error displayed is:

The itinerary could not be deleted because it has been assigned to an order release.

more...

delete from itinerary where itinerary_gid=?; [ GUEST.SAMPLE]
ORA-2292: integrity constraint ( FK_OR_ASSIGNED_ITIN) violated - child record found

The following classification of Oracle errors are mapped in the ORACLE_ERROR table:

• SQL parsing or evaluation errors - to support diagnosis of user-defined Saved Query SQL
• Resource errors - out of memory, extents
• Primary key, foreign key, constraint errors
• VPD policy errors
• Communication, connection errors