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-1946234.1
Update Date:2018-04-06
Keywords:

Solution Type  Problem Resolution Sure

Solution  1946234.1 :   EPAP Software Stop Running and Unable to Bring Up Application Process.  


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


Created from <SR 3-9817153501>

Applies to:

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

Symptoms

The EPAP software is down and syscheck reporting Server Application Process Error.

*         run: FAILURE:: MINOR::5000000000000002 -- Server Application Process Error
*         run: FAILURE:: Only 0 instance(s) of maint running. 1 instance(s) required!
*         run: FAILURE:: MINOR::5000000000000002 -- Server Application Process Error
*         run: FAILURE:: Only 0 instance(s) of rtdb running. 1 instance(s) required!
*         run: FAILURE:: MINOR::5000000000000002 -- Server Application Process Error
*         run: FAILURE:: Only 0 instance(s) of topnode running. 2 instance(s) required!
*         run: FAILURE:: MINOR::5000000000000002 -- Server Application Process Error
*         run: FAILURE:: Only 0 instance(s) of prov running. 1 instance(s) required!
*         run: FAILURE:: MINOR::5000000000000002 -- Server Application Process Error
*         run: FAILURE:: Only 0 instance(s) of provRMTP running. 4 instance(s) required!
*         run: FAILURE:: MINOR::5000000000000002 -- Server Application Process Error
*         run: FAILURE:: Only 0 instance(s) of provRcvr running. 4 instance(s) required!
*         run: FAILURE:: MINOR::5000000000000002 -- Server Application Process Error
*         run: FAILURE:: Only 0 instance(s) of epapsmdbmntr running. 1 instance(s) required!
One or more module in class "proc" FAILED

Cause

An attempt to restart EPAP software was not successful. The process appears to be stucked and not starting up.

PDBA application continue running and working fine.

The EPAP software remain as down.

[root@mps]#  service Epap start
~~ /etc/init.d/Epap start ~~
"EPAP_RELEASE" is set to "15.0."
EPAP application started.

[root@mps]# service Epap status
~~ /etc/init.d/Epap status ~~
--------------------------
process maint is down.
process prov is down.
process provRcvr is down.
process provRMTP is down.
process rtdb is down.
process topnode is down.
process eirlog is down.
process eaglelog is down.
process epapsmdbmntr is down.
--------------------------
EPAP application is stopped.

[root@mps]# service Pdba status
~~ /etc/init.d/Pdba status ~~
PDBA application is running.

Solution

1. Ensure you have a copy of current backup of RTDB and PDB. Otherwise, take a backup of the current RTDB and PDB. (refer to EPAP Administration manual in online documentation for Oracle Communications Documentation for Tekelec Products.)

2. Execute below command to restart the server:-
  # /etc/init.d/Epap stop
  # /etc/init.d/Pdba stop
  # init 6

3. After server comes back, verify process status:-
  # manageBannerInfo -l
  # syscheck
  # service Epap status


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