onbar question

Hello, I have two instances of informix running on the same machine. Let's call them instance A & B. They have the same INFORMIXDIR but obviously different INFORMIXSERVER and ONCONFIG variables. Both instances are set to use onbar to automatically back up the logical logs when they become full via the ALARMPROGRAM variable. Instance B seems to be working the way it should, as in when each logical log becomes full, the backup kicks off. However, instance A seems to wait until all the logical logs become full before backing them up, and sometimes it doesn't automatically kick off right away either. Any ideas as to why? Just for reference, instance A was set up just recently (@ 2 months ago). Doing a manual onbar -l works just fine on instance A. Furthermore, I have a cronjob set to do a level 0 archive every night on both instances, and that works fine. So the signal from informix to the storage manager appears to be getting through, except for the ALARMPROGRAM signal from instance A. Did I miss something in the recent set up of instance A? Oh, and the ALARMPROGRAM on A is set to run the same log_full.sh script that instance B uses. Jukebox - Sun Storedge L11000 Software - Veritas Netbackup 3.2 /w database extensions OS - Solaris 2.6 Informix version - 7.30.UC5 Any help is greatly appreciated. -- Phillip Tien

When the script is run, how do you point to the proper Informix instance? Could it be that your script is always trying to run against instance B? HTH Doug Agnew DBA Charlotte Pipe & Foundry dagnew@charlottepipe.com "Phillip Tien" <phillip.tien@wholefoods.com> wrote in message news:38690B59.EBAF752B@wholefoods.com... > Hello, > > I have two instances of informix running on the same machine. Let's > call them instance A & B. They have the same INFORMIXDIR but obviously > different INFORMIXSERVER and ONCONFIG variables. Both instances are set > to use onbar to automatically back up the logical logs when they become > full via the ALARMPROGRAM variable. Instance B seems to be working the > way it should, as in when each logical log becomes full, the backup > kicks off. However, instance A seems to wait until all the logical logs > become full before backing them up, and sometimes it doesn't > automatically kick off right away either. Any ideas as to why? > > Just for reference, instance A was set up just recently (@ 2 months > ago). Doing a manual onbar -l works just fine on instance A. > Furthermore, I have a cronjob set to do a level 0 archive every night on > both instances, and that works fine. So the signal from informix to the > storage manager appears to be getting through, except for the > ALARMPROGRAM signal from instance A. Did I miss something in the recent > set up of instance A? Oh, and the ALARMPROGRAM on A is set to run the > same log_full.sh script that instance B uses. > > Jukebox - Sun Storedge L11000 > Software - Veritas Netbackup 3.2 /w database extensions > OS - Solaris 2.6 > Informix version - 7.30.UC5 > > Any help is greatly appreciated. > > -- > Phillip Tien > > >