Diameter Signaling Router (DSR) : High CPU Utilization in SOAM due to IDIH

Asset ID:	1-72-2291717.1
Update Date:	2017-07-31
Keywords:

Solution Type Problem Resolution Sure

Solution 2291717.1 : Diameter Signaling Router (DSR) : High CPU Utilization in SOAM due to IDIH

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.3.0 and later
Tekelec

Symptoms

There are Two DSR SOAMs namely SO-A and SO-B. Only SO-A displays a higher CPU utilization.
What can be the reason of SO-A showing higher CPU utilization compared to similar SO-B which is at a lower CPU level?

Cause

IDIH application log shows attempt by IDIH to sync database with DSR OAM which already exists in IDIH Oracle DB

2017-06-23 08:03:06,391 - INFO - idih-a - Trace Reference Data Adapter - trda - SYSTEM - IDIH-10013: Polling cycle successfully completed, WSDL version retrieved: 7.3.6.
2017-06-23 08:03:16,859 - INFO - idih-a - Trace Reference Data Adapter - trda - SYSTEM - IDIH-10034: Total 0 rows inserted successfully for Managed Object Type: AppRouteRule in Database.
2017-06-23 08:03:19,968 - ERROR - idih-a - Trace Reference Data Adapter - trda - SYSTEM - IDIH-10032: DataAccessException while inserting Managed Object Type: PeerRouteRule in Database. - org.springframework.dao.DuplicateKeyException: PreparedStatementCallback; SQL [INSERT INTO RD_PEER_ROUTE_RULE (NAME, MCL, PRIORITY, ACTION, ROUTE_LIST_NAME, DIAM_ANS_CODE, ERROR_MSG, MSG_PRIORITY, MSG_CPY_CFG_SET, VENDOR_ID, PEER_ROUTE_TABLE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; ORA-00001: unique constraint (NSP.RDA_RD_PRR_MCL_UIDX) violated

IDIH application log shows attempt by IDIH to sync database with DSR OAM which already exists in IDIH Oracle DB

Solution

from IDIH appserver go to path:

/trace-refdata-adapter

Run these commands as user 'tekelec':

ant clean.data
ant app.enable

If the issue reoccurs, catch below trace before clean/resync the iDIH TRDA data using the above procedure.

Get output of following command from from site (both active and standby SO is preferred):
- iqt -E PeerRouteRule
Execute the MCL value via below steps from IDIH server:
- login to appserver as "tekelec" user
- sqlplus /@NSP;
- select NAME,MCL from RD_PEER_ROUTE_RULE;

Please open a SR to share the results of the above commands to solve the case

References

<NOTE:2214161.1> - Peak CPU Utilization Measurements Regularly Hit 100% For OAM Servers

Attachments

This solution has no attachment