Siebel Business Process & Functionality (MOSC)

MOSC Banner

CTI: Errors when both Agent and also AfterWork attempt to update same EventLog activity record at en

edited Dec 12, 2012 1:39PM in Siebel Business Process & Functionality (MOSC) 1 commentAnswered
It is standard Siebel behavior that two different sessions cannot update the same record.     The solution is that one session must wait until after the other session has committed the record, then re-query for the record, then can commit it.

CTI Bookshelf has a note about this common occurrence if an agent is updating the same Log record that will be updated by AfterWork log parameter as the call is terminated.

One customer has offered the following experience in working around this behavior.   

This has not been tested within Oracle, but I thought I would offer it for information, and to see if others have come up with any other approaches ?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center