The PIbeClient Core Dumps When Querying a Wallet Containing More Than 2K of Data.

(Doc ID 1318750.1)

Last updated on MARCH 27, 2015

Applies to:

Oracle Communications Network Charging and Control - Version: 4.3.0 and later   [Release: 4.3 and later ]
Oracle Solaris on SPARC (64-bit)


The PIbeClient binary core dumps on the Service Management System (SMS) when an attempt to query some particular subscribers is made through the Provisioning Interface.

This problem occurs when a PI query command (CCSCD1=QRY) is sent to a wallet with more than 2K of data. PIbeClient is unable to handle the large amount of data returned and core dumps.

The version of the software only supports Escher messages with a maximum size of 2K - This is a design limitation in the software. When a wallet go over a certain size, the resulting Escher messages goes over that limit of 2k. The PiBeclient is not protected against that type of message and - upon reception - produces a core dump.

To protect itself against such Escher messages, the PiBeClient truncates messages bigger than 2k and produces the following error message :

"%s: Reply has been truncated size greater than %d"

where %d is PI configuration item PIBECLIENT_MAX_FIFO_MSG_SZ.

This is usually defined as 2000 and is defined in the code, so not changeable via a parameter.


No particular changes are required to observe this behavior, as it is a limitation in the length of the messages the PIbeClient can receive 


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 hundreds of Community platforms