Oracle Database Applicance Release 2.10.0.0.0


On 1. May 2014 Oracle released the 2.10.0.0.0 patch for Oracle Database Appliance.

Major changes

This release doesn’t contain many new features, but some internal important internal bug fixes, so i’vh renames this section to “Major changes”

  • Oracle PSU 11.2.0.3.10 and 11.2.0.4.2 for GI and Database
  • Out of Place for Grid Infrastructure update supportes the upgrade from 11.2.0.3.x to 11.2.0.4.2
  • ODAchk has been renamed to ORAchk
  • Bug 17896838, has been fixed on 2.10.0.0.0. See here

NOTICE: ODA Note 888888.1 has been updated right now

Description:

  • ODA Bundle Patch
    Contains patches to the following components: OS, Component Firmware and Oracle Appliance Manager Modules, Grid Infrastructure, and RDBMS.
  • End-User GI/RDBMS Clone files
    Contains the latest Grid Infrastructure and RDBMS components, for deployment on an Oracle Database Appliance in the “shipped from factory” state, or an Oracle Database Appliance that has been re-imaged using the OS ISO Image.
  • OS ISO Image
    Used to restore the OS to the “shipped from factory” state. Use only when necessary.
  • Bare Metal
    Refers to the non-virtualized ODA configuration.

IMPORTANT:

  • There are some problems with the Shared Repository. Please read “Known Issues 2.10.0.0.0” section in MOS ID 888888.1 carefully!
  • X4-2 core Key generation not yet working on MOS. This is going to be fixed in Apr-2014. Until then, please open an SR requesting keys for X4-2. (Virtualized Deployment with core binding is working. This doesn’t need a core key)

Patch ID’s:

  • Patch 18284007     Oracle Database Appliance Patch Bundle 2.10
  • Patch 16186163     Oracle Database Appliance 2.10 Virtualized OS ISO Image (Dom0)
  • Patch 16186172     Oracle Database Appliance Template download for Virtualized Platform (ODA_BASE)
  • Patch 12999313     Oracle Database Appliance Bare Metal OS ISO Image
  • Patch 12978712     Oracle Database Appliance End User Bundle
  • Patch 17770873     Oracle Database Appliance 11.2.0.4.2 End-User (RDBMS clone)
  • Patch 14777276     Oracle Database Appliance 11.2.0.3.10 End-User (RDBMS clone)
  • Patch 14349293     Oracle Database Appliance 11.2.0.2.12 End-User (RDBMS clone, not changed since 2.8.0.0.0)

Version Changes:

Component Name X4-2 Hardware X3-2 Hardware V1 Hardware
Controller 11.05.03.00 11.05.03.00 11.05.03.00
Expander 0018 0018 342
SSD_SHARED 9440 9440 E12B
HDD_LOCAL A606 A450 SF04,SA03
HDD_SHARED A600 A600 0B25,A700
ILOM 3.1.2.30.a r83840 3.1.2.10.d r 83372 3.0.16.22.d r83408
BIOS 25010601 17050100 12010311
IPMI 1.8.10.5 1.8.10.5 1.8.10.5
HMP 2.2.6.5 2.2.6.5 2.2.6.5
OAK 2.10.0.0.0 2.10.0.0.0 2.10.0.0.0
ORACLE LINUX 5.9 5.9 5.9
Kernel 2.6.39-400.126.1.el5uek 2.6.39-400.126.1.el5uek 2.6.39-400.126.1.el5uek
OVS 3.2.3 3.2.3 3.2.3
Dom0 Kernel 2.6.39-400.126.1.el5uek 2.6.39-400.126.1.el5uek 2.6.39-400.126.1.el5uek
GI_HOME 11.2.0.4.2(18031740) 11.2.0.4.2(18031740) 11.2.0.4.2(18031740)
DB_HOME 11.2.0.4.2(18031668) 11.2.0.4.2(18031668) 11.2.0.4.2(18031668)
ASR 4.7 4.7  4.7

How to update see here

Oracle Database Appliance // Virtualization // Shared Repositories


Today I’vh setup my ODA as virtualized platform which is possible since 2.5 Image. I’vh done my installation with the latest stable release (2.9) which is available right now. I want you show you how setup an shared repository with is possible since 2.8 image. First the theory:

shared_repo_arch
Source: docs.oracle.com

I will show from setup the repository until the installation of the virtual machine:

1. Create a shared repository

Show actual configuration:

>oakcli show repo

          NAME                          TYPE            NODENUM         STATE
          odarepo1                      local           0               N/A       
          odarepo2                      local           1               N/A    

Create repository shared1 in Diskgroup +RECO with the size of 250GB:

>oakcli create repo shared1 -dg reco -size 250

Created Shared Repo : SharedRepoType

Show new configuration:

>oakcli show repo       
           
          NAME                          TYPE            NODENUM         STATE                                                                
          odarepo1                      local           0               N/A 
          odarepo2                      local           1               N/A 
          shared1                       shared          0               ONLINE                                                               
          shared1                       shared          1               ONLINE                   

Show details:

akcli show repo shared1 -node 0
Resource: shared1_0
        AutoStart       :       restore        
        DG              :       RECO           
        Device          :       /dev/asm/shared1-72
        ExpectedState   :       Online         
        MountPoint      :       /u01/app/sharedrepo/shared1
        Name            :       shared1_0      
        Node            :       all            
        RepoType        :       shared         
        Size            :       256000         
        State           :       Online        

2. Check the implementation on the oda_base nodes

>showmount -e
Export list for oda_base_node0:
/u01/app/sharedrepo/shared1 192.168.16.24

>showmount -e
Export list for oda_base_node1:
/u01/app/sharedrepo/shared1 192.168.16.25

ATTENTION: The exports are done dynamically by oak. If you restart nfs service on ODA_BASE the configuration is lost until oak will reapply. >cat /etc/exports will be empty!

3. Check the implementation in vm hosts

[root@odavm01 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/md1               19G  1.1G   17G   6% /
tmpfs                 1.7G     0  1.7G   0% /dev/shm
/dev/md3              519G  209G  284G  43% /OVS
/dev/md0              487M   41M  421M   9% /boot
none                  1.7G  112K  1.7G   1% /var/lib/xenstored
192.168.16.27:/u01/app/sharedrepo/shared1
                      250G  649M  250G   1% /OVS/Repositories/shared1

[root@odavm02 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/md1               19G  1.1G   17G   6% /
tmpfs                 1.7G     0  1.7G   0% /dev/shm
/dev/md3              519G  181G  311G  37% /OVS
/dev/md0              487M   41M  421M   9% /boot
none                  1.7G  112K  1.7G   1% /var/lib/xenstored
192.168.16.28:/u01/app/sharedrepo/shared1
                      250G  649M  250G   1% /OVS/Repositories/shared1

ATTENTION: The NFS mount point will be mounted with oracle best practice options, so this mounts are HARD mounts which will be a problem on simple reboot!

192.168.16.27:/u01/app/sharedrepo/shared1 on /OVS/Repositories/shared1 type nfs (rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,actimeo=0,nfsvers=3,timeo=600,addr=192.168.16.27)

192.168.16.28:/u01/app/sharedrepo/shared1 on /OVS/Repositories/shared1 type nfs (rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,actimeo=0,nfsvers=3,timeo=600,addr=192.168.16.28)

So please stop all VMs, execpt oda_base on vm host before reboot. Otherwise the reboot will hang on unmount NFS mountpoint!

4. Create vm template

There is nothing special, on local node import. So straight forward:

>oakcli import vmtemplate w2k8_template -assembly /tmp/stage/w2k8_template.ova -repo odarepo1

Imported VM Template 

>oakcli show vmtemplate

        NAME                                            MEMORY          VCPU            REPOSITORY
        w2k8_template                                   4096               1            odarepo1            

5. Create virtual machine

>oakcli clone vm w2k8 -vmtemplate w2k8_template -repo shared1 -node 0

Cloned VM Template 

We have created a virtual machine which starts only on NODE 0 and is located on shared Repository “shared1”

5. Configure virtual machine

>oakcli show vm w2k8
Resource: w2k8
        AutoStart       :       restore        
        CPUPriority     :       100            
        Disks           :       |file:/OVS/Repositories/shared1/Vir
                                tualMachines/w2k8/183d0200dd0c
                                485f8a47a2880b7daf0a.img,xvda,w|
        Domain          :       XEN_PVM        
        ExpectedState   :       online         
        FailOver        :       true           
        IsSharedRepo    :       true           
        Keyboard        :       de             
        MaxMemory       :       8192           
        MaxVcpu         :       4              
        Memory          :       8192           
        Mouse           :       USB_MOUSE      
        Name            :       w2k8      
        Networks        :       |type=netfront,bridge=net1||type=ne
                                tfront,bridge=net2|
        NodeNum         :       1              
        NodeNumStart    :       1              
        OS              :       WIN_2008       
        PrefNodeNum     :       0              
        PrivateIP       :       None           
        ProcessorCap    :       100            
        RepoName        :       shared1        
        State           :       Online         
        TemplateName    :       otml_w2k8_template
        Vcpu            :       4              
        cpupool         :       reports_pool   
        vncport         :       0              

You may configure your vm now.

ATTENTION: During clone of vm you may run in a BUG which causes one of both Nodes a Oracle Cluster Crash of ASM, the Private Interconnect may be not responed anymore until you force umount the ACFS Respository on vm host!
You may get the following:

...
64 bytes from 192.168.16.28: icmp_seq=675 ttl=64 time=0.347 ms
64 bytes from 192.168.16.28: icmp_seq=676 ttl=64 time=0.290 ms
64 bytes from 192.168.16.28: icmp_seq=677 ttl=64 time=0.298 ms
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
...

or

...
nfs: server 192.168.16.27 not responding, still trying
nfs: server 192.168.16.27 not responding, still trying
INFO: task cp:29088 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
cp              D 0000000000000000     0 29088  29087 0x00000000
 ffff880146cddb68 0000000000000282 ffff880146cdda98 0000000000012180
 ffff88015121c240 ffff880154ebe2c0 ffff880146cddb28 ffff8801011f3bc0
 ffff880146cddab8 ffffffff810410c1 ffff880146cddab8 00000000009824aa
Call Trace:
 [] ? pvclock_get_nsec_offset+0x11/0x50
 [] ? pvclock_clocksource_read+0x29/0x80
 [] ? xen_clocksource_read+0x20/0x30
 [] ? xen_clocksource_get_cycles+0x9/0x10
 [] ? ktime_get_ts+0xb1/0xf0
 [] schedule+0x45/0x60
 [] io_schedule+0x71/0xb0
 [] sleep_on_page+0xe/0x20
 [] __wait_on_bit+0x5e/0x90
 [] ? __lock_page+0x80/0x80
 [] wait_on_page_bit+0x75/0x80
 [] ? autoremove_wake_function+0x50/0x50
 [] ? pagevec_lookup_tag+0x27/0x40
 [] filemap_fdatawait_range+0xf7/0x180
 [] ? nfs_file_direct_read_iter+0x50/0x50 [nfs]
 [] filemap_fdatawait+0x2b/0x30
 [] writeback_single_inode+0x1ce/0x230
 [] sync_inode+0x4a/0x80
 [] nfs_wb_all+0x46/0x50 [nfs]
 [] nfs_setattr+0x12f/0x140 [nfs]
 [] notify_change+0x18b/0x2f0
 [] do_truncate+0x63/0x90
 [] do_sys_ftruncate+0x114/0x130
 [] sys_ftruncate+0x13/0x20
 [] system_call_fastpath+0x16/0x1b
...

Reference:
Bug 17896838 – DOMU LOST NETWORK CONNECTION DURING COPYING BIG FILES OVER NFS

Workaround:
This issue is caused by known kernel bug 17896838, which is fixed in kernel 2.6.39-214.1 and above. ODA July (2.10.0.0.0?) release will come with the new kernel that includes the fix. In the meantime, the workaround is to set or increase the dom0_mem in /boot/grub/grub.conf to 8192M on dom0 then reboot the dom0:

kernel /xen.gz dom0_mem=8192M crashkernel=256M@64M

In cause of my SR there have been raised a note you can refer to:
ODA DOM0 Lost Network Communications Between Nodes While running ‘okacli clone vm’ or Copy (cp) Commands of Large Files over NFS (Doc ID 1665055.1)

6. Done, now start up vm and have fun!

>oakcli show vm

          NAME                                  NODENUM         MEMORY          VCPU            STATE           REPOSITORY
          w2k8                                  1               8192               4            ONLINE          shared1                  

Oracle Database Appliance X4-2: Copper vs. Fiber


With the Database Applicance Release X4-2 hardware you can choose between 10GbE SFP+ and 10GBase-T (Dual Port) for interconnect or public network.

At initial deployment you are able to choose the configuration you want to use:

copper_vs_fiber

Delivery

If a new x4-2 has been ordered, it will be delivered with 2x SFP+ and 2x Ethernet Cable for both interconnect options

ethtool for fiber card

Settings for eth0
        Supported ports: [ FIBRE ]
        Supported link modes:   10000baseT/Full 
        Supports auto-negotiation: No
        Advertised link modes:  10000baseT/Full 
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Speed: 10000Mb/s
        Duplex: Full
        Port: Direct Attach Copper
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: off
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
        Link detected: yes

Settings for eth1
        Supported ports: [ FIBRE ]
        Supported link modes:   10000baseT/Full 
        Supports auto-negotiation: No
        Advertised link modes:  10000baseT/Full 
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Speed: 10000Mb/s
        Duplex: Full
        Port: Direct Attach Copper
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: off
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
        Link detected: yes

Oracle Database Applicance Release 2.9.0.0.0


On 20. February 2014 Oracle released the 2.9.0.0.0 patch for Oracle Database Appliance.

New features

  • Import of http based templates on ODA_BASE
  • Send Key support to the VM via xenstore.
  • Oracle Database Patch Set Update (PSU) 11.2.0.4.1 and 11.2.0.3.9.
  • Software enhancements:
    • New template available for Very Very Small databases
    • Support for SNMP Version 3 which can be used, optionally, instead of SNMP Version 2
    • Hardware Monitoring Tool enhanced to collect information about storage enclosures
    • Revised prompts and tools for managing the selection of Fiber or Copper public network
    • New Oracle Appliance Manager option to update the first-boot installation configuration of a virtual machine
  • Oracle Appliance Manager updates include
    • The oakcli show command has a new option, enclosure, to monitor storage enclosures
    • The oakcli modify vm command has a new parameter, -s, to define and send a message to a virtual machine

Major Updates

  • Database Update 11.2.0.2.12, 11.2.0.3.9 or 11.2.0.4.1 (PSU JAN-2014 included)
  • Hardware Monitoring on X4-2

NOTICE: ODA Note 888888.1 has been updated right now
Description:

  • ODA Bundle Patch
    Contains patches to the following components: OS, Component Firmware and Oracle Appliance Manager Modules, Grid Infrastructure, and RDBMS.
  • End-User GI/RDBMS Clone files
    Contains the latest Grid Infrastructure and RDBMS components, for deployment on an Oracle Database Appliance in the “shipped from factory” state, or an Oracle Database Appliance that has been re-imaged using the OS ISO Image.
  • OS ISO Image
    Used to restore the OS to the “shipped from factory” state. Use only when necessary.
  • Bare Metal
    Refers to the non-virtualized ODA configuration.

IMPORTANT:

  • There are some problems with the Shared Repository. Please read “Known Issues 2.9.0.0.0” section in MOS ID 888888.1 carefully!
  • X4-2 core Key generation not yet working on MOS. This is going to be fixed in Apr-2014. Until then, please open an SR requesting keys for X4-2. (Virtualized Deployment with core binding is working. This doesn’t need a core key)

Patch ID’s:

  • Patch 17630388     Oracle Database Appliance Patch Bundle 2.9
  • Patch 16186163     Oracle Database Appliance 2.9 Virtualized OS ISO Image
  • Patch 16186172     Oracle Database Appliance Template download for Virtualized Platform
  • Patch 12999313     Oracle Database Appliance Bare Metal OS ISO Image
  • Patch 12978712     Oracle Database Appliance End User Bundle
  • Patch 17770873     Oracle Database Appliance 11.2.0.4.1 End-User (RDBMS clone)
  • Patch 14777276     Oracle Database Appliance 11.2.0.3.9 End-User (RDBMS clone)
  • Patch 14349293     Oracle Database Appliance 11.2.0.2.12 End-User (RDBMS clone)

Version Changes:

V1 Hardware:

Depending on your hardware, the output should look similar to the output below:    
System Version  Component Name            Installed Version         Supported Version       
--------------  ---------------           ------------------        ----------------       
2.9.0.0.0                                                                                   
                Controller                11.05.03.00               Up-to-date              
                Expander                  0342                      Up-to-date              
                SSD_SHARED                E12B                      Up-to-date
                HDD_LOCAL                 SF04                      Up-to-date              
                HDD_SHARED                A700                      Up-to-date              
                ILOM                      3.0.16.22.d r83408        Up-to-date  
                BIOS                      12010311                  Up-to-date              
                IPMI                      1.8.10.5                  Up-to-date              
                HMP                       2.2.6.5                   Up-to-date              
                OAK                       2.9.0.0.0                 Up-to-date              
                OEL                       5.9                       Up-to-date
                GI_HOME                   11.2.0.4.0(17721778)      Up-to-date
                DB_HOME                   11.2.0.4.1(17478514)      Up-to-date              
                ASR                       4.6                       Up-to-date

X3-2 Hardware:

Depending on the hardware, the output should look similar to the output below:    
System Version  Component Name            Installed Version         Supported Version        
--------------  ---------------           ------------------        ----------------    
2.9.0.0.0                                                                                   
                Controller                11.05.03.00               Up-to-date              
                Expander                  0018                      Up-to-date              
                SSD_SHARED                9440                      Up-to-date
                HDD_LOCAL {               A450                      Up-to-date              
                HDD_SHARED {              A600                      Up-to-date
                ILOM                      3.1.2.10.d r83372         Up-to-date  
                BIOS                      17050100                  Up-to-date              
                IPMI                      1.8.10.5                  Up-to-date              
                HMP                       2.2.6.5                   Up-to-date              
                OAK                       2.9.0.0.0                 Up-to-date
                OVM                       3.2.3                     Up-to-date              
                OEL                       5.9                       Up-to-date
                GI_HOME                   11.2.0.4.0(17721778)      Up-to-date    
                DB_HOME                   11.2.0.4.1(17478514)      Up-to-date              
                ASR                       4.6                       Up-to-date

X4-2 Hardware:

Depending on the hardware, the output should look similar to the output below:    
System Version  Component Name            Installed Version         Supported Version       
--------------  ---------------           ------------------        ----------------    
2.9.0.0.0                                                                                   
                Controller                11.05.03.00               Up-to-date              
                Expander                  0018                      Up-to-date              
                SSD_SHARED                9440                      Up-to-date
                HDD_LOCAL {               A606                      Up-to-date              
                HDD_SHARED {              A600                      Up-to-date
                ILOM                      3.1.2.30.a r83840         Up-to-date  
                BIOS                      25010601                  Up-to-date              
                IPMI                      1.8.10.5                  Up-to-date              
                HMP                       2.2.6.5                   Up-to-date              
                OAK                       2.9.0.0.0                 Up-to-date
                OVM                       3.2.3                     Up-to-date              
                OEL                       5.9                       Up-to-date
                GI_HOME                   11.2.0.4.0(17721778)      Up-to-date    
                DB_HOME                   11.2.0.4.1(17478514)      Up-to-date
                ASR                       4.6                       Up-to-date

How to update see here

Oracle Database Appliance X4-2 is out!


On 04. December 2013 Oracle release the 3rd generation of Oracle Database Appliance over night. There is a good news: When Oracle changed v1 into X3-2 the price increased a “bit” … The price difference between x3-2 and x4-2 is zero which make me happy if I saw it the first time. No more discussions about “Why oracle increases prices in that matter …”. Further Oracle didn’t release a the option to run 12c on the Database Appliance. Maybe at the next ODA release 2.9.0.0.0?

A few days ago oracle also published the datasheet and whitepaper:

Here are the main specs:

  • 2x Server Nodes each with:
    • 2x E5-2697 v2 12-core 2.7 Ghz CPUs
    • Service processor w/ILOM 3.1
    • 256GB (16x 16GB) memory
    • 1x Dual Port 10GbE SFP+ NIC (PCIe cards)
    • 2x Dual port external SAS-2 (PCIe cards)
    • 1x Internal SAS-2 (PCIe cards)
    • 2x 2.5″ 10K 600GB SAS disks
    • 4x (onboard) 10GBase-T ports
  • One DE2-24P storage shelf (optional 2nd shelf can be ordered):
    • 4x 2.5″ 200GB SSDs
    • 20x 2.5″ 10K 900GB SAS HDDs

As you can see there are just a few technical innovations

  • Newer Server Case (4x-2) and mainboard
  • More cores. There are 2x 12 Cores each node
  • 10Gbit SFP+ Connect instead of 10GBit T-Base for Interconnect
  • Optional 10GbE SFP+ or 10GBase-T external networking connectivity

For further information visit the following links:

Oracle Database Applicance Release 2.8.0.0.0


On 19. Novermber 2013 Oracle released the 2.8.0.0.0 patch for Oracle Database Appliance.

New Features

  • Shared Repository support for Oracle Database Appliance Virtualized Platform
  • Virtual Local Area Network support for Oracle Database Appliance Virtualized Platform
  • Hardware Monitoring Tool reports data from sensors in subsystems
  • Initial deployment does not require configuration of initial Oracle Database or Oracle Enterprise Database Control

Major Updates

  • Out-of-place update Grid Infrastructure from 11.2.0.3.x to 11.2.0.4.0.
  • Virtualized platform shared repositories support
  •  Hardware Monitoring on X3-2
  • Virtualized platform VLAN support

NOTICE: ODA Note 888888.1 has been updated right now
Description:

  • ODA Bundle Patch
    Contains patches to the following components: OS, Component Firmware and Oracle Appliance Manager Modules, Grid Infrastructure, and RDBMS.
  • End-User GI/RDBMS Clone files
    Contains the latest Grid Infrastructure and RDBMS components, for deployment on an Oracle Database Appliance in the “shipped from factory” state, or an Oracle Database Appliance that has been re-imaged using the OS ISO Image.
  • OS ISO Image
    Used to restore the OS to the “shipped from factory” state. Use only when necessary.
  • Bare Metal
    Refers to the non-virtualized ODA configuration.

IMPORTANT: There are many problems with the new Features VLANs, Shared Repository and ACFS. Please read “Known Issues 2.8.0.0.0” section in MOS ID 888888.1 carefully!

Patch ID’s:

  • ORACLE DATABASE APPLIANCE PATCH BUNDLE 2.8.0.0.0 [ Patch 17630367]
  • ORACLE DATABASE APPLIANCE 2.8.0.0.0 VIRTUALIZED OS ISO IMAGE [Patch 16186163]
  • ORACLE DATABASE APPLIANCE 2.8.0.0.0 END-USER BUNDLE (GI/RDBMS Clone) [Patch 12978712]
  • ORACLE DATABASE APPLIANCE 2.8.0.0.0 BARE METAL OS ISO IMAGE [Patch 12999313]
  • ORACLE DATABASE APPLIANCE 2.8.0.0.0 (GI/RDBMS Clone) TEMPLATE DOWNLOAD FOR VIRTUALIZED PLATFORM [Patch 16186172]
  • ORACLE DATABASE APPLIANCE 2.8.0.0.0 END-USER BUNDLE (GI/RDBMS Clone, 11.2.0.4.0) [Patch 17770873]
  • ORACLE DATABASE APPLIANCE 2.8.0.0.0 END-USER BUNDLE (GI/RDBMS Clone, 11.2.0.3.8) [Patch 14777276]
  • ORACLE DATABASE APPLIANCE 2.8.0.0.0 END-USER BUNDLE (GI/RDBMS Clone, 11.2.0.2.12) [Patch 14349293]

Version Changes:

Component Name X3-2 Hardware V1 Hardware
Controller 11.05.03.00 11.05.03.00
Expander 0018 342
SSD_SHARED 9440 E12B
HDD_LOCAL A3D0 SF04,SA03
HDD_SHARED A31A 0B25,A700
ILOM 3.1.2.10.d r 83372 3.0.16.22.d r83408
BIOS 17050100 12010311
IPMI 1.8.10.5 1.8.10.5
HMP 2.2.6.4 2.2.6.4
OAK 2.8.0.0.0 2.8.0.0.0
ORACLE LINUX 5.9 5.9
Kernel 2.6.39-400.126.1.el5uek 2.6.39-400.126.1.el5uek
OVS 3.2.3 3.2.3
Dom0 Kernel 2.6.39-400.126.1.el5uek 2.6.39-400.126.1.el5uek
TFA 2.5.1.5 2.5.1.5
GI_HOME 11.2.0.4.0 11.2.0.4.0
DB_HOME 11.2.0.3.8(16902043,17076717) 11.2.0.3.8(16902043,17076717)
ASR 4.5 4.5

How to update see here