Blog

ODA re-image 12.1.2.6

Share this article

Doing an ODA re-image 12.1.2.6 on an ODA X3-2 (the installed version was 2.10, as in 2.10 without 12.1 in front of it 🙂 ) seems like an easy task, but it isn’t. 12.1.2.6 doesn’t contain a firmware upgrade because it has the upgrade from OEL5 to EL6 and otherwise the patch would be too big. Since it’s not documented anywhere I’ll explain it to you in this post.

One of our customers wanted to re-image their ODA to 12.1.2.6, or just the latest version. Because the storage redundancy was set to high they didn’t have enough storage space left. So they bought a storage expansion and asked us to re-install the whole thing. One additional advantage to this approach was the opportunity to go from bare-metal to a virtualised setup.

Some additional info: we moved all the databases from the ODA to big-ass vmware VM’s with dataguard. That way we had some more time (which proved to be useful in the end) and the downtime was reduced to minutes instead of hours.

So now why we’re all here…
As stated above, the 12.1.2.6 software doesn’t contain the firmware upgrades. So I started out with 12.1.2.5 because this one (like any other normal update) does have the latest firmware.
After re-imageing with 12.1.2.5 I expected the firmware to be upgraded. But it wasn’t…

After doing some research and talking with a more ODA-experienced co-worker the conclusion was to do the deployment for 12.1.2.5 as well. Almost half a day later the deployment was done.
My face after doing the following command was apparently priceless:

[root@test ~]# oakcli show version -detail
Reading the metadata. It takes a while...
System Version  Component Name            Installed Version         Supported Version
--------------  ---------------           ------------------        -----------------
12.1.2.5.0
                Controller_INT            11.05.03.00               Up-to-date
                Controller_EXT            11.05.03.00               Up-to-date
                Expander                  0018                      Up-to-date
                SSD_SHARED {
                [ c1d44,c1d45,c1d46,      A122                      A29A
                c1d47 ]
                [ c1d20,c1d21,c1d22,      9440                      944A
                c1d23 ]
                             }
                HDD_LOCAL                 A606                      A720
                HDD_SHARED {
                [ c1d0,c1d1,c1d2,c1d      A600                      A720
                3,c1d4,c1d5,c1d6,c1d
                7,c1d8,c1d9,c1d10,c1
                d11,c1d12,c1d13,c1d1
                4,c1d15,c1d16,c1d17,
                c1d18,c1d19 ]
                [ c1d24,c1d25,c1d26,      A720                      Up-to-date
                c1d27,c1d28,c1d29,c1
                d30,c1d31,c1d32,c1d3
                3,c1d34,c1d35,c1d36,
                c1d37,c1d38,c1d39,c1
                d40,c1d41,c1d42,c1d4
                3 ]
                             }
                ILOM                      3.1.2.10.d r83372         3.2.4.26.b r101722
                BIOS                      17050100                  17110500
                IPMI                      1.8.12.0                  Up-to-date
                HMP                       2.3.2.4.1                 Up-to-date
                OAK                       12.1.2.5.0                Up-to-date
                OL                        5.11                      Up-to-date
                OVM                       3.2.9                     Up-to-date

So yeah… It’s clearly not upgraded…
Since it wasn’t upgraded, running a manual upgrade for the infrastructure on 12.1.2.5 seemed like a good choice. And since the version details were showing me that an upgrade was available, it was safe to assume that the packages were there to do the upgrade. If that explanation isn’t enough, the whole thing just got re-imaged with the software containing the firmware upgrades. So I tried to start it but I always got the error message that certain packages weren’t unpacked.

Note 888888.1 (or the well known ODA download page) on mos had some small text somewhere right below ODA “Bundle Patch” that said:

For 12.1.2.6.0 patching, the minimum compatible required version is 12.1.2.5.0. For easy reference:
ODA Patch 12.1.2.5.0 Patch 21645601
File Name: p21645601_121250_Linux-x86-64_1of2.zip & p21645601_121250_Linux-x86-64_2of2.zip
Please make sure all ILOM, BIOS, Controller, Expander, disk firmwares are all up-to-date before pursuing to 12.1.2.6.0 patching.

So I downloaded the upgrade packages and followed the normal upgrade path. The unpack commands need to be run on both nodes:

[root@test firmware]#  oakcli unpack -package /u01/firmware/p21645601_121250_Linux-x86-64_1of2.zip
Unpacking takes a while,  pls wait....
tar: ./pkgrepos/thirdpartypkgs/Firmware/Expander/SUN/T4-es-Storage/0342/Base/t4h-0342.fw: Cannot open: File exists
tar: Error exit delayed from previous errors
Error: Failed to unpack the package /u01/firmware/p21645601_121250_Linux-x86-64_1of2.zip

This confirms the suspicion that the packages were already on the ODA… Although on the second node, the first part succesfully unpacked. The end part didn’t give any trouble:

[root@test firmware]#  oakcli unpack -package /u01/firmware/p21645601_121250_Linux-x86-64_2of2.zip
Unpacking takes a while,  pls wait....
Successfully unpacked the files to repository.

There you have it… After this I was able to start the upgrade and the necessary updates were done:

[root@test firmware]# oakcli update -patch 12.1.2.5.0 --infra
INFO: DB, ASM, Clusterware may be stopped during the patch if required
INFO: Both nodes may get rebooted automatically during the patch if required
Do you want to continue: [Y/N]?: y
INFO: User has confirmed the reboot
INFO: Patch bundle must be unpacked on the second node also before applying this patch
Did you unpack the patch bundle on the second node?: [Y/N]?: y
INFO: All the VMs except OdaBase will be shutdown forcefully if needed
Do you want to continue: [Y/N]?: y
INFO: Running pre-install scripts
INFO: Running  prepatching on node 0
INFO: Running  prepatching on node 1
...
INFO: 2016-04-25 01:52:15: ----------------Patching the Storage-------------------
INFO: 2016-04-25 01:52:15: ....................Patching SSDs...............
INFO: 2016-04-25 01:52:15: Updating the  Disk : d20 with the Firmware : Z16IZF4EUSUN200G 944A
SUCCESS: 2016-04-25 01:52:52: Successfully updated the Firmware on  Disk : d20 to Z16IZF4EUSUN200G 944A
...
Other parts were updated as expected of.

To be sure:

[root@test ~]# oakcli validate -c ospatch -ver 12.1.2.5.0
INFO: Validating the OS patch for the version 12.1.2.5.0

INFO: 2016-04-25 03:25:09: Running a dry run for OS patching
INFO: 2016-04-25 03:25:32: OS is already Up-to-date. No need to apply the OS patch

To be really really sure:

[root@test ~]# oakcli show version -detail
Reading the metadata. It takes a while...
System Version  Component Name            Installed Version         Supported Version
--------------  ---------------           ------------------        -----------------
12.1.2.5.0
                Controller_INT            11.05.03.00               Up-to-date
                Controller_EXT            11.05.03.00               Up-to-date
                Expander                  0018                      Up-to-date
                SSD_SHARED {
                [ c1d20,c1d21,c1d22,      944A                      Up-to-date
                c1d23 ]
                [ c1d44,c1d45,c1d46,      A29A                      Up-to-date
                c1d47 ]
                             }
                HDD_LOCAL                 A720                      Up-to-date
                HDD_SHARED                A720                      Up-to-date
                ILOM                      3.2.4.26.b r101722        Up-to-date
                BIOS                      17110500                  Up-to-date
                IPMI                      1.8.12.0                  Up-to-date
                HMP                       2.3.2.4.1                 Up-to-date
                OAK                       12.1.2.5.0                Up-to-date
                OL                        5.11                      Up-to-date
                OVM                       3.2.9                     Up-to-date

From there on out I did an ODA re-image 12.1.2.6.

Long story short:

  • ODA re-image 12.1.2.5
  • oda_base deploy to 12.1.2.5
  • Downloading and unpacking the 12.1.2.5 upgrade package
  • Installing the 12.1.2.5 infra upgrade
  • ODA re-image 12.1.2.6
Tags: Blog
The easiest database appliance becomes faster, cheaper and more flexible!
Exadata install partner specialization announcement!

You May Also Like