My Oracle Support Banner

The smsDbCleanup Script Does Not Delete Any Alarms if Alarm Retention Period Is Set to 0 (Doc ID 1387543.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Communications Network Charging and Control - Version: 2.4.0 to 4.4.0 - Release: 2.4 to 4.4
Information in this document applies to any platform.


The smsDbCleanup script is a script run on a regular basis on the Service Management System (SMS) server, usually from the smf_oper user's crontab. The role of this script is mainly maintenance - it cleans up old alarms and statistics to avoid unnecessary tablespace usage.

For more information about smsDbCleanup, please refer to the Service Management System (SMS) technical guide - There is a link to a document describing how to download Network Charging and Control (NCC) documentation in this document's references.

One could want to delete all alarms history on each script execution by changing a parameter in smsDbCleanup's configuration section in eserv.config configuration file, one of the way of doing so is setting the parameter alarmAge to 0.

The script does not clean any alarms when the parameter alarmAge is set to 0.

Example eserv.config section :

SMS = { smsDbCleanup = { alarmAge = 0 alarmMax = 1000000 auditAge = 7 commit = 100 statsAge = 3 templateAge = 1 unknownMax = 5000

This can be easily verified by checking the number of rows in the table smf_alarm_message before and after a script execution, using the following query :

SQL> SELECT count(*) FROM smf_alarm_message;

The number of rows will not change, or will even increase with new alarms being risen.


Changing the parameter alarmAge to 0 in the eserv.config file is the cause of this issue.


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.