0442 - RTDB Database Capacity is 90% Full

EPAP database capacity alarms are triggered by allocated capacity, whereas EAGLE alarms are triggered by provisioned capacity.

Allocated Capacity refers to the amount of memory that is currently dedicated to storing each RTDB entity-type. For instance when the very first DN is added to the EPAP RTDB, the EPAP allocates a block of memory large enough to store 6 million DNs. Although most of this memory is not in-use (provisioned) it has been demarcated for future use and cannot be utilized to store other non-DN entities (such as IMSIs or DN-Blocks, etc).

Provisioned Capacity refers to the provisioned RTDB entries versus the max RTDB entries allowed on an EAGLE SM card by the EPAP/ELAP related quantity features activated on EAGLE. EAGLE RTDB capacity alarms are triggered when the provisioned capacity passes the 80% and 90% levels. Furthermore, if the EAGLE RTDB provisioned capacity is below 80% and the allocation of the next memory block by EPAP would cause overallocation of the DSM Memory on an EPAP SM card, the EAGLE will report the 80% capacity alarm for that card.

Example

RLGHNCXA21W 14-05-07 11:02:30 EST  EAGLE 46.0.0
0100.0442  *C CARD 1108  VSCCP   RTDB database capacity is 90% full

Alarm Level:Critical

Recovery

1. For ELAP, perform the following:
   1. Use the rept-stat-sccp command to identify all SCCP cards.

      tekelecstp 000623 13:34:22 EST  EAGLE5 36.0.0
          SCCP SUBSYSTEM REPORT IS-NR          Active      
               SCCP ALARM STATUS = No Alarms
          INPQ SUBSYSTEM REPORT IS-ANR         Restricted  -----
               ASSUMING MATE’S LOAD
               INPQ: SSN STATUS = Allowed     MATE SSN STATUS  = Prohibited
               INPQ ALARM STATUS = No Alarms
          GFLEX SERVICE REPORT IS-ANR         Active
               GFLEX ALARM STATUS = No Alarms
          MNP SERVICE REPORT   IS-ANR         Active
               MNP ALARM STATUS   = No Alarms
      
          SCCP Cards Configured=4  Cards IS-NR=2
          System TPS Alarm Threshold = 100% Total Capacity
          System Peak SCCP Load = 3000 TPS
          System Total SCCP Capacity = 5000 TPS
      
          CARD   VERSION      PST          SST         AST       MSU USAGE  CPU USAGE
          --------------------------
          1212   101-001-000  IS-NR        Active      ALMINH       45%         30%
          1301 P 101-001-000  IS-NR        Active      ------       35%         40%
          1305   -----------  OOS-MT       Isolated    ------        0%          0%
          2112   -----------  OOS-MT-DSBLD Manual      ------        0%          0%
          ---------------------------
          SCCP Service Average MSU Capacity = 40%       Average CPU Capacity = 35%
      
          AVERAGE CPU USAGE PER SERVICE: 
            GTT   = 15%  GFLEX =  5%  MNP = 10%
            INPMR =  2%  INPQ  =  3%   
      
          TOTAL SERVICE STATISTICS:
                                            FAIL     REROUTE\      FORWARD
            SERVICE    SUCCESS    ERRORS   RATIO     WARNINGS        TO GTT     TOTAL
            GTT:          1995         5      0%            -             -     2000  
            GFLEX:         500         1      0%            4            10      515
            MNP:           800         0      0%            2             3      805
            INPMR:          50         5      0%            0            15       70
            INPQ:          499         1      0%            -             -      500
      
          Command Completed.

   2. Use the rept-stat-card:loc=xxxx:mode=full command to determine daughterboard memory on each SCCP card.

      where xxxx is the SCCP card location. Verify the DSM’s database memory size.

      rlghncxa03w 05-07-27 16:43:42 EST  EAGLE 30.0.0
      CARD  VERSION     TYPE    APPL     PST           SST       AST
      1113  023-102-000 GPSM    EOAM     IS-NR         Active    -----
        ALARM STATUS      = No Alarms.
        BPDCM GPL version = 023-001-000
        IMT BUS A         = Conn
        IMT BUS B         = Conn
        CLOCK A           = Active
        CLOCK B           = Idle
        CLOCK I           = Idle
        MBD BIP STATUS    = valid 
        DB STATUS         = valid
        DBD MEMORY SIZE   = 256M
        TROUBLE TEXT VER. = Rev 1.6
      Command Completed.
      ;

   3. Use the rtrv-ctrl-feat command to verify the LNP Database feature quantity purchased for this system.
   4. Refer to ELAP Administration and LNP Feature Activation Guide to view the DSM requirements for the LNP telephone number quantity verified under rtrv-ctrl-feat. Contact your Oracle Communications Sales Representative or Account Representative if larger DSMs are needed.

      Proceed to next step if DSM capacity is not the issue.

   5. From the ELAP GUI, execute View RTDB Status and verify the ELAP is reporting the same alarm as the EAGLE.
   6. Verify the TN Counts listed on the GUI.
   7. Go to View LNP Qty Features on the ELAP GUI and verify the LNP ported TNs. This value should reflect the same information as seen under rtrv-ctrl-feat in the EAGLE.
   8. If the TN Count under View RTDB Status is 90% of the LNP ported TNs shown under View LNP Qty Features, this is the cause of the UAM 0442 – RTDB database capacity is 90% full.
   9. If the TN Count is not 90% of the LNP ported TNs, check to see if the NPANXX or LRN Counts are 90% of the LNP ported NPANXXs or LRNs values.
   10. Reduce the number of either TNs, LRNs, or NPANXXs by utilizing features/tools on the LSMS. Refer to Database Administrator's Guide for LSMS.
   11. If reducing the number of TNs, LRNs, or NPANXXs is not a viable option, increase the LNP telephone number quantity. Refer to the section "Activating the LNP Feature on the EAGLE" in Administration and LNP Feature Activation Guide for ELAP. Contact My Oracle Support (MOS) if you do not currently have the next higher TN quantity key.
2. For EPAP, perform the following:
   1. Use the rtrv-stpopts command to determine the status of EPAP data quantity related options. The following example shows the status of the EPAP240M Feature:

      Command Accepted - Processing
          tekelecstp 16-03-16 12:05:53 MST  EAGLE5 46.3.0.0.0-68.14.0
          STP OPTIONS
          -------------------------------
          EPAP240M                    off

   2. Use the rtrv-ctrl-feat:status=on command to determine the status of EPAP data related features that are currently activated. The following example shows the status of the EPAP Data Split feature:

      rlghncxa03w 12-03-13 16:40:40 EST EAGLE 46.4.0
      The following features have been permanently enabled:
      
      Feature Name               Partnum    Status  Quantity
      
      EPAP Data Split            893039801   on     ----
      Dual ExAP Config           893040501   on     ----

   3. Run the rtrv-bip:loc=<> command and use the part number of the card to determine the hardware type:

      Command Accepted - Processing
      
          eagle1 16-10-03 18:31:34 EST   EAGLE 46.3.0.0.1-68.27.0
          rtrv-bip:loc=1317
          Command entered at terminal #13.
      ;
      
          eagle1 16-10-03 18:31:34 EST   EAGLE 46.3.0.0.1-68.27.0
          --------------------------------------------------------------------------
          Location:  1317 - MBD
      
          Part Number:    870-2990-01
          Revision:       F                          Week/Year:        14/2012
          Serial Number:  10212145089
      
          Software Match ID:   EG - 001              Max Power Rating :  1537mA
          --------------------------------------------------------------------------
          END OF REPORT

      See the "Hardware Baseline EAGLE Release 45.0 - 46.x" table in Hardware Reference for card part numbers.
   4. Run the rept-stat-card:mode=full:loc=<> command and use the GPL name to determine the GPL type (32-bit or 64-bit) the card is running.
      See Chapter 3, "Introduction" in Database Administration - System Management to determine the GPL types.

      Command Accepted - Processing
      
          eagle1 16-10-03 18:18:12 EST   EAGLE 46.3.0.0.1-68.27.0
          rept-stat-card:mode=full:loc=1317
          Command entered at terminal #13.
      ;
      
          eagle1 16-10-03 18:18:12 EST   EAGLE 46.3.0.0.1-68.27.0
          CARD   VERSION      TYPE      GPL        PST            SST        AST
          1317   138-022-000  DSM       SCCP64     IS-NR          Active     -----
            ALARM STATUS       = No Alarms.
            BLDC64  GPL version = 138-023-000
            IMT BUS A           = Conn
            IMT BUS B           = Disc
            CLOCK A             = Active
            CLOCK B             = Fault
            CLOCK I             = Idle
            MBD BIP STATUS      = Valid
            MOTHER BOARD ID     = SMXG B
            DBD STATUS          = Valid
            DBD TYPE            = None
            DBD MEMORY SIZE     = 8192M
            HW VERIFICATION CODE = ----
            CURRENT TEMPERATURE   =  28C ( 83F)
            PEAK TEMPERATURE:     =  32C ( 90F)     [16-09-21 02:02]
            SCCP % OCCUP        = 0%
            SCCP SM DATA TYPE   = DN
            APPLICATION SERVICING
                                              MFC         MFC
                SNM     REQ STATUS =   24 hr: ---, 5 min: ---
                INM     REQ STATUS =   24 hr: ---, 5 min: ---
                MTP3    REQ STATUS =   24 hr: ---, 5 min: ---
                SFLOG   REQ STATUS =   24 hr: ---, 5 min: ---
            IPLNK STATUS
                IPLNK  IPADDR             STATUS     PST
                A      192.168.120.13     UP         IS-NR
                B      192.168.121.13     UP         IS-NR
            DSM IP CONNECTION
                PORT   PST             SST
                A      IS-NR           Active          
                B      IS-NR           Active
      
          Command Completed.

   5. Refer to the "EAGLE Feature and EPAP DB Capacity Combinations" table in Database Administration - GTT User's Guide to determine the maximum RTDB capacity based on the installed hardware and EPAP Quantity features activated in the system.
   6. Do one of the following:
      • Reduce the size of the database to match the installed hardware capacities.
      • Obtain and install a larger capacity SM card.
      • Obtain and activate the appropriate EPAP Quantity features.
      • Verify that the SM card is running the appropriate GPL type (32-bit or 64-bit).
   7. If the SM card requires 64-bit GPLs and the card is currently running 32-bit GPLs, see "Conversion of SM8G-B Cards" or "Conversion of SLIC Cards" in Database Administration - System Management User's Guide to convert 32-bit GPLs to 64-bit.