You can use the console to apply fixes, which apply code
updates to deployed instances such as virtual applications, virtual
systems, databases, and shared services.
Before you begin
To add content to the catalog, you must
be assigned the Create new catalog content permission or the Workload resources administration role with Full permission. When you create your emergency fix, be
aware that most browsers limit uploads to around 2 GB. If an archive
file exceeds this limit, you might not be able to upload it by using
the browser interface; in this case, you must use the command-line interface.Important: If you disabled the
sudo facility for the root user after deployment, you must enable
it before applying an update from the Instance Console.
About this task
Before you apply an emergency fix, verify whether there is
already an official service update available that addresses your update
needs, or see whether you can wait for an official service update
to be available. By applying an official service update or fix pack,
you can take full advantage of the ease of applying the service update
by using the Cloud Pak System Software console.
You can avoid the extra effort of packaging your own emergency fix,
and you can be assured that the metadata displays the correct fix
levels in any deployed systems that you update.If you apply your
own emergency fix built from a stand-alone fix pack, or if you apply
a fix by logging in to a virtual machine and applying it directly,
the version on the virtual machine no longer matches the version that
is displayed in the console. This configuration might cause problems if
you attempt to apply official fix packs in the future.