CM Log Write Loop Due To A Core Dump (Doc ID 2900515.1)

Last updated on FEBRUARY 15, 2024

Applies to:

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

When a core dump is generated due to a code error, a write loop occurs in the cm log, this loop is only stopped with a cm process kill command.

Errors cm.pinlog:

	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

Goal

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