Dear Experts,
I had read below content on internet on COPA extraction. We have implemented note 1274565 too to correct the issue. The issue of RD156 is now resolved.
My question is if COPA is successful in getting a lock on CESVB during extraction doesnt it block vf01 activities which are done during the time on extraction ? How does the CESVB lock concept work when extractor has already got the lock and vf01 processing is attempted during that time.
CO-PA Datasource Lock
COPA Lock
- CO-PA Datasource extracts Actual & Plan Data
- CO-PA deltas are based on Timestamp with a safety interval of 30 minutes.
- The CO-PA Actual extractor at times fails every hour with error message
“The selected datasource is locked by another process”Root Cause - CO-PA conflict
- A conflict between CO-PA and VF01 occurs.
- VF01 is a billing transaction which establishes an update lock on structure CESVB.
- CO-PA extractor also accesses the CSEVB structure while actual and plan extraction and fails if it doesn’t get the lock on it.
Resolution
- Vigil SM12 in R/3 for CESVB.
- Stop CO-PA Extractor if there is a lock on CESVB.
- Monitor this lock as VF01 holds it for few seconds.
- If the lock persists for quite some time, delete the lock.
- Start the CO-PA extractor once CESVB lock is released.
- Make necessary change in extractor logic to access CESVB ten times instead of only once. This should be done if the issue becomes consistent.