Forums

by Rich >> Wed, 20 Aug 2008 8:24:38 GMT

Hi,

We are looking at upgrading our Jade versions from 6.1.07 to 6.2.15 in the near future. I have read the documentation for the upgrade and all seems straight forward, however, it doesn't mention time.

Does anybody know roughly how long this process will take? Also, we are running 12 databases, do we need to upgrade them all one by one or if we install 6.2 will it just upgrade all Jade components? Does anybody have any other tips or warnings for our upgrade?

Also, if we upgraded to 6.2, would it still be possible to restore from a backup taking prior to the upgrade? Would this work using the same version of jdbutil as before?

Sorry for all the questions, any help would be appreciated.

Rich

by Allistar >> Wed, 20 Aug 2008 10:10:56 GMT

Hi,

We are looking at upgrading our Jade versions from 6.1.07 to 6.2.15 in the near future. I have read the documentation for the upgrade and all seems straight forward, however, it doesn't mention time.

The upgrade is, as far as I know, not dependant on actual database size. (Actually, there is a verification step that is dependant on user schema size, but that doesn't take that long). I would estimate half an hour for each database. Of course - this depends on your hardware.

Does anybody know roughly how long this process will take? Also, we are running 12 databases, do we need to upgrade them all one by one or if we install 6.2 will it just upgrade all Jade components? Does anybody have any other tips or warnings for our upgrade?

You'll need to upgrade them all one by one, although I see no reason why you couldn't do them in parallel. I assume that each of those 12 databases has their own unique bin directory - if not you need to make sure that is the case (and that's a sensible setup anyway).

Also, if we upgraded to 6.2, would it still be possible to restore from a backup taking prior to the upgrade? Would this work using the same version of jdbutil as before?

To restore to a system running 6.1.07 you'll need to use 6.1.07 binaries.

Sorry for all the questions, any help would be appreciated.

If the platform you host these databases on is Linux, you'll need to upgrade the OS from either SLES9 -> SLES10, or RHEL3 -> RHEL4 during the upgrade process.
--
A.

by Murray Symon >> Wed, 20 Aug 2008 10:49:32 GMT

The Jade requirement for RedHat is RHEL5 (or are you implying that 6.2 will run OK on RHEL4?). RHEL4 seems to have been skipped, maybe it's because of the timing of the RHEL5 release? It's quite a big jump from RH3 to RH5. Also, it's annoying that you have to do both the O/S and Jade together, they didn't allow for any overlap in their specification. It would have been nice (IMHO) if 6.1 ran on RHEL3 & 4 and 6.2 ran on RHEL4 & 5 to allow for a step by step approach to upgrading.

by Allistar >> Wed, 20 Aug 2008 22:48:56 GMT

You are right - my direct experience is with SLES9 -> SLES10, and I made the assumption in my post that the RH was a single version number change too.

It is a pain to have to upgrade the OS to upgrade Jade. I think it's all to do with the version of openssl.
--
A.

by Patwos >> Thu, 21 Aug 2008 21:45:45 GMT

"The upgrade is, as far as I know, not dependant on actual database size. (Actually, there is a verification step that is dependant on user schema size, but that doesn't take that long). I would estimate half an hour for each database. Of course - this depends on your hardware."

Looking at the details of hot fix 54 for Jade 6.2.14 in PARSYS you could have a long upgrade if you have lots of data in your _userdef.dat file.