Server Manager - Update Database - Fatal Error - Management Base fail to update - ERROR relation already exists

This page outlines the following issue you may face when migrating your management schema.

The below mentioned error may occur:

          ERROR:  Internal error occurred.
                            The application is closing. Call CAST support now providing the log file at C:\Users\xxx\AppData\Local\Temp\35\CAST\CAST\1.0\CAST-MS1.log.txt
                            com.castsoftware.java.MessageRuntimeException:Internal error occurred.
                            The application is closing. Call CAST support now providing the log file at C:\Users\xxx\AppData\Local\Temp\35\CAST\CAST\1.0\CAST-MS1.log.txt
                              com.castsoftware.java.IOMonitor.fail(IOMonitor.java:252)
                              com.castsoftware.java.IOMonitor.throwGeneralError(IOMonitor.java:194)
                              com.castsoftware.mda.run.ConfiguredApplication$2.call(ConfiguredApplication.java:251)
                              com.castsoftware.mda.run.ConfiguredApplication$2.call(ConfiguredApplication.java:1)
                              com.castsoftware.util.logger.Logging.execute(Logging.java:491)
                              com.castsoftware.util.logger.Logging.runInNewContext(Logging.java:383)
                              com.castsoftware.mda.run.ConfiguredApplication.run(ConfiguredApplication.java:227)
                              com.castsoftware.pmc.run.CLIPMCConfiguredApplication.executeInLogContext(CLIPMCConfiguredApplication.java:87)
                              com.castsoftware.pmc.run.CLIPMCConfiguredApplication$1.call(CLIPMCConfiguredApplication.java:53)
                              com.castsoftware.pmc.run.CLIPMCConfiguredApplication$1.call(CLIPMCConfiguredApplication.java:1)
                              com.castsoftware.util.logger.Logging.execute(Logging.java:491)
                              com.castsoftware.util.logger.Logging.runInNewContext(Logging.java:383)
                              com.castsoftware.pmc.run.CLIPMCConfiguredApplication.execute(CLIPMCConfiguredApplication.java:47)
                              com.castsoftware.pmc.CLI.main(CLI.java:24)
                              sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                              sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
                              sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
                              java.lang.reflect.Method.invoke(Unknown Source)
                              com.castsoftware.bootstrap.JarBootstrap.executeMain(JarBootstrap.java:529)
                              com.castsoftware.bootstrap.JarBootstrap.main(JarBootstrap.java:755)
                            Error while executing Update: create index pk__CPP_Analysis on xxx_mngt.CMS_CPP_Analysis(Object_ID)
                              com.castsoftware.java.InternalException:Error while executing Update: create index pk__CPP_Analysis on xxx_mngt.CMS_CPP_Analysis(Object_ID)
.....

 com.castsoftware.bootstrap.JarBootstrap.main(JarBootstrap.java:755)
                              ERROR: relation "pk__cpp_analysis" already exists
                                org.postgresql.util.PSQLException:ERROR: relation "pk__cpp_analysis" already exists
                                  org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)

You can find the mentioned error in CAST-MS log file. Refer the page (CAST Management Studio - Information - How to find logs) to find the log file. 

1. Duplicate a Table with the same definition but without index.
2. Rename
3. Upgrade the Databases.
4. Select the management base.
5. Run the update.
6. Migration fails with the above mentioned error.

1. Search in the error message what is the name of the index of the table that cannot be created and the name of the table where the index is supposed to be defined:
   
   In the above example, the index name is pk__CPP_Analysis and the table name is CMS_CPP_Analysis. The table name is prefixed by the schema name.
2. Restore the schema backup before migration.

3. Run the following query:

   Query

   set search_path = <Schema name>
   DROP INDEX pk__cpp_analysis;
    

4. Upgrade the database again.
5. If the above points do not help you, contact CAST Technical Support and provide the Relevant input in order to reproduce the issue.

Impact of issue: Up-gradation of CAST MNGT schema fails.

Impact after applying solution: CAST MNGT schema up-gradation is successful.