patch apply failed for home /u01/app/11.2.0.3/grid

During GI & OH patching the error was appeared:
patch ...  apply  failed  for home  /u01/app/11.2.0.3/grid

Here the full log:
[root@ed01db02 yum.repos.d]# opatch auto /store/13734832 -och /u01/app/11.2.0.3/grid
Executing /usr/bin/perl /u01/app/11.2.0.3/grid/OPatch/crs/patch112.pl -patchdir /store -patchn 13734832 -och /u01/app/11.2.0.3/grid -paramfile /u01/app/11.2.0.3/grid/crs/install/crsconfig_params
opatch auto log file location is /u01/app/11.2.0.3/grid/OPatch/crs/../../cfgtoollogs/opatchauto2012-05-23_17-02-42.log
Detected Oracle Clusterware install
Using configuration parameter file: /u01/app/11.2.0.3/grid/crs/install/crsconfig_params
OPatch  is bundled with OCM, Enter the absolute OCM response file path:
/tmp

Unable to determine if /u01/app/11.2.0.3/grid is shared oracle home
Enter 'yes' if this is not a shared home or if the prerequiste actions are performed to patch this shared home (yes/no):yes
Successfully unlock /u01/app/11.2.0.3/grid
patch /store/13734832/13734832  apply  failed  for home  /u01/app/11.2.0.3/grid
ACFS-9300: ADVM/ACFS distribution files found.
ACFS-9312: Existing ADVM/ACFS installation detected.
ACFS-9314: Removing previous ADVM/ACFS installation.
ACFS-9315: Previous ADVM/ACFS components successfully removed.
ACFS-9307: Installing requested ADVM/ACFS software.
ACFS-9308: Loading installed ADVM/ACFS drivers.
ACFS-9321: Creating udev for ADVM/ACFS.
ACFS-9323: Creating module dependencies - this may take some time.
ACFS-9154: Loading 'oracleoks.ko' driver.
ACFS-9154: Loading 'oracleadvm.ko' driver.
ACFS-9154: Loading 'oracleacfs.ko' driver.
ACFS-9327: Verifying ADVM/ACFS devices.
ACFS-9156: Detecting control device '/dev/asm/.asm_ctl_spec'.
ACFS-9156: Detecting control device '/dev/ofsctl'.
ACFS-9309: ADVM/ACFS installation correctness verified.
CRS-4123: Oracle High Availability Services has been started.

The error raised because of mistake in my response:
OPatch  is bundled with OCM, Enter the absolute OCM response file path:
/tmp


The right answer is /tmp/ocm.rsp.

How do register an Exadata with Unbreakable Linux Network (ULN)?

I am doing the installation of last FSQDPE patch 11.2.3.1.0 at April 2012.

Unlike previous patches the new the 11.2.3.1.0 Exadata Storage Server patch requires that the OS Linux on DB  nodes will be updated.  In section "6.1 Updating Oracle Linux Database Servers in Oracle Exadata Database Machine X2-2" Oracle say to register an Exadata with ULN.
My system is fresh (installed in March 2012) and have not been registered in ULN and have no patches yet.

So I get the error for YUM command:

[root@ed01db01 Server]# yum --enablerepo=exadata_dbserver_11.2.3.1.0_x86_64_base repolist
Error getting repository data for exadata_dbserver_11.2.3.1.0_x86_64_base, repository not found

The YUM Repository Setup give the advice:
Register the machine on the Unbreakable Linux Network with commands:

rpm --import /usr/share/rhn/RPM-GPG-KEY

up2date-nox --register

But there are no RPM-GPG-KEY file and up2date command in the fresh Exdata!

Another step was ound in Metalink:
NOTE 1234710.1, "Enable database hosts in Exadata Database Machine for using up2date or yum and vncserver"

This note offers to run this command to install up2date:

rpm -Uhv --nodeps curl-7.15.5-9.el5.x86_64.rpm gnupg-1.4.5-14.x86_64.rpm rhnlib-2.5.22-3.el5.noarch.rpm rhpl-0.194.1-1.0.2.x86_64.rpm rpm-python-4.4.2.3-18.el5.x86_64.rpm up2date-5.10.1-41.8.el5.x86_64.rpm

After it:
[root@ed01db01 Server]# rpm -Uhv --nodeps curl-7.15.5-9.el5.x86_64.rpm gnupg-1.4.5-14.x86_64.rpm rhnlib-2.5.22-3.el5.noarch.rpm rhpl-0.194.1-1.0.2.x86_64.rpm rpm-python-4.4.2.3-18.el5.x86_64.rpm up2date-5.10.1-41.8.el5.x86_64.rpm
warning: curl-7.15.5-9.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ########################################### [100%]
        package rpm-python-4.4.2.3-18.el5.x86_64 is already installed

But up2date have not been installed after this cmd!
One modification was required to finally set up up2date:

[root@ed01db01 Server]# rpm -Uhv --nodeps gnupg-1.4.5-14.x86_64.rpm rhnlib-2.5.22-3.el5.noarch.rpm rhpl-0.194.1-1.0.2.x86_64.rpm  up2date-5.10.1-41.8.el5.x86_64.rpm
warning: gnupg-1.4.5-14.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ########################################### [100%]
   1:rhpl                   ########################################### [ 25%]
   2:gnupg                  ########################################### [ 50%]
   3:rhnlib                 ########################################### [ 75%]
   4:up2date                ########################################### [100%]
[root@ed01db01 Server]#

Only ater such long way we have working up2date !

And the key file appeared:
[root@ed01db02 Server]# ls -l /usr/share/rhn/RPM-GPG-KEY
-rw-r--r-- 1 root root 1397 Nov 11  2007 /usr/share/rhn/RPM-GPG-KEY

And next step ewre executed well:
[root@ed01db01 Server]# rpm --import /usr/share/rhn/RPM-GPG-KEY
[root@ed01db01 Server]#

And the up2date --register works well.

Right Parallel degreee: 300 times more !

Ранее, я уже писал  о большой мощности ввода-вывода в Экзадате и
необходимости задействовать эти мощности путем параллельного выполнения запросов.
Теперь реальный пример того, как это работает в приложениях, после установки правильной степени параллельности: