OpManager DB migration from PgSQL to MSSQL

OpManager DB migration from PGSQL to MSSQL on the same server in Version 12.3

Please follow the below mentioned steps to migrate DB from PGSQL to MSSQL on the same server. These steps are applicable only on builds 12.3.045 and above. If you are in older versions below 12.3.045, please upgrade to 12.3.045 and follow these steps.


1. Stop the OpManager Service.

2. Ensure OpManagerTrayicon, java and Postgres processes are stopped completely in the task manager, if not, end them manually.

3. Rename the existing OpManager folder to OpManager_PGSQL

4. Download the same version from archives.


5. Uninstall the existing OpManager and install the OpManager again in the same version with the MSSQL setup.

6. At the end of the installation wizard, don't click "Finish" button.  Leave it and let it be.

7. Now open cmd prompt as an administrator, go to the PGSQL installation \OpManager_PGSQL\bin\ directory

8. Execute migrateDB.bat mssql E:\OpManager\
conf\database_params.conf (Replace with your Folder Name accordingly and point the database_params.conf file from your new MSSQL setup)

9. Change the Recovery Model to Simple by following the steps below:

Go to MSSQL server-->OpManagerDB properties-->Options-->Recovery Model-->Simple. (You can replace it with full mode later).

10. Copy bcp.exe and bcp.rll  files from your MSSQL server to OpManager home folder and OpManager/bin folder. Also, MSSQL native client should be installed on OpManager server based on the Operating system (64/32 bit) on the server.

11. It takes some time to migrate depending on the data size.

12.  After migration completes, navigate to PGSQL \OpManager_PGSQL\conf\OpManager\ folder and copy the data-dictionary.xml file and replace it into MSSQL  \OpManager\conf\OpManager\ 

13. Copy AdventNetLicense.xml, Petinfo.dat and Product.dat from PGSQL  \OpManager_PGSQL\lib\ and replace into MSSQL  \OpManager\lib\ 

14. Now click the "Finish" button in the installation wizard, this will start OpManager Service by itself.

Check if it is started without any error and able to connect the web client. 


          • Related Articles

          • OpManager DB migration from PGSQL to MSSQL in Version 125230

            For OpManager version 125230: PGSQL to MSSQL Migration Steps : In the PGSQL setup, go to OpManager home → bin, start Command Prompt with administrator privilege from this path and run DBConfiguration.bat. In the popup shown, please chose MSSQL, check ...
          • Database Migration - MySQL to PgSQL

            The DB migration from MySQL to PgSQL involves taking a PgSQL compatible backup, re-installing the product with PgSQL database and restoring the backup. The procedure for the above is a little tedious and time consuming in version 9 & 10. So, please ...
          • Migrating OpManager setup with MSSQL DB from one server to another.

            Question : I have OpManager with MSSQL DB and both are installed in same server. I want to move both from one server to another. Steps to be followed : 1. Take a SQL DB backup using SQL Management tool. 2. Download and install a fresh setup of ...
          • Steps for setting up a password for PgSQL DB

            The steps are verified and tested until 12.4.072.  We request you to take a VM snapshot or a folder backup of the OpManager server itself (stop the OpManager service) as a first measure. Below mentioned steps are applicable for Postgres version till ...
          • Moving OpManager from one server to another server without reinstalling OpManager

            Question : How do I move OpManager from one server to another without reinstalling OpManager. Solution:  It is easy to move OpManager from one Server to another just by copying  the complete OpManager folder and installing  the service. Steps: 1)Stop ...