Troubleshooting In SMLG

Problem: -- Problem with the response time collector on SAP systems. SMLG: --When transaction SMLG is executed, the MS maintained lo!on !roups screen shows a table with entries "or lo!on !roups and the associated instances. An entry in this table, which is characteri#ed by an instance and a lo!on !roup, is $nown as assi!nment. A lo!on !roup to which multiple instances belon! there"ore consists o" multiple assi!nments in this table, where an assi!nment contains one instance in each case. %&ery "i&e minutes, or a"ter e&ery "i&e lo!ons, each application ser&er writes its own per"ormance statistics data to a memory-resident table on the messa!e ser&er. 'he current lo!on ser&er is re"reshed "or each !roup. 'rans"errin! per"ormance data to the monitor architecture is per"ormed by the system automatically usin! the Autoabap. Sometimes there is a problem with the response time collector on some production system(s application ser&ers. )or some reason the MS collector stops and the application ser&er reports a * response time in SMLG. As a conse+uence the ser&er !ets o&erloaded. Some Problems that may occur in SMLG: -A> Loa -balancing oes not !in application ser"er -- 'his beha&ior can occur i" a system is set up with , separate networ$s. -n this case, each application ser&er has at least two networ$ cards. .ne "or the communication with the "ront ends and the second "or the communication between application ser&er and database. /urin! the !roup lo!on procedure, the -P address o" the networ$ card that corresponds to the host name becomes $nown to the messa!e ser&er. -" this address is not &isible "or the "ront-end hosts 0because it is in the other networ$1, the connection will "ail. Solution: -- -" it is necessary to set up the networ$ in a way that de&iates "rom the SAP recommendations, you can o&erwrite the -P address stored in the messa!e ser&er &ia Maintenance 'ransaction SMLG and thus enter the -P address which is &isible "or the "ront-end hosts. 'his ta$es place in the Assi!nment o" Lo!on Groups to -nstances, in the detail data, in "ield 2)ront-end--nstance connection2. As mentioned abo&e, you only ha&e to "ill this "ield i" your networ$ con"i!uration de&iates. #> $e%ly a e logon group o not %or& -- A"ter addin! new !roups, it can happen that the table bu""ers on the instances mi!ht be out o" sync. -n this case, i" the load balancin! pro!ram runs on a ser&er where the new !roups are not in the bu""er, it will update the shared memory with outdated in"o leadin! to this error. .ne ma3or symptom o" this issue is that in the SMLG Load /istribution screen, the current lo!on instance "or this newly created lo!on !roup will be empty. Solution: -- Simply resettin! the table bu""ers will sol&e this problem.

'> Long runtime %hen re!reshing loa istribution -- When we re"resh load distribution in transaction SMLG 0SMLG -4 Load /istribution 0)51 -4 6e"resh 0)511, response time may be ta$in! &ery lon!. Solution: -- -mport the Support Pac$a!e or implement the correction instructions. Support Pac$a!es SAP89AS-S 6elease :** Pac$a!e 7ame SAP;9:**<=

(> The process belo% escribes the proce ure o! resetting the collector: -<. ,. >. Lo! on to the Production system. %xecute 'ransaction SMLG. lic$ on the Load /istribution button or press )5.

=.

-" ALL the application ser&ers report response time ?4 *, e&erythin! seems to be .;.

5.

%&ery "i&e minutes, or a"ter e&ery "i&e lo!ons, each application ser&er writes its own per"ormance statistics data to a memory-resident table on the messa!e ser&er. 'he number o" users lo!!ed-in in each ser&ers can be &iewed by Goto Alert monitor.

/ouble clic$ on any o" the ser&er it will ta$e control to the screen o" AL*@ showin! all the user list currently in the system.

A.

-" any o" the /-A 0/ialo!1 instances "ound ha&in! response time B * then the "ollowin! steps to be "ollowed-- %xecute transaction 6C,* )rom the menu select %D'6AS Acti&ate Maintenance )unction

%xpand the E MS Monitor SetsF 'emplates. )rom the expanded options select E%ntire SystemF and double-clic$ on it.

 %xpand P6< 0in this case as example ta$en o" P6< system1 6G> Ser&ices /ialo! instance reportin! response time B *.

Select the 6esponse'ime 0Standard'ran.1 node. 'hen "rom the menu select %dit 7odes 0M'%1 6eset0C1.

lic$ E.;F on the con"irmation window.

A"ter some time 0approximately 5 minutes1, the correct response time will be reported in SMLG. As e&ery "i&e minutes, or a"ter e&ery "i&e lo!ons, each application ser&er writes its own per"ormance statistics data to a memory-resident table on the messa!e ser&er. 'he current lo!on ser&er is re"reshed "or each !roup.