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-72-2383755.1
Update Date:2018-04-29
Keywords:

Solution Type  Problem Resolution Sure

Solution  2383755.1 :   Epap 16.1 Early Checks Failed with error TKSPLATMI2|tpdApplicationProcessError|1.3.6.1.4.1.323.5.3.18.3.1.3.2|32501|Processing Error|Software Program Error|HOST-RESOURCET  


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
Symptoms
Changes
Cause
Solution


Created from <SR 3-17172669391>

Applies to:

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

Symptoms

Source Release: 16.1
Target Release:  16.2

Problem Details:
===========
Epap Software upgrade completed for Server B. Server A Failed in Early upgrade checks.

Error:
====

ERROR: There are alarms on the system!
ERROR: <<<   OUTPUT   >>>
ERROR:  SEQ: 190 UPTIME: 1808376 BIRTH: 1522274706 TYPE: SET ALARM: TKSPLATMI2|tpdApplicationProcessError|1.3.6.1.4.1.323.5.3.18.3.1.3.2|32501|Processing Error|Software Program Error|HOST-RESOURCET
ERROR: <<< END OUTPUT >>>
ERROR: earlyUpgradeChecks() code failed for Upgrade::EarlyPolicy::TPDEarlyChecks
ERROR: Failed running earlyUpgradeChecks() code
Whitelisted alarms:
ERROR: Early Upgrade Checks Failed!


SYSCHECK on Server A Showed pdba not running

=================================

Running modules in class proc...
*         run: FAILURE:: MINOR::5000000000000002 -- Server Application Process Error
*         run: FAILURE:: Only 0 instance(s) of pdba running. 1 instance(s) required!
One or more module in class "proc" FAILED

 

 

Changes

 

Cause

The cause of the issue is the Early Upgrade check script is catching the pdba alarm on the Server A which is expected. When incremental upgrade is initiated on the local Server B, the scripts controlling the incremental upgrade will cause the local Server B to communicate using Secure-Shell to both the local Server A and the remote Server A to stop the PDBA software. The PDBAs should be restarted only after both the local and remote EPAP systems have successfully completed the upgrade. Since the PDBA software is not running the syscheck utility will alarm the fact that the PDBA is not running on the local and remote EPAP A-servers
 

Solution

This is expected. To overcome this, alarm needs to be put into whitelist as mentioned in R16.2 Incremental Upgrade/Installation Guide


Open the file  /usr/TKLC/plat/etc/upgrade/upgrade.conf and add below line as a root user.
EARLY_CHECK_ALARM_WHITELIST=TKSPLATMI2


 


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