My Oracle Support Banner

Database Cleanup Scripts Do Not Log Information and Fail Silently (Doc ID 2470338.1)

Last updated on MARCH 19, 2019

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.0 to 12.0.1.0.0 [Release 6.0 to 12.0.0]
Oracle Communications Network Charging and Control - Version 4.3.0 to 12.0.1.0.0 [Release 4.3 to 12.0.0]
Information in this document applies to any platform.

Symptoms

On all versions of Oracle Communications Convergent Charging Controller (OC3C or 3C) and Oracle Communications Network Charging and Control (OCNCC or NCC) up to and including 12.0.1.0, neither of the database cleanup scripts (ACS/bin/acsDbCleanup.sh and SMS/bin/smsDbCleanup.sh) log any useful information to the system logs.

In all current versions, smsDbCleanup.sh will only log a warning if another instance is already running and acsDbCleanup.sh will logs nothing.

It is expected that each script will log the following levels of information to the system log:

It is also expected that both scripts log to stdout (so the process logs respectively) the same information as the system log as well as all NOTICE messages.

As a result, failures in the scripts are never logged/reported which can cause further issues in the future as tables/tablespaces fill up.

Changes

 

Cause

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
Symptoms
Changes
Cause
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.