EMS Migration from Oracle to Postgres Database

Initial Date of Publication: 11/24/2014

Document Number

ENG-010470

Introduction

Beginning with FP 28.0 release, Panorama PON EMS version 28.x starts supporting Postgres database as an alternative to the more expensive Oracle database. For technical or economic considerations, it may be desirable to migrate from Oracle to Postgres database. This Application Note describes the few simple steps to make that happen.

Applies To

This Application Note applies to Panorama PON EMS version 19.x for FP 27.1 with Oracle database.

Assumptions

One of the assumptions for this procedure is that the new 28.x EMS will be installed on a new server machine or VM. The other one is that there is no 1100 Voice Gateway system in the network.

Migration Procedure

The procedure below describes the general steps to migrating EMS database from Oracle to Postgres while upgrading EMS from 19.x to 28.x. Unless noted separately, this procedure applies to both Windows and Solaris-based EMS servers. The steps for backing up data are included so the system can be restored in case of failure.

1. Install the 28.x EMS on a new server (or VM) and choose Postgres as the database.
2. Enter the HTTP account information, it does not have to be identical to the username/password for 19.x EMS, but it has to be created.
3. Create EMS user accounts like they were created in 19.x EMS. These user accounts will not be migrated from the old server.
4. Verify the default profiles have the same settings as the default profiles on the 19.x EMS. These profiles include PoE, Port, LLDP, PAE, RSTP, PON, Service, and NAC profiles. Special note on the default PoE profile, PoE is enabled in this profile.
5. With the introduction of ONT template in 28.x EMS, the PoE settings for various types of ONT are now controlled by this template. Make sure the settings in the default ONT template are the same as they are in 19.x EMS.
6. Back up the OLT on 19.x EMS server and archive the backup files.
7. Back up the EMS on 19.x EMS server and archive the backup files.
8. Delete the OLT from the 19.x EMS server.
9. Add the OLT to the new 28.x EMS server with the READ option. Do not choose to erase configuration on the OLT.
10. Back up the OLT on 28.x EMS server and archive the backup files.
11. Back up the EMS on 28.x EMS server and archive the backup files.
12. Validate that the profiles are working correctly and then perform the upgrade of the OLT to FP28.
13. The old 19.x EMS server can be decommissioned.

Summary

The main idea behind these steps is that the most current configuration data is on the OLT themselves and EMS can discover all this data by reading it back from the OLT. For EMS specific data, like HTTP account, user accouts, they need to be manually created. For global data like profiles and templates, they need to be verified to make sure the customized settings are properly configured in the new installation. If any of the two assumptions outlined is not met, the customer is encouraged to contact TAC for assistance.