Problem with alarmprogram.bat on Windows

Hi, We are running IDS 10.00.TC6X2 on Windows 2003 server. We use Onbar and the Alarmprogram.bat for logical log backups. Our problem is that during larger archiving of data informix starts up several hundred cmd processes on the server that are never exited, this of course drains the OS of memory and CPU. The problem only occurs when a large amount of logs are needed to be backed up (about 10 logical logs per minute). Size of each log is 2000 KB. Alarmprogram.bat runs BACKUP_CMD=onbar -b -l and logs are backed up to a TSM-server. Online log says: ... 05:44:48 Logical Log 23142 Complete, timestamp: 0xdaf6d84b. 05:44:58 Logical Log 23143 Complete, timestamp: 0xdafba933. 05:45:05 Logical Log 23144 Complete, timestamp: 0xdb003f66. ... The onbar log are empty at the above time. Logs aren't beeing backed up until the entire process of archiving data is over. Does anyone have an idea of why the alarmprogram.bat cmd processes aren't being run and exited? Could it be just an overload?

On Oct 22, 11:50 am, kem...@gmail.com wrote: > Hi, > > We are running IDS 10.00.TC6X2 on Windows 2003 server. We use Onbar > and the Alarmprogram.bat for logical log backups. Our problem is that > during larger archiving of data informix starts up several hundred cmd > processes on the server that are never exited, this of course drains > the OS of memory and CPU. The problem only occurs when a large amount > of logs are needed to be backed up (about 10 logical logs per minute). > Size of each log is 2000 KB. > > Alarmprogram.bat runs BACKUP_CMD=onbar -b -l and logs are backed up to > a TSM-server. > > Online log says: > ... > 05:44:48  Logical Log 23142 Complete, timestamp: 0xdaf6d84b. > 05:44:58  Logical Log 23143 Complete, timestamp: 0xdafba933. > 05:45:05  Logical Log 23144 Complete, timestamp: 0xdb003f66. > ...> > The onbar log are empty at the above time. Logs aren't beeing backed > up until the entire process of archiving data is over. > > Does anyone have an idea of why the alarmprogram.bat cmd processes > aren't being run and exited? Could it be just an overload? Well, yes, overload is probably a good phrase :-/ Why are your logs filling every ... 1 second! Would suggest that you size your logs to fill one every 10 minutes, which would suggest increasing the size to 600 Mb! But that sounds wrong diddly ong dong. What is actually filling your logs at 05:44 in the morning? Presumably you are using ISM on this windows machine as well, just out of interest, when do you do level 0 archives and what have you got BAR_MAX_BACKUP set to and what onbar command do you use to backup? Mash it up 'arry.

On 22 Okt, 14:40, TBP <TheBigPota...@nothere.co.uk> wrote: > On Oct 22, 11:50 am, kem...@gmail.com wrote: > > > > > Hi, > > > We are running IDS 10.00.TC6X2 on Windows 2003 server. We use Onbar > > and the Alarmprogram.bat for logical log backups. Our problem is that > > during larger archiving of data informix starts up several hundred cmd > > processes on the server that are never exited, this of course drains > > the OS of memory and CPU. The problem only occurs when a large amount > > of logs are needed to be backed up (about 10 logical logs per minute). > > Size of each log is 2000 KB. > > > Alarmprogram.bat runs BACKUP_CMD=onbar -b -l and logs are backed up to > > a TSM-server. > > > Online log says: > > ... > > 05:44:48  Logical Log 23142 Complete, timestamp: 0xdaf6d84b. > > 05:44:58  Logical Log 23143 Complete, timestamp: 0xdafba933. > > 05:45:05  Logical Log 23144 Complete, timestamp: 0xdb003f66. > > ...> > > The onbar log are empty at the above time. Logs aren't beeing backed > > up until the entire process of archiving data is over. > > > Does anyone have an idea of why the alarmprogram.bat cmd processes > > aren't being run and exited? Could it be just an overload? > > Well, yes, overload is probably a good phrase :-/ > > Why are your logs filling every ... 1 second! > > Would suggest that you size your logs to fill one every 10 minutes, > which would suggest increasing the size to 600 Mb! But that sounds > wrong diddly ong dong. > What is actually filling your logs at 05:44 in the morning? > Presumably you are using ISM on this windows machine as well, just out > of interest, when do you do level 0 archives and what have you got > BAR_MAX_BACKUP set to and what onbar command do you use to backup? > > Mash it up 'arry. Well, what we're doing is an extensive archiving of data from one database to another. Basically we insert one row of data in one table and delete if from another. Right now we have archived more then 400 million rows of data during an entire weekend, that's why we're doing it at 4 in the morning. Level 0 are performed twice every day (normally), but during this archiving process it's been more or less once every day. BAR_MAX_BACKUP is set to 16 in the Onconfig file. Command is "onbar -b -l" for logs and "onbar -b" for level 0.

On 22 Oct, 14:20, kem...@gmail.com wrote: > On 22 Okt, 14:40, TBP <TheBigPota...@nothere.co.uk> wrote: > > > > > On Oct 22, 11:50 am, kem...@gmail.com wrote: > > > > Hi, > > > > We are running IDS 10.00.TC6X2 on Windows 2003 server. We use Onbar > > > and the Alarmprogram.bat for logical log backups. Our problem is that > > > during larger archiving of data informix starts up several hundred cmd > > > processes on the server that are never exited, this of course drains > > > the OS of memory and CPU. The problem only occurs when a large amount > > > of logs are needed to be backed up (about 10 logical logs per minute). > > > Size of each log is 2000 KB. > > > > Alarmprogram.bat runs BACKUP_CMD=onbar -b -l and logs are backed up to > > > a TSM-server. > > > > Online log says: > > > ... > > > 05:44:48  Logical Log 23142 Complete, timestamp: 0xdaf6d84b. > > > 05:44:58  Logical Log 23143 Complete, timestamp: 0xdafba933. > > > 05:45:05  Logical Log 23144 Complete, timestamp: 0xdb003f66. > > > ...> > > > The onbar log are empty at the above time. Logs aren't beeing backed > > > up until the entire process of archiving data is over. > > > > Does anyone have an idea of why the alarmprogram.bat cmd processes > > > aren't being run and exited? Could it be just an overload? > > > Well, yes, overload is probably a good phrase :-/ > > > Why are your logs filling every ... 1 second! > > > Would suggest that you size your logs to fill one every 10 minutes, > > which would suggest increasing the size to 600 Mb! But that sounds > > wrong diddly ong dong. > > What is actually filling your logs at 05:44 in the morning? > > Presumably you are using ISM on this windows machine as well, just out > > of interest, when do you do level 0 archives and what have you got > > BAR_MAX_BACKUP set to and what onbar command do you use to backup? > > > Mash it up 'arry. > > Well, what we're doing is an extensive archiving of data from one > database to another. Basically we insert one row of data in one table > and delete if from another. Right now we have archived more then 400 > million rows of data during an entire weekend, that's why we're doing > it at 4 in the morning. > > Level 0 are performed twice every day (normally), but during this > archiving process it's been more or less once every day. > > BAR_MAX_BACKUP is set to 16 in the Onconfig file. Command is "onbar -b > -l" for logs and "onbar -b" for level 0. Soooo .... was a backup running around about 05:44 time? I would suggest BAR_MAX_BACKUP set to 16 (IF you are using the local ISM - Informix Storage Manager) is probably causing issues. At the end of each dbspace backup (of which you will potentially have 16 dbspace backups running at the same time!), a logical log backup may try and occur. You have already max'd out the ISM which will only have (AT MOST depending on how you configure things) 4 devices. I would suggest you shutdown BAR_MAX_BACKUP to 2 or 3, leaving one device available for logical log backups.