SMF Tables Not Maintained due to smsDbCleanup.sh Failing to Connect to Oracle DB

(Doc ID 2418865.1)

Last updated on JULY 11, 2018

Applies to:

Oracle Communications Network Charging and Control - Version 6.0.0 and later
Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Information in this document applies to any platform.

Symptoms

On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C) versions 6.0.0 (inclusive) and above, the smsDbCleanup.sh script is no longer able to connect to the Oracle Database.

When the script is executed, the following is logged:

ERROR:
ORA-01017: invalid username/password; logon denied

SP2-0306: Invalid option.
Usage: CONN[ECT] [{logon|/|proxy} [AS {SYSDBA|SYSOPER|SYSASM|SYSBACKUP|SYSDG|SYSKM}] [edition=value]]
where <logon> ::= <username>[/<password>][@<connect_identifier>]
      <proxy> ::= <proxyuser>[<username>][/<password>][@<connect_identifier>]
SP2-0306: Invalid option.
Usage: CONN[ECT] [{logon|/|proxy} [AS {SYSDBA|SYSOPER|SYSASM|SYSBACKUP|SYSDG|SYSKM}] [edition=value]]
where <logon> ::= <username>[/<password>][@<connect_identifier>]
      <proxy> ::= <proxyuser>[<username>][/<password>][@<connect_identifier>]
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
ERROR:
ORA-01017: invalid username/password; logon denied

ERROR:
ORA-01017: invalid username/password; logon denied

/IN/service_packages/SMS/bin/smsDbCleanup.sh Completed

This script is responsible for:

  1. Removing old records from the SMF_AUDIT table
  2. Removing old records from the SMF_STATISTICS table
  3. Removing old records from the SMF_ALARM_MESSAGE table
  4. Removing records from the SMF_ALARM_MESSAGE table if the number of rows exceeds the maximum configured
  5. Removing UNKNOWN records from the SMF_ALARM_UNKNOWN table if the number of rows exceeds the maximum configured
  6. Rebuilds all the indexes on the aforementioned tables

Over time, if this script is not corrected, then the performance of the DB will be compromised (degraded performance or full tablespaces).

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms