Anyone else care to pitch in an Informix opinion? It would much appreciated. It is obvious to me that TSM is not the booger here, but somehow it keeps ending up in my court. Too bad it's not Night Court, I'd send in Bull Shannon...
-----Original Message----- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Friday, April 21, 2006 6:44 PM To: Bell, Charles (Chip) Subject: Re: Slow Informix backups every 8 days? On Apr 19, 2006, at 1:04 PM, Bell, Charles ((Chip)) wrote: > What can I gather from this? > > START_TIME: 2006-04-19 01:00:53.000000 > END_TIME: 2006-04-19 04:27:26.000000 > ACTIVITY: BACKUP > NUMBER: 1917621 > ENTITY: INFORMIX_PHAR > COMMMETH: Tcp/Ip > ADDRESS: 10.10.154.19:54898 > SCHEDULE_NAME: PHAR_INFORMIX_NIGHTLY > EXAMINED: 0 > AFFECTED: 1 > FAILED: 0 > BYTES: 18896547851 > IDLE: 0 > MEDIAW: 0 > PROCESSES: 1 > SUCCESSFUL: YES > VOLUME_NAME: > DRIVE_NAME: > LIBRARY_NAME: > LAST_USE: > COMM_WAIT: 12352 > NUM_OFFSITE_VOLS: Chip - That's a whopping communications wait... where the server spent waiting 3.4 hours for the client to speak. This is making me suspect that the Informix side of the middleware involved in the backup is blocked by Informix, possibly due to a held lock in the Informix database or the like. You may want to use some combination of lsof and truss commands to see what's going on there. I'm disappointed that no Informix customers have chimed in, as they have expertise in that area, where I've had no experience. Richard ----------------------------------------- Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information.
