Useful ODA documents:<br />

• Database Appliance Administration and Reference Guide (12.1.2.9)<br />
• Database Appliance Administration and Reference Guide (12.1.2.2)
• Master ODA document
• Oracle Database Appliance - 12.1.2 and 2.X Supported ODA Versions & Known Issues (Doc ID 888888.1)
• 12.1.0.2 Proactive Database Bundle Patches

<br />

Bundle patches for ODA are installed in 3 stages.<br > Upto and including 12.1.2.6, this is performed as so:<br >

0@@

From 12.1.2.7 onwards this has changed to:<br />

1@@

Show version details of all ODA components<br /> Note: all oakcli commands must be executed as root

2@@

Patching ODA means patching the O/S, the Grid Infrastructure (GI) and the RDBMS (or any combination thereof).<br />

Latest ODA patches are found in Oracle Database Appliance - 12.1.2 and 2.X Supported ODA Versions & Known Issues (Doc ID 888888.1)

Download the files on the relevant patch page for your hardware, copy them to wherever you store patches on the server and Read the README.

Copy the zip files from your patch storage area to /tmp on both ODA_BASE nodes.

Make sure there is enough space in /root, /tmp, $ORACLE_HOME, and /opt for the unzippped / installed files.

3@@

Do not use unzip!

4@@

If unpack -package was successful, files can be removed from /tmp.

5@@

The following command will inform you whether the patch will succeed. If the output indicates a possible problem, for example, an unpacked version of the patch is not available on the system, you may wish to defer applying the patch until you have downtime to fix the expected problem.<br /> From Node 0:

6@@

If the validation check reveals any RPMs, they must be removed prior to patching.<br /> Note: Perform check on both nodes, there may be differences!

7@@

This file will probably be modified by any server patches

8@@

The oakcli patching process has component specific logging enabled for each component being patched.<br /> These log files can be found under the directory <tt>/opt/oracle/oak/log/$(hostname)/patch/12.1.2.9.0</tt>

9@@

and add space if necessary

10@@

Before updating the repository, agent, server, or database, ensure that there will be no jobs running or pending during the update window.

Perform any specifics such as

• Set database in blackout in OEM
• Any other monitoring software?
• Ensure archivelogs are not deleted. They will be needed for application on physical standby later.
• anything else that could be a problem.

For example, here we use rlwrap for command line editing so these aliases will no longer work as we just uninstalled the readline package so comment them for now.

11@@

If these commands are going to be used, they will need unaliasing before use! e.g.

12@@

13@@

14@@

15@@

Note: Do this on both nodes!

16@@

17@@

After tarball has been successfully created, ODA_BASE can be restarted.

18@@

This was done before applying GI patch but as server patch now includes GI, stop repositories before applying server patch.

19@@

If any component shows as “Up-to-date” for the supported version, then it indicates that the existing version on the system is current and that component will not be patched.

20@@

Nodes can be patched one at a time by using the -local switch<br /> If both nodes are to be patched automatically (rolling patch), do not specify -local switch but command must then be executed from node 0.

21@@

Note: If using '-local' switch, do not run this command simultaneously on both nodes!

Check cluster is working ok.

22@@

List mount points that should be mounted

23@@

List mount points that are mounted

24@@

Note: As of 12.1.2.7.0, this step is included in the '–server' patch<br />

25@@

Note: As of 12.1.2.7.0, this step is included in the '–server' patch<br /> <br /> Carefully read the known issues before applying the GI Patch.

26@@

27@@

Note: This section is new as of 12.1.2.7.0<br />

28@@

Note: The storage patching has no '-local' option. It must start from node 0, node 0 is patched first followed by the node 1. Both nodes will be rebooted.<br /> From node 0:

29@@

30@@

31@@

Check for higher values of variables.

Once the infrastructure and GI patches (or server and storage) have been completed successfully, the RDBMS patches can be applied.<br /> It can be applied locally on each node or as a rolling upgrade and both nodes will be patched automatically.<br /> If '-local' is not specified, the command must be run from node 0.

32@@

33@@

34@@

35@@

36@@

Log in to each of the VMs in turn

37@@

login to OMS server

38@@

Kill any old processes and restart agent

39@@

Check for later versions?

• Nagios plugin

40@@

• Oracle Snap Management Utility

41@@

• other

42@@

Like these aliases setup for readline wrapping

43@@

…and any other monitoring software

Patching may destroy public keys

44@@

If password is requested, keys are corrupt.

45@@

• Solution

Recreate STAGING volume on ODA_BASE.

46@@

47@@

• Solution

Clean the / directory and ensure at least 3G available!

48@@

• Solution

Stop the shared repositories

49@@

50@@

• Problem

Grid agent was probably started from wrong ORACLE_HOME

• Solution

Kill any old agent processes and restart

51@@