Debugging a failed consolidation run

[Former Member]

We're on BPC 10.1 NW. Recently when we ran the consolidation, even after couple of hours the consolidation monitor showed the process is 'Running'. Usually it would take about 1-2 mins to complete the run but for once it got freeze for quite long time. Later we 'Reset' the process in consolidation monitor and when we reran it, the consolidation run was successful.

I checked the UJP_PROC_STEP table, based on the process ID it showed that the run has failed. I checked the UJP_PROC_LOG table and saw that the run ended at the last but one step during write back of records, last step being the end of write back. We couldn't find short dumps on ST22 or SLG1...

To analyze what was the root cause of the issue, could you guide on what else needs to be done to avoid such future occurrences.

Thank you

[Former Member]

Hi Lucas, the process ended (failed) long back and there are no failed runs after that. Probably we shall set a external break point in CL_UJP_CONSOLIDATION and try to debug the process, but for now I'm more interested in understanding what went wrong which caused the consolidation run to hung for couple of hours.

[lucas_costa3]

Your question was how to debug a failed a consolidation, to debug you need to set the breakpoints and run it again.

It can be a number of things, but if this only happened once, it is likely to be related to the state of your system at the time. If it's happening again, you should definitely debug and find the cause. Sometimes, not even debugging, but turning the traces on for example (SAT or ST12) would tell you the bottlenecks in the process.

Also, check https://blogs.sap.com/2018/03/05/embedded-consolidation-troubleshooting/ (this is for Embedded, but might be useful).

[lucas_costa3]

Hi, to check whether the process is still running you can use SM50 (Current processes).

To debug the process look for the class CL_UJP_CONSOLIDATION and set an external break point in the method RUN_CONSOLIDATION