cp onconfig.std onconfig

chown informix:informix onconfig

vi onconfig

dnf install ncurses-compat-libs libaio

#!/bin/sh
# ======================================================================
# Este documento contiene datos propiedad intelectual de DEISTER
# S.A. Este documento no puede ser  publicado,  copiado o cedido
# total o parcialmente sin permiso escrito de DEISTER S.A.
#
# Al utilizar este software, usted reconoce y concuerda que su uso
# es bajo su responsabilidad y que ninguna de las partes involucradas
# en la creación, producción o prestación del servicio es responsable
# de cualquier perjuicio directo, incidental, consecuente, indirecto
# o punitivo o de pérdida, costo o gasto alguno (incluyendo honorarios
# legales, honorarios de peritos u otro desembolso) que pueda surgir
# directa o indirectamente a través de su uso, incluyendo pero no
# limitado a lo causado por virus, defectos, acción humana o inacción
# del sistema informático, línea telefónica, hardware, software o errores
# en el programa.
#
# description: Version of Informix log_full.sh sample event script to backup
#              automatically logical logs to disk using ontape -a triggered by
#              the log completed event.
#
# Comments:
#     Be sure to adjust the directory and file name of the log archive file
#     to match the value of the ONCONFIG parameter LTAPEDEV.  If the IDS engine
#     is running you will have to use onmonitor to change LTAPEDEV for the
#     running instance.  You will have to bounce the engine to install this
#     script as the event handler (modify the ONCONFIG parameter ALARMPROGRAM).
#
# processname: alarmprog_deister.sh
#
# $Id: alarmprog_deister.sh  $
#
#   Severity Description
#   1        Trivial.
#            The event is not reported to the alarm program
#            (for example, date change in the message log).
#   2        Information.
#            No error has occurred, but some routine event completed successfully
#            (for example, checkpoint or log backup completes).
#   3        Attention. This event does not compromise data or prevent the use of the system; however,
#            it warrants attention (for example, one chunk of a mirrored pair goes down).
#   4        Emergency. Something unexpected occurred that might compromise data or access to data
#            (assertion failure, or oncheck reports data corrupt).  Take action immediately.
#   5        Fatal. Something unexpected occurred and caused the database server to fail.
#
# Descripcion de los eventos:
# ID    Class Message
# 1     Table failure: 'dbsname:"owner".tabname'
# 2     Index failure: 'dbsname:"owner".tabname-idxname'
# 3     Blob failure: 'dbsname:"owner".tabname'
# 4     Chunk is offline, mirror is active: chunk number
# 5     Dbspace is offline: 'dbspace name'
# 6     Internal subsystem failure: 'message'
# 7     Database server initialization failure
# 8     Physical restore failure
# 9     Physical recovery failure
# 10    Logical recovery failure
# 11    Cannot open chunk: 'pathname'
# 12    Cannot open dbspace: 'dbspace name'
# 13    Performance improvement possible
# 14    Database failure. 'database name'
# 15    High-Availability Data-Replication failure
# 16    Backup completed: 'dbspace list'
# 17    Backup aborted: 'dbspace list'
# 18    Log backup completed: log number
# 19    Log backup aborted: log number
# 20    Logical logs are full?backup is needed
# 21    Database server resource overflow: 'resource name'
# 22    Long transaction detected
# 23    Logical log 'number' complete
# 24    Unable to allocate memory
# 25    Internal subsystem initialized: 'message' (starts the optical subsystem)
# 26    Dynamically added log file logid
# 27    Log file required
# 28    No space for log file
#
# Los eventos 6, 15, 21 y 24 puede producirse de forma muy seguida por lo
# que tenemos que proteger el envio de e-mails
# ======================================================================
 
# ########################################
# PUBLIC SECTION : CONFIGURATION VARIABLES
# ########################################
 
EVTMINUTE=60            # Expiration minutes for renotify special events
DAYSSAVED=2             # Dias que se almacenan los logical logs
ALARMADMIN=0            # Severity event to send e-mail
ADMINEMAIL=email1@company.com,email2@company.com
 
# ########################################
#     PRIVATE SECTION : INTERNAL VARIABLES
# ########################################
 
[ `uname -s` = "SunOS" ] && MAIL=mailx || MAIL=mail
 
ALRM_NOTWORTHY=1
ALRM_INFO=2
ALRM_ATTENTION=3
ALRM_EMERGENCY=4
ALRM_FATAL=5
 
EVENT_SEVERITY=$1
EVENT_CLASS=$2
EVENT_MSG="$3"
EVENT_ADD_TEXT="$4"
EVENT_FILE="$5"
 
INFORMIXDIR=${INFORMIXDIR:-`grep "^informix:" /etc/passwd | awk -F: '{ print $6 }'`}
INFORMIXSERVER=${INFORMIXSERVER:-`uname -n|awk -F'.' '{print $1}'`}
DB_LOCALE=${DB_LOCALE:-es_es.8859-1}
export INFORMIXDIR INFORMIXSERVER DB_LOCALE
 
TMPFILE=/tmp/__TMPFILE_$$
MAILBODY=/tmp/__MAILBODY_$$
BACKUPCMD="$INFORMIXDIR/bin/ontape -a -d"
ONSTATCMD="$INFORMIXDIR/bin/onstat"
eval MSGPATH=`${INFORMIXDIR}/bin/onstat -c | grep '^MSGPATH' | awk '{ print $2 }'`
eval LTAPEDEV=`${INFORMIXDIR}/bin/onstat -c | grep '^LTAPEDEV' | awk '{ print $2 }'`
 
EXIT_STATUS=0
 
case "$EVENT_SEVERITY" in
  1) EVENT_SEVERITY_NAME="Trivial";;
  2) EVENT_SEVERITY_NAME="Information";;
  3) EVENT_SEVERITY_NAME="Attention";;
  4) EVENT_SEVERITY_NAME="EMERGENCY!!";;
  5) EVENT_SEVERITY_NAME="FATAL EVENT!!";;
esac
 
echo "`date +%H:%M:%S`  `basename $0`: Started for event $EVENT_CLASS severity: $EVENT_SEVERITY_NAME ***" >> $MSGPATH
 
# Cleanup the mail header and the mail body file
rm -f $MAILBODY
 
# Set mail header for all events
MAILHEAD="$INFORMIXSERVER : $EVENT_SEVERITY_NAME : $EVENT_MSG"
echo "$EVENT_ADD_TEXT" >> $MAILBODY
 
case "$EVENT_CLASS" in
         4)
                # CHUNK IS OFFLINE
 
                echo "$EVENT_ADD_TEXT" >> $MAILBODY
                echo "-------------------------------------" >> $MAILBODY
                echo "RELATED INFORMATION:" >> $MAILBODY
                echo "-------------------------------------" >> $MAILBODY
                $ONSTATCMD -d | grep -v Blocked: | grep -v Block: | tail +4 >> $MAILBODY
                echo "-------------------------------------" >> $MAILBODY
                $ONSTATCMD -m | grep -v Blocked: | grep -v Block: | tail +4 >> $MAILBODY
                ;;
        6)
                # INTERNAL SUBSYSTEM FAILURE
 
                echo "$EVENT_ADD_TEXT" >> $MAILBODY
 
                # Many things cause this problem see the online.log
                echo "-------------------------------------" >> $MAILBODY
                echo "RELATED INFORMATION:" >> $MAILBODY
                echo "-------------------------------------" >> $MAILBODY
                $ONSTATCMD -m | grep -v Blocked: | grep -v Block: | tail +4 >> $MAILBODY
                ;;
        17)
                # ARCHIVE FAILED
                echo "$EVENT_ADD_TEXT\n" >> $MAILBODY
                # With we will be able to get the stack trace for the ontape thread
                echo "-------------------------------------" >> $MAILBODY
                echo "RELATED INFORMATION:" >> $MAILBODY
                echo "-------------------------------------" >> $MAILBODY
                onstat -g ath | grep ontape > $TMPFILE
                for i in `cat $TMPFILE | awk '{print $1}'`; do
                        $ONSTATCMD -g stk $i | grep -v Blocked: | grep -v Block: | tail +4 >> $MAILBODY
                        echo "-------------------------------------" >> $MAILBODY
                done
                ;;
 
        16)     # Archive completed
                # Remove old logical logs...
                if [ "$LTAPEDEV" != "/dev/null" ]; then
                  echo "`date +%H:%M:%S`  `basename $0`: Cleanning logs from `dirname $LTAPEDEV` $DAYSSAVED days old" >> $MSGPATH
                  #Log file name
                  #cd /tmp; find `dirname $LTAPEDEV` -name "`basename $LTAPEDEV`.*" -ctime +$DAYSSAVED -print -exec rm "{}" \; >> $MSGPATH
                  #Auto log file name
                  cd /tmp; find $LTAPEDEV -name "$INFORMIXSERVER_*" -ctime +$DAYSSAVED -print -exec rm "{}" \; >> $MSGPATH
                  echo STATUS = $? >> $MSGPATH
                fi
                ;;
 
        23)
                # LOGICAL LOG FILE COMPLETED
                if [ "$LTAPEDEV" != "/dev/null" ]; then
 
                  # This is compatible with Sun, Linux and AIX
                  logno=`echo $4 | awk '{ print $3 }'`
 
                  # If logical log file is writable, perform the backup
                  if [ -w $LTAPEDEV ]; then
                    $BACKUPCMD 2>&1 >> $MSGPATH
                    EXIT_STATUS=$?
                    echo "`date +%H:%M:%S` `basename $0`: logical log backup completed" >> $MSGPATH
                  else
                    EVENT_SEVERITY=3    # Attention
                    echo "-------------------------------------" >> $MSGPATH
                    echo "WARNING: Can not write in file $LTAPEDEV" >> $MSGPATH
                    echo "-------------------------------------" >> $MSGPATH
                  fi
                fi
                ;;
 
# One program is shared by all event alarms.  If this ever gets expanded to
# handle more than just archive events, uncomment the following:
        *)
#               EXIT_STATUS=1
        ;;
esac
 
# Special processing when alarm class is 6, 15,21 or 24 to prevent duplicate alarms from swamping mail.
# If alarm class is 23 (log filled), perform a logical (transaction) log backup to UNIX file system.
# If any other class, simply exit.  Our work is complete.
case "$EVENT_CLASS" in
       6|15|21|24) # Special processing for these classes since they can create many alarms quickly.
                # Ignore if severity is only 1 or 2.
                if [ $EVENT_SEVERITY -lt 3 ]; then
                        ALARMADMIN=0
                fi
                ISSUE="old"
                # Determine if this is a new or "existing" issue by checking to see if a
                # previous event file with this class is in /tmp.  If not, it is a new issue.
 
                # Si no existe el evento es que es la primera vez...
                if [ ! -f /tmp/ibmids_event.${EVENT_CLASS} ]; then
                   ISSUE="new"
                else
                   FOUND=`find /tmp -name "ibmids_event.${EVENT_CLASS}" -cmin +${EVTMINUTE} -print | wc -l`
                   # Si encuentra el fichero y es mas antiguo de lo esperado, lanza de nuevo el mensaje
                   if [ $FOUND -gt 0 ]; then
                      ISSUE="new"
                   fi
                fi
 
                if [ "${ISSUE}" = "new" ]; then
                        # Create file containing status information for review later.
                        rm -f /tmp/ibmids_event.${EVENT_CLASS}
                        STFILE=/tmp/ibmids_event.${EVENT_CLASS}
                        cp ${MAILBODY} ${STFILE}
                        date >> ${STFILE}
                else
                        # Since the event file is less than 1 hour old, this is an
                        # existing issue.  Do not notify operations or email DBA's.
                        ALARMADMIN=0
                fi
                ;;
esac
 
if [ $ALARMADMIN -ne 0 ]; then
  if [ $EVENT_SEVERITY -ge $ALARMADMIN ]; then
    if [ x"$ADMINEMAIL" != x"" ]; then
        MAILTO=$ADMINEMAIL
    fi
  fi
else
  echo "Event Severity = $EVENT_SEVERITY is lower than ALARMADMIN=$ALARMADMIN"
  echo "No mail will be sent to $ADMINEMAIL"
fi
 
# Intenta averiguar la sesion que ha producido el error
SESSION=`grep "session id" $MAILBODY | head -n 1 | sed -e 's/.*session id/session /' | awk '{ print $2 }'`
if [ -n "$SESSION" ]; then
    ${INFORMIXDIR}/bin/onstat -g sql $SESSION >> $MAILBODY
fi
 
if [ x${MAILTO} != x ]; then
    $MAIL -s "$MAILHEAD" $MAILTO < $MAILBODY
fi
 
rm -f $MAILBODY $TMPFILE 2>&1 >>/dev/null
 
exit $EXIT_STATUS

cat > alarmprog_deister.sh

chmod +x alarmprog_deister.sh

chown informix:informix alarmprog_deister.sh