Rick, ask L1/L2 about how to make db2 on aix use tcpip to communicate with dsmserv. aix has a problem doing the massive amount of ipc processing which db2 generates.
I learned of this recently when the rhel 6.6 kernel bug bit us. The switch to tcpip is available on all platforms. TSM will run slower but at least it will run. Good luck! Bill Colwell Draper Lab -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rhodes, Richard L. Sent: Friday, February 13, 2015 9:49 AM To: ADSM-L@VM.MARIST.EDU Subject: v6.3.5 hung db2?? Two days ago we upgrade one of our TSM instances to v6.3.5 (from v6.3.4). This is our first v6.3.5 instance. It runs on a AIX server. Last night at 19:32 it looks like DB2 went into some kind of a loop. The instance became unresponsive. Dsmadmc cmds hung (didn't error, just hung). Dsmserv process was getting almost no cpu, while ds2sync was running the box At 65-70% but had no disk I/O. I killed dsmserv, but db2 didn't go down. I tried db2stop but it did nothing. Finally rebooted to get everything up. The actlog shows no nasty errors. Just wondering if anyone else has had a runaway db2. Thanks Rick ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message. ________________________________ Notice: This email and any attachments may contain proprietary (Draper non-public) and/or export-controlled information of Draper Laboratory. If you are not the intended recipient of this email, please immediately notify the sender by replying to this email and immediately destroy all copies of this email. ________________________________
