Install Oracle Database 11.2.x on Fedora 17-20


NOTICE: This workaround works for Fedora 20 (beta) too.

During installation of 11.2.x of Oracle Database software you may get an error during LINK part of installation:

Exception String: Error in invoking target 'agent nmhs' of makefile '/opt/oracle/app/product/11.2.0.4/dbhome_1/sysman/lib/ins_emagent.mk'.

install_11204_problem

In the Installationlog you will see the following errors

INFO: gcc -o /opt/oracle/app/product/11.2.0.4/dbhome_1/sysman/lib/emdctl -L/opt/oracle/app/product/11.2.0.4/dbhome_1/lib/ -L/opt/oracle/app/product/11.2.0.4/dbhome_1/sysman/lib/        `cat /opt/oracle/app/product/11.2.0.4/dbhome_1/lib/sysliblist` -Wl,-rpath,/opt/oracle/app/product/11.2.0.4/dbhome_1/lib -lm    `cat /opt/oracle/app/product/11.2.0.4/dbhome_1/lib/sysliblist` -ldl -lm   -L/opt/oracle/app/product/11.2.0.4/dbhome_1/lib /opt/oracle/app/product/11.2.0.4/dbhome_1/sysman/lib//s0nmectl.o -lnmectl -lclntsh -
INFO: L/opt/oracle/app/product/11.2.0.4/dbhome_1/lib  -L/opt/oracle/app/product/11.2.0.4/dbhome_1/sysman/lib/ -lnmemso -lcore11 -Wl,-rpath,/opt/oracle/app/product/11.2.0.4/dbhome_1/lib/:/opt/oracle/app/product/11.2.0.4/dbhome_1/sysman/lib/:/opt/oracle/app/product/11.2.0.4/dbhome_1/jdk/jre/lib/amd64/server:/opt/oracle/app/product/11.2.0.4/dbhome_1/jdk/jre/lib/amd64 -L/opt/oracle/app/product/11.2.0.4/dbhome_1/jdk/jre/lib/amd64/server -L/opt/oracle/app/product/11.2.0.4/dbhome_1/jdk/jre/lib/amd64 -z lazyload -ljava -
INFO: ljvm -lverify -z nolazyload -Wl,-rpath,/opt/oracle/app/product/11.2.0.4/dbhome_1/lib/:/opt/oracle/app/product/11.2.0.4/dbhome_1/sysman/lib/:/opt/oracle/app/product/11.2.0.4/dbhome_1/jdk/jre/lib/amd64/server:/opt/oracle/app/product/11.2.0.4/dbhome_1/jdk/jre/lib/amd64 -Wl,--allow-shlib-undefined    `cat /opt/oracle/app/product/11.2.0.4/dbhome_1/lib/sysliblist` -ldl -lm

INFO: /usr/bin/ld: warning: -z lazyload ignored.
/usr/bin/ld: warning: -z nolazyload ignored.
/usr/bin/ld: /opt/oracle/app/product/11.2.0.4/dbhome_1/sysman/lib//libnmectl.a(nmectlt.o): undefined reference to symbol 'B_DestroyKeyObject'
/usr/bin/ld: note: 'B_DestroyKeyObject' is defined in DSO /opt/oracle/app/product/11.2.0.4/dbhome_1/lib/libnnz11.so so try adding it to the linker command line
/opt/oracle/app/product/11.2.0.4/dbhome_1/lib/libnnz11.so: could not read symbols: Invalid operation

INFO: collect2: error: ld returned 1 exit status

INFO: make[1]: *** [/opt/oracle/app/product/11.2.0.4/dbhome_1/sysman/lib/emdctl] Error 1

INFO: make[1]: Leaving directory `/home/dhafner/oracle/app/product/11.2.0.4/dbhome_1/sysman/lib'

INFO: make: *** [emdctl] Error 2

INFO: End output from spawned process.
INFO: ----------------------------------
INFO: Exception thrown from action: make
Exception Name: MakefileException
Exception String: Error in invoking target 'agent nmhs' of makefile '/opt/oracle/app/product/11.2.0.4/dbhome_1/sysman/lib/ins_emagent.mk'. See '/opt/oracle/oraInventory/logs/installActions2013-08-28_08-44-20PM.log' for details.
Exception Severity: 1

To correct this error edit the file <ORACLE_HOME>/sysman/lib/ins_emagent.mk from

171 #===========================
172 #  emdctl
173 #===========================
174
175 $(SYSMANBIN)emdctl:
176         $(MK_EMAGENT_NMECTL)

to

171 #===========================
172 #  emdctl
173 #===========================
174
175 $(SYSMANBIN)emdctl:
176         $(MK_EMAGENT_NMECTL) -lnnz11

Now save and click “RETRY” in installer prompt. The installation should complete successful now

Oracle Database Patchset 11.2.0.4 released


On 27.08.2012 Oracle released the 11.2.0.4 patchset.

Actual the patchset is available for (29.08.2013)

  • Linux x86_64
  • Linux x86
  • Solaris x86_64
  • Solaris x86
  • Solaris SPARC (64Bit)
  • Solaris SPAR (32Bit)

Here an overview of the new features:

  1. Oracle Data Redaction
    See Oracle Database Advanced Security Administrator’s Guide for details
  2. Trace File Analyzer and Collector
    See Oracle Clusterware Administration and Deployment Guide for details
  3. RACcheck – The Oracle RAC Configuration Audit Tool
    See Oracle Real Application Clusters Administration and Deployment Guide for details
  4. Database Replay Support for Database Consolidation
    See Oracle Database Real Application Testing User’s Guide for details
  5. Dynamic Statistics
    See Oracle Database Performance Tuning Guide for details
  6. Optimization for Flashback Data Archive History Tables
    See Oracle Database Advanced Application Developer’s Guide for details
  7. New sqlnet.ora Parameter SSL_EXTENDED_KEY_USAGE
    See Oracle Database Advanced Security Administrator’s Guide for details
  8. New PrimaryLostWriteAction Property
    See Oracle Data Guard Broker for details
  9. ENABLE_GOLDENGATE_REPLICATION for Oracle GoldenGate
    See Oracle Database Reference for details

See For futher information refer to the 11.2.0.4 new features guide

Desupported Features:

The following features are desupported in Oracle Database 11g Release 2 (11.2):

  • The -cleanupOBase flag of the deinstallation tool is desupported. There is no replacement for this flag.
  • The DES, RC4, and MD5 algorithms are desupported.

See Oracle Database Upgrade Guide for details

Schedules and Roadmap:

This will be the terminal patchset for 11.2. Here the roadmap:

DB_Roadmap_Jan_2013_v4

For further information about Release Schedules and Maintenance refer to “Release Schedule of Current Database Releases (Doc ID 742060.1)”.

References:

  • 11.2.0.4 Patch Set – Availability and Known Issues (Doc ID 1562139.1)
  • Release Schedule of Current Database Releases (Doc ID 742060.1)
  • 11.2.0.4 Patch Set – List of Bug Fixes by Problem Type(Doc ID 1562142.1)
  • New Features Guide 11.2.0.4

Database 12c: Create Container Database


To create a CDB there are two methods to do so:

  1. Create CDB with DBCA
  2. Create CDB manually

1. Create CDB with DBCA

To create a CDB with DBCA , there is nothing special to do. If you install in Basic Mode, you are able to configure CDB on the start site:

createcdb1

If you are installing in Advanced Mode you are able on the second site:

createcdb2

2. Create CDB manually or with “CREATE DATABASE”

1. Setup init file with the according parameters. In my example I used the OFM creation method:

*.db_create_file_dest='/opt/oracle/app/oradata'
*.enable_pluggable_database=TRUE

2. Execute the “CREATE DATABASE” statement with the “ENABLE PLUGGABLE DATABASE”:

CREATE DATABASE db12ee2
USER SYS IDENTIFIED BY welcome1
USER SYSTEM IDENTIFIED BY welcome1
EXTENT MANAGEMENT LOCAL
DEFAULT TABLESPACE users
DEFAULT TEMPORARY TABLESPACE temp
UNDO TABLESPACE undotbs1
ENABLE PLUGGABLE DATABASE
   SEED
   SYSTEM DATAFILES SIZE 125M AUTOEXTEND ON NEXT 10M MAXSIZE UNLIMITED
   SYSAUX DATAFILES SIZE 100M;

3. Execute catcdb.sql

@?/rdbms/admin/catcdb.sql

This step is a problem right now, because the required file catcdb.sql is not shipped with the installation. The problem is already in progress:
Bug 17033183 – $OH/rdbms/admin/catcdb.sql is missing from 12c release (Doc ID 17033183.8)

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: ORA-27137: unable to allocate large pages to create a shared memory segment


On ODA Hugepages is activated by default.

For the deployment type “Oracle Enterprise Edition” (for single or active/passive configurations) the second node will not be correct configured.

This may be a problem:

>sqlplus / as sysdba 
 SQL*Plus: Release 11.2.0.3.0 Production on Sat Feb 16 00:43:20 2013
 Copyright (c) 1982, 2011, Oracle. All rights reserved.
 Connected to an idle instance.
 SQL> startup
 ORA-27137: unable to allocate large pages to create a shared memory segment
 Linux-x86_64 Error: 1: Operation not permitted
 SQL>

Per default at ODA 26000 Largepages (52000 MB) are configured:

>grep Huge /proc/meminfo 
 HugePages_Total: 26000
 HugePages_Free:  26000
 HugePages_Rsvd:  0
 HugePages_Surp: 0
 Hugepagesize: 2048 kB 

Here an Example:

Database SGA size Largepages
testdb1 20GB = 20GB * 1024 = 20480MB / 2MB (Hugepagesize) = 10240 Hugepages
testdb2 20GB = 20GB * 1024 = 20480MB / 2MB (Hugepagesize) = 10240 Hugepages
testdb3 10GB = 10GB * 1024 = 10240MB / 2MB (Hugepagesize) = 5120 Hugepages
testdb4 10GB = 10GB * 1024 = 10240MB / 2MB (Hugepagesize) = 5120 Hugepages
Sum: 60GB SGA == 30720 Largepages

The new calculated number must be added to /etc/sysctl.conf:

#vm.nr_hugepages=26000
vm.nr_hugepages=40000

Finally – as ROOT – execute sysctl -p to activate the new value.

Maybe you have to increase the memlock limits in /etc/security/limits.conf

The Oracle Database Appliance: Update & Patching


Patching or Updating an Oracle Database Appliance is normally an easy thing. The whole update procedure will be done in 4 steps.

  1. Unpacking patch to repository
  2. Patching Infrastructure (–infra)
    • Firmwares
    • ILOM
    • BIOS
    • Disks
  3. Patching Grid Infrastructure (–gi)
    • Oracle Grid Infrastructure
  4. Patching Databasehome and Databases (–database)
    • Database Homes and Databases

1. Check current version

[root@oak1 ~]# oakcli show version -detail
Reading the metadata. It takes a while...
System Version  Component Name            Installed Version         Supported Version        
--------------  ---------------           ------------------        -----------------        
2.6.0.0.0                                                                                    
                Controller                11.05.02.00               Up-to-date               
                Expander                  0342                      Up-to-date               
                SSD_SHARED                E12B                      Up-to-date               
                HDD_LOCAL                 SA03                      Up-to-date               
                HDD_SHARED                A700                      Up-to-date               
                ILOM                      3.0.16.22.b r78329        Up-to-date               
                BIOS                      12010310                  Up-to-date               
                IPMI                      1.8.10.5                  Up-to-date               
                HMP                       2.2.6.1                   Up-to-date               
                OAK                       2.6.0.0.0                 Up-to-date               
                OEL                       5.8                       Up-to-date               
                TFA                       2.5.1.4                   Up-to-date               
                GI_HOME                   11.2.0.3.6(16056266,      Up-to-date               
                                          16083653)                                          
                DB_HOME                   11.2.0.3.6(16056266,      Up-to-date               
                                          16083653)                                          
                ASR                       4.4                       Up-to-date

2. Copy software, unpack and deploy to repository with oakcli

[root@oak1 ~]# oakcli unpack -package p16760967_27000_Linux-x86-64.zip
Unpacking takes a while, pls wait....
Successfully unpacked the files to repository.

[root@oak2 ~]# oakcli unpack -package p16760967_27000_Linux-x86-64.zip
Unpacking takes a while, pls wait....
Successfully unpacked the files to repository.

3. Verify components to update

[root@oak1 ~]# oakcli update -patch 2.7.0.0.0 --verify
Component Name            Installed Version         Proposed Patch Version   
---------------           ------------------        -----------------        
Controller                11.05.02.00               Up-to-date               
Expander                  0342                      Up-to-date               
SSD_SHARED                E12B                      Up-to-date               
HDD_LOCAL                 SA03                      Up-to-date               
HDD_SHARED {                                                                 
[ c2d0,c2d2,c2d3,c2d      A700                      Up-to-date               
4,c2d5,c2d6,c2d7,c2d                                                         
8,c2d9,c2d10,c2d11,c                                                         
2d12,c2d13,c2d14,c2d                                                         
15,c2d16,c2d17,c2d18                                                         
,c2d19 ]                                                                     
[ c2d1 ]                  0B25                      Up-to-date               
             }                                                               
ILOM                      3.0.16.22.b r78329        3.0.16.22.c r80379       
BIOS                      12010310                  12010311                 
IPMI                      1.8.10.5                  Up-to-date               
HMP                       2.2.6.1                   2.2.6.2                  
OAK                       2.6.0.0.0                 2.7.0.0.0                
OEL                       5.8                       5.9                      
TFA                       2.5.1.4                   2.5.1.5                  
GI_HOME                   11.2.0.3.6(16056266,      11.2.0.3.7(16619892,     
                          16083653)                 16742216)                
DB_HOME                   11.2.0.3.6(16056266,      11.2.0.3.7(16619892,     
                          16083653)                 16742216)

4. Patch Infrastructure

[root@oak1 ~]# oakcli update -patch 2.7.0.0.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

Please enter the 'root' user password: 
Please re-enter the 'root' user password: 
INFO: Setting up the SSH..........done
INFO: Running pre-install scripts..........done
INFO: 2013-08-16 16:44:21: Running pre patch script for 2.7.0.0.0
INFO: 2013-08-16 16:44:37: Completed pre patch script for 2.7.0.0.0

INFO: 2013-08-16 16:44:51: ------------------Patching HMP-------------------------
SUCCESS: 2013-08-16 16:45:33: Successfully upgraded the HMP

INFO: 2013-08-16 16:45:34: ----------------------Patching OAK---------------------
SUCCESS: 2013-08-16 16:46:09: Succesfully upgraded OAK 

INFO: 2013-08-16 16:46:13: -----------------Installing / Patching  TFA-----------------
SUCCESS: 2013-08-16 16:48:12: Successfully updated / installed the TFA
...

INFO: 2013-08-16 16:48:13: ------------------Patching OS-------------------------
INFO: 2013-08-16 16:48:28: Clusterware is running on one or more nodes of the cluster
INFO: 2013-08-16 16:48:28: Attempting to stop clusterware and its resources across the cluster
SUCCESS: 2013-08-16 16:50:58: Successfully stopped the clusterware

ERROR: 2013-08-16 16:51:04: Failed to run /usr/bin/yum update --disablerepo=* --enablerepo=ODA_REPOS_LOC -y 
ERROR: 2013-08-16 16:51:05: Failed to update the OS

## Note: Leaving /var/opt/SUNWsasm/configuration directory in place
## to maintain settings on package upgrade.
## For a complete uninstall, manually remove this directory.

INFO: 2013-08-16 16:51:26: ----------------------Patching ASR---------------------
SUCCESS: 2013-08-16 16:51:56: Succesfully upgraded ASR 

INFO: 2013-08-16 16:51:57: ----------------------Patching IPMI---------------------
INFO: 2013-08-16 16:51:57: IPMI is already upgraded or running with latest version 

INFO: 2013-08-16 16:52:05: ----------------Patching the Storage-------------------
INFO: 2013-08-16 16:52:05: ....................Patching SSDs...............
INFO: 2013-08-16 16:52:05: Disk : d20  is already running with : ZeusIOPs G3 E12B
INFO: 2013-08-16 16:52:06: Disk : d21  is already running with : ZeusIOPs G3 E12B
INFO: 2013-08-16 16:52:06: Disk : d22  is already running with : ZeusIOPs G3 E12B
INFO: 2013-08-16 16:52:06: Disk : d23  is already running with : ZeusIOPs G3 E12B
INFO: 2013-08-16 16:52:06: ....................Patching shared HDDs...............
INFO: 2013-08-16 16:52:06: Disk : d0  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:06: Disk : d1  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:06: Disk : d2  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:06: Disk : d3  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:07: Disk : d4  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:07: Disk : d5  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:07: Disk : d6  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:07: Disk : d7  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:07: Disk : d8  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:07: Disk : d9  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:07: Disk : d10  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:08: Disk : d11  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:08: Disk : d12  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:08: Disk : d13  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:08: Disk : d14  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:08: Disk : d15  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:08: Disk : d16  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:08: Disk : d17  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:09: Disk : d18  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:09: Disk : d19  is already running with : HUS1560SCSUN600G A700
INFO: 2013-08-16 16:52:09: ....................Patching local HDDs...............
INFO: 2013-08-16 16:52:09: Disk : c0d0  is already running with : ST95001N SA03
INFO: 2013-08-16 16:52:09: Disk : c0d1  is already running with : ST95001N SA03
INFO: 2013-08-16 16:52:09: ....................Patching Expanders...............
INFO: 2013-08-16 16:52:09: Expander : x0  is already running with : T4 Storage 0342
INFO: 2013-08-16 16:52:09: Expander : x1  is already running with : T4 Storage 0342
INFO: 2013-08-16 16:52:10: ....................Patching Controllers...............
INFO: 2013-08-16 16:52:10: No-update for the Controller: c0 
INFO: 2013-08-16 16:52:10: Controller : c1  is already running with : 0x0072 11.05.02.00
INFO: 2013-08-16 16:52:10: Controller : c2  is already running with : 0x0072 11.05.02.00
INFO: 2013-08-16 16:52:10: ------------Finished the storage Patching------------

INFO: 2013-08-16 16:52:11: -----------------Patching Ilom & Bios-----------------
INFO: 2013-08-16 16:52:11: Getting the ILOM Ip address
INFO: 2013-08-16 16:52:11: Updating the Ilom using LAN+ protocol
INFO: 2013-08-16 16:52:13: Updating the ILOM. It takes a while
INFO: 2013-08-16 16:56:42: Verifying the updated Ilom Version, it may take a while if ServiceProcessor is booting
INFO: 2013-08-16 16:56:43: Waiting for the service processor to be up

SUCCESS: 2013-08-16 17:00:22: Successfully updated the ILOM with the firmware 3.0.16.22.c r80379

INFO: Patching the infrastructure on node: oak2 , it may take upto 30 minutes. Please wait...............done
INFO: Infrastructure patching summary on node: 192.168.16.24
SUCCESS: 2013-08-16 17:17:45:  Successfully upgraded the HMP
SUCCESS: 2013-08-16 17:17:45:  Succesfully updated the OAK
SUCCESS: 2013-08-16 17:17:45:  Successfully updated the TFA
SUCCESS: 2013-08-16 17:17:45:  Successfully upgraded the OS
SUCCESS: 2013-08-16 17:17:45:  Succesfully updated the ASR
INFO: 2013-08-16 17:17:45:  IPMI is already upgraded
INFO: 2013-08-16 17:17:45:  Storage patching summary
SUCCESS: 2013-08-16 17:17:45:  No failures during storage upgrade
SUCCESS: 2013-08-16 17:17:45:  Successfully updated the ILOM & Bios
INFO: Infrastructure patching summary on node: 192.168.16.25
SUCCESS: 2013-08-16 17:17:45:  Successfully upgraded the HMP
SUCCESS: 2013-08-16 17:17:45:  Succesfully updated the OAK
SUCCESS: 2013-08-16 17:17:45:  Successfully upgraded the OS
INFO: 2013-08-16 17:17:45:  IPMI is already upgraded
INFO: 2013-08-16 17:17:45:  Storage patching summary
SUCCESS: 2013-08-16 17:17:45:  No failures during storage upgrade
SUCCESS: 2013-08-16 17:17:45:  Successfully updated the ILOM & Bios
INFO: Running post-install scripts............done
INFO: Some of the patched components require node reboot. Rebooting the nodes
INFO: Setting up the SSH............done

NOTICE: You can use the –noreboot switch to avoid rebooting at the end. Sometimes both Nodes will be rebooted at the same time. So you have the chance to do node by node reboot

5. Patching of Grid Infrastructure

[root@oak1 ~]# oakcli update -patch 2.7.0.0.0 --gi

Please enter the 'root' user password: 
Please re-enter the 'root' user password: 

Please enter the 'grid' user password: 
Please re-enter the 'grid' user password: 
Given passwords are not matching
Please re-enter the passwords

Please enter the 'grid' user password: 
Please re-enter the 'grid' user password: 
INFO: Setting up the SSH
..........done
INFO: Running pre-install scripts
..........done
INFO: 2013-08-16 18:06:41: Running pre patch script for 2.7.0.0.0
INFO: 2013-08-16 18:06:44: Completed pre patch script for 2.7.0.0.0
...
...
..........done
...
SUCCESS: All nodes in /opt/oracle/oak/temp_clunodes.txt are pingable and alive.
INFO: 2013-08-16 18:07:12: Setting up the ssh for grid user
..........done
...
SUCCESS: All nodes in /opt/oracle/oak/temp_clunodes.txt are pingable and alive.
INFO: 2013-08-16 18:07:32: Patching the GI home on node oak1
INFO: 2013-08-16 18:07:32: Updating the opatch
INFO: 2013-08-16 18:08:31: Performing the conflict checks
SUCCESS: 2013-08-16 18:08:46: Conflict checks passed for all the homes
INFO: 2013-08-16 18:08:46: Checking if the patch is already applied on any of the homes
INFO: 2013-08-16 18:08:49: No home is already up-to-date
SUCCESS: 2013-08-16 18:09:25: Successfully stopped the dbconsoles
SUCCESS: 2013-08-16 18:09:40: Successfully stopped the EM agents
INFO: 2013-08-16 18:09:45: Applying patch on the homes: /u01/app/11.2.0.3/grid
INFO: 2013-08-16 18:09:45: It may take upto 15 mins
SUCCESS: 2013-08-16 18:21:54: Successfully applied the patch on home: /u01/app/11.2.0.3/grid
SUCCESS: 2013-08-16 18:22:08: Successfully started the dbconsoles
SUCCESS: 2013-08-16 18:22:24: Successfully started the EM Agents
INFO: 2013-08-16 18:22:24: Patching the GI home on node oak2
...
..........done
INFO: GI patching summary on node: oak1
SUCCESS: 2013-08-16 18:35:03:  Successfully applied the patch on home /u01/app/11.2.0.3/grid
INFO: GI patching summary on node: oak2
SUCCESS: 2013-08-16 18:45:28:  Successfully applied the patch on home /u01/app/11.2.0.3/grid
INFO: Running post-install scripts
..........done
INFO: Setting up the SSH
..........done

Notice: Patching GI will be done node by node

6. Patching database homes and databases

[root@oak1 ~]# oakcli update -patch 2.7.0.0.0 --database

Please enter the 'root' user password: 
Please re-enter the 'root' user password: 

Please enter the 'oracle' user password: 
Please re-enter the 'oracle' user password: 
INFO: Setting up the SSH
..........done
INFO: Running pre-install scripts
..........done
INFO: 2013-08-16 18:59:18: Running pre patch script for 2.7.0.0.0
INFO: 2013-08-16 18:59:21: Completed pre patch script for 2.7.0.0.0
...
...
..........done
...
SUCCESS: All nodes in /opt/oracle/oak/temp_clunodes.txt are pingable and alive.
INFO: 2013-08-16 18:59:47: Getting the possible database homes for patching
...
INFO: 2013-08-16 18:59:53: Patching 11.2.0.3 Database homes on node oak1

Found the following 11.2.0.3 homes possible for patching:

HOME_NAME                      HOME_LOCATION                                          
---------                      -------------                                          
OraDb11203_home1               /u01/app/oracle/product/11.2.0.3/dbhome_1              

[Please note that few of the above database homes may be already up-to-date. They will be automatically ignored]

Would you like to patch all the above homes: Y | N ? :y
INFO: 2013-08-16 18:59:55: Setting up ssh for the user oracle
..........done
...
SUCCESS: All nodes in /opt/oracle/oak/temp_clunodes.txt are pingable and alive.
INFO: 2013-08-16 19:00:15: Updating the opatch
INFO: 2013-08-16 19:01:56: Performing the conflict checks
SUCCESS: 2013-08-16 19:02:12: Conflict checks passed for all the homes
INFO: 2013-08-16 19:02:12: Checking if the patch is already applied on any of the homes
INFO: 2013-08-16 19:02:16: No home is already up-to-date
SUCCESS: 2013-08-16 19:02:48: Successfully stopped the dbconsoles
SUCCESS: 2013-08-16 19:03:03: Successfully stopped the EM agents
INFO: 2013-08-16 19:03:08: Applying patch on the homes: /u01/app/oracle/product/11.2.0.3/dbhome_1
INFO: 2013-08-16 19:03:08: It may take upto 15 mins
SUCCESS: 2013-08-16 19:09:07: Successfully applied the patch on home: /u01/app/oracle/product/11.2.0.3/dbhome_1
SUCCESS: 2013-08-16 19:09:23: Successfully started the dbconsoles
SUCCESS: 2013-08-16 19:09:40: Successfully started the EM Agents
INFO: 2013-08-16 19:09:43: Patching 11.2.0.3 Database homes on node oak2
INFO: 2013-08-16 19:14:10: Running the catbundle.sql
INFO: 2013-08-16 19:14:12: Running catbundle.sql on the database testdb1
INFO: 2013-08-16 19:14:24: Running catbundle.sql on the database testdb2
..........done

INFO: DB patching summary on node: oak1
SUCCESS: 2013-08-16 19:15:14:  Successfully applied the patch on home /u01/app/oracle/product/11.2.0.3/dbhome_1

INFO: DB patching summary on node: oak2
SUCCESS: 2013-08-16 19:15:14:  Successfully applied the patch on home /u01/app/oracle/product/11.2.0.3/dbhome_1

INFO: Setting up the SSH
..........done
Notice: Patching GI will be done node by node

7. Verfiy update

[root@oak1 ~]# oakcli update -patch 2.7.0.0.0 --verify
                Component Name            Installed Version         Proposed Patch Version   
                ---------------           ------------------        -----------------        
                Controller                11.05.02.00               Up-to-date               
                Expander                  0342                      Up-to-date               
                SSD_SHARED                E12B                      Up-to-date               
                HDD_LOCAL                 SA03                      Up-to-date               
                HDD_SHARED                A700                      Up-to-date               
                ILOM                      3.0.16.22.c r80379        Up-to-date               
                BIOS                      12010311                  Up-to-date               
                IPMI                      1.8.10.5                  Up-to-date               
                HMP                       2.2.6.2                   Up-to-date               
                OAK                       2.7.0.0.0                 Up-to-date               
                OEL                       5.9                       Up-to-date               
                TFA                       2.5.1.5                   Up-to-date               
                GI_HOME                   11.2.0.3.7(16619892,      Up-to-date               
                                          16742216)                                          
                DB_HOME                   11.2.0.3.7(16619892,      Up-to-date               
                                          16742216)