Symptom
Category ABAP programming error
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_LMDB_UNEXPECTED_CARDINALITY
ABAP Program CL_LMDB_API_FOR_CIM===========CP
Application Component SV-FRN-INF-LDB
----------------------------------------------------------------------------------------------------
|What happened? |
| The exception of class "CX_LMDB_UNEXPECTED_CARDINALITY" was triggered but not |
| caught anywhere in the |
| call hierarchy. |
| |
| Since exceptions represent error situations, and this error was not |
| adequately responded to, ABAP program "CL_LMDB_API_FOR_CIM===========CP" had |
| to be terminated. |
----------------------------------------------------------------------------------------------------
|Error analysis |
| An exception has occurred in class "CX_LMDB_UNEXPECTED_CARDINALITY". As this |
| exception was not |
| caught, a runtime error occurred. The reason for the exception |
| occurring was: |
| 1 max. results, 2 found, first result = |
| 'SAP_DatabaseSystem.CreationClassName="SAP_DatabaseSystem",Name="<SID>.DBTypeForS |
| AP.SYB.SystemHome.<host>' |
| |
----------------------------------------------------------------------------------------------------
Read more...
Environment
SAP Focused Run
Product
Keywords
UNCAUGHT_EXCEPTION, CX_LMDB_UNEXPECTED_CARDINALITY, SAP_DatabaseSystem, CL_LMDB_API_FOR_CIM===========CP, ASSERT_ONE_RESULT , KBA , SV-FRN-INF-LDB , Landscape Management Database (LMDB) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview