desynchronization after DB failover

Hello,

here my Observations :

2 times we note the same problem : For technical reason a DB failover of CPS has been processed. After the failover, the normal jobs (set with a start time) , continue to be executed without error.

But we have 2 chains with a start based on an event raised from the backend system and intercepted by CPS.
each time before the DB failever the interception works properly.
As a db failever occurs , then the event is still properly raised by the backend system, BUT CPS cannot see/intercept it.

As soon as I restart the process server of the backend system in CPS, immediately the events are intercepted and the related jobs start.

Questions :

• Why after a db failover CPS seems loses the “synchronization” with the event history ?
  why an execution of SAP_SynchronizeEventHistoryCriteria does not solve the problem and I have to restart the related process server in CPS ?
• How can I trace the mechanism of the interception as soon as the event has been raised in the backend system ? What J2ee component is involved in this case ?
• Why only the 2 last event raised by the backend system are intercepted and not the previous ?

for info :

Context :

• CPS : version M33.98 / Netweaver 7.31
• Backend system : SAP ECC 6.0 (Release 7.02)

Thanks for your opinion / solution

Kind regards;

Delphine