Hi all,
I’m working on an upgrade of 6.1b (on W2K SP4, Apache/Tomcat, SQL Server repository) to 6.5.1. Does anyone out there have any tips/pitfalls/experiences they can share? Was it easy? What were the biggest pain areas? How did the ZABO upgrades and WebI Java applet upgrades go? Did you do a fresh uninstall/reinstall of the server, or was it possible to run it as an upgrade?
Thanks and Happy New Year!
Chris
cjweis (BOB member since 2003-10-02)
We did a clean install on the servers. We saved our storage directory and then put it back after the install. It’s much faster to do it from scratch and do a typical configuration than it is to do an upgrade.
ZABO upgrades worked perfectly. We even found that you could upgrade a full-client user via ZABO. The process detected that they had Designer and/or Supervisor and upgraded those as well.
Applets were not problem, but JVM can sometimes be an issue. 6.5.1 requires Sun’s JDK. Some users already had one. In a few cases, I just had to deinstall their JDK and let WebI install what it wanted. Once it worked it could be upgraded just fine.
Do some research into Connection Server. It’s a pain. It keeps connections to you database open. I adjusted both parameters on the servers so that connections would die instantly. It has helped, but not completely solved the problem. We can talk about that one offline
We’ve also had a few problems with WebI applets not being able to connect. We think this is due to our configuration, but we get a WIJ0002 error more often than we would like.
Steve Krandel 
(BOB member since 2002-06-25)
FYI to all – Here’s a bunch of threads I was able to find that relate to 6.5.1 upgrades:
Supervisor 6.5.1 Gotcha
License Key Issues
BO 6.5.1 : Supervisor Web configuration problem
Webi 6.5.1 issue with “send to user” functionality
Repository table upgrade from 61b to 6.5
6.5.1 - Publisher install problems
Error when configuring ORB 6.5 (Error : CFT 06203)
Does Supervisor or Designer work in 3-tier mode in 6.5.1?
6.5 released
6.5.1 Install Errors Saying Install Wizard Interrupted
256 Character Limit in 6.5.1
Regards,
Chris
cjweis (BOB member since 2003-10-02)
Awesome, thanks so much Steve! 
One more question: Has anyone had any experience with Auditor data during a 6.1b-to-6.5.1 upgrade? Was there any corruption of data? (In 5.x upgrades, Auditor was a pain in the neck because the last primary key was a value stored in the Windows registry).
Regards,
Chris
cjweis (BOB member since 2003-10-02)
When we upgraded Auditor from 5 to 6, we had to start over and lost all of our audit data.
With 6.5, we haven’t done anything. Auditor reports and universes still seem to work. We haven’t even looked at the 6.5.1 versions of the reports or universes to see if we needed to make any changes.
Steve Krandel (BOB member since 2002-06-25)
I guess they added logic to get the highest auditor key value from the repository (the way 5.x should have been) (?) Great! Thx
cjweis (BOB member since 2003-10-02)