Why Does Siebel MQReceiver Log Files Show Entries Of 2-3 Seconds Time Gaps Frequently Where There Is No Execution Nor Details Occurring?
(Doc ID 2139085.1)
Last updated on FEBRUARY 03, 2019
Applies to:Siebel CRM - Version 18.104.22.168.14 [IP2013] and later
Information in this document applies to any platform.
Why does the Siebel MQReceiver log files show entries of 2-3 seconds time gaps frequently where there is no execution/details occurring? Such as the following showing a 2 second gap in between the log entries:
ObjMgrSqlCursorLog Prepare 5 0000001257030050:38480 2016-04-05 17:40:06 Begin: PrepareStmt for Sql Cursor at 3f865d98
ObjMgrSqlCursorLog Prepare 5 0000001257030050:38480 2016-04-05 17:40:06 End: PrepareStatement for Sql Cursor at 3f865d98
ObjMgrSqlLog Detail 4 0000001257030050:38480 2016-04-05 17:40:08
***** SQL Statement Prepare Time for SQL Cursor with ID 3F865D98: 0.000 seconds *****
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|