Results 1 to 5 of 5

Thread: TR from 9.2.1.1 to 9.2.3.x. - 32-bit

  1. #1
    Member
    Join Date
    May 2001
    Location
    Toronto, Canada
    Posts
    135

    TR from 9.2.1.1 to 9.2.3.x. - 32-bit

    Hello List.

    Our BP is planning our TR from 9.2.1.1 to 9.2.3.x. Currently we are;

    Application Release: 9.2
    Tools Release: 9.2.1.1
    Application (Enterprise) Servers - 2012 standard x64 (64-bit)
    Web Servers - 2012 standard R2 Datacenter x64 (64-bit)
    Database servers - 2012 standard R2 Datacenter x64 (64-bit) / SQL server 2014
    WebLogic Server Administration Console 12c (12.2.1.0.0)

    We’ve been informed below will take 278 hours to apply the tools release to;

    1 deployment server
    1 server manager server
    1 DV enterprise server, 1 DV web server
    2 PY enterprise servers, 1 PY web server
    5 Production enterprise servers, 4 PD web servers
    2 BSSV servers
    2 OVR/BI DAD servers
    16 fat clients

    As well, we have been informed it’s mandatory we provision new VM’s for every server that has WLS installed as the required WLS upgrade from 12.2.1.0.0 to WLS 12.2.1.3 can’t be done ‘in place’ and with multi foundation we’ll require a code freeze to production until 9.2.3.x is applied in Production.

    Might someone who’s done this upgrade be able to comment? Somewhat concerned about having to provision 11 new servers for the WLS upgrade and more importantly a 278 hour code freeze to Production.

    Thanks in advance for any assistance,

    Michael

  2. #2
    I would think based on the fact your currently on Windows 2012, the new server provisioning may also be due to getting you on the latest version of Windows as well, which would explain a lot of the time / new server requirement as well. In place with no application upgrade is pretty straight forward. Though not sure why would you have to freeze code if you're not doing an application upgrade.

  3. #3
    Member craig_welton's Avatar
    Join Date
    Oct 2000
    Location
    Litchfield, CT
    Posts
    977
    Maybe the code freeze because of the ESUs needed for 64 bit safe BSFNs?
    Craig Welton
    PatWel Group Inc.
    http://www.patwel.com
    Home of the FREE JDE Object Browser, JDETrace and NERDup Tools

    E1 9.0 8.98.4.2 Wintel SQL 2008
    E1 9.2 9.2.1.4 iSeries

  4. #4
    Member
    Join Date
    May 2001
    Location
    Toronto, Canada
    Posts
    135
    TFZ, Craig, thank you for responding.

    As an FYI, were implementing 32-bit, not 64 and we will not be upgrading any software other than our version of WLS since our current version doesn’t meet the MTR. It’s been many years since I’ve done a TR upgrade but the 278 hours seemed a bit long and the 7 week code freeze caught us off guard not to mention having to provision 11 new VMS solely for the WLS software upgrade as opposed to doing it in place.

    Thanks again for responding.

  5. #5
    Member
    Join Date
    Jun 2001
    Location
    Colorful Colorado
    Posts
    469
    Even if you're staying 32 bit, there is a large set of ESUs required before going to 9.2.3 that make it possible for you to even consider going 64 bit in the future, and 9.2.3 flat out requires them as a pre-requisite as the tools foundation, even in 32 bit, probably had changes that require some BSFN changes.
    --john

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.