Upgrade tricks
Hello, my name's Bob (hello bob). It's been over a year since my last upgrade...
Moved from Luminis 4.2.0.67 to 4.2.2.68. As always, learned some new things that may help someone.
* Do not mess with $CP_HOME/install.
At some point I went looking for disc space and purged files with names like backup-luminis*.zip. Not a good idea. These files are necessary for backing out a patch.
(You must back out to 4.2.0.0 before you can move up , you've got to get down to get up).
These backups (named $CP_HOME/install/backup-luminis-4.x.x.x.zip) contain certain files that are specific to the version it is replacing. So patchcp -u luminis-4.2.0.67
uses backup-luminis-4.2.0.67.zip to restore certain files specific to 4.2.0.0.
Fortunately, our backup team retrieved these files from tape and I got to try again.
* Keep your log files in check.
Once I got the backup files restored and unpatched to 4.2.0.0, the upgrade failed with the error:
File "/usr/local/lib/python2.4/zipfile.py", line 503, in close OverflowError: long int too large to convert to int ERROR [E000] An unexpected error has occurred.
This is a known defect: 1-4I29JV
Solution is to purge some log files: both from $CP_HOME/logs and .../tomcat-cp.logs
The problem is in creating the above mentioned backup file. The max file size of this backup is reported to be 2Gig (although mine failed at 4Gig).
Bob.
Same Boat
Hi Bob,
Mike here from Eastern Washington University. Hey, we are about to do the same upgrade from 4.2.0.67 to 4.2.2.68 on a parallel deployment (both test & prod) on Windows 2003 (...yea...I know). What are you running on?
Can I do the upgrade straight from 4.2.0.67 to 4.2.2.68 directly or do I need to do incremental upgrades?
Glad I ran across your post. This is just what I was looking for.
MLC
Go down then up
It will be a three step process.
1) unpatch to 4.2.0.0 (this is where $CP_ROOT/install files are crucial)
2) run the patch command (LP-4.2.2.0-{servertype}) to patch to 4.2.2.0 (this will happen in two stages: 4.2.1, then 4.2.2 and create backups for each)
3) patch to 4.2.2.68
I would recommend at least clearing out the tomcat-cp/logs directory. Also, check that there's no junk in $CP_ROOT/logs. This will keep the unpatch backups to a minimum and avoid the patch failure.
Bob.
Thanks Bob
Thanks Bob, this will be very helpful as we delve into it.
Mike