Before You Begin
Review Installation Considerations in Oracle Solaris 11.4 Release Notes for system memory and disk space requirements and for platform support, including firmware and device support.
If the system to be updated is running Oracle Solaris 11.3 SRU 23 or newer, continue to Step 2.
If the system to be updated is running a release of Oracle Solaris 11.3 that is older than SRU 23, update to at least Oracle Solaris 11.3 SRU 23.
Ensure that the configured publishers provide Oracle Solaris 11.3 SRU 23 or a newer Oracle Solaris 11.3 SRU. The following command lists all Oracle Solaris 11.3 SRUs that are available from the publishers that are configured on the system:
$ pkg list -af firstname.lastname@example.org NAME (PUBLISHER) VERSION IFO entire 0.5.11-0.175.3.27.0.4.0 --- entire 0.5.11-0.175.3.26.0.5.0 --- entire 0.5.11-0.175.3.25.0.3.0 --- entire 0.5.11-0.175.3.24.0.4.0 --- entire 0.5.11-0.175.3.23.0.5.0 --- entire 0.5.11-0.175.3.22.0.3.0 ---
The following example shows updating to Oracle Solaris 11.3 SRU 27:
$ pkg update --be-name 11.3.27 email@example.com
Use one of the following methods:
Go to the Oracle Solaris 11 downloads site on Oracle Technology Network (OTN) to accept the license and download the Oracle Solaris 11.4 Beta package repository file.
See Creating Package Repositories in Oracle Solaris 11.4 for information about downloading and installing a local package repository, configuring the solaris publisher to use the local repository, and providing access to the local repository from other systems.
Confirm that the system can access Oracle Solaris 11.4 packages:
$ pkg list -af entire@latest NAME (PUBLISHER) VERSION IFO entire 11.4-18.104.22.168.1.3.0 ---
If you do not see Oracle Solaris 11.4 packages, make sure you did not skip solaris publisher location configuration in the previous step.
The license associated with Oracle Solaris 11.4 must be accepted in order to perform the update. View the contents of this license prior to acceptance, to ensure that you understand it. The following command shows the summary license:
$ pkg info -r --license firstname.lastname@example.org
The full license is available at http://www.oracle.com/technetwork/licenses/solaris-ea-license-4255446.html. This is the same license that you viewed on OTN or on the pkg-register site. If you agree to accept this license, then proceed with the update.
If any software on the system has been obsoleted in Oracle Solaris 11.4, that software will be removed when you upgrade to Oracle Solaris 11.4, as noted in Platform Support in Oracle Solaris 11.4 Release Notes. To see the list of packages that will be removed on upgrade, use the pkg update -nv command. The –n option shows what will be done but does not actually perform the update. The –v option shows what packages will be removed, and shows the full package versions. For software that will be removed, check the End of Features (EOF) Planned for Future Releases of Oracle Solaris 11 list for a suggested replacement or other workaround.
Using the –-accept option signals your legal acceptance of the above license.
$ pkg update --accept --be-name 11.4.0
Check that your new BE is updated as expected:
In your browser, navigate to https://pkg-register.oracle.com/.
On the Product Details page, select the “certificate page” link or navigate to https://pkg-register.oracle.com/register/certificate/.
In the following command, the arguments to the -c and -k options are one of the following:
The certificate and key files that you downloaded in the previous step.
The /var/pkg/ssl/certfile and /var/pkg/ssl/keyfile copied from the output of the pkg publisher solaris command if you already have a key and certificate for the solaris publisher for the support repository.
$ pkg set-publisher -g https://pkg.oracle.com/solaris/beta/ \ -c certfile -k keyfile solaris
If the Oracle Solaris release repository location is configured, remove that location:
$ pkg set-publisher -G http://pkg.oracle.com/solaris/release/ solaris
The following command confirms that the beta repository location is configured. In this example, the support repository location was already configured, and the key and certificate are the same for both locations:
$ pkg publisher solaris Publisher: solaris Alias: Origin URI: https://pkg.oracle.com/solaris/beta/ SSL Key: /var/pkg/ssl/0ee1490f184a54a158f0f343bd93cb378d79aca5 SSL Cert: /var/pkg/ssl/788ca49060b2478ddd10a824ac350af2f6bfa066 Cert. Effective Date: Thu Jan 11 09:25:50 2018 Cert. Expiration Date: Sun Jan 19 09:25:50 2020 Origin URI: https://pkg.oracle.com/solaris/support/ SSL Key: /var/pkg/ssl/0ee1490f184a54a158f0f343bd93cb378d79aca5 SSL Cert: /var/pkg/ssl/788ca49060b2478ddd10a824ac350af2f6bfa066 Cert. Effective Date: Thu Jan 11 09:25:50 2018 Cert. Expiration Date: Sun Jan 19 09:25:50 2020 Client UUID: d961698c-6c3f-11e5-a9af-f568c8b02ce3 Catalog Updated: Tue Apr 17 22:59:39 2018 Enabled: Yes