2884821 - IPHR in-memory tracing, some s_bufman.cxx messages still being logged to the IQMSG - SAP IQ

• To qualify as a match for this issue the IQ system must be running with the IPHR in-memory trace flags -iqiphrtracing   and   -iq_thread_msg_buf_size  set. If this is not the case then this KBA is not applicable.
  
  
• In-memory trace messages are not being redirected correctly to the in-memory logs. Instead they are getting printed to the .iqmsg SAP IQ log file.  An example of these messages are as follows.

I. 01/03 14:01:26. 0000023185 IPHR INST{140663715243776-717} 0x7feefc71c588 (26463594,137769)4 MOD 74..74 => 71..74; slib/s_bufman.cxx:5218 121639228,3
I. 01/03 14:01:26. 0000023185 IPHR INST{140663769024256-616} 0x7feefc434328 (26463604,596812)4 MOD 74..74 => 71..74; slib/s_bufman.cxx:5218 121639228,3

• The additional logging may cause the iqmsg file to grow in size rapidly and unexpectedly.

Applies SAP IQ versions that include the in-memory IPHR tracing feature

• SAP IQ 16.0 SP11 PL22
• SAP IQ 16.1 SP02 PL14
• SAP IQ 16.1 SP03 PL04
• SAP IQ 16.1 SP04 PL01

sybase, hung, inmemory, tracing, CR820967, CR#820967, 820967, stacktrace, stktrc, stack trace, IQMSG, messages, filling up, 'size increase', growing, logfile, size, growht, filesystem, crash, hang , KBA , BC-SYB-IQ , Sybase IQ , Problem