Before updating the system, perform the following checks:
If the system/locale/setterm package is installed in any native zone but not in the global zone, do one of the following:
Install the system/locale/setterm package in the global zone.
Uninstall the system/locale/setterm package from all native zones.
If the system has this issue, a pkg update will display an error like the following:
Reason: No version matching 'incorporate' dependency firstname.lastname@example.org can be installed ---------------------------------------- Reject: pkg://email@example.com Reason: Package system/locale/setterm is not installed in global zone.
If your java mediated link does not have version 1.8 as its value, see Using Java 8. Use the following command to check the value of the java mediated link:
$ pkg mediator java
First boot of a system after update to Oracle Solaris 11.4 can take a very long time if certain directories under /var, such as /var/tmp, contain large amounts of data. See Clean up /var/tmp for more information.
If MySQL 5.1 is installed, see How to Update to MySQL 5.5 Before Updating Your System To Oracle Solaris 11.4.
On any system that is running an OpenLDAP server, export the LDAP database to LDAP Data Interchange Format (LDIF) in order to migrate the data to the newly updated system. See How to Migrate Existing OpenLDAP Server Configuration in Working With Oracle Solaris 11.4 Directory and Naming Services: LDAP for instructions. A system that is running an OpenLDAP server has the svc:/network/ldap/server:openldap enabled and online.
Oracle provides a pre-update checker to help you determine whether a system that is running Oracle Solaris 11.3 SRU 35 or newer is ready to update to Oracle Solaris 11.4. The report generated by this checker identifies superseded software versions and unsupported hardware. This checker is part of the Enterprise Health Check (EHC) tool. See Updating Your Operating System to Oracle Solaris 11.4 for information about how to install and use the pre-update checker.