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-2357222.1
Update Date:2018-02-05
Keywords:

Solution Type  Technical Instruction Sure

Solution  2357222.1 :   EPAP 16.2 Upgrade causes RTDB to be Inconsistent if the REPL logs were not cleared  


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




In this Document
Goal
Solution
References


Created from <SR 3-16750781761>

Applies to:

Oracle Communications EAGLE (Software) - Version EPAP 16.2 and later
Tekelec

Goal

EPAP 16.2 Upgrade document doesn't specify the steps to clear the REPL logs.

Solution

We found that it was a documentation error in our EPAP 16.2 Upgrade document, procedure 7 Page 36 , which doesn’t mention the steps to clear the REPL logs :

https://docs.oracle.com/cd/E87668_01/doc.162/E87679_rev_1.pdf

Document BUG 27469826 is opened to add this steps in procedure 7.

As a workaround , It is suggested to perform the procedure 7 Page 38 of EPAP 16.1 Upgrade document which has the steps to clear the REPL logs.:

https://docs.oracle.com/cd/E60140_01/doc.161/E75563_rev_06.pdf   

Please note that here in procedure 7 , step 4 of EPAP 16.1 upgrade document , it doesn't mention to stop the EPAP software in mate i.e. EPAP B. So, we have to stop the EPAP Software in mate as well while following EPAP 16.1 upgrade document procedure 7.

Rest all of the procedures will be followed from EPAP 16.2 Upgrade guide only.

This workaround to be used until the new EPAP 16.2 Upgrade document is published.

Note : Due to absence of this step , when the EPAP process restarts after PDB restore , it will do some validation and if it found any abnormality, it will set the RTDB level as Inconsistent. It is not confirmed that we will face the problem everytime if the REPL logs were not removed during procedure 7 , basically it depends on what level the replLog has stored and depends upon the stage at which the PDB backup was taken. But truncating or removing the replLog during procedure 7 makes sure that the problem will not happen due to replLog issue.

References

<BUG:27469826> - ADD REPLLOG TRUNCATION STEP BEFORE PDB BACKUP

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