Masking or Reducing the Severity of Login Errors in the CM Log (Doc ID 2438931.1)

Last updated on JULY 11, 2022

Applies to:

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

Goal

On all versions of Oracle Communications Billing and Revenue Management (BRM), when a failed login attempt is made, the following errors are logged by Connection Manager (CM) to cm.pinlog:

Is it possible to prevent this alarm from being logged when incorrect credentials are used to log into BRM or at least reduce the severity from an error to something lower?

Solution

	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

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.

Masking or Reducing the Severity of Login Errors in the CM Log (Doc ID 2438931.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!