This section contains the following Quick Path steps for patching an OES 11 server:
Do not use the zypper up command by itself to update an OES server. Always use the -t patch option as described in Section 7.9.2, Command Line Quick Path for Updating OES 11 SP3.
If the -t patch option is omitted, zypper includes SLES packages in the download that can cripple or completely break OES services.
The -t patch option also ensures that patch metadata (including script files, etc.) is downloaded so that SLES can correctly update the system.
Make sure you have the following:
A Novell Customer Center account
If you don’t have one, create it at http://www.novell.com/register. This is the same account that you use for Bugzilla.
Activation Codes for both SLES 11 SP4 and OES 11 SP3
A valid installation source
An established connection to the Internet
All of the services installed that you need on the server.
Enough disk space in /var/cache/zypp/ where the update process downloads all the updates to.
Depending on the number of patches that you are going to apply, you might need about 3 GB.
A backup of the current data on the server.
Register the server in the Novell Customer Center (one time only).
Log in to the server as root or su to root.
At the command line, enter
suse_register -a email=email_address -a regcode-sles=SLES11_registration_code -a regcode-oes=oes11_registration_code
For example,
suse_register -a email=joe@example.com -a regcode-sles=4adab769abc68 -a regcode-oes=30a74ebb94fa
Verify that the server is registered by checking to see whether you have the service types and catalogs needed for updates.
To verify the service types, enter:
zypper sl
To verify that you have the catalogs you need, enter:
zypper lr
Update the server with all available updates:
Refresh all services by entering:
zypper ref -s
See whether updates are available by entering:
zypper lu -r SLES11-SP4-Updates -r OES11-SP3-Updates
Update the server with all available SLES 11 SP4 and OES 11 SP3 patches by entering:
zypper up -t patch -r SLES11-SP4-Updates -r OES11-SP3-Updates
Repeat Step 3.b and Step 3.c until there are no more SLES 11 SP4 or OES 11 SP3 patches.
When there are no more patches, continue with Step 3.e.
If the update requires a server reboot, do so when intimated by the system.
Rebooting the server activates the new kernel and ensures that OES services that need restarting after patching are restarted.
You can also update your server with specific maintenance patches.
Log in to the server as root or su to root.
At the command line, enter the following commands:
To refresh all services, enter:
zypper ref -s
To check for available updates, enter:
zypper lu -r SLES11-SP4-Updates -r OES11-SP3-Updates
To list the patches and their status, enter:
zypper pch SLES11-SP4-Updates OES11-SP3-Updates
To view specific patch information, enter:
zypper patch-info patch_name
For example:
zypper patch-info slessp4-sax2
To list all installed patches, enter:
zypper search -t pch -i
To update the server with specific patches, choose from the following:
To install all patches from one or more catalogs of a particular category:
zypper patch -r catalog1 -r catalog2 -g category_name
Replace category_name with security, recommended, or optional.
For example:
zypper patch -r SLES11-SP4-Updates -r OES11-SP3-Updates -g security
To install one version of a patch without confirmation, enter:
zypper --non-interactive in -t patch patch_name-version
For example:
zypper --non-interactive in -t patch oes11-CASA-3904-0
To install all versions of a patch, enter:
zypper in -t patch patch_name*
If the update requires a server reboot, do so when intimated by the system. This ensures that any changes to the kernel are activated, and applicable OES 11 services are restarted.