Upgrade Workload Partitions (WPAR)
As seen on the page one level above, I had a 6100-05 system which was migrated to 7100-00. To be able to use the WPARs within, I had to upgrade them separately.
What happens if you try to start a 6.1 WPAR on a 7.1 global system? This should not work anyway, but why not to try?
# startwpar wp_namestartwpar: 0960-667 The operating system level within the workload partition is not supported.There is a command to upgrade WPARs to the system's OS level:
# migwpar wp_nameShared /usr WPAR list: noneCleaning up ...A little explanation here. A WPAR can be created in three ways:
- System WPAR: on a separate disk
- WPAR with a private /usr = detached WPAR
- Shared WPAR (/usr is common)
I didn't want to share anything from the global system with the WPARs, therefore they have their own /usr.
So it turns out that you need the 7.1 base filesets when your WPAR has its own /usr because the installer (installp) must update every fileset, just as the main installer did on the global system.
This would be the command, assuming that you have a DVD mounted on /mnt:
# migwpar -d /mnt/installp/ppc wp_nameI will update the page as soon as I have done it. Done, 2011-09-18.
During the upgrade, you will see these temporary mount points appear:
/app/lpp 31457280 12779944 60% 799 1% /wpars/wp_name/usr/sys/inst.images/usr/lib 5242880 2077224 61% 33221 12% /wpars/wp_name/usr/lib/alt_mig/usr/lib/usr/ccs/lib 5242880 2077224 61% 33221 12% /wpars/wp_name/usr/lib/alt_mig/usr/ccs/libIn the meantime, lswpar shows WPAR state 'T' = Transitional.
Just for the record: a 7100-00-01 WPAR will start on a 7100-00-03 global AIX instance.
Update WPAR
Every existing update on the global system must be available in the update directory, when syncing the OS level.
Here, the command fails because I forgot the compiler update pack:
# syncwpar -p -d /path/to/7100-00-03 -D wp_name...syncwpar: 0960-582 The following filesets could not be synchronized because the required software level was not found on the installation media:Fileset Name WPAR Level Global Levelvac.C 11.1.0.2 11.1.0.7vac.aix53.lib 11.1.0.2 11.1.0.7...Shutting down all workload partition processes.Unloading workload partition.Unmounting all workload partition file systems.syncwpar: 0960-264 Error synchronizing workload partition wp_name.Return Status = FAILURE.Copy missing update filesets to the same location. Make sure you remove the .toc file!
Then run the command again:
# syncwpar -p -d /path/to/7100-00-03 -D wp_name*******************************************************************************Synchronizing workload partition wp_name (1 of 1).*******************************************************************************Mounting all workload partition file systems.Loading workload partition.Executing syncd_install_sync in workload partition wp_name.Previewing install operations to synchronize wp_name:Note: Further operations may be necessary to complete synchronization:Fileset levels to be applied: Java5.sdk 5.0.0.395 ...There is no 'SUCCESS' or similar message at the end if the preview was successful.
Update gets stuck in a loop if it detects a full WPAR /usr:
...FILESET STATISTICS------------------ 291 Selected to be installed, of which: 291 Passed pre-installation verification ---- 291 Total to be installedfile_type failed: A file or directory in the path name does not exist.file_type failed: A file or directory in the path name does not exist.0503-008 installp: There is not enough free disk space in filesystem /usr (930568 more 512-byte blocks are required). An attempt to extend this filesystem was unsuccessful. Make more space available then retry this operation.inuwpar: Operation Summary:Environment Return Code-------------------------------------------------------- wp_name 255syncwpar: 0960-580 Synchronization operation halted due to a cycle detected while processing syncwpar.Previewing install operations to synchronize wp_name:Note: Further operations may be necessary to complete synchronization:inuwpar: The operation will be attempted in these environments: wp_nameinuwpar: ==== Performing operation on wp_name ====installp: Using alternate installation device /tmp/aaaFvaOK, let's get over it and increase the WPAR /usr manually, then retry. For the next time, don't forget the -X flag ;)
The syncwpar operation brings up the WPAR and updates the necessary filesets. In my case, there were 285 filesets to work on.
installp: * * * A T T E N T I O N ! ! ! Software changes processed during this session require this system and any of its diskless/dataless clients to be rebooted in order for the changes to be made effective.inuwpar: Operation Summary:Environment Return Code-------------------------------------------------------- wp_name 0inuwpar: The operation will be attempted in these environments: wp_nameinuwpar: ==== Performing operation on wp_name ====...After the update, the commit follows automatically, it means this update cannot be rejected... seems like a reject operation will only be possible by using the host (global) system's filesets..?
installp: COMMITTING software for: rsct.core.microsensor 3.1.0.3Finished processing all filesets. (Total time: 1 mins 28 secs).+-----------------------------------------------------------------------------+ Summaries:+-----------------------------------------------------------------------------+Installation Summary--------------------Name Level Part Event Result-------------------------------------------------------------------------------Java6.sdk 6.0.0.265 USR COMMIT SUCCESSinuwpar: Operation Summary:Environment Return Code-------------------------------------------------------- wp_name 0Workload partition wp_name synchronized successfully.Return Status = SUCCESS.Issue a stop/startwpar or a rebootwpar just to make sure everything is fine.