My Oracle Support Banner

VWS Processes Generating Core Dump Files When Oracle Database Client Version is 9.2.0.1.0 (Doc ID 1562434.1)

Last updated on SEPTEMBER 12, 2018

Applies to:

Oracle Communications Network Charging and Control - Version 4.4.0 to 5.0.0 [Release 4.4 to 5.0]
Information in this document applies to any platform.

Symptoms

The VWS (Voucher Wallet Server) processes are intermittently generating core dump files, mainly on the primary VWS node.  Its syslog reports the following type of messages:

 May 24 20:00:44 vws01 genunix: [ID 603404 kern.notice] NOTICE: core_log: beServer[9500] core dumped: /var/crash/core-vws01-9500-beServer
 May 24 20:00:22 vws01 genunix: [ID 603404 kern.notice] NOTICE: core_log: beCDRMover[18401] core dumped: /var/crash/core-vws01-18401-beCDRMover
 May 24 20:00:29 vws01 genunix: [ID 603404 kern.notice] NOTICE: core_log: beVWARS[28544] core dumped: /var/crash/core-vws01-28544-beVWARS
 May 24 20:00:37 vws01 genunix: [ID 603404 kern.notice] NOTICE: core_log: beGroveller[18412] core dumped: /var/crash/core-vws01-18412-beGroveller
 May 24 20:00:44 vws01 genunix: [ID 603404 kern.notice] NOTICE: core_log: beServer[9500] core dumped: /var/crash/core-vws01-9500-beServer
 May 24 20:00:52 vws01 genunix: [ID 603404 kern.notice] NOTICE: core_log: dapIF[18508] core dumped: /var/crash/core-vws01-18508-dapIF
 May 24 20:02:10 vws01 genunix: [ID 603404 kern.notice] NOTICE: core_log: beVWARS[27417] core dumped: /var/crash/core-vws01-27417-beVWARS
 May 24 20:03:03 vws01 genunix: [ID 603404 kern.notice] NOTICE: core_log: ccsSLEEChangeDae[18621] core dumped: /var/crash/core-vws01-18621-ccsSLEEChangeDae

A sample gdb back trace of a beServer core file reports issues with /u01/app/oracle/product/9.2/lib32/libclntsh.so.9.0 database library:

Core was generated by `/IN/service_packages/E2BE/bin/beServer'.
Program terminated with signal 6, Aborted.
[New process 87921 ]
#0 0xff0cdcdc in _lwp_kill () from /usr/lib/libc.so.1
(gdb) thread apply all bt

Thread 1 (process 87921 ):
#0 0xff0cdcdc in _lwp_kill () from /usr/lib/libc.so.1
#1 0xff066fb4 in raise () from /usr/lib/libc.so.1
#2 0xff042078 in abort () from /usr/lib/libc.so.1
#3 0x000331a4 in sigsegvHandler (signo=11) at beServer.cc:84
#4
#5 0x00000000 in ?? ()
#6 0xfe8d0430 in ttcdrv () from /u01/app/oracle/product/9.2/lib32/libclntsh.so.9.0
#7 0xfe7bba8c in nioqwa () from /u01/app/oracle/product/9.2/lib32/libclntsh.so.9.0
#8 0xfe54fa9c in upirtrc () from /u01/app/oracle/product/9.2/lib32/libclntsh.so.9.0
#9 0xfe54fa9c in upirtrc () from /u01/app/oracle/product/9.2/lib32/libclntsh.so.9.0

Other gdb back traces show a similar pattern.

To know more about gdb back trace please refer to <note 1368101.1> - Use GDB to Read a Core File and View Backtrace Information on a Solaris System.

Cause

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
Symptoms
Cause
Solution
References


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