When running RLMMDB_CR_CONTENT_HASH as directed in SAP Note - 1939864 - Check if SAP CR Content is corrupt in LMDB or SLD the job fails after one second with the following error
"Internal session terminated with a runtime error UNCAUGHT_EXCEPTION (see ST22"
In St22 the following dump is observed.
"Category ABAP Programming Error
Runtime Errors UNCAUGHT_EXCEPTION
ABAP Program CL_LMDB_CR_CONTENT_HASHER=====CP"
| An exception has occurred that was not caught.
| Exception 'CX_WBEM_EXCEPTION' was raised, but it was not caught anywhere along
| call hierarchy.
| Since exceptions represent error situations, and this error was not
| adequately responded to, ABAP program 'CL_LMDB_CR_CONTENT_HASHER=====CP' had
| to be terminated.
| An exception has occurred which is explained in more detail below. The
| exception, which is assigned to class 'CX_WBEM_EXCEPTION' was not caught and |
| therefore caused a runtime error. The reason for the exception is:
| Invalid response from HTTP server: No result for CIM operation
SAP Solution Manager 7.2
RLMMDB_CR_CONTENT_HASH, SLD , Class CX_WBEM_EXCEPTION, CL_LMDB_CR_CONTENT_HASHER=====CP, Invalid response from HTTP server: No result for CIM operation, "GET_SORTED_INSTANCE_HASHES" , KBA , SV-SMG-LDB , Landscape Management Database (LMDB) , BC-CCM-SLD , System Landscape Directory / Component Repository , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.