Last updated on MARCH 27, 2015
Applies to:Oracle Communications Network Charging and Control - Version: 3.1.0 to 4.4.0 - Release: 3.1.0 to 4.4
Information in this document applies to any platform.
For further details about the ccsBeOrb process, please refer to the Charging Control Services (CCS) technical guide. To download the documentation, use the link in the references at the bottom of this document.
From that guide, here is a brief description of this process' role:
[...] ccsBeOrb interface is responsible for updating and retrieving subscriber account states for other processes. Updates to an account are also made from this ORB (object request broker) interface to the other Voucher And Wallet Server in the pair.[...]
This also applies to data gathered for the vouchers information screens.
When running a backtrace against the core file (Have a look through this document's references for details about running a backtrace and general gdb usage), the following output can be observed:
#0 .0xfebb1d50 in gethrtime () from /usr/lib/libc.so.1
#1 .0x000715cc in _ORBIT_skel_ccs_be_Voucher_queryByNumber (
.._ORBIT_servant=0x29a370, _ORBIT_recv_buffer=0x2998a0, ev=0xffbfe400,
.. _impl_queryByNumber=0x4cb7d8) at ccsBeOrb-skels.c:1676
.. at orbit_poa.c:513
#3 .0x0007c85c in ORBit_handle_incoming_request (recv_buffer=0x2998a0)
.. at server.c:90
#4 .0x00033b1c in pollORB () at orb.cc:330
#5 .0x00030a54 in main (argc=785408, argv=0xbfc00) at ccsBeOrb.cc:85
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms