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-71-2214891.1
Update Date:2017-01-03
Keywords:

Solution Type  Technical Instruction Sure

Solution  2214891.1 :   Diameter Signaling Router (DSR) - How to Verify There is no rpm Corruption Prior to an Upgrade?  


Related Items
  • Oracle Communications Diameter Signaling Router (DSR)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
  •  




In this Document
Goal
Solution


Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.0 and later
Information in this document applies to any platform.

Goal

To verify that there is no rpm database corruption that would cause an upgrade to fail.

Solution

On rare occasions the rpm database in the operating system can become corrupted. This is caused by a corrupted filesystem due to disk issues.

The corrupted rpm database will cause an upgrade to fail. Run the following on a server that is being considered for an upgrade to verify that this issue is not present:

rpm -qa | wc -l

The output of this command should be compared to the output of a different server on the system.

The output will be a number that should be the same for all dsr servers on the same release.

For example, shown for a soam and mp server on DSR 7.0.1:

[admusr@soam-a ~]$ rpm -qa | wc -l
906
[admusr@mp-1 ~]$ rpm -qa | wc -l
906
[admusr@mp-1 ~]$

Note that a server with rpm database corruption would need to be rebuilt via Disaster Recovery prior to upgrade.

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