RE: HDR monitoring
solaris 10 - 64-BIT IDS 11.50.FC5 A couple of weeks ago I asked about monitoring replication between an HDR pair. I was told that the error code to watch for is "15". I modified the "case" statement in my alrmprogram.sh to add a case for 15. I then stopped the secondary instance and watched. Apparently, it never called the alrmprogram.sh because I never saw any results. Am I going about this incorrectly, or do I just need to tweak something? Larry
Class code 15 is a Severity '2' event. Is your script perhaps ignoring all events with a severity <3? Do you have ALRM_ALL_EVENTS set to 1? Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) IIUG Board of Directors (art@iiug.org) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Wed, Mar 2, 2011 at 2:57 PM, LARRY SORENSEN <lsorensen25@msn.com> wrote: > solaris 10 - 64-BIT > IDS 11.50.FC5 > > A couple of weeks ago I asked about monitoring replication between an HDR > pair. I was told that the error code to watch for is "15". I modified the > "case" statement in my alrmprogram.sh to add a case for 15. I then stopped > the > secondary instance and watched. Apparently, it never called the > alrmprogram.sh > because I never saw any results. Am I going about this incorrectly, or do I > just need to tweak something? > > Larry > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --20cf300faa8d3ad8d7049d85984a
In the ALARMPROGRAM, you need to check for 'severity = 3' and 'class = 15'. Actually, any alarm with 'severity = 3' you are probably in big trouble; all TX logs used up, all locks used up, LTX, etc. Bob ----- Original Message ----- From: "LARRY SORENSEN" <lsorensen25@msn.com> To: ids@iiug.org Sent: Wednesday, March 2, 2011 2:57:05 PM Subject: RE: HDR monitoring [22966] solaris 10 - 64-BIT IDS 11.50.FC5 A couple of weeks ago I asked about monitoring replication between an HDR pair. I was told that the error code to watch for is "15". I modified the "case" statement in my alrmprogram.sh to add a case for 15. I then stopped the secondary instance and watched. Apparently, it never called the alrmprogram.sh because I never saw any results. Am I going about this incorrectly, or do I just need to tweak something? Larry ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.