Get Started with Redwood for Oracle Cloud HCM Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Bi Publisher - Scheduled Job Failure Details
Summary
Additional detail to ess_request_historyContent
Hello,
Is it possible to access the log message details for a failed job? I'm familiar with the ess_request_history table but want to get at the actual reason for the failure.
For example:
Waiting Time: 0.5 seconds
Data Fetch Time: 14.9 seconds
Total Execution Time: 28.6 seconds
Job Priority: Normal
Waiting Time: 0.5 seconds
Data Fetch Time: 14.9 seconds
Total Execution Time: 28.6 seconds
Job Priority: Normal
Job processor caused exception
[INSTANCE_ID=bip.bi_server1] [INSTANCE_JOB_ID=8224087]
DATA_PROCESSING_FAILED
[INSTANCE_ID=bip.bi_server1]
There is no data to process
[INSTANCE_ID=bip.bi_server1] oracle.xdo.servlet.scheduler.ProcessingException:
Tagged:
0