IC64873: AF IN OUT OF MEMORY CONDITION WHEN TRIGGER CALL EXECUTES MULTIPL ESTORED PROCEDURES

APAR status

• Closed as program error.

Error description

• In an instance that is out of virtual memory, a dml statment
  that executes a trigger which calls a stored procedure is
  causing an af with the following stack:
  
  16:17:15  Assert Failed: Exception Caught. Type: MT_EX_OS,
  Context: mem
  16:17:15   Who: Session(3462, informix@server, 30510,
  0x487d6790)
                  Thread(4338, sqlexec, 487a9e6c, 4)
                  File: mtex.c Line: 417
  16:17:15   Action: Please notify IBM Informix Technical Support.
  16:17:15  Raw hex dump of stack located in
  /work/product/11.50.UC5/tmp/af.14da635b.rawstk
  16:17:15  Stack for thread: 4338 sqlexec
  
   base: 0x4a923000
    len:   135168
     pc: 0x089316a0
    tos: 0x4a94096c
  state: running
     vp: 4
  
  afstack
  afhandler
  affail_interface
  mt_ex_throw_sig
  afsig_handler
  </lib/libc.so.6>strcpy
  mi_trigger_tabname
  </work/product/11.50.UC5/extend/ccm/libdbfuncs.so>changeNotify
  udrlm_clang_execute_internal
  udrlm_clang_execute
  udrlm_exec_routine
  udr_execute
  exroutine
  execproc
  aud_execproc
  excommand
  dotrstmts
  dotrigs
  ferafttrig
  dodmlrow
  dodelupd
  excommand
  ip_evalsql
  runproc
  udrlm_spl_execute
  udrlm_exec_routine
  udr_execute
  exroutine
  execproc
  aud_execproc
  excommand
  sq_execute
  sqmain
  spawn_thread
  startup
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * User with schema involving triggers that calls stored        *
  * procedures. Only occurs when machine is out of memory state. *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * An assertion file (AF) is created after invalid memory       *
  * access due to failed memory allocation.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to 11.50.xC7 and above.                              *
  ****************************************************************
  

Problem conclusion

• Fix provided in 11.50.xC6. The new behavior is to properly
  check allocation to avoid bad memory access.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  IBM IDS ENTRP E

• Fixed component ID

  5724L2304

Applicable component levels

• RB15 PSY

     UP