When the solidDB database server software is upgraded, the master database server must be upgraded prior to upgrading any replica database servers. To ensure that data is converted from the previous format to the new format, you should start the upgraded server and use either the -x convert or -x autoconvert option on the command line. See Upgrading solidDB to a new release level, and Command line options for more details.

If you are using solidDB HotStandby, you must first set the primary server to PRIMARY ALONE state to allow upgrade of the secondary server. After the primary server has been switched to PRIMARY ALONE state, the secondary server can be shut down and upgraded. After the secondary server is upgraded, it is restarted. After successful catchup, the original primary server is shut down and the secondary server is immediately switched to PRIMARY ALONE state. The original primary server can be upgraded while former secondary server runs in PRIMARY ALONE state. Finally, the original primary server is started as a secondary server and runs in catchup mode using the transaction log of the new primary server. For more details, see Using HotStandby with applications.

When you use solidDB with Shared Memory Access (SMA) or Linked Library Access (LLA), the application typically changes when the schema changes. This means that a new build of the application and the SMA or LLA library might be needed as part of the schema upgrade process.