We had an issue with the upgrade to TSM 5.2.1.1 that some might want to know about. We upgraded last Monday, to disastrous results. On one instance, TSM would hang hard when migration started. We were told to audit our database, because of some messages that indicated we had an invalid storage pool id. Then the second instance started doing the same thing, only with backup stgpool. TSM level 2 had me run a trace, and told me that it was in bos.net.tcp.client of all things. I upgraded to AIX 5.1 ML4, and it has been working since (Thursday). Here is my environment:
RS6000 P670 AIX 5.1 ML2 upgraded to ML4 TSM 5.2.1.1 Gresham EDT Distributape 6.4.4 Andy Carlson |\ _,,,---,,_ Senior Technical Specialist ZZZzz /,`.-'`' -. ;-;;,_ BJC Health Care |,4- ) )-,_. ,\ ( `'-' St. Louis, Missouri '---''(_/--' `-'\_) Cat Pics: http://andyc.dyndns.org/animal.html