MDM 321 – SAP Netweaver Master Data Management

Symptom

If MDM is using CPU time and it is not clear what operations the MDS is executing. the clix command mdsMonitor can be used to monitor the operations that the MMDS is executing
Other terms

MDM Performance, clix, monitoring
Reason and Prerequisites

There are some time consuming operation that MDM executes in order to process requests. It is not always obvious what operations are being performed or why the MDS is working at peak CPU.
Solution

The solution is to run the clix command “mdsMonitor”.
This will report on the action the mds is currently executing.
In windows the command for 7.1 should be run from the clix directory frome the exe directory for MDM 7.1
C:\usr\sap\MDS\MDS01\exe>clix mdsMonitor localhost >monitorinfo.txt
This command can also be placed in a script which will repeat the command in order to verify the sequence of operations being performed.
An example of this script for HP-UX would be the following:
#!/bin/ksh
while true
do
date >> MdsMonitorResults.txt
clix mdsMonitor localhost Admin: >> MdsMonitorResults.txt
sleep 1
done
The output for this command (stored in the file “monitorinfo.txt is displayed in the following format:
Thread State User Protocol Command Locks Elapsed Connection Repository
========================================================================
======
2160 R JSmith CatMgr ImportRecords -W—W– 7440 MDM Import XYZ_BP
2622 W ATran CatMgr GetRecordIDs -R—— 5234 MDM Data M XYZ_BP
For more details on CLIX and on this specific command please refer to
the MDM Console Reference Guide 5.5 SP6 July 25, 2008 found in SAP
Market Place.
Go to “PART 10: CLIX COMMAND LINE INTERFACE ” chapter, page 48BCLIX