Details Required when Logging an Oracle Utilities Real-time Scheduler (ORS) v1 Service Request
(Doc ID 472734.1)
Last updated on OCTOBER 17, 2019
Oracle Real-Time Scheduler - Version 10.1.0 and later Information in this document applies to any platform.
When reporting any issues with Oracle Real-Time Scheduler (ORS), it is necessary to provide Customer Support with steps to recreate the issue, screen-shots, specific error messages and any other information relevant to the problem. This detail is needed in conjunction with all applicable log files or traces detailed below.
Collecting the logs from all ORS components is generally required to ensure an accurate and efficient investigation. While some logs may not be required for certain problems, it's not always clear which logs can be omitted therefore, we recommend that all logs be gathered at the time of logging an SR to ensure they are available if needed.
For some types of issues, certain logs are more likely to contain the most important details for beginning an investigation. To help prioritize the gathering and upload of logs in these cases the order of logs listed for each case below are in the order of highest to lowest priority. We do still recommend gathering and providing all logs from all components at the time of the issue to ensure they are available if needed. Failure to provide this information at the time of logging an SR greatly increases the time required for investigation and may limit our ability to resolve your issue.
This bulletin is recommended for consideration by anyone logging a service request for ORS.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!