Re: return code for onbar backups

Hi, OK. Your IDS Version is not quite the newest ... :) There were a couple of things in the area that got fixed in the meantime. That is why the messages are, well not so straight forward to grasp in the old version. :-( You are doing whole system backup (denoted by the "-w" in the onbar backup command.) That is important and correct when you are not backing up logical logs (which you are not doing as you have LTAPEDEV set to /dev/null). The whole system backups are the only backups that you can restore in this scenario. Therefore you are OK. The exit code "1" in the online.log (vs. 152 in bar activity log) is because the alarmprogram does not properly propagate the return code from onbar. Since for these instances you are not doing log backup anyway (with LTAPEDEV set to /dev/null), you can use "no_log.sh" as ALARMPROGRAM instead of the "log_full.sh". (Or if you've customized something in the script, you can adopt for log backup the section from "no_log.sh" instead of from "log_full.sh" ...) This will then fix the calling of un-necessary "onbar -b -l" commands for log backup attempts that will not work anyway. With that you'll avoid all the error messages in online.log and in bar activity log. Of course you'd have to remember and change it back in case you'd ever decide to actually backup the logs. Since for the one instance you are actually backing up the logs, you do not get any of these error messages there. That is normal, too. Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Information Management Informix URLs list: http://home.arcor.de/mfu1/informix/urls.html informix-list-bounces@iiug.org wrote on 16.11.2006 14:35:27: > Hi, > The command I use is onbar -b -L0 -w. > > The one instance that does not get the return code is using unbuffered logging. The others do not have logging. > The one without the return codes get's the logical logs backed up through onbar ( onbar -b -l ) with log_full.sh. > The others have /dev/null in LTAPEDEV and use alarmprogram.sh. > > The bar_act_logs show an exit code of 152, which means that the logical log backup can't be done. Normal. > > Do you think that the return code in the online.log of 1 is because of that onbar exit code of 152 ? > The archives are completing sucessfully, and we have done restores from them. > > Thanks. > > ======================== > -<<Floyd Wellershaus>>- > Database Administrator > Unix Administrator > > email: fwellers@yahoo.com > Home: 703-430-0805 > Cell: 703-477-6045 > ======================== > http://www.one.org/ > > ----- Original Message ---- > From: Martin Fuerderer <MARTINFU@de.ibm.com> > To: Floyd Wellershaus <fwellers@yahoo.com> > Cc: informix-list@iiug.org; informix-list-bounces@iiug.org > Sent: Thursday, November 16, 2006 8:25:23 AM > Subject: Re: return code for onbar backups > Hi, > > what command do you mean when you say you are > doing an "onbar full archive"? > (Is this just a level-0 archive or is it a level-0 whole system archive?) > > What do you mean by "transaction logging turned on"? > (Is it just the logging mode of the database? Or does it include > whether log backup is being done or not? -> see value of onconfig > parameter LTAPEDEV ... is it /dev/null ?) > > Please check onbar's activity log (onconfig parameter BAR_ACT_LOG). > There may well be some more information about onbar's exit code, > the reason, etc. > > Regards, > Martin > -- > Martin Fuerderer > IBM Informix Development Munich, Germany > Information Management > > Informix URLs list: http://home.arcor.de/mfu1/informix/urls.html > > informix-list-bounces@iiug.org wrote on 16.11.2006 12:49:54: > > Hello, > > I wonder what this means, if anyone can tell me. > > We have some databases that do not have transaction logging turned on. > > On those databases when the onbar full archive completes we get the > following message running IDS9.4FC3. > > > > Process exited with return code 1: /bin/sh /bin/sh -c > /usr/online9.40.FC3/etc/alarmprogram.sh 2 16 > > "Archive completed: 'rootdbs, llogs_1, llogs_2, physlog_1 > > > > I know that the alarmprogram.sh is being called with a simple > informational message to say that the backups are complete. > > But why the Return code of 1 ? > > > > Some more info: > > On the one database we have that we log transactions on, we don't get > that. > > > > Also, on our IDS10.FC5 box, we get the same thing, except the Return > code is 127. > > > > Thanks. > > Floyd > > > > ======================== > > -<<Floyd Wellershaus>>- > > Database Administrator > > Unix Administrator > > > > email: fwellers@yahoo.com > > Home: 703-430-0805 > > Cell: 703-477-6045 > > ======================== > > http://www.one.org/ __ > > Informix-list mailing list > > Informix-list@iiug.org > > http://www.iiug.org/mailman/listinfo/informix-list > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list