Frequently Asked Questions (FAQs)

What is the upgrade sequence for NFs and cnDBTier when there are multiple NFs in a network?

You can perform upgrade of an NF followed by cnDBTier in a site. This is the only recommended upgrade sequence. There's no fixed order of upgrade between multiple NFs.

For Example: NRF, SCP, or SEPP are deployed in the network, if the NFs are 3GPP compliant, upgrade sequence between NFs isn't dependent. If you upgrade NRF first, then follow the upgrade of cnDBTier connected to NRF. For more information about the upgrade sequence, see the Overview section.

What if during the upgrade of a site, the upgrade fails? What should be the upgrade sequence?

There's no change in the upgrade sequence. You can perform upgrade of an NF followed by cnDBTier. This is the only recommended upgrade sequence. In case the upgrade fails, perform fault recovery procedures for the site. For more information about the upgrade sequence, see the Overview section.

If it's a NF, then follow the fault recovery procedure provided in NF-specific Installation, Upgrade, and Fault Recovery Guide.

If it's the cnDBTier, then follow the fault recovery procedure provided in Oracle Communications Cloud Native Core DBTier Installation, Upgrade, and Fault Recovery Guide.

During the upgrade, if georeplication fails then what are recommended upgrade procedures to recover the sites?

In case the replication fails during upgrade or postupgrade, then resync the replication after upgrade completion using cnDBTier procedures. For more information about the resync, see Oracle Communications Cloud Native Core DBTier Installation, Upgrade, and Fault Recovery Guide. If the issue persists, contact My Oracle Support.

What is the upgrade impact if the NF schema version changes when georeplication is enabled?

NF upgrade takes care of any schema changes automatically. If any NF requires an alternate update strategy due to non-backward compatibility issues, it will be documented in NF-specific Installation, Upgrade, and Fault Recovery Guide.

If I want all the NFs to be at the same version before upgrading cnDBTier, does this impact the upgrade strategy?

It isn't suggested upgrading a layer of same NFs across all sites, before moving to the next. There's a higher risk of rollback scenarios of all the sites, which can impact the service. The recommended upgrade sequence is provided in the Overview section.

For Example: In three-site georedundancy, if NRF, SCP, and cnDBTier are deployed, upgrade cnDBTier and the NFs in the specific site, instead of first upgrading cnDBTier across all the sites and then the NFs.

What should I do if I see an error while upgrading?

If you see any upgrade or rollback error, see NF-specific Troubleshooting Guide. In case the error persists, collect the log and report it to My Oracle Support.

How do I verify if the upgrade is successful?

Perform verification tasks provided in NF-specific Installation, Upgrade, and Fault Recovery Guide. For more information about the upgrade, see the "Upgrade Tasks" section in the NF-specific Installation, Upgrade, and Fault Recovery Guide.

When I have a non-Oracle CNE, how do I check if the NFs are compatible or not?

Perform compatibility check between the NFs and non-Oracle CNE. For more information about the procedure, see Compatibility Check of Target NF Component with Installed Non-Oracle cloud native environment.

A Frequently Asked Questions (FAQs)