Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
Upgrade to 9.0.1?
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jessica
Past 24 Hours:
2
Prev. 24 Hours:
0
Overall:
5164
People Online:
Visitors:
252
Members:
0
Total:
252
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Systems Administration
Upgrade to 9.0.1?
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
wintergreen
Veteran Member
Posts: 93
4/22/2010 7:22 PM
we are currently on 9.0.0.4 on windows 32bit platform. I don't know if we should go to the 9.0.0.8 or directly to 9.0.1? Any suggestion?
John Henley
Senior Member
Posts: 3348
4/22/2010 8:45 PM
901 has diff dependencies than 900. =
wintergreen
Veteran Member
Posts: 93
4/22/2010 8:57 PM
John, what do you mean 'diff dependencies'? Sorry that I have no clue about 901. Thank you!
John Henley
Senior Member
Posts: 3348
4/23/2010 12:45 AM
Assuming you are running WAS 6.0, you will need to upgrade to 6.1/7.0 as well as JDK and Bouncy Castle. =
mark.cook
Veteran Member
Posts: 444
4/23/2010 1:17 PM
In addition to the technical changes as John pointed out, you should also concider the impact to your users. We knew that we would not be able to schedule testing for the MSP/ESP release and then follow up with another upgrade in the near future after that, so we made the jump as much to take advantage of 9.01 technology as to eliminate testing /upgrade cycles for our users.
Jimmy Chiu
Veteran Member
Posts: 641
4/23/2010 1:30 PM
If you have virtualization platform in place, I would open this up as another migration project.
Deploy a new 64 bit 9.0.1.5 and migrate at your own pace. You can take advantage of websphere 7 64 bit and the added support for SQL 2008 if you are running it. SQL 2008's real time data compression is great feature and serve as an alternative for data archiving. On my initial pass, my database shrunk from 370GB to below 190GB. (at around 5gb data growth rate per year, i just bought myself another 20 years worth of time). My read based tranasction performance actually gone up, write based transactions performance went down by slightly. You can target specific table/index for real time compression. Enabling it for most read access table is the best bet.
The best of all however is what vitualzation offers. Ability to snapshot VM and failover VM to avoid downtime results from physical server failure. Taking server image backup becomes a matter of seconds instead of minutes. Upgrading hardware and assigning additional hardware resources to the VM running lawson becomes painless.
Going 64 bit also resolves memory bottleneck issue.
Note: Do not use the new LUU (lawson unix utility), stay with MKS. Some lawson delivered upgrade programs do not work with LUU. (TA>LP upgrade program for example or any program that invokes sh/ksh.)
Check with the compatibility matrix also to see some of the application minimal requirement. 9.0.1.5 ENV requires minimal 9.0.1.0007 RSS version etc.
Brian Allen
Veteran Member
Posts: 104
4/23/2010 1:47 PM
Jimmy, Can you please elaborate on the memory bottleneck issue. We occasionally get an out of memory error on our JVM on test (WAS6.1, env 9.0.0.8). I've since increased the JVM max heap to 2048 at the Lawson Sizing groups recommendation for our case. I'd like to more about the issue you're referring to. We're running under AIX, so this may or may not apply. Thanks.
Jimmy Chiu
Veteran Member
Posts: 641
4/23/2010 2:14 PM
32 bit websphere has memory bottleneck limited by the OS. 2GB is the maximum heap size you can allocate to the application server regardless of what your physical server has in memory.
With 64 bit websphere, that limit has been lifted. Thus, whatever your physical server has, is what you can allocate minus some overhead for the OS/application. IE: on a 16GB server, you can allocated a whooping 10GB to the JVM heap size if that's what your application need.
On my 64 bit developer server, I run 4GB min/max on my websphere 7 heap size.
Brian Allen
Veteran Member
Posts: 104
4/23/2010 2:31 PM
That's great news - thanks for the information!
wintergreen
Veteran Member
Posts: 93
4/23/2010 8:01 PM
Thank you all for the input. Since the windows 2003 will be decommissioned in 2012, I think a new 64bit windows 2008 is the way to go. Maybe SQL 2008 is needed too.
John Henley
Senior Member
Posts: 3348
4/27/2010 6:22 PM
http://blog.lawsonguru.co...upgrade-crazy-train/
You are not authorized to post a reply.