cancel
Showing results for 
Search instead for 
Did you mean: 

HANA Cloud version missing to upgrade and maintain sync between landscape

sagarsv
Explorer
0 Kudos

Hello,

I have stuck in a strange situation, let me explain I hope if some of you have answer

On October 9th (today) : Morning I have updated our development instance to latest version of HANA cloud which is 2023.28.7(QRC 3/2023)

On same day(October 9th (today)) we planned to upgrade our pre-prod instance as well in the afternoon , now version 023.28.7(QRC 3/2023) is no more available but a new version is available 2023.28.8(QRC 3/2023)

This is very confusing for me on how to plan upgrades to be in sync , that I have took downtime for development instance upgrade with business , now I am stuck with 2023.28.7(QRC 3/2023) in DEV and no similar version available for pre-prod 😞

I also checked using BTP CLI to find if version is available using following command: but no luck 2023.28.7(QRC 3/2023) is not available
"btp get services/instance --name <instance name> --subaccount <subaccount ID> --show-parameters "

regards

sagar

Accepted Solutions (0)

Answers (1)

Answers (1)

AlexPJ
Explorer
0 Kudos

Hello Sagar,

this is "works as designed". You can only install/upgrade to/patch to the latest available (released) SAP HANA Cloud patch.
Though you can chose whether you want to upgrade (apply a newer QRC) or apply a patch (stay within a QRC) you cannot chose the patch level. Within a QRC there is no choice, only the latest patch is available.
Therefore it may happen that the patch levels differ within a landscape if you do not upgrade/patch your instances at the same time. We decided to apply new releases/patches close together with at maximum of one day delay between systems. In the worst case, if SAP releases a new patch to customers in between (as in your case), we may end up with small differences in the patch levels.
The only way out is to start over with your development system and apply the latest patch on the first system(s) again. We rather decided to ignore small differences in the patch levels in such cases (which we have seen very rarely in the last two years, fortunately).

Best regards,
Alexander