Re: ALARMPROGRAM (was DSA 7.22 UC1 on HP-UX 10.10 Crash )
At 07:06 PM 1/26/98 GMT, W. H. SMITH wrote:
}Mark Collins wrote:
}>
}> > No help there errno 5 is the dreaded generic "I/O error". Anyway there
}> > are three problems here:
}> >
}> > The first problem (at 14:43:33) looks like a failure of a pipe
}> > connection. This is either a bug or someone/something destroyed a pipe
}> > connection.
}> >
}> > The second problem at 14:34:34 the invokation of the alarm program
}> > failed because ALARMPROGRAM was set to "/dev/null". If you want no
}> > alarm program just leave the parameter blank:
}> >
}> > ALARMPROGRAM # No program wanted
}>
}> Hmmm, from reading the manual that looks correct. It just doesn't seem
to match what I just
}> saw, though. Today I upgraded a 7.14.UD1 instance to 7.23.UC6. I left
ALARMPROGRAM blank,}> as it had been in the 7.14 onconfig. When I ran oninit for the first
time, the message log
}> reported:
}>
}> 10:22:52 INFORMIX-OnLine Stopped.
}>
}> Mon Jan 26 10:34:16 1998
}>
}> 10:34:16 Event alarms enabled. ALARMPROG =
'/opt/informix/7.23.UC6/etc/log_ful
}> l.sh'
}> 10:34:20 DR: DRAUTO is 0 (Off)
}> 10:34:21 INFORMIX-OnLine Initialized -- Shared Memory Initialized.
}> 10:34:21 Physical Recovery Started.
}> 10:34:21 Physical Recovery Complete: 0 Pages Restored.
}> 10:34:21 Logical Recovery Started.
}> 10:34:24 Logical Recovery Complete.
}> 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks
}> 10:34:24 Onconfig parameter ALARMPROGRAM modified from <blank> to
/opt/informix
}> /7.23.UC6/etc/log_full.sh.
}> 10:34:24 Dataskip is now OFF for all dbspaces
}> 10:34:25 On-Line Mode
}> 10:34:25 Converting 'sysmaster' database ...
}> 10:34:25 Checkpoint Completed: duration was 0 seconds.
}>
}> It seems that for some reason, under 7.23.UC6 at least, that a blank
value for ALARMPROGRAM
}> may cause the engine to default to $INFORMIXDIR/etc/log_full.sh, whether
you want it or not.
}> Remember, I said I left the ALARMPROGRAM blank in the onconfig, yet we
see that the engine
}> notes the parameter has changed. To get around this, I changed it to
}> $INFORMIXDIR/etc/no_log.sh. Has anyone else seen this?
}>
}>
}
}Right here . . . we upgraded from 7.13 to 7.23 and that was one of the
}first things I noticed; it really cluttered up the online.log.
}Unfortunately, the no_log.sh was the only way to go. It seems that
}Informix will automatically assume an ALARMPROGRAM is active. Not too
}bad, really . . . I've always wanted to experiment with Informix alarm
}capabilities.
Informix uses (starting in 7.22/7.23) ALARMPROGRAM to initiate OnBar
logical log backups. using the log_full script. If I recall, this is the
only way
to achieve an 'automatic' equivalent log backup, when using OnBar.
}John Carlson
}Informix DBA
}WH Smith, Inc
}
-----------------------------------------------------------------------
Jon C. Vemo jon@etcscan.com
Database Administration
Deluxe Payment Protection Systems/SCAN
Bothell, WA
(425) 489-1120
-----------------------------------------------------------------------