My Oracle Support Banner

OAM Configured for RDBMS Auditing Fails to Start with Error *** Glibc Detected *** (Doc ID 727244.1)

Last updated on MARCH 08, 2017

Applies to:

COREid Identity - Version: 10.1.4 and later   [Release: 10g and later ]
Information in this document applies to any platform.
Checked for relevance on 11-Apr-2010


OAM has been configured for auditing to Oracle RDBMS Database. When the server processes are started the following errors occur:

$ start_ois_server
OIS Server started with pid: 18490
$ *** glibc detected *** free(): invalid pointer: 0xb7cdb190 ***
Starting OIS server Watchdog.....
OIS Server Watchdog cannot run, because there is no OIS Server to watch.

$ start_access_server
Access Server started with pid: 19384 
$ *** glibc detected *** double free or corruption (out): 0x089fba70 ***
Starting Access Server Watchdog.....
Access Server Watchdog cannot run, because there is no AAA Server to watch. 

The $ORACLE_HOME, $PATH and $LD_LIBRARY_PATH environment variables are correctly set and exported i.e.

ORACLE_HOME=<RDBMS client home>; export ORACLE_HOME


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

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

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