E9.2 Question about 64-bit upgrade and TR 9.2.6 upgrade

[bluelake]

Hi,

We are on 9.2.4.x 32-bit. Is it possible we upgrade 32 to 64 bit and TR 9.2.6 at the same time? For example, we setup multi-foundation on deployment server. One foundation is 9.2.4.x 32 bit, a new foundation is 9.2.6.x 64-bit.

Thanks
Bluelake

 

[TFZ]

Sure, it's possible, but I would do the latest 9.2.5.x on 32bit to get as close to 9.2.6.1/2 as possible so that your devs get used to the simplified dev client.

 

[glen7x]

it is not just multifoundation. You also need to consider the application of ASU's. UN5 / UN6 is a pre requisite for a move to 64bit processing. So you also need to consider the retrofit effort to customizations. This is however, you have not applied the ASU already.

 

[bluelake]

it is not just multifoundation. You also need to consider the application of ASU's. UN5 / UN6 is a pre requisite for a move to 64bit processing. So you also need to consider the retrofit effort to customizations. This is however, you have not applied the ASU already.

Understand the effort for retrofit. But in additional to Planner ESU and App enhancement roll up ESU, are there any ASU required to apply for 64-bit upgrade? Oracle doc does not mention it.

 

[TFZ]

There used to be a whole section of ESU's devoted to 64 bit uplift of BSFN's. In change assistant, the topic is still out there. These over the years have made it in to UN5/6. The same ESU's can safely be applied to both bitnesses.

 

[bluelake]

There used to be a whole section of ESU's devoted to 64 bit uplift of BSFN's. In change assistant, the topic is still out there. These over the years have made it in to UN5/6. The same ESU's can safely be applied to both bitnesses.

Yes. A step in Oracle's doc for 64-bit upgrade is to apply those ESU's to allow standard BSFNs support both 32-bit and 64-bit.

 

[ice_cube210]

Understand the effort for retrofit. But in additional to Planner ESU and App enhancement roll up ESU, are there any ASU required to apply for 64-bit upgrade? Oracle doc does not mention it.

There are specific ESUs for 64bit to deliver changes to standard C Business Functions and related objects. Many times these ESUs have dependencies on other Baseline ESUs which in turn have dependencies etc. So if you haven't taken any ESUs in a long time you will suddenly find yourself having to apply 100+ ESUs for 64 bit which then has a bigger impact on retrofitting and testing efforts. UN5/UN6 aren't specifically a prereq but taking something like UN6 will include all the required 64-bit ESUs.

 

[bluelake]

There are specific ESUs for 64bit to deliver changes to standard C Business Functions and related objects. Many times these ESUs have dependencies on other Baseline ESUs which in turn have dependencies etc. So if you haven't taken any ESUs in a long time you will suddenly find yourself having to apply 100+ ESUs for 64 bit which then has a bigger impact on retrofitting and testing efforts. UN5/UN6 aren't specifically a prereq but taking something like UN6 will include all the required 64-bit ESUs.

We are considering upgrade UN6 as well.

 

[bluelake]

There are specific ESUs for 64bit to deliver changes to standard C Business Functions and related objects. Many times these ESUs have dependencies on other Baseline ESUs which in turn have dependencies etc. So if you haven't taken any ESUs in a long time you will suddenly find yourself having to apply 100+ ESUs for 64 bit which then has a bigger impact on retrofitting and testing efforts. UN5/UN6 aren't specifically a prereq but taking something like UN6 will include all the required 64-bit ESUs.

Here is my question about these specific ESU for 64-bit. Do we need to apply them to DV before we upgrade deployment server and DV to 9.2.6? Can we apply them after we upgrade deployment server and DV path code to 9.2.6?

 

[tblancett]

We recently went to 64 bit over the summer. At that time our platform was on 9.2.4.x 32 bit. The first thing we did was install the all of the ESU's from the "Preparing for 64 bit" in change assistant (we did this prior to changing any of the tools components to 64 bit). As a side note, we also took UN5 during this time since we knew we were going to be performing/testing a lot of retrofits already. Once we had the retrofits tested/approved/promoted to production, only then did we begin the 64 bit upgrade process. Even though 9.2.5 was available at the time, we elected to upgrade to 9.2.4.x 64 bit, for no other reason than to minimize the variables for testing (in essence we were performing only a bitness change on the tools release, as opposed to performing a bitness change AND a new tools release).

To answer your last question specifically, yes, you will want to apply the prerequisite 64 bit ESU's before you upgrade your deployment server to the 64 bit tools release. I would also recommend trying to upgrade to the 64bit tools release within your existing tools release (9.2.4) before you try to throw 9.2.5 or 9.2.6 in the mix, just to minimize adding too many variables to an already sizeable project.

-TB

 

[MFreitag]

Here is my question about these specific ESU for 64-bit. Do we need to apply them to DV before we upgrade deployment server and DV to 9.2.6? Can we apply them after we upgrade deployment server and DV path code to 9.2.6?

For the Deployment Server you def. need the Planner ESU as per the guide and you will need the "Preparing for 64-bit (BSFNs)" once you want to build your first 64-bit package

 

[bluelake]

New question: our deployment server is running on Win2012. But target tools release 9.2.6.x is certificated with Win2019. Can we upgrade deployment server to TR9.2.6.X on Win 2012?

 

[BOster]

Win2012 is getting close to EOL (Oct 2023) so you may want to keep that in mind. We are upgrading our WebSphere (non-JDE) servers from 8.5 to 9.x mainly because the server OS is Win2012.

 

[TFZ]

It certainly seems from your questions that now would be the time to do it right and put in a 2019 server for Dep, there's a pretty thorough "how to swap out" guide on Oracle support. I'm not saying 2012 won't work, but you may as well future proof your install a little while you have the opportunity and not worry about the whole "no longer works / not certified" possibility.

 

[bluelake]

It certainly seems from your questions that now would be the time to do it right and put in a 2019 server for Dep, there's a pretty thorough "how to swap out" guide on Oracle support. I'm not saying 2012 won't work, but you may as well future proof your install a little while you have the opportunity and not worry about the whole "no longer works / not certified" possibility.

Understand. But I do have a question that the current 9.2.4.x is not certificated with Win 2019. We need multi-foundation on deployment server during the upgrade. Will it be an issue if deployment server is upgraded to Win 2019, while 9.2.4.x foundation is still in use? I wonder if we can keep Win 2012 until we finish TR9.2.6.x upgrade. Then upgrade deployment server to Win 2019.

 

[TFZ]

Multi foundation on the deployment server is not quite like that You're not swapping back and forth between system on the fly, your main foundation is 9.2.6.x, and you have an alt foundation that you select for pkg builds only that's 9.2.4.x. So you wouldn't need to worry about 9.2.4.x certification as your Deployment Server would be tools 9.2.6.x.

 

[MFreitag]

Understand. But I do have a question that the current 9.2.4.x is not certificated with Win 2019. We need multi-foundation on deployment server during the upgrade. Will it be an issue if deployment server is upgraded to Win 2019, while 9.2.4.x foundation is still in use? I wonder if we can keep Win 2012 until we finish TR9.2.6.x upgrade. Then upgrade deployment server to Win 2019.

Concerning the deployment server and development clients my experience is that they will basically run on any Windows OS with any tools release as Oracle changes veeeery little to those kind of things. So as TFZ says, since you will be using 9.2.6.x mainly you should be fine and just use 9.2.4.x while you still need it and ignore the certification for that time span.
One thing to look out for is the E1Local though, that might have some more harsh dependencies where it might check for the OS etc.

 

[bluelake]

Concerning the deployment server and development clients my experience is that they will basically run on any Windows OS with any tools release as Oracle changes veeeery little to those kind of things. So as TFZ says, since you will be using 9.2.6.x mainly you should be fine and just use 9.2.4.x while you still need it and ignore the certification for that time span.
One thing to look out for is the E1Local though, that might have some more harsh dependencies where it might check for the OS etc.

Thank you for your comment. Since OS is not an issue to run different Tools release, this will give us more options to consider for this upgrade. It is true that E1Local causes many problems in client installation if previous client is not fully removed.

 

[bluelake]

One more thing: Change Assistant has 32-bit version and 64-bit version. Is it required to upgrade Change Assistant to 64-bit first before we install a number of 64-bit ESUs using Change Assistant?

 

[TFZ]

Change Assistant should match the bitness of your deployment server, so its not needed until your dep server is 64 bit.