Hi Jens,
I'm pretty sure that the "don't reboot" requirement is specific to using the internal database and is related to how the internal database is updated during the upgrade process.
If you're using an external database the the schema changes have to be made manually using the scripts provided on the appliance. The release notes cover this.
I must caveat all this by saying I have not done an update with an external database. If it was me I'd want to test any upgrade process before doing it a production system (or have a verified backup).
Cheers... Jon.
------------------------------
Jon Harry
Consulting IT Security Specialist
IBM
------------------------------
Original Message:
Sent: 07-10-2018 10:04
From: Jens Petersen
Subject: 9.0.5 Upgrade and Clustering
Hi John,
is this also true for external DB? Shouldn't make a difference as you need to update the DB separately anyway.
Thanks,
Jens
------------------------------
Jens Petersen
Original Message:
Sent: 06-29-2018 03:22
From: Jon Harry
Subject: 9.0.5 Upgrade and Clustering
Hi Peter,
I asked our internal support folks. They confirm that you don't need to break the cluster to update to 9.0.5.0.
They did say (as written in release notes):
Upgrade the Primary Master and DO NOT REBOOT IT BEFORE UPGRADE THE SECONDARY IF USING THE INTERNAL DB.
Cheers... Jon.
------------------------------
Jon Harry
Consulting IT Security Specialist
IBM
Original Message:
Sent: 06-28-2018 00:51
From: Peter Lambrechtsen
Subject: 9.0.5 Upgrade and Clustering
Reading through the release notes for 9.0.5: https://www.ibm.com/support/knowledgecenter/SSPREK_9.0.5/com.ibm.isam.doc/productoverview/task/tsk_upgrading.html
One thing that seems to have changed is the requirement remove all cluster nodes from the cluster whereas previously you always had to.
Is this an oversight in the documentation or is it ok (safe?) to upgrade the Primary node, let it reboot, then upgrade the secondary without any configuration changes.
Looking to run through this in a lab but wanted confirmation this is an intentional change.
------------------------------
Peter Lambrechtsen
------------------------------