Image Update Best Practices
-
Before you update, perform the following steps:
-
Review the license. Displaying License Requirements describes how to list packages that require you to accept their license. You might need to specify the
--acceptoption to install or update these packages. Displaying Package Licenses describes how to show the license text. -
Read the release notes. Release notes for an Oracle Solaris release are provided on
docs.oracle.com. Release notes for an SRU are provided onsupport.oracle.com. -
Check the package versions that are available from your configured publisher origin. See Check Available Versions. You might need to run the
pkg refreshcommand on the publisher or run thepkgrepo refreshcommand on a particular location of the publisher. If you create your own repository, do not create a partial repository; create a complete repository as described in Creating Package Repositories in Oracle Solaris 11.4. -
Use the
pkg updatecommand with the-nvoptions to display the list of packages that will be updated without actually performing the update. See Preview the Update Operation.
-
-
When you update, use the
--be-nameor--require-new-beoption to make the changes in a new boot environment, not in the current boot environment, as described in Specify a New Boot Environment. -
If the update fails, check Troubleshooting Package Installation and Update.
-
After you update, verify the installed packages.
$ beadm mount name-of-new-BE /mntMake sure you got what you wanted in the update:
$ pkg -R /mnt list -v entireVerify the packages:
$ pkg -R /mnt verify -vIf errors are reported, use the
pkg fixcommand and then verify that the errors are fixed.$ pkg -R /mnt fix -v $ pkg -R /mnt verify -v
Remember to unmount the BE.
$ beadm unmount name-of-new-BE -
Use the
-Noption with thepkg historycommand to see whether release notes are reported in any updated or installed package. -
Keep your systems updated with all support updates as described in Applying Support Updates. The “Oracle Solaris Binary and Source Guarantee Program” (Doc ID 1391762.1) ensures that updating across release boundaries is low risk.