Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2223083.1
Update Date:2017-01-19
Keywords:

Solution Type  Problem Resolution Sure

Solution  2223083.1 :   The System Status for DDB in Aud-Data Command or Rept-Stat-DDB Command Is Aborted  


Related Items
  • Oracle Communications EAGLE (Hardware)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec Eagle 5
  •  




In this Document
Symptoms
Cause
Solution


Created from <SR 3-13970603791>

Applies to:

Oracle Communications EAGLE (Hardware) - Version EAGLE 3x.x and later
Information in this document applies to any platform.

Symptoms

The system status for the DDB audit is reported as ABORTED

> rept-stat-ddb

eaglestp 17-01-04 14:25:36 EAGLE5 45.0.1-64.70.35
DDB AUDIT REPORT
SYSTEM STATUS : ABORTED
ACTIVE MTP CARDS : 92
NON RESPONDING CARDS : 0
RESPONDING CARDS : 92
CARDS WITH NO DATA : 0
CARDS WITH DATA : 92
CARDS FAILING QUIET PRD : 6
CARDS WITH DDB UPD IN PRG : 0
CARDS CONSIDERED FOR CKSM : 0
INCONSISTENT CARDS : 0
CONSISTENT CARDS : 0
AUDIT START TIME : 04/01/2017 14:17:31
QUIET PERIOD : 500 ms

 

Cause

The IP network is likely too dynamic causing frequent status changes in the system, the DDB audit may get aborted (This is because the system uses default QUIET PERIOD value of 500ms while doing DDB audit)
 
We can see each time a number of cards failing the quiet period : CARDS FAILING QUIET PRD : 6
 

Solution

The customer has to solve the congestion issue which is causing the DDB inconsistency.

In the meantime, to get a proper status for the audit command, the quiet period must be reduced to 100 ms : aud-data:type=ddb:ddbqp=100

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback