live cache error

[Former Member]

Hi,

The error

' Application error in the release to live cache'

'COM - ERROR 2'

occured in the batch job execution. In spool list of that job we found this error, but job status is finished.

APO 3.10

Pls tell me what causes this error and how to solve?

thanks in adv.

[Former Member]

Hi PG,

can you please give more details about COM error 2 as we are also facing this issue when releasing forecast using bathc jobs.

Regards

Pawan

[former_member187488]

Hello,

There're two similar COM errors regarding lock conflict.

COM error 2 occurs when,

A liveCache object could not be locked, because it is in use by a different process (user).

COM error 3 occurs when,

LiveCache tries to access an object that has been changed by a different transaction since the start of the current transaction. This usually happens during highly parallel operation on real data.

So first please avoid other processing when running the job. And you should be aware that if parallel processing is used in your job, sometimes the COM error 2 or 3 is unavoidable, e.g., you have fixed aggregates defined for your MPOS.

In case that fixed aggregates are defined in your MPOS, and you want to run DP job with parallel processing, it is suggested that you first deactivate the fixed aggregates before you start the job, and re-activate them after the job. Otherwise parallel processing may affect the performance instead of improve the performance, because the failed CVCs will be reprocessed (Note 1243265) and locking conflict may happen again and again.

Best Regards,

Ada

[Former Member]

This error happens when the batch job is trying to do something while a CVC is locked or corrupted. Check using the job logs if something was hapening at the same time or if someone was on a CVC in the planning area (though you get specific user LOCKED errors in that case)

Run the Planning area consistency jobs and the PLOB - TS sync jobs and run the job again for the specific combinations that got this error

Check if this is happeninig occassionally or was a freak happening

[Former Member]

Hi,

Do you know where you can see the "specific user LOCKED errors" referred to above? We occasionally have the same problem as descibed above and have ruled out other DP jobs running at the same time. It looks like a user is in the planning book on a CVC in change mode. The problem is we cannot tell which user it is and we usually detect the problem some hours after it has occurred, therefore looking in SM12/RS12 does not help. Thanks.

Laurence.

[srinivas_krishnamoorthy]

Can you specify what you were doing when this error came up ? Was it a release to SNP job or something else ?

COM error is a major error in Live Cache. I would suggest you to look into LC10 transaction and check if you see all greens. In the main menu under APO Administration, there are consistency check jobs that you would need to run to make sure everything is fine in Live Cache. Also run LC consistency check in the planning areas you are dealing with.

Please definitely check OSS notes and also the SAP Forum under LiveCache and Db for further clues putting appropriate search terms.

[Former Member]

the below error showing many times in spool list of the batch job.

=== Error start ====================================================

New order

Object is locked at present

Error end

Application error in the release to liveCache

COM - error 2

COM - error 2

COM - error 2 .....

In LC10 status is green. If this is bcoz object locked, how to check which object locked at that time and who locked it?

regards

P G

[Former Member]

Hi

As Srinivas says it would be useful to know what batch job is causing this error, is it a release from DP to SNP for example?

Regards

Ian

[Former Member]

this is the job

OFC_EXS_DLY_REL2

[Former Member]

🐵

P G - What area do you work in?

[Former Member]

If your background is related to Demand planning.

Please do the consistency check of time series,

After doing consistency check this error will go off