We continue to struggle with obtaining downtime - more so in a sap environment where some post-processing steps need to be done after database version upgrade. 

Currently, only rolling fixpack upgrades are allowed with db2 hadr - will it be possible to complete database version upgrade with minimal downtime using core db2 functionality in this forthcoming new release? 

Thank you.

There is work in progress to reduce downtime.

The intend is that DB upgrade becomes recoverable (consists of fully logged operations only). As a consequence,

- no offline backup is required before upgrade, a online backup or snapshot backup is enough.

- DB upgrade gets performed on HADR standby as well by log record shipping (no need to re-establish HADR standby after DB upgrade)

This should minimize the required downtime dramatically from hours to less than a hour.

In downtime problematic setups, you for sure should still perform a test upgrade on a database clone first.

To my knowledge you need V10.5 FP7 as basis for this minimized downtime upgrade.

We continue to struggle with obtaining downtime - more so in a sap environment where some post-processing steps need to be done after database version upgrade. 

Currently, only rolling fixpack upgrades are allowed with db2 hadr - will it be possible to complete database version upgrade with minimal downtime using core db2 functionality in this forthcoming new release? 

Thank you.

There is work in progress to reduce downtime.

The intend is that DB upgrade becomes recoverable (consists of fully logged operations only). As a consequence,

- no offline backup is required before upgrade, a online backup or snapshot backup is enough.

- DB upgrade gets performed on HADR standby as well by log record shipping (no need to re-establish HADR standby after DB upgrade)

This should minimize the required downtime dramatically from hours to less than a hour.

In downtime problematic setups, you for sure should still perform a test upgrade on a database clone first.

To my knowledge you need V10.5 FP7 as basis for this minimized downtime upgrade.

We continue to struggle with obtaining downtime - more so in a sap environment where some post-processing steps need to be done after database version upgrade. 

Currently, only rolling fixpack upgrades are allowed with db2 hadr - will it be possible to complete database version upgrade with minimal downtime using core db2 functionality in this forthcoming new release? 

Thank you.

There is work in progress to reduce downtime.

The intend is that DB upgrade becomes recoverable (consists of fully logged operations only). As a consequence,

- no offline backup is required before upgrade, a online backup or snapshot backup is enough.

- DB upgrade gets performed on HADR standby as well by log record shipping (no need to re-establish HADR standby after DB upgrade)

This should minimize the required downtime dramatically from hours to less than a hour.

In downtime problematic setups, you for sure should still perform a test upgrade on a database clone first.

To my knowledge you need V10.5 FP7 as basis for this minimized downtime upgrade.

We continue to struggle with obtaining downtime - more so in a sap environment where some post-processing steps need to be done after database version upgrade. 

Currently, only rolling fixpack upgrades are allowed with db2 hadr - will it be possible to complete database version upgrade with minimal downtime using core db2 functionality in this forthcoming new release? 

Thank you.

There is work in progress to reduce downtime.

The intend is that DB upgrade becomes recoverable (consists of fully logged operations only). As a consequence,

- no offline backup is required before upgrade, a online backup or snapshot backup is enough.

- DB upgrade gets performed on HADR standby as well by log record shipping (no need to re-establish HADR standby after DB upgrade)

This should minimize the required downtime dramatically from hours to less than a hour.

In downtime problematic setups, you for sure should still perform a test upgrade on a database clone first.

To my knowledge you need V10.5 FP7 as basis for this minimized downtime upgrade.

We continue to struggle with obtaining downtime - more so in a sap environment where some post-processing steps need to be done after database version upgrade. 

Currently, only rolling fixpack upgrades are allowed with db2 hadr - will it be possible to complete database version upgrade with minimal downtime using core db2 functionality in this forthcoming new release? 

Thank you.

There is work in progress to reduce downtime.

The intend is that DB upgrade becomes recoverable (consists of fully logged operations only). As a consequence,

- no offline backup is required before upgrade, a online backup or snapshot backup is enough.

- DB upgrade gets performed on HADR standby as well by log record shipping (no need to re-establish HADR standby after DB upgrade)

This should minimize the required downtime dramatically from hours to less than a hour.

In downtime problematic setups, you for sure should still perform a test upgrade on a database clone first.

To my knowledge you need V10.5 FP7 as basis for this minimized downtime upgrade.

We continue to struggle with obtaining downtime - more so in a sap environment where some post-processing steps need to be done after database version upgrade. 

Currently, only rolling fixpack upgrades are allowed with db2 hadr - will it be possible to complete database version upgrade with minimal downtime using core db2 functionality in this forthcoming new release? 

Thank you.