Symptom
- Interface Channel monitoring or Application monitoring has stopped working, data is not being collected after updating ST-PI and/or ST-A/PI on the managed system.
- For Interface Channel monitoring objects, while running SE38 -> ICMON_TROUBLESHOOT_IS the results are "No entry in ACE_DB_EVENT" and/or "No entry in E2EREP_MAPPING".
-
On Solution Manager Alerting Framework, DPC PULL CORE extractor of managed system with extended context "ST_PI_CLNTXXX" has yellow warnings with a return code = 95 for data provider /SDF/E2E_BPMON_IC_MON_PROVIDER and/or /SDF/E2E_BPMON_APPMON_PROVIDER.
- On Solution Manager Alerting Framework, DPC PULL CORE extractor of managed system with extended context "ST_PI_CLNTXXX" shows red rating and message "/SDF/E2E_BPMON_APPMON_PROVIDER: An exception with the type CX_SY_REF_IS_INITIAL was raised, but not handled locally or declared in a RAISING clause."
-
On managed system, in SLG1 (Object /SDF/E2E, Subobject: /SOMO/BPMON) you find error message: "Failed to lock object XXX" or "Fetch for ... returned RC = 95. Scheduling skipped".
- On managed system, the logs of job BPM_DATA_COLLECTION* show message "No open MO found".
Read more...
Environment
SAP SOLUTION MANAGER 7.2
Product
Keywords
interface monitoring, idocs, appmon, DPC PULL CORE, /SDF/E2E_BPMON_IC_MON_PROVIDER, /SDF/E2E_BPMON_APPMON_PROVIDER, RC=95 , KBA , SV-SMG-MON-BPM-MON , Monitoring , SV-SMG-MON-IPO-IC , Interface Monitoring , SV-SMG-MON-BPM-DCM , Data Consistency Management , 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