logical log backups & Net Backup

We recently upgraded two instances from 11.7.FC4 to 11.7.FC5 on AIX 6.1 Strange situation arose in that the automatic firing of backing up the logical logs stopped happening. On instance one, it eventually started working "out of the blue". Instance two is now where instance one was at and I'd like to figure out the mystery. We have confirmed with the SysAdmins that the Policies set up with NetBackup look correct. The ONCONFIG has LOG_BACKUP_MODE set to CONT and the ALARMPROGRAM has BACKUPLOGS=Y. Have an open PMR currently. Also, The messages used to look like this: 14:32:31 Logical Log 174026 Complete, timestamp: 0x67895e55. 14:32:32 Logical Log 174026 - Backup Started 14:32:57 Logical Log 174026 - Backup Completed and now it looks like this for instance two (no auto log backup happening): 14:39:42 Logical Log 100161 Complete, timestamp: 0xd620bc8b. 14:39:42 Process exited with return code 126: /bin/sh /bin/sh -c /home/informix/iif2000/ids_11_7_FC5/etc/alarmprogram.sh 2 23 "Logical Log 100161 Complete, timestamp: 0xd620bc8b." "Logical Log 100161 Complete, timestamp: 0xd620bc8b." "" 23001 and like this for instance one (auto log backup is happening): 08:23:21 Logical Log 1900 Complete, timestamp: 0x78bb0dea. 08:23:21 Process exited with return code 126: /bin/sh /bin/sh -c /home/informix/iif2000/ids_11_7_FC5_archive/etc/alarmprogram.sh 2 23 "LogicalLog 1900 Complete, timestamp: 0x78bb0dea." "Logical Log 1900 Complete, timestamp: 0x78bb0dea." "" 23001 08:27:26 Checkpoint Completed: duration was 1 seconds. Thanks for any insight Tom

On Friday, July 27, 2012 3:07:45 PM UTC-5, tom...@gmail.com wrote: > We recently upgraded two instances from 11.7.FC4 to 11.7.FC5 on AIX 6.1 > > Strange situation arose in that the automatic firing of backing up the logical logs stopped happening. On instance one, it eventually started working "out of the blue". Instance two is now where instance one was at and I'd like to figure out the mystery. We have confirmed with the SysAdmins that the Policies set up with NetBackup look correct. The ONCONFIG has LOG_BACKUP_MODE set to CONT and the ALARMPROGRAM has BACKUPLOGS=Y. Have an open PMR currently. > > > > Also, The messages used to look like this: > > 14:32:31 Logical Log 174026 Complete, timestamp: 0x67895e55. > > 14:32:32 Logical Log 174026 - Backup Started > > 14:32:57 Logical Log 174026 - Backup Completed> > > > > > and now it looks like this for instance two (no auto log backup happening): > > 14:39:42 Logical Log 100161 Complete, timestamp: 0xd620bc8b. > > 14:39:42 Process exited with return code 126: /bin/sh /bin/sh -c /home/informix/iif2000/ids_11_7_FC5/etc/alarmprogram.sh 2 23 "Logical Log 100161 Complete, timestamp: 0xd620bc8b." "Logical Log 100161 Complete, timestamp: 0xd620bc8b." "" 23001> > > > and like this for instance one (auto log backup is happening): > > 08:23:21 Logical Log 1900 Complete, timestamp: 0x78bb0dea. > > 08:23:21 Process exited with return code 126: /bin/sh /bin/sh -c /home/informix/iif2000/ids_11_7_FC5_archive/etc/alarmprogram.sh 2 23 "Logical> > Log 1900 Complete, timestamp: 0x78bb0dea." "Logical Log 1900 Complete, timestamp: 0x78bb0dea." "" 23001 > > 08:27:26 Checkpoint Completed: duration was 1 seconds.> > > > > > Thanks for any insight > > Tom Well, it appears in both the working and non-working case, the onbar -b -l that's running in the alarmprogram.sh is exiting with a non-zero return code. So that non-zero return code is detected and reported in the MSGPATH file. As for why onbar isn't getting a non-zero exit status, I'd look at your BAR_ACT_LOG file and possibly the need to turn on BAR_DEBUG and look at the BAR_DEBUG_LOG file. I'm not familiar with NetBackup but I assume it has log files as well that you would probably want to look at, specifically around the time stamps of when the log backups should have been fired. Jacques Renaut IBM Informix Advanced Support APD Team