RE: alarmprogram.sh

Posted in 2003

Mark.Roach@soi.com — Wed, 11 Jun 2003 11:11:40 -0400 — source: Usenet: comp.databases.informix

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C3302B.C2A89160 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Our platform is: IDS 9.40 UC1 Redhat Linux 7.2 It seems that we are having the same trouble with ontape -c waiting to Complete each Logical Log Backup after the Logical Logs are Full. I = tried changing the ALARMPROGOGRAM to no_log.sh which is just "exit(0)". With ontape -c running, online.log shows the Message "Logical Log 12345 Complete"; then "Logical Log 12345 Backup Started". But, it will = not give the message "Logical Log 12345 Backup Complete" until the logical = logs are full. With the same ALARMPROGRAM setting on IDS 7.31 on HP-UX, we would get the "... Backup Complete" message immediately after "... Backup Started". Is the new behavior in IDS 9.4 intentional? Are we being = pushed to use onbar ?? Mark Roach=20 IT - Programmer/Analyst Strategic Outsourcing, Inc. -----Original Message----- From: Mark D. Stock [mailto:mdstock@MydasSolutions.com] Sent: Thursday, June 05, 2003 6:06 AM To: Sadi G=FCrsoy Cc: IIUG Subject: Re: alarmprogram.sh Sadi G=FCrsoy wrote: > Hi all, > Our platform is: > IDS 9.40 FC1 > AIX 5.2 >=20 > We want to modify alarmprogram.sh. We want the program to work like > ontape -c. That is, when one logical log becomes full, we want it to =be > archived, not wait until all logs are full. The default alarm program ($INFORMIXDIR/etc/log_full.sh), which I=20 presume is still supplied with version 9.40, does this already, albeit=20 using onbar. This is very difficult using ontape and is probably more easily = achieved=20 using ontape -c without being triggered by alarm events. Remember that=20 ontape -c will continue writing to the end of a tape, whereas ontape -a = will OVERWRITE the tape, unless you do some clever shuffling of tapes = or=20 disk files. If you do use an alarm program, one thing to be careful of is that=20 ontape -a will backup ALL completed logs. However, the alarm program=20will be triggered for each individual log that fills, so you need to be = careful that the alarm program first checks to see that ontape is not=20 already running. If you are concerned about your logs filling up, then one trick that=20 used to be supplied in a sample alarm program in $INFORMIXDIR/etc was = to=20 check the percentage of logs that are full after each log fills, then=20 perform a backup after that threshold is exceeded. But again, you would = need to ensure that the previous backup device is safe. > For this purpose, we investigated the commands: > ALRM_NOTWORTHY=3D1 > ALRM_INFO=3D2 > ALRM_ATTENTION=3D3 > ALRM_EMERGENCY=3D4 > ALRM_FATAL=3D5 These are the alarm severity values. Only values 2-5 trigger your alarm = program. > EVENT_SEVERITY=3D$1 > EVENT_CLASS=3D$2 > EVENT_MSG=3D"$3" > EVENT_ADD_TEXT=3D"$4" > EVENT_FILE=3D"$5" These are the 5 parameters that can be passed to your alarm program, = the=20 last 2 being optional. > but we could not find any descriptions about them. > Do you have any suggestions? See the chapter on "Event Alarms" in the "Informix Administrator's=20 Reference for IDS" manual. Cheers, --=20 Mark. +----------------------------------------------------------+-----------+= | Mark D. Stock mailto:mdstock@MydasSolutions.com |//////// = /| | Mydas Solutions Ltd http://MydasSolutions.com |///// / = //| | +-----------------------------------+//// / = ///| | |We value your comments, which have |/// / = ////| | |been recorded and automatically |// / = /////| | |emailed back to us for our records.|/ = ////////| +----------------------+-----------------------------------+-----------+= ------_=_NextPart_001_01C3302B.C2A89160 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2653.12"> <TITLE>RE: alarmprogram.sh</TITLE> </HEAD> <BODY> Our platform is: IDS 9.40 UC1 Redhat Linux 7.2         It seems = that we are having the same trouble with ontape -c waiting to Complete = each Logical Log Backup after the Logical Logs are Full. I tried = changing the ALARMPROGOGRAM to no_log.sh which is just = "exit(0)".         With = ontape -c running, online.log shows the Message "Logical Log 12345 = Complete"; then "Logical Log 12345 Backup Started". But, =it will not give the message "Logical Log 12345 Backup = Complete" until the logical logs are full.         With the = same ALARMPROGRAM setting on IDS 7.31 on HP-UX, we would get the = "... Backup Complete" message immediately after "... = Backup Started". Is the new behavior in IDS 9.4 intentional? Are = we being pushed to use onbar ?? Mark Roach IT - Programmer/Analyst Strategic Outsourcing, Inc. -----Original Message----- From: Mark D. Stock [<A = HREF=3D"mailto:mdstock@MydasSolutions.com">mailto:mdstock@MydasSolutions= .com</A>] Sent: Thursday, June 05, 2003 6:06 AM To: Sadi G=FCrsoy Cc: IIUG Subject: Re: alarmprogram.sh Sadi G=FCrsoy wrote: > Hi all, > Our platform is: > IDS 9.40 FC1 > AIX 5.2 > > We want to modify alarmprogram.sh. We want the = program to work like > ontape -c. That is, when one logical log = becomes full, we want it to be > archived, not wait until all logs are = full. The default alarm program = ($INFORMIXDIR/etc/log_full.sh), which I presume is still supplied with version 9.40, does = this already, albeit using onbar.@@

RE: alarmprogram.sh

Related threads

Your privacy choices