liveCache COM routine ended with own error code 3

[Former Member]

Dear All,

I am getting the following error.

liveCache COM routine ended with own error code 3

Appreciate any responses.

Regards

Kumar

[Former Member]

This message was moderated.

[former_member229109]

Hello Venkata,

-> Did you get the liveCache COM routine error code 3 during the liveCache application run?

< See the LCA RC info in /sapapo/om10.

Run TA /n/sapapo/om10 -> Returncode: 3 ->

Object changed since the last access

( om_object_out_of_date )

< click on '? ' to see more detailed text info > >

-> If yes, please create the ticket to the component BC-DB-LCA to get liveCache application support from SAP on this issue.

-> Without knowledge of the application scenario, the system version & liveCache/application version it's difficult to give additional suggestions about this error .

In some cases the debugging or additional LCA tracing will be needed to get clear on the issue with the liveCache COM routine error code 3.

Thank you and best regards, Natalia Khlopina

[former_member229109]

Hello Kumar,

If the LCA routine failed with LCA RC 3 => APO_OBJ_OUT_OF_DATE

Error. As Ashwath wrote, it could be, that 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. If possible, you could try using transactional simulations to bypass this error.

But it could be another reason.

Did you see the GUID of the object with RC error during the debug?

Are you using standard SAP reports/functions in your application run?

< See the LCA RC info in /sapapo/om10.

Run TA /n/sapapo/om10 -> Returncode: 3 ->

Object changed since the last access

( om_object_out_of_date )

< click on '? ' to see more detailed text info > >

But for the further analysis of this issue additional information is needed:

-> What is the version of your system? SCM SP ?

-> What are the versions of the liveCache/LCA including the builds?

-> What kind of the application scenario did you run at the time when the problem occurred?

-> What is the name of the LC routine which is failed?

-> We need to check the issue with the LCA trace < !! > & may be additional information is needed;

-> As SAP customer you could create the ticket to the component

BC-DB-LCA to get liveCache application support from SAP on this issue.

Thank you and best regards, Natalia Khlopina

Message was edited by:

Natalia Khlopina

[Former Member]

Hi Kumar,

can you please post the knldiag.err file here?

Errorcode 3 means 'Object out of date'. This error is raised 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. If possible, try using transactional simulations to bypass this error.

Thanks,

Ashwath