What is a specific reason why some systems are marked as SCMON capable, why others not (only UPL) in the SAP Solution Manager Configuration: Custom Code Management. The systems are part of the same landscape - DEV system is SCMON capabable, while TST and PRD systems not:
I would suppose that all (SAP NetWeaver 7.31) systems should be SCMON capable - at least the same ST-PI version (2008_1_710 SP21) is implemented in them.
I found that info for the screenshot above comes from SM:SCMON_CONTROL job. And for the system mentioned above I can read:
Checking PRD system
SCMON extractor is configured to fetch Usage data from PRD system based on UPL ST-PI (Multi-cube)
Checking TST system
SCMON extractor is configured to fetch Usage data from TST system based on UPL ST-PI (Multi-cube)
Checking DEV system
SCMON extractor is configured to fetch Usage data from DEV system based on SCMON (ST-PI)
What can be done to be able to activate SCMON also for PRD and TST systems?
1 Answer
-
Posted on Nov 04, 2019 at 04:15 PM
In the end I found a solution by myself. The following info is mentioned in a document 'Changes for Custom Code Lifecycle Management (CCLM) in SAP Solution Manager 7.2 SP07' | https://www.sap.com/documents/2018/11/88999c30-2a7d-0010-87a3-c30de2ffd8ff.html:
If you detect that in a managed system SCMON was not automatically activated by SAP Solution Manager although the prerequisites are met please make sure that the kernel information of this system is available in SAP Solution Manager LMDB. This information is the basis for the decision to start SCMON.
In my case it was faulting sldreg that resulted in an outdated kernel info in SLD/LMDB. After a correction, restarting sapstartsrv and running SM:SCMON_CONTROL the UPL/SCMON indicator works as expected.
Add a comment
Add a comment