Siebel Reports Scheduled are Failing With 'Execution Wait Time Exceeds Specified Timeout Limit {0} (seconds)' Error.
(Doc ID 3059506.1)
Last updated on JANUARY 13, 2025
Applies to:
Siebel CRM - Version 22.3 and laterInformation in this document applies to any platform.
Symptoms
When attempting to schedule a Siebel report with thousand records, it is taking hours and then failing with the error below:
From bipublisher.log located under <rootdir>\Middleware\Oracle_Home\user_projects\domains\bip\servers\bi_server1\logs\bipublisher
]]
[2024-01-13T19:35:02.377+00:00] [bi_server1] [NOTIFICATION] [] [oracle.xdo] [tid: 346] [userId: weblogic] [ecid: f052d2b1-a7ed-4a1d-b81e-5e8a7a0ef79e-0000000f,0:2153:1] [APP: bipublisher] [partition-name: DOMAIN] [tenant-name: GLOBAL] [xdojobid: 1109] [essjobid: null] [240113_07350002][dp id:1057475804][sch info:JobId:1109[ESS RequestId:null]]oracle.xdo.dataengine.datasource.plugin.DataAccessException: Execution wait time exceeds specified timeout limit {0} (seconds)[[
The issue can be reproduced at will with the following steps:
1. Log into Siebel Application.
2. Navigate to a view with more than 60 thousand records. For example : Contacts list
3. Schedule Siebel report to run immediately and submit.
4. Log into BIP application and navigate to Report Job History.
5. Review the status of the report job.
Changes
Applied latest Patch 35601492(OBI STACK PATCH BUNDLE 12.2.1.4.230713) on BIP which includes 12.2.1.4.230628, to address security vulnerabilities.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |