My Oracle Support Banner

Enhancing 2GB Size Limit Of Cm.pinlog (Doc ID 2696542.1)

Last updated on JANUARY 26, 2024

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.



One is facing a widely known issue related to the 2GB size limit of cm.pinlog related to 32 bit architecture.

While doing the copy/truncate operations , cm is not writing to the log. Some log events are lost forever as the rotation takes time . One of the potential solutions would be to redirect it to the other log.

For example:

  1. Change the pin.conf log pointer
  2. Send kill -HUP (Hook-UP) to the CM PID (Private Identifier)

But the above approach is not working because CM (Connection Manager) does not handle kill -HUP this way.

Would it be feasible to Enhance this so that the CM can handle the HUP properly to make the pin.conf changes possible, when the process is running?


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.