EPAP B Server Is Not Coming Up And GUI DB Status Internal Error, EuiDB not created in B server, All EPAP processes do not start

Asset ID:	1-71-2256124.1
Update Date:	2017-04-19
Keywords:

Solution Type Technical Instruction Sure

Solution 2256124.1 : EPAP B Server Is Not Coming Up And GUI DB Status Internal Error, EuiDB not created in B server, All EPAP processes do not start

Applies to:

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

Goal

EuiDB not present in B server after Full upgrade of EPAP 16.1. All EPAP processes do not start after the procedure is competed.

Solution

The replication between A and B server was not successful due to which the EuiDB was created only on the A server and not replicated to B server.

Symptom:

After Full upgrade of EPAP 16.1 servers, all EPAP processes are not running. in the log file /usr/TKLC/epap/logs/gd.dbg, a log is present indicating "EuiDB" is not present in B server.

04/10/17-15:55:12 (TID 7f02a64be720): Wasn't able to open EuiDB

How to recover:

1. Create a dummy EuiDB in the B server as follows

a. Login to mysql prompt. mysql -uroot -p <password>

mysql> create database EuiDB;

mysql> exit;

2. resetReplication from A server to B server

/usr/TKLC/appl/config/resetReplication

Make sure to input option so that the replication happens from A server to B server i.e.

Which side do you want to copy FROM? (A/B) [B]: A (Input A here).

3. After reset Replication is complete, reboot the B server (minicom mate from A server and then reboot)

4. Check that all EPAP services are running. Then check that EPAP A and B have same RTDB level (View RTDB status).

service Epap status.

Attachments

This solution has no attachment