Go to primary content
User Data Repository Alarms, KPIs, and Measurements
Release 12.4
E82598-01
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

TmSingleTransQueueFull

Measurement ID
9415
Measurement Group
Transport Exception
Measurement Type
Simple
Measurement Dimension
Arrayed (per Transport)
Description
The number of egress messages that were discarded because the single Transport Writer Queue was full.
Collection Interval
30 min
Peg Condition
Check whether the single peers transmit data queue limit has reached its max limit (1000). If max limit is reached or exceeded then peg the measurement and discard the low priority events.
Measurement Scope
NE, Server

Recovery

  1. This measurements indicates that the Transport is backed up and there could be messages that will get discarded. If it's above the defined critical threshold, it results in generating Alarm 19408 - Single Transport Egress-Queue Utilization (refer to the DSR Alarms and KPIs Reference for details about this alarm).
  2. The percent utilization of the MP's Transport Writer Queue is approaching its maximum capacity. If this problem persists and the queue reaches 100% utilization, all new egress messages from the Transport will be discarded.
    This alarm should not normally occur when no other congestion alarms are asserted. This may occur for a variety of reasons:
    1. An IP network or Adjacent node problem may exist preventing SCTP from transmitting messages into the network at the same pace that messages are being received form the network.
    2. The SCTP Association Writer process may be experiencing a problem preventing it from processing events from its event queue. The alarm log should be examined form Main Menu > Alarms & Events.
    3. If one or more MPs in a server site have failed, the traffic will be distributed amongst the remaining MPs in the server site. MP server status can be monitored form Main Menu > Status & Control > Server Status.
    4. The mis-configuration of Adjacent Node IP routing may result in too much traffic being distributed to the MP. Each MP in the server site should be receiving approximately the same ingress transaction per second.
    5. There may be an insufficient number of MPs configured to handle the network traffic load. The ingress traffic rate of each MP can be monitored from Main Menu > Status & Control > KPI Display. If all MPs are in a congestion state then the offered load to the server site is exceeding its capacity.
  3. It is recommended to contact My Oracle Support for assistance if needed.