Re: onbar -b -w

It may be by design. During archive checkpoints the instance is temporarily halted from updates/inserts . . . I don't know the Informix architecture as well as I'd like to, but these three blocked processes may be part of the archive checkpoint? Can you restore from the backup? Informix does a lot of complaining when something goes wrong, and if usually if there isn't a warning/error, there isn't a problem. Hope this helps. Brice Avila Minneapolis, Minnesota zombie <zombie_member@newsguy.com> wrote in message news:<cfphv70qp8@drn.newsguy.com>... > Hi DBA's, > I have an installation of informix 9.40 FC1. > Every time we run the nightly backup onbar -b -w , it adds three processes to > the list of blocked processes in the O/S. > > Can anyone guide me towards troubleshooting this problem. The backup completes > successfully. > > There are no errors in the online.log file or the bar_act.log file. > The only problem, when I run a vmstat the number of processes in the blocked > state increases by three. Any idea whats going on here? > > Any help is greatly appreciated! > > +Zombie

It certainly is not a problem with informix. It is running well. However the OS shows these procs as being in a wait state infinitely. need to resolve the problem soon. By the end of every week there are 21 additional procs in wait state. In article <c46e3ec5.0408160551.5d973e8@posting.google.com>, Brice Avila says... > >It may be by design. During archive checkpoints the instance is >temporarily halted from updates/inserts . . . I don't know the >Informix architecture as well as I'd like to, but these three blocked >processes may be part of the archive checkpoint? Can you restore from >the backup? > >Informix does a lot of complaining when something goes wrong, and if >usually if there isn't a warning/error, there isn't a problem. Hope >this helps. > >Brice Avila >Minneapolis, Minnesota > > >zombie <zombie_member@newsguy.com> wrote in message >news:<cfphv70qp8@drn.newsguy.com>... >> Hi DBA's, >> I have an installation of informix 9.40 FC1. >> Every time we run the nightly backup onbar -b -w , it adds three processes to >> the list of blocked processes in the O/S. >> >>Can anyone guide me towards troubleshooting this problem. The backup completes >> successfully. >> >> There are no errors in the online.log file or the bar_act.log file. >> The only problem, when I run a vmstat the number of processes in the blocked >> state increases by three. Any idea whats going on here? >> >> Any help is greatly appreciated! >> >> +Zombie

zombie wrote: > > It certainly is not a problem with informix. It is running well. > However the OS shows these procs as being in a wait state infinitely. > need to resolve the problem soon. By the end of every week there are 21 > additional procs in wait state. > > In article <c46e3ec5.0408160551.5d973e8@posting.google.com>, Brice Avila says... > > > >It may be by design. During archive checkpoints the instance is > >temporarily halted from updates/inserts . . . I don't know the > >Informix architecture as well as I'd like to, but these three blocked > >processes may be part of the archive checkpoint? Can you restore from > >the backup? > > > >Informix does a lot of complaining when something goes wrong, and if > >usually if there isn't a warning/error, there isn't a problem. Hope > >this helps. > > > >Brice Avila > >Minneapolis, Minnesota > > > > > >zombie <zombie_member@newsguy.com> wrote in message > >news:<cfphv70qp8@drn.newsguy.com>... > >> Hi DBA's, > >> I have an installation of informix 9.40 FC1. > >> Every time we run the nightly backup onbar -b -w , it adds three processes to > >> the list of blocked processes in the O/S. > >> > >>Can anyone guide me towards troubleshooting this problem. The backup completes > >> successfully. > >> > >> There are no errors in the online.log file or the bar_act.log file. > >> The only problem, when I run a vmstat the number of processes in the blocked > >> state increases by three. Any idea whats going on here? > >> > >> Any help is greatly appreciated! > >> > >> +Zombie How *exactly* do you run the nightly backup: a shell script in cron, a TSM TIVOLI module starting a shell, ..... there are so many ways to do it! Often zombified processes are simply childs of shell processes, where the parent shell does neither hand the child over to the init process, nor does it execute the wait statement -> orphaned child So I need details please, then maybe I can help. dic_k -- Richard Kofler SOLID STATE EDV Dienstleistungen GmbH Vienna/Austria/Europe