IY90786: OBJECTSERVER IS CORING AFTER A JOURNAL ENTRY HAS BEEN MADE

APAR status

• Closed as program error.

Error description

• Description of problem
  
  Objectserver is coring after a journal entry has been made
  
  full details below
  
  
  
  Customers steps
  
  
  More to the point we managed to reduce the problem to one single
  nco_sql statement that crashes the Objectserver every time. The
  statemtn is in the attached file crash.sql. Replace the first
  number
  with a valid Serial in your ObjectServer and load it into
  nco_sql.
  After the go, the server is gone.
  Please provide us most urgently with an emergency patch that
  fixes this
  problem.
  Thank you,
  
  
  
  
  Support Replication steps  Summary
  
  
  installed version omnibus 7.1
  location
  
  /opt/netcool3/
  sub.sup.micromuse.com
  
  Objectserver name is called NCOMS
  
  
  if you nco_sql into this objectserver
  
  username root
  password is blank
  
  
  and insert the following command
  
  
  the objectserver cores without giving any warning
  
  call jinsert (1011, 65534, getdate,
  'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx')
  ;
  
  
  
  this part
  
  'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx')
  
  
  is 258 characters long
  
  text fields usually have a limit of 255 however it should not
  core
  
  core file is in $NCHOME/omnibus/bin
  
  
  
  many thanks
  

Local fix

• If there is no need for multibyte (e.g. non-ascii) then the
  jinsert function from 7.0.7 can be used:
  
  
  
  Just apply this over existing database.
  
  Please advice if workaround is sufficient.
  
  
  
  
  
  customer has applied this and it currently works
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of jinsert() will encounter a          *
  *                 segmentation fault with particular widths of *
  *                 the journal string.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: The split_multibyte() function cores    *
  *                      when certain string lengths are passed  *
  *                      to it.                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  *                                                              *
  ****************************************************************
  wcsrtombs() will set the source pointer to NULL if end of
  string is reached. The code assumed that this did not happen.
  

Problem conclusion

• split_multibyte() and therefore jinsert() now work as expected.
  

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:

Modules/Macros

•    NETCOOL
  

Fix information

• Fixed component name

  NETCOOL/OMNIBUS

• Fixed component ID

  5724O4800

Applicable component levels

• R710 PSY

     UP