Frequently Asked Questions - How do I upgrade the database schema?

Follow these steps after upgrading an existing CMS database cluster for versions 3.3 or older. Versions 3.4 and newer have a revised process to follow for upgrading database clusters.

The new process for upgrading CMS database clusters, version 3.4 or newer, can be found here:

https://meeting-infohub.cisco.com/faq/index.phpaction=artikel&cat=5&id=517&artlang=e

This FAQ does not apply when you first set up database clustering, but these steps must be run after every subsequent Core server software update; otherwise the Call Bridges and databases may be out-of-step with regards to the database schema.

The upgrade path for a clustered system is:

Upgrade each database node one by one, ensuring each node is up and the database cluster status command reports full connection to the cluster, BEFORE upgrading the next one.

At this stage database cluster status should report healthy on all nodes, but the Call Bridges will not be operating correctly and will show database errors.

Use the command database cluster status to identify the primary node.
Log into this primary node’s MMP and issue the command
database cluster upgrade_schema
Verify that the operation was successful by using database cluster status.

A status of Enabled means success, whereas Error indicates an issue.

Last update:: 14-Jul-2025
FAQ ID:: 1246