3 Supported Upgrade and Rollback Paths
This chapter lists the supported upgrade and rollback paths in Release 23.4.x. For more information about upgrade and rollback procedures, see Oracle Communications Cloud Native Core, Unified Data Repository Installation, Upgrade, and Fault Recovery Guide.
Release 23.4.2
The following table lists the supported upgrade paths in release
23.4.2:
Table 3-1 Supported Upgrade Paths
| Source Release | Target Release |
|---|---|
| 23.4.x | 23.4.2 |
| 23.3.x | 23.4.2 |
| 23.2.x | 23.4.2 |
The following table lists the supported rollback paths in release
23.4.2:
Table 3-2 Supported Rollback Paths
| Source Release | Target Release |
|---|---|
| 23.4.2 | 23.4.0 |
| 23.4.2 | 23.3.x |
| 23.4.2 | 23.2.x |
Release 23.4.1
The following table lists the supported upgrade paths in release
23.4.1:
Table 3-3 Supported Upgrade Paths
| Source Release | Target Release |
|---|---|
| 23.4.0 | 23.4.1 |
| 23.3.x | 23.4.1 |
| 23.2.x | 23.4.1 |
The following table lists the supported rollback paths in release
23.4.1:
Table 3-4 Supported Rollback Paths
| Source Release | Target Release |
|---|---|
| 23.4.1 | 23.4.0 |
| 23.4.1 | 23.3.x |
| 23.4.1 | 23.2.x |
Release 23.4.0
The following table lists the supported upgrade paths in release
23.4.0:
Table 3-5 Supported Upgrade Paths
| Source Release | Target Release |
|---|---|
| 23.3.x | 23.4.0 |
| 23.2.x | 23.4.0 |
The following table lists the supported rollback paths in release
23.4.0:
Table 3-6 Supported Rollback Paths
| Source Release | Target Release |
|---|---|
| 23.4.0 | 23.3.x |
| 23.4.0 | 23.2.x |
Upgrade and Rollback of Multiple Sites Deployments:
You must follow a specific order during upgrade and rollback of multiple
sites deployment. You must upgrade one site at a time starting with the NF and then
cnDBTier and you must rollback all cnDBTier sites and then rollback UDR across all
sites. For example, in a three-site setup, you must follow the below order for NF
and cnDBTier upgrade:
- Upgrade site 1 UDR, Provisioning Gateway, CNC Console, and Tools (subscriber bulk import and subscriber export tool) deployments if present.
- Upgrade site 1 cnDBTier
- Upgrade site 2 UDR, Provisioning Gateway, CNC Console, and Tools (subscriber bulk import and subscriber export tool) deployments if present.
- Upgrade site 2 cnDBTier
- Upgrade site 3 UDR, Provisioning Gateway, CNC Console, and Tools (subscriber bulk import and subscriber export tool) deployments if present.
- Upgrade site 3 cnDBTier
- Rollback site 1 cnDBTier
- Rollback site 2 cnDBTier
- Rollback site 3 cnDBTier
- Rollback site 1 UDR, Provisioning Gateway, CNC Console, and install rollback version of the tools (subscriber bulk import and subscriber export tool) deployments if present.
- Rollback site 2 UDR, Provisioning Gateway, CNC Console, and install rollback version of the tools (subscriber bulk import and subscriber export tool) deployments if present.
- Rollback site 3 UDR, Provisioning Gateway, CNC Console, and install rollback version of the tools (subscriber bulk import and subscriber export tool) deployments if present.
The above order is required because of the SQL rollback limitation
applicable for cnDBTier:
- If there are schema changes on any of the tables when running on the higher n+1 release version of cnDBTier, then when you rollback the NF to "n" version of cnDBtier, the schema changes which happened on the higher n+1 version will not be handled and the tables with these changes are dropped and are not re-created on the lower version. For more information, see the Prerequisites section in the Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.
- Rollback of cnDBTier must be performed carefully as per the above specified order because UDR, Provisioning Gateway, and Tools (subscriber bulk import and subscriber export tool) upgrade and rollback procedure includes database schema change.
- There must not be database schema change in the current cnDBTier version to rollback. If there is any database schema change after cnDBtier is upgraded, then these schema changes must be reverted. You must contact My Oracle Support for assistance.
Note:
- During the upgrade procedure if there is an issue on UDR, Provisioning Gateway, or Tools in any sites, then UDR, Provisioning Gateway, or Tools must be rolled back immediately. Do not rollback cnDBTier. cnDBTier must be rolled back only if there is a cnDBTier upgrade issues.
- Verify the cnDBTier after the upgrade is complete. If there are issues, rollback the cnDBTier immediately. Do not rollback UDR, Provisioning Gateway, or Tools, they can remain on the higher version and are compatible with n-1 cnDBTier release.
- To avoid failures during cnDBTier rollback due to schema changes (for example, helm upgrade, rollback performed on UDR, Provisioning Gateway, and subscriber bulk import and subscriber export tool deployments), you can drop the modified schema tables manually before rollback and re-create the modified schema tables after the rollback is complete. For more information, see the Prerequisites section in the Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide and contact My Oracle Support for assistance.
If the Provisioning Gateway, nudr-bulk-import, and nudr-export-tool are
deployed in the site, the upgrade must be preformed in the order as follows:
- Upgrade UDR
- Upgrade Provisioning Gateway
- Upgrade nudr-bulk-import
- Upgrade nudr-export-tool
- Upgrade cnDBTier
Note:
Enable the flagndb_allow_copying_alter_table when installing cnDBTier 23.4.0
on UDR 23.4.0.