Enhancing Application Error Usability
Application Event logs now display error messages that retain actionable, user-relevant information while omitting internal system details such as stack traces, implementation references, and redundant data already present in report fields. The new format ensures error messages remain clear and helpful, with standardized placeholder text used where technical information has been removed (e.g., “Technical exception details have been removed…”). When your action is applicable, concise guidance is included; for other errors, you are directed to contact support with the new Error ID for further investigation.
The Application Error Event Report has also been enhanced as part of this release.
- The report now features a new "Error ID" column positioned after the existing "Application Event ID," providing a direct reference for troubleshooting and support.
- The "Event Status" and "Resolution Comments" columns has been removed, as relevant context is now included within the message description when applicable.
- Reference information has been added to the report, providing explanations for each column. This includes a list of possible events with descriptions of when they may be triggered, along with guidance on how to effectively use the report for error triage.
This update provides you with streamlined, readable error logs for more efficient troubleshooting and improved support interactions.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- Only new error logs and reports are affected; prior events remain unchanged.
- Use the Error ID when contacting Oracle Support for troubleshooting.
- Groovy-related error messages are not affected by this release.
- Error messages are now shorter and may omit redundant or technical details already available in other fields.
Key Resources
- For more information on the associated Customer Ideas, see these resources: