Richard,
Thanks for the reply and suggestions. We have a tried a few of your
suggestions. IBM TSM support did have us run the following show
commands. I just tried to run 'show memory' on this server and had to
break out of the command because it began to cause failures with object
retrievals memory/paging. AIX is having us run perfpmr as the next
troubleshooting step so hopefully that will help us get down to the bottom
of the memory hog. IBM did have us run a few commands that I left out
from original email.
1. restart the dsmserv process
2. collect the output of 'SHOW ALLOC' one time per hour for the next 48
hours. Also collect AIX command output for 'ps aux | grep dsmserv' at the
same time.
3. at the end of step 2 collect the last 48 hours of unfiltered activity
log
Nancy Backhaus
Enterprise Systems
HealthNow, NY
716-887-7979
Richard Sims <rbs AT BU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
07/28/2008 11:03 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
Re: [ADSM-L] Memory Issue: Since Upgrading TSM Server from 5.2 to TSM 5.5
and installation of Centera SDK 3.2.1 - anyone experiencing similar
problem?
Nancy -
Confer with your AIX people on identifying processes using the most
memory in your server system, where 'ps' and various other monitoring
facilities can report what's using what.
In TSM, you can use the SHow MEMory command to report a summary of
memory usage and the SHow ALLOC command to report by module. SHow
THReads will report what threads are in play.
Also, note that you are running base level TSM code, with no
maintenance, which is not a good idea.
Richard Sims
CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole
use of the intended recipient(s) and may contain proprietary, confidential,
trade secret or privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited and may be a violation of law. If you
are not the intended recipient or a person responsible for delivering this
message to an intended recipient, please contact the sender by reply email and
destroy all copies of the original
message.
|