This year's upgrade process will be in 6 parts.

1. Setup the read-only mode copy of Eau Claire's Voyager (outage early in the morning)
2. Patch Oracle to 10.0.2.4 and apply CPU
3. Upgrade Voyager to 7.2.0
4. Apply Voyager Service Pack to get to 7.2.1
5. Do all split server configuration work
6. Eau Claire library tests and customizes as needed, then switch back production (short outage).

Read Only Mode (starting at 2am - completed 5:41am)
- Take down production (completed 2:55am)
- Comment out cron jobs (completed 2:55am)
- Configure UPG zones on widener (completed 3:25am)
- Copy zones from production to UPG zones on widener (completed 4:00am)
- Copy backups to UPG zones (completed 4:00am)
- Bring up UPG zones as production (completed 4:15am)
- Verify all is well (completed 4:15am)
- Set Voyager read-only mode (completed 4:15am)
- set Oracle tablespace to read-only (completed 4:15am)
- Modify production zones to use UPG ip addresses and check firewall rules, add temporary disk space (completed)
- Oracle listener configuration (completed)
-- /oracle/app/oracle/product/10.2.0/db_1/network/admin/listener.ora backup and change (completed)
- /etc/inet/hosts files in each zone (completed)
- Make a backup copy of production web zone /m1/voyager/xxxdb to be referred to for customizations later (completed)

Patch Oracle to 10.0.2.4 and apply CPU (starting at 5:45am - completed 10:15am)
bw - 6:20am - taking an hour or two break while the Oracle update installer runs - back at 9am
- Copy oracle patch files to /m1/incoming/oracle (completed 5:50am)
- Uncompress (completed)
- Pre-installation steps (completed 6am)
- Install 10.2.0.4 update (completed 6:15am)
- Run upgrade script and recompile script (completed 10:15am)
- Install Oracle CPU (not doing at this time)

Install Voyager 7.2.0 upgrade (completed - starting at 10:15am, completed at 7:45pm)
- Copy the voyager upgrade files to /m1/incoming/v720 (completed 10:40am)
- Run 7.2.0 upgrade (in progress)
- change /m1/voyager/xxxdb mountpoint so it's not a mountpoint for the upgrade.pl run (completed 11:05am)
- install new jdk from SHARED tarball in both web and db zones (complete)
- verify /m1/voyager/xxxdb/ini/voyager.env has JAVA_HOME set correctly (complete)
- move /m1/shared/apache2 to /m1/shared/httpd/2.2.6 and make a symlink from /m1/shared/httpd/2.2.6 to /m1/shared/apache2 (complete)
- Files upgrade.pl (complete - next steps in progress - on step 4.1.14 at 1:10pm)
- Verify /m1/voyager/xxxdb/tomcat/vxws/conf/server.xml entries -
-- <Valve className="org.apache.catalina.valves.RemoteAddrValve" allow="128.104.22."/> --> (completed)
-- url="jdbc:oracle:thin:@HOSTNAME:PORT:VGER" (completed)
- RE-verify /m1/voyager/xxxdb/ini/voyager.env has JAVA_HOME set correctly (completed)
-bw longer break than expected here, working on it again
- Oracle schema update (completed - 6:20pm)
- (Run regen) - not this year (not this year)
- Post setup steps (in progress - 6:20pm)
-- UB (completed)
-- Media scheduler (completed)
-- Authorities Keyword stuff (completed)
-- Run through full Authority Headings piece, including ctxsys recreation and running ./create_single_index.ksh $USERPASS (will do if needed after testing)
-- recreate readonly user (completed)
- Service re-setup - make sure the /m1/voyager/xxxdb directories are only the valid ones or the voyager service setup will do funny things with the extras (completed)

Install Voyager 7.2.1 service pack (completed - 8:50pm)
- Install service pack on DB server (completed 8:02pm)
- shut down zones and change /m1/voyager/xxxdb mountpoint so it is a mountpoint again and rsync the new xxxdb directory over to it (completed)

Post Service pack server splits (completed 9:40pm)
- Split web server - don't use maketomcatwebserver.ksh method (completed)
-- verify upgraded java jdk to 1.6 version (completed)
-- cleaned up older bin/lib/utility/sbin directories (completed)
-- built tarball with -
--- sudo tar cvf webserver.tar uwecirrdb/etc uwecirrdb/webvoyage uwecirrdb/ini uwecirrdb/tomcat/vwebv clairedb/etc clairedb/webvoyage clairedb/ini clairedb/tomcat/vwebv lib/2007.2.1 bin/2007.2.1/*exe bin/2007.2.1/*cgi (completed)
-- sudo vi *db/etc/webvoyage/voyager.ini (completed)
-- under xxxdb/tomcat/vwebv find the WEB-INF/web.xml and verify XServiceHost is pointing to the right place (completed)
-- start things up (completed)
-- Had to modify the server.xml for vxws to setup IP access permissions right for traindb and uwecirrdb (completed)
-- remember to disable/enable the correct Pwebvoyage service

- Split z3950 server (going to split off after all upgrades are complete - have to setup new pieces on z3950 instance)
-- with prod switch over, will need to modify for prod IPs and stop/start voyager on z3950
--- Build with their tar command - leave out voyager and oracle libraries - scp them over afterwards
--- as voyager ; cd /m1/voyager/lib/2007.2.1 (already done with first instance setup - Stout)
--- scp user@xxxdbupg.wisconsin.edu:/oracle/app/oracle/product/10.2.0/db_1/lib32/libnnz10.so .
--- scp user@xxxdbupg.wisconsin.edu:/oracle/app/oracle/product/10.2.0/db_1/lib32/libclntsh.so.10.1
--- scp user@xxxdbupg.wisconsin.edu:/oracle/app/oracle/product/10.2.0/db_1/lib32/libclntsh.so.9.0 .
--- modify /m1/voyager/stoutdb/etc/ascopac/opac.ini from localhost to xxxdbupg
--- /m1/voyager/stoutdb/ini/z3950svr.ini from localhost to xxxdbupg

- Split staff client server (not for Eau Claire, at least this year)
-- build zone/create users/groups/home directories, etc.

Customize upgraded Webvoyage and test staff clients (in progress)
- Use the eaulibupg.wisconsin.edu address for customizations
- Copy of pre-upgrade xxxdb directory should be /m1/v710-xxx
- Point upgraded staff client at eauvoydbupg.wisconsin.edu address for testing upgraded
- Fix newbooks

Switch over (scheduled for 9am)
- Take down read-only production zones
- Reboot upgraded zones to come back up as production
-- take down read-only production zones (outage starts here)
-- for upgraded zones -
-- zone configuration files back into place
-- /etc/inet/hosts in each zone back to production values
-- /oracle/app/oracle/product/10.2.0/db_1/network/admin/listener.ora backup into place
-- apache configuration changes if anything has an IP address hard coded
-- shut down zones
-- boot zones (should come up as production)
-- uncomment cron jobs for voyager and nightly backups
-- update nightly backup scripts as needed
-- on z3950 update z3950svr.ini and xxxdb/etc/ascopac/opac.ini and stop/start voyager (z3950.wisconsin.edu brief downtime at this point)
- Do any cleanup needed