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-2163915.1
Update Date:2016-07-27
Keywords:

Solution Type  Technical Instruction Sure

Solution  2163915.1 :   How to run repairDB.pl to correct corrupted DN count (Corrupted after running checkDnNEAssoc script in EPAP 15.0)  


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




In this Document
Goal
Solution


Created from <SR 3-12089245891>

Applies to:

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

Goal

Run the script repairDB.pl to correct corrupted DN count (Corrupted after running checkDnNEAssoc script in EPAP 15.0)

Solution

When the script checkDnNeAssoc was run as part of EPAP 15 migration, there is a high chance it corrupted the dn count for NEs. A new script repairDB.pl is made which will repair the corrupted DB.

Procedure:

1. Download the repairDB.pl and the README from MOS. The script repairDB.pl and README are attached in this KM.

2. The script should be run on EPAP 15.0 system where checkDnNeAssoc script was run earlier. Also it can be run on a EPAP 16.0 system which was upgraded from EPAP 15.0 server where the script was run earlier as part of EPAP 15.0 migration.

3. ORACLE personnel should execute the entire procedure as mentioned in the README. ORACLE personnel should be present during the entire execution of the procedure.

4. After the procedure is completed, ORCALE personnel should remove the script (repairDB.pl) from the server. This script is made for one time use in the server and should be removed after the job is done.

5. The script should be run before upgrade to EPAP 16.1. if there is any discrepancy reported by the script, it should be corrected before the upgrade.

Note:
Maximum time is spent by the script to find the discrepancy. Once discrepancy is found out, the correction does not take too much time (around a minute required).
Unless there is specific need to just find out the discrepancy, choose option "Y", when script asks for repair DB after it has found out the discrepancy.

 


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