My Oracle Support Banner

*** glibc detected *** double free or corruption (out): 0x085a93e0 *** Error When Starting Concurrent Managers (Doc ID 1490640.1)

Last updated on MARCH 29, 2022

Applies to:

Oracle Concurrent Processing - Version to [Release 11.5]
Oracle Communications Billing and Revenue Management - Version to [Release 7.5.0]
Information in this document applies to any platform.
Concurrent manager crashes intermittently (almost daily) on one environment while the other one on the same node works fine. ICM log shows following errors:

From the concurrent manager logs found the following error

*** glibc detected *** double free or corruption (out): 0x085a93e0 ***
sh: line 71: 8780 Aborted FNDLIBR FND CPMGR "FNDCPMBR sysmgr=\"\" $maxreq $sleep $pmon $quesiz $diag logfile=$logfile $target" < $sysmanager

The _0903@ internal concurrent manager has terminated with status 134 - giving up.

Check that your system has enough resources to start a concurrent manager process
Starting QTC_Fin_Standard_Collections Concurrent Manager


- You have 2 environments/instances  set on one machine/box : instance 1 is working fine, instance 2  has the error intermittently

- Both environments have the same configuration:

Non Working and working environment
1) grep -i  LD_ASSUME_KERNEL .profile
export LD_ASSUME_KERNEL=2.4.19

2) LD_PRELOAD  this value not set in working env

3)  ls -ltr /usr/lib/
ls: /usr/lib/ No such file or directory

4)  cd $ORACLE_HOME/lib/stubs

  ls -ltr
-rwxr-xr-x  1 oats4bvp dba 261328 Jul 15 19:48*


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.