Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 9/10 Installation Guide: Solaris Live Upgrade and Upgrade Planning |
Part I Upgrading With Solaris Live Upgrade
1. Where to Find Solaris Installation Planning Information
2. Solaris Live Upgrade (Overview)
3. Solaris Live Upgrade (Planning)
4. Using Solaris Live Upgrade to Create a Boot Environment (Tasks)
5. Upgrading With Solaris Live Upgrade (Tasks)
6. Failure Recovery: Falling Back to the Original Boot Environment (Tasks)
7. Maintaining Solaris Live Upgrade Boot Environments (Tasks)
8. Upgrading the Solaris OS on a System With Non-Global Zones Installed
9. Solaris Live Upgrade (Examples)
10. Solaris Live Upgrade (Command Reference)
Part II Upgrading and Migrating With Solaris Live Upgrade to a ZFS Root Pool
11. Solaris Live Upgrade and ZFS (Overview)
12. Solaris Live Upgrade for ZFS (Planning)
13. Creating a Boot Environment for ZFS Root Pools
14. Solaris Live Upgrade For ZFS With Non-Global Zones Installed
B. Additional SVR4 Packaging Requirements (Reference)
C. Using the Patch Analyzer When Upgrading (Tasks)
Upgrading to a Solaris Update Release
Note - To run the analyze_patches script, the installed system and the Solaris Operating System DVD, Solaris Software CDs, or network installation image must be accessible by the script either through NFS or locally mounted media.
In this example, the image is located on locally mounted media.
# cd /cdrom/cdrom0/Solaris_10/Misc
# ./analyze_patches -R rootdir -N netdir -D databasedir
rootdir is the root of the installed system. The default is /.
netdir is the path to the root of the OS image to be installed. The default is /cdrom/cdrom0. netdir is the path to the directory that contains the Solaris_10 directory. You must use this option if you are running the patch_analyzer from an NFS mount point.
If the script is invoked from a directory other than the Misc/ directory in the OS image, the program cannot find the database it uses for patch analysis. Use the -D option to supply the path to the database. Without this database, which is located in Solaris_10 /Misc/database on the OS image, the script does not work properly.