Re: 4.2 server memory corruption
2002-02-20 15:52:50
Thomas,
I believe that this is a known issue with the TSM 4.2.0.0 server on all
platforms. We have always cycled our ADSM and now TSM servers once a week
on OS/390 as we use FDR to backup all of the TSM data base and storage pool
volumes over a weekend. If you go to the Tivoli product support site you
can find patch levels 4.2.1.8 and 4.2.1.9 for the OS/390 server.
Hope this helps.
Brian
Brian L. Nick
Systems Technician - Storage Solutions
The Phoenix Companies Inc.
100 Bright Meadow Blvd
Enfield CT. 06082-1900
E-MAIL: Brian.Nick AT phoenixwm DOT com
PHONE: (860)403-2281
"Thomas Denier"
<Thomas.Denier@MAI To: ADSM-L AT VM.MARIST DOT EDU
L.TJU.EDU> cc:
Sent by: "ADSM: Subject: 4.2 server memory
corruption
Dist Stor Manager"
<[email protected].
EDU>
02/20/02 03:41 PM
Please respond to
"ADSM: Dist Stor
Manager"
We have a 4.2.0.0 server running under OS/390. We recently started seeing
increasingly serious performance problems with no obvious cause. The server
froze up entirely this morning. I had some difficulty shutting it down. The
server accepted a 'halt' command and generated an 'ANR5963I ADSM server
termination complete' complete message fairly rapidly. However, the started
task continued to run, and continued to use large amounts of CPU time, even
after the message. I finally cancelled the started task. The server came
back up without incident and is now performing much better. One of my
co-workers noted that the server had been up for 32 days, which was by far
the longest stretch of continued uptime since we went to 4.2 (we had
previously IPLed OS/390 every week or two for reasons unrelated to TSM).
This raises the suspicion of some kind of memory corruption that causes
server performance to degrade over time. Is the 4.2.0.0 server known to
suffer from any problems of this sort?
|
|
|