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 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

The Oracle Database Appliance: ORA-15025: could not open disk


1. Wrong ASM Permissions

Szenario

A new ODA with Single Instance deploment for a failover configuration. During initial start of the database on, the other node, the database will die as it switches into MOUNT mode:

...
ORA-15025: could not open disk "/dev/mapper/HDD_E0_S00_531029776p1"
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 9
ORA-15025: could not open disk "/dev/mapper/HDD_E0_S01_530979052p1"
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 9
...

The problem is, that the deployment set the ASM GID, according to the deployment type. In a RAC deployment the problem should not exist. To solve the problem:

Startingpoint

[grid@oak1 ~]$ ls -l /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/oracle
-rwsr-s--x 1 oracle asmadmin 232472632 Feb 5 13:42 /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/oracle
[grid@oak2 ~]$ ls -l /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/oracle
-rwsr-s--x 1 oracle oinstall 232472632 Feb 5 13:43 /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/oracle

 Solution

[grid@oak2 ~]$ setasmgidwrap o=/u01/app/oracle/product/11.2.0.3/dbhome_1/bin/oracle
[grid@oak2 ~]$ ls -l /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/oracle
-rwsr-s--x 1 oracle asmadmin 232472632 Feb 5 13:43 /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/oracle
[grid@oak2 ~]$

Check

[grid@oak1 ~]$ ls -l /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/oracle
-rwsr-s--x 1 oracle asmadmin 232472632 Feb 5 13:42 /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/oracle
[grid@oak2 ~]$ ls -l /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/oracle
-rwsr-s--x 1 oracle asmadmin 232472632 Feb 5 13:43 /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/oracle

2. Wrong Group Permissions

Szenario

A new ODA with NO DATABASE deploment. During initial start of the database on one of both nodes you will get:

...
ORA-15025: could not open disk "/dev/mapper/HDD_E0_S00_531029776p1"
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 9
ORA-15025: could not open disk "/dev/mapper/HDD_E0_S01_530979052p1"
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 9
...

The problem is, that the oracle group permissions are not deployed correctly. To solve the problem:

Startinpoint

[bash ~]# id oracle
uid=1001(oracle) gid=1001(oinstall) groups=1001(oinstall),1002(dba),1003(racoper),1004(asmdba)

ASM Disk permission

[bash ~]# ls -l /dev/mapper/HDD_E0_S*
brw-rw---- 1 grid asmadmin 252,  0 Feb 21 15:55 /dev/mapper/HDD_E0_S00_1128733508
...

Solution
Change /etc/group from

oinstall:x:1001:grid,oracle
dba:x:1002:oracle
racoper:x:1003:grid,oracle
asmdba:x:1004:grid,oracle
asmoper:x:1005:grid
asmadmin:x:1006:grid

to

oinstall:x:1001:grid,oracle
dba:x:1002:oracle
racoper:x:1003:grid,oracle
asmdba:x:1004:grid,oracle
asmoper:x:1005:grid,oracle
asmadmin:x:1006:grid,oracle

Repeat on the second node.
Check

[bash ~]# id oracle
uid=1001(oracle) gid=1001(oinstall) groups=1001(oinstall),1002(dba),1003(racoper),1004(asmdba),1005(asmoper),1006(asmadmin)

The Oracle Database Appliance: Initial Configuration


Initial configuration via ILOM

The ILOM interface gets a DHCP adress per default, if a DHCP is available.

1. Logon at ILOM

ILOM is  reachable via SSH and has the following default access data:

  • Username: root
  • Password: changeme
# ssh root@<ILOM IP Addresse>
The authenticity of host '172.16.0.52 (172.16.0.52)' can't be established.
RSA key fingerprint is e6:50:f7:b2:02:71:f8:2c:87:06:20:87:cc:fc:c8:e1.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '172.16.0.52' (RSA) to the list of known hosts.
Password: 

Oracle(R) Integrated Lights Out Manager

Version 3.0.14.13 r66865

Copyright (c) 2011, Oracle and/or its affiliates. All rights reserved.

Warning: password is set to factory default.

->

2. Start textconsole

The default OS access data:

  • Username: root
  • Passwort: welcome1
-> start /HOST/console

Are you sure you want to start /HOST/console (y/n)? y 

Serial console started. To stop, type ESC (

Enterprise Linux Enterprise Linux Server release 5.5 (Carthage)
Kernel 2.6.18-194.32.1.0.1.el5 on an x86_64

oak1 login: root
Password: 
Last login: Sat Mar 3 08:19:11 on ttyS0

3 . Check Interfaces

[root@oak1 bin]# ethtool bond0

Settings for bond0:

Link detected: yes

[root@oak1 bin]# ethtool bond1

Settings for bond1:

Link detected: no

[root@oak1 bin]# ethtool bond2

Settings for bond2:

Link detected: no

[root@oak1 ~]# ifconfig bond0

bond0 Link encap:Ethernet HWaddr 00:21:28:F0:77:EC

inet6 addr: fe80::221:28ff:fef0:77ec/64 Scope:Link

UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1

RX packets:9430512 errors:0 dropped:0 overruns:0 frame:0

TX packets:6 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:697083697 (664.7 MiB) TX bytes:468 (468.0 b)

 4 Initiale Networkconfiguration

[root@oak1 ~]# /opt/oracle/oak/bin/oakcli configure firstnet
Select the interface to configure network on [bond0 bond1 bond2 xbond0]:bond0
Configure DHCP on bond0?(yes/no):no
INFO: Static configuration selected
Enter the IP address to configure:172.16.0.58
Enter the netmask address to configure:255.255.254.0
Enter the gateway address to configure:172.16.0.1
INFO: Plumbing the IPs now
INFO: Restarting the network
Shutting down interface bond0: bonding: bond0: Warning: the permanent HWaddr of eth2 - 00:21:28:F0:77:EC - is still in use by bond0. Set the HWaddr of eth2 to a different address to avoid conflicts. [ OK ]
Shutting down interface bond1: bonding: bond1: Warning: the permanent HWaddr of eth4 - A0:36:9F:03:86:3D - is still in use by bond1. Set the HWaddr of eth4 to a different address to avoid conflicts. [ OK ]
Shutting down interface bond2: bonding: bond2: Warning: the permanent HWaddr of eth6 - A0:36:9F:03:86:3F - is still in use by bond2. Set the HWaddr of eth6 to a different address to avoid conflicts. [ OK ]
Shutting down interface eth0: [ OK ]
Shutting down interface eth1: [ OK ]
Shutting down interface eth8: bonding: xbond0: Warning: the permanent HWaddr of eth8 - 90:E2:BA:0E:25:B0 - is still in use by xbond0. Set the HWaddr of eth8 to a different address to avoid conflicts. [ OK ]
Shutting down interface eth9: [ OK ]
Shutting down interface xbond0: bonding: unable to remove non-existent slave eth8 for bond xbond0. bonding: unable to remove non-existent slave eth9 for bond xbond0. [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface bond0: [ OK ]
Bringing up interface bond1: [ OK ]
Bringing up interface bond2: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Bringing up interface xbond0: [ OK ]
[root@oak1 ~]#

DONE. The first machine should be reachable via SSH right now. The same procedure must be repeated on the second node (oak2).

NOTICE: The interconnect IP must not be configured. This is done per default.