Alejandro Vargas

Exadata is the best database machine available to run every Oracle database workload. But many times, within Exadata proliferate a large number of test and development databases, that do not require the special features available with Exadata, the Storage cells and ASM.

One possibility is to move these large and less demanding databases to a storage layer that is also less expensive, ZFS is a perfect match, can be connected to Exadata, available to RAC databases, and connected via InfiniBand or RoCE for managing RMAN backups.

Its implementation is fast and simple, is fully explained on a few MOS documents:

1: Set Up and Configure Exadata X8M Backup with ZFS Storage ZS7-2 (Doc ID 2635423.1)

This document describe the hardware deployment that is followed by Oracle Field Service enginneers

2: Guidelines When Using ZFS Storage in an Exadata Environment (Doc ID 2087231.1)

This document describe how to setup the Best Practices for Data Warehousing (DWH), for Online Transactional Processing (OLTP) Type Workloads; explain configuring
projects and shares on ZFS Storage and mounting shares on
Exadata and configuring the oranfstab.

Once these tasks have been completed you can create a test database on the ZFS mount points and query v$dnfs_servers, if you see the 2 ZFS heads reported as Dnfs servers then you can start moving your databases from ASM to ZFS.

3: "Exadata Hybrid Columnar Compression" Is Not Working in Exadata Using ZFS Storage Appliance (ZFSSA) and Failing with [ORA-64307: Exadata Hybrid Columnar Compression is not Supported for Tablespaces on This Storage Type] (Doc ID 2393108.1)

If you need to use HCC, there is an additional step to run, setting up SNMP on the ZFS heads. for this please follow the instructions on this note. Once SNMP is setup on the heads you need to restart the databases to be able to use HCC:

 

I've been adding storage cells to Exadatas for a long while, usually newer storage cells to a bit older Exadata.

Yesterday I had the oposite case, moving six X3-2 cells to an X-7 Exadata.

This mix of old and new storage cells is supported and can be done, but it took me a while to understand that the syntax of /opt/oracle.cellos/cell.conf had to remain as X-3.

Usually I take the cell.conf from a working cell, and edit it to match the names and IP's on the cell to add, then run ipconf with the new version of cell.conf to setup the network.

Having done this, when validating the new cell.conf it didn't pass:

Active bond ib setting value in /opt/oracle.cellos/cell.conf "yes" must match the runtime configuration: FAILED
Master interface ib0 must be defined in /opt/oracle.cellos/cell.conf                : FAILED
Master interface ib1 must be defined in /opt/oracle.cellos/cell.conf                : FAILED
1 configured bond over ib interfaces must be defined in /opt/oracle.cellos/cell.conf: FAILED
[Error]: Overall status of verification of /opt/oracle.cellos/cell.conf             : FAILED

That led me to check and find that active-active InfiniBand, without a bond, is not supported on X3-2 cells.

If you need to change the IP's and you do that editing the cell.conf file, then you must use a copy of the same X-3 cell.conf, and change the IP's there, and use the bonded InfiniBand networks with only one IP.

Note that you may succeed to manually configure active-active with 2 IP's, without a bond, as I did, including having the cell to recognize the two interconnects and bring up all cell services, but the ipconf validation will fail, and if you are going to upgrade the cell, then patchmgr validation will fail as well.

In the end, using the X3-2 cell.conf I've changed the IP's, upgraded the cells from 12.2.1.0 to 20.1.3.0, initialize celldisks and griddisks and created a new ASM diskgroup on these six old storage cells, that provided 100TB of usable space to my customer to run some development and test databases.

State    Total_MB    Free_MB   Req_mir_free_MB   Usable_file_MB  Name
MOUNTED    203497344      203493912 2826352                      100333780              DATA1/

Synchronizing a MySQL slave database on the BDA is something I've done several times as part of the pre-requisites of a BDA upgrade.

Is a simple task and there are two goods douments that provide a step by step guide to implement it.

My favorite one is Doc 2152683.1, because almost does not affect online work, except for the time it takes to dump the Master database.

• How to Reset MySQL Slave Replication without Full BDA Cluster Downtime (Doc ID 2152683.1)

If downtime is possible then Doc 2237773.1

• How to Restore A MySQL Master Which Has Stopped Generating Binary Log Files and/or Reset MySQL Slave
  Replication With Cluster Downtime on Oracle Big Data Appliance (Doc ID 2237773.1)

Now the reason I'm writing this post is not to remind about these documents, but to tell about a case I had recently, 2 issues were there, that affected the procedure:

1. The MySQL master was, in MySQL terms, quite big: about 200GB.
   1. The problem here is the time it takes to dump such a big MySQL database. Problematic for a cluster with minimal downtime requirements.
   2. Even though the cluster remains up and hdfs activities can continue, we have to lock the tables for read and this affect hue/hive/cloudera manager activities
2. At some time in the past was introduced on the Slave MySQL configuration file /etc/my.cnf the parameter innodb_force_recovery=2. This is used to force open a database that has some level of corruption, and should never be used on a BDA Slave database.

About case 1:

The reason for a very big MySQL database many times is related to a long Cloudera Navigator retention time, in the case of my customer was 60 days, that amounted for about 160GB of data.

By reducing on Cloudera Manager the parameter Navigator Audit Server Data Expiration Period  = 60 day(s) ​​​​​​ to 7 days, instead of 60, we reduced the size of the MySQL dump to 30GB, it took about 30 minutes to create the dump.

About case 2:

When reaching the step of importing the dump into the slave, still I havent noticed the presence of innodb_force_recovery=2 on /etc/my.cnf , then I've got this error:

# mysql -uroot -p -h$mysqlslavehost < $dumpdir/mysqldump.sql | tee $dumpdir/mysqlimport.out
ERROR 1881 (HY000) at line 2834: Operation not allowed when innodb_forced_recovery > 0

Removing the parameter from /etc/my.cnf is not enough, after many different trials I understood the only way out of this situation is to reinitialize the slave. 

Oracle support helped me with these steps:

1.  Shut down MySQL

# service mysql stop

2.  Check the innodb_force_recovery line has been removed from /etc/my.cnf

# grep innodb_force_recovery /etc/my.cnf

3.  Remove all files and subdirectories from the MySQL datadir

# rm -rf /var/lib/mysql/*  (confirm that you are on the MySQL Slave server before pressing enter)

4.  If the slave is running 5.6, as was my case, run "mysql_install_db" from the bash shell.

# mysql_install_db

After that I was able to start the slave and continue with the synchronization procedure.

One additional note, after reinitialization with mysql_install_db, root access to the slave was possible without using a password.

Only after the import was completed and after running the START SLAVE; comand, root password was resynchronized and enforced again.

 

 

OEDACLI is a powerful administration tool for Exadata, one of the actions more appreciated by customers is adding a new database home, this is a summary of the steps required:

•     invoque oedacli (can be done on Windows or Linux)
  •     on windows is located on the same directory from where you run the graphic version of OEDA
  •     on Linux is located at /u01/install/linux-x64 on a physical installation
•     load the xml file

         oedacli> load file name=test_Systems-x8m.xml
         SUCCESS - file loaded OK
         Customer : test Systems - 000

•     run the add databasehome, save action and merge actions commands (will edit the xml in memory adding the new oracle home)

        oedacli> ADD DATABASEHOME OWNER='oracle' DBVERSION='12.1.0.2.170418' DBHOMENAME='dbhome_2' DBHOMELOC='/u01/app/oracle/product/12.1.0.2/dbhome_2' WHERE CLUSTERNUMBER=1
        oedacli> save action
        oedacli> merge actions
         processMerge
         processMergeActions
         Merging Action : ADD DATABASEHOME OWNER='oracle' DBVERSION='12.1.0.2.170418' DBHOMENAME='dbhome_2' DBHOMELOC='/u01/app/oracle/product/12.1.0.2/dbhome_2' WHERE CLUSTERNUMBER=1
         Merging ADD DATABASEHOME
         Action Validated and Merged OK

•     run the list database homes command to see the patch numbers required by this version, look at the patch numbers of the version you choose to add, in this example 12.1.0.2.170418

        oedacli> list databasehomes
           version : "ZipInstall"
          cluster :
            id : "Cluster-cb3ad0db4-e22a-3be6-bf88-824a5a425df3_id"
          databaseHomeName : "DbHome_1"
          databaseSwOwner : "e9976514-060b-37a4-036c-2199cea027cf"
          databaseVersion : "19.5.0.0.191015"
          databaseHomeLoc : "/u01/app/oracle/product/19.0.0.0/dbhome_1"
          inventoryLocation : "/u01/app/oraInventory"
          installType : "rac_database"
          language : "all_langs"
          machines :
            machine :
              machine :
              id : "x8mcompute01_id"
              machine :
              id : "x8mcompute02_id"
          patches :
            patch :
              patchNumber : "30116789"
              patchNumber : "30128191"
              patchNumber : "30165493"
              patchNumber : "30165503"
          basedir : "/u01/app/oracle"
          id : "DbHome_4588acdc-e74a-a434-f81d-faa6b9c33a84_id"
          version : "ZipInstall"
          cluster :
            id : "Cluster-cb3ad0db4-e22a-3be6-bf88-824a5a425df3_id"
          databaseHomeName : "dbhome_2"
          databaseSwOwner : "e9976514-060b-37a4-036c-2199cea027cf"
          databaseVersion : "12.1.0.2.170418"
          databaseHomeLoc : "/u01/app/oracle/product/12.1.0.2/dbhome_2"
          inventoryLocation : "/u01/app/oraInventory"
          language : "all_langs"
          machines :
            machine :
              machine :
              id : "x8mcompute01_id"
              machine :
              id : "x8mcompute02_id"
          patches :
            patch :
              patchNumber : "25433352"
              patchNumber : "20641213"
              patchNumber : "21923026"
              patchNumber : "24944847"
              patchNumber : "25437695"
              patchNumber : "26729494"
              patchNumber : "28305362"
              patchNumber : "28683167"
          basedir : "/u01/app/oracle"
          useZfs : "false"
          id : "Cluster-cb3ad0db4-e22a-3be6-bf88-824a5a425df3_databaseHome1"

•     Download the patches from MOS and upload them to the /u01/install/linux-x64/Workdir directory.
•     If you run the oedacli on Windows save the xml to a new configuration, upload it to the /u01/install/linux-x64 directory and start oedacli from there to deploy the new database home

        oedacli> save file name='test-new-config.xml'
         File : test-new-config.xml saved OK

    Run the Deploy Actions 12.1.0.2.170418 command on the exadata, it will install the new oracle home

        oedacli> load file name=test-new-config.xml
         SUCCESS - file loaded OK
         Customer : test Systems - 000

        oedacli> deploy actions
         Deploying Action ID : 1 ADD DATABASEHOME OWNER='oracle' DBVERSION='12.1.0.2.170418' DBHOMENAME='dbhome_2' DBHOMELOC='/u01/app/oracle/product/12.1.0.2/dbhome_2' WHERE CLUSTERNUMBER=1
         Deploying ADD DATABASEHOMEOn 08/01/2020 03:10
        ... ...  ...

NOTES:

The xml will have these new section:

<actions>

        <action id="1" merged="true" deployed="false">

            <subCommand>ADD DATABASEHOME OWNER='oracle' DBVERSION='12.1.0.2.170418' DBHOMELOC='/u01/app/oracle/product/12.1.0.2/dbhome_2' WHERE CLUSTERNUMBER=1</subCommand>

        </action>

    </actions>

 

AND

 

<databaseHome id="Cluster-cb3ad0db4-e22a-3be6-bf88-824a5a425df3_databaseHome1">

                <version>ZipInstall</version>

                <cluster id="Cluster-cb3ad0db4-e22a-3be6-bf88-824a5a425df3_id"/>

                <databaseHomeName>dbhome_2</databaseHomeName>

                <databaseSwOwner>e9976514-060b-37a4-036c-2199cea027cf</databaseSwOwner>

                <databaseVersion>12.1.0.2.170418</databaseVersion>

                <databaseHomeLoc>/u01/app/oracle/product/12.1.0.2/dbhome_2</databaseHomeLoc>

                <inventoryLocation>/u01/app/oraInventory</inventoryLocation>

                <language>all_langs</language>

                <machines>

                    <machine id="tlvx8mcompute01_id"/>

                    <machine id="tlvx8mcompute02_id"/>

                </machines>

                <patches>

                    <patch>

                        <patchNumber>25433352</patchNumber>

                    </patch>

                    <patch>

                        <patchNumber>20641213</patchNumber>

                    </patch>

                    <patch>

                        <patchNumber>21923026</patchNumber>

                    </patch>

                    <patch>

                        <patchNumber>24944847</patchNumber>

                    </patch>

                    <patch>

                        <patchNumber>25437695</patchNumber>

                    </patch>

                    <patch>

                        <patchNumber>26729494</patchNumber>

                    </patch>

                    <patch>

                        <patchNumber>28305362</patchNumber>

                    </patch>

                    <patch>

                        <patchNumber>28683167</patchNumber>

                    </patch>

                </patches>

                <basedir>/u01/app/oracle</basedir>

                <useZfs>false</useZfs>

            </databaseHome>

 

Kerberos and Sentry help us defining access privileges for a limited set of object living on HDFS

We can extend the control by using access control lists, ACL's 

Requesting the ACL's on a directory will show us if "dfs.namenode.acls.enabled" is set to tru on HDFS:

[root@linux-x64]# hdfs dfs -getfacl /user
# file: /user
# owner: hdfs
# group: supergroup

getfacl: The ACL operation has been rejected.  Support for ACLs has been disabled by setting dfs.namenode.acls.enabled to false.

In this case as it is set to false we need to enable it, for this we go to Cloudera Manager > HDFS > Configuration and search for "dfs.namenode.acls.enabled" and we mark it as enabled.

We need to restart the stale services to enable ACL's

First I'll create a new user for testing

[root@sf_D_DRIVE]# adduser avargas

[root@media]# grep avargas /etc/passwd avargas:x:502:504::/home/avargas:/bin/bash Then I will create a user hdfs a directory inside HDFS for user avargas [root@media]# sudo su -hdfs -bash-4.1$ hdfs dfs -mkdir /user/avargas -bash-4.1$ hdfs dfs -ls /user Found 9 items drwxr-xr-x   - hdfs     supergroup          0 2019-04-29 12:42 /user/avargas drwxr-xr-x   - cloudera cloudera            0 2019-01-24 08:45 /user/cloudera drwxr-xr-x   - mapred   hadoop              0 2018-12-24 23:39 /user/history drwxrwxrwx   - hive     supergroup          0 2017-10-23 09:17 /user/hive drwxrwxrwx   - hue      supergroup          0 2018-12-19 07:44 /user/hue drwxrwxrwx   - oozie    supergroup          0 2017-10-23 09:16 /user/oozie drwxrwxrwx   - root     supergroup          0 2017-10-23 09:16 /user/root drwxr-xr-x   - hdfs     supergroup          0 2017-10-23 09:17 /user/spark As the owner user hdfs I'll assign rwx permissions on the directory /user/avargas to user avargas sh-4.1$ hdfs dfs -setfacl -m user:avargas:rwx /user/avargas -bash-4.1$ hdfs dfs -getfacl /user/avargas # file: /user/avargas # owner: hdfs # group: supergroup user::rwx user:avargas:rwx group::r-x mask::rwx other::r-x Now I'll upload a file as user avargas root@sf_D_DRIVE]# su - avargas [avargas@~]$ hdfs dfs -ls /user > filelist.txt [avargas@~]$ hdfs dfs -put filelist.txt /user/avargas File /user/avargas/filelist is owned by user avargas:supergroup [avargas@~]$ hdfs dfs -ls /user/avargas Found 1 items -rw-r--r--   1 avargas supergroup        680 2019-04-29 13:26 /user/avargas/filelist.txt Directory /user/avargas still owned by hdfs:supergroup, but note the + sign indicating additional permissions assigned on it: [avargas@~]$ hdfs dfs -ls /user | grep avargas drwxrwxr-x+  - hdfs     supergroup          0 2019-04-29 13:26 /user/avargas We can also set ACL’s for several users and groups on a single command

-bash-4.1$ hdfs dfs -setfacl -m user:avargas:rwx,user:hadoop:rwx,group::rwx,other::rwx /user/avargas

-bash-4.1$ hdfs dfs -getfacl /user/avargas
# file: /user/avargas
# owner: hdfs
# group: supergroup
user::rwx
user:avargas:rwx
user:hadoop:rwx
group::rwx
mask::rwx
other::rwx

Note that permissions were not changed for a file

-bash-4.1$ hdfs dfs -ls /user/avargas
Found 1 items
-rw-r--r--   1 avargas supergroup        680 2019-04-29 13:26 /user/avargas/filelist.txt

We can set ACL’s for several users and groups and recursively on all folders and files using the -R flag

-bash-4.1$ hdfs dfs -setfacl -m -R user:avargas:rwx,user:hadoop:rwx,group::rwx,other::rwx /user/avargas

-bash-4.1$ hdfs dfs -ls /user/avargas
Found 1 items
-rw-rwxrwx+  1 avargas supergroup        680 2019-04-29 13:26 /user/avargas/filelist.txt

Whenever we run a BDA upgrade we see as one of the prerequisites checks, to have the httpd service up and running on the first node of the cluster

- The httpd service must be started on Node 1 of the cluster. It should be stopped on all other nodes.

This is only needed during cluster upgrade or reconfiguration, but it is recommended to have it running at all times.

The reason for that is because we will run yum from every node in the cluster pointing to the repository that is created on node 1 when we deploy the bundle with the new release.

On /etc/yum.repos.d/bda.repo we can see that baseurl is using the first node and http protocol:

-  baseurl=http://<node01.domain>/bda

The repository is used on the event of upgrades and patching, and during these operation the httpd service must be up on node 1 of the cluster.

During normal operation, whenever upgrades or patching is not being run, the http service can be brought down if desired.

 

Reference:

MOS Upgrade documents

ie: 

Upgrading Oracle Big Data Appliance(BDA) CDH Cluster to V4.13.0 from V4.9, V4.10, V4.11, V4.12 on OL6 and from V4.12 on OL7 Releases using Mammoth Software Upgrade Bundle for OL6 or OL7 (Doc ID 2451940.1)

It may happen that when trying to reach the Exadata machine using the management network, the data center switch that connects to the Exadata Cisco switch get a 'connection rejected' error.

On X7-2 port 48 of the Cisco switch is setup by default as ‘spanning tree network’ that set the BPDU* filter to disable, and communications between customer switch and the Cisco are rejected.

To solve run this command on the Cisco:

• spanning tree BPDU filter en

Enabling BPDU filtering in the interface level stops sending or receiving BPDU on this interface; this is the same as disabling spanning tree on the interface.

See on My Oracle Support: Cisco 93108 switch is getting Error Disabled on the Uplink Switch (Doc ID 2360702.1)

* BPUD stands for: Bridge Protocol Data Unit. BPDUs are data messages that are exchanged across the switches within an extended LAN that uses a spanning tree protocol topology

 

Recently I had a BDA server that was refusing to come up. Every trial to run a start /SYS failed.

We were able to identify this as a motherboard failure, then the motherboard was replaced and we were able to bring up the server using the ILOM.

Back on track I've tried to setup the management network, but this failed because the eth0 NIC was missing.

[root@bdanode01 ~]# ethtool -i eth0 Cannot get driver information: No such device

But I've noticed we had eth1 available, nevertheless not functioning.

[root@bdanode01 ~]# ethtool -i eth1 driver: igb version: 5.3.0-k firmware-version: 3.25, 0x80000681 bus-info: 0000:02:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no

First step was to check that the mac address of eth0 was correct, for that I've checked it on the ILOM cli and on file /etc/sysconfig/network-scripts/ifcfg-eth0

-> show /SYS/MB/NET0 /SYS/MB/NET0 Targets: Properties: type = Network Interface ipmi_name = MB/NET0 fru_description = 1G Ethernet Controller fru_manufacturer = INTEL fru_part_number = i210 fru_macaddress = 00:10:e0:de:5d:84 fault_state = OK clear_fault_action = (none) On  /etc/sysconfig/network-scripts/ifcfg-eth0 we have a missing mac address, so I've added it.

Then I've checked /etc/udev/rules.d/70-persistent-net.rules

On this file we had the mismatch. It seems the mac address from the previous motherboard remained in place for eth0 while the new one was assigned to eth1

Then I've edited the file leaving only one line for eth0 and with the correct mac address

[root@bdanode01 ~]# cat /etc/udev/rules.d/70-persistent-net.rules

# This file was automatically generated by the /lib/udev/write_net_rules # program, run by the persistent-net-generator.rules rules file. ## You can modify it, as long as you keep each rule on a single # line, and change only the value of the NAME= key. # PCI device 0x8086:0x1533 (igb) (custom name provided by external tool) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:10:e0:de:5d:84", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

After reboot eth0 was back to work and I was able to setup the network.
 

Lately I had to help various customers to replace their old storage cells with the new X7-2 ones.

There are huge benefits in doing this, the X7 has 25.5TB of flash, 12 x 10TB disks and 192 GB of DDR4 Memory.

 

 

 

 

 

 

 

 

 

 

The question my customers asked the most was: Can we do the migration from our old storage to the new X7 without downtime and without risk?

The answer was: YES!

For doing this I've prepared and implemented a procedure that cover step by step how to migrate critical data, from production databases, while these databases are online, without downtime and without risk.

So far I've done two of these migrations in 2 weeks, one in Haifa and one in Istanbul.

The haifa migration was run on a machine without customers working on it. The Istanbul migration was implemented on a critical production database with full customer load.

Customer was very happy to see how the data was transferred in a fast and safe way without affecting the online business.

This is the power of both Exadata and ASM, a migration that only a few years ago may have imposed tremendous effort of planning and most probably required downtime, is now possible to be run online and without affecting the performance of critical workloads!

In summa

ry the steps of the migration includes the following:

1. Attach the new cells to Exadata and setup the ILOM to the final IP on customer network

2. Connect via ILOM to the new storage and setup the network to customer values

3. Upgrade the new storage servers to latest Exadata storage version

4. Customize the new servers to reflect customer preferences, mail alerts, writeback, asr server, etc

5. Create celldisks and griddisks to match existing diskgroups

6. Extend existing disk groups into the new cells and wait for first rebalance to complete

7. Once second rebalance completes, drop failgroups from the old cells and wait for second rebalance to complete

8. Once second rebalance complete flush the flashcache on the old cells, drop its griddisks and celldisks and shutdown the cells

9. Check the free space available on new cells and increase the size of the griddisks to use all of it as required

10. On the ASM instance resize all griddisks on the disk groups where you increase the size of the griddisks, wait for the third rebalance to complete.

 

 

 

 

Setting passwordless ssh root connection using dcli is fast and simple and will easy later to execute commands on all servers using this utility.

In order to do that you should have either:

DNS resolution to all Database and Storage nodes OR have them registered in /etc/hosts

1) Create a parameter file that contains all the server names you want to reach via dcli, tipically we have a cell_group for storage cells, a dbs_group for database servers and an all_group for both of them.

The parameter files will have only the server name, in short format

ie: all_group will have on an Exadata quarter rack:

dbnode1
dbnode2
cell1
cell2
cell3

2) As root user create ssh equivalence:

ssh-keygen   -t    rsa

3) Distribute the key to all servers

dcli -g ./all_group -l root -k -s '-o StrictHostKeyChecking=no'

4) check 

dcli -g all_group -l root hostname 

 

Normal
0




false
false
false

EN-US
X-NONE
HE













MicrosoftInternetExplorer4

DefSemiHidden="true" DefQFormat="false" DefPriority="99"
LatentStyleCount="267">
UnhideWhenUsed="false" QFormat="true" Name="Normal"/>
UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>


















UnhideWhenUsed="false" QFormat="true" Name="Title"/>

UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>
UnhideWhenUsed="false" QFormat="true" Name="Strong"/>
UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>
UnhideWhenUsed="false" Name="Table Grid"/>

UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>
UnhideWhenUsed="false" Name="Light Shading"/>
UnhideWhenUsed="false" Name="Light List"/>
UnhideWhenUsed="false" Name="Light Grid"/>
UnhideWhenUsed="false" Name="Medium Shading 1"/>
UnhideWhenUsed="false" Name="Medium Shading 2"/>
UnhideWhenUsed="false" Name="Medium List 1"/>
UnhideWhenUsed="false" Name="Medium List 2"/>
UnhideWhenUsed="false" Name="Medium Grid 1"/>
UnhideWhenUsed="false" Name="Medium Grid 2"/>
UnhideWhenUsed="false" Name="Medium Grid 3"/>
UnhideWhenUsed="false" Name="Dark List"/>
UnhideWhenUsed="false" Name="Colorful Shading"/>
UnhideWhenUsed="false" Name="Colorful List"/>
UnhideWhenUsed="false" Name="Colorful Grid"/>
UnhideWhenUsed="false" Name="Light Shading Accent 1"/>
UnhideWhenUsed="false" Name="Light List Accent 1"/>
UnhideWhenUsed="false" Name="Light Grid Accent 1"/>
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>
UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>

UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>
UnhideWhenUsed="false" QFormat="true" Name="Quote"/>
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>
UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>
UnhideWhenUsed="false" Name="Dark List Accent 1"/>
UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>
UnhideWhenUsed="false" Name="Colorful List Accent 1"/>
UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>
UnhideWhenUsed="false" Name="Light Shading Accent 2"/>
UnhideWhenUsed="false" Name="Light List Accent 2"/>
UnhideWhenUsed="false" Name="Light Grid Accent 2"/>
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>
UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>
UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>
UnhideWhenUsed="false" Name="Dark List Accent 2"/>
UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>
UnhideWhenUsed="false" Name="Colorful List Accent 2"/>
UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>
UnhideWhenUsed="false" Name="Light Shading Accent 3"/>
UnhideWhenUsed="false" Name="Light List Accent 3"/>
UnhideWhenUsed="false" Name="Light Grid Accent 3"/>
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>
UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>
UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>
UnhideWhenUsed="false" Name="Dark List Accent 3"/>
UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>
UnhideWhenUsed="false" Name="Colorful List Accent 3"/>
UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>
UnhideWhenUsed="false" Name="Light Shading Accent 4"/>
UnhideWhenUsed="false" Name="Light List Accent 4"/>
UnhideWhenUsed="false" Name="Light Grid Accent 4"/>
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>
UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>
UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>
UnhideWhenUsed="false" Name="Dark List Accent 4"/>
UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>
UnhideWhenUsed="false" Name="Colorful List Accent 4"/>
UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>
UnhideWhenUsed="false" Name="Light Shading Accent 5"/>
UnhideWhenUsed="false" Name="Light List Accent 5"/>
UnhideWhenUsed="false" Name="Light Grid Accent 5"/>
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>
UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>
UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>
UnhideWhenUsed="false" Name="Dark List Accent 5"/>
UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>
UnhideWhenUsed="false" Name="Colorful List Accent 5"/>
UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>
UnhideWhenUsed="false" Name="Light Shading Accent 6"/>
UnhideWhenUsed="false" Name="Light List Accent 6"/>
UnhideWhenUsed="false" Name="Light Grid Accent 6"/>
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>
UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>
UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>
UnhideWhenUsed="false" Name="Dark List Accent 6"/>
UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>
UnhideWhenUsed="false" Name="Colorful List Accent 6"/>
UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>
UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>





/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:Arial;
mso-bidi-theme-font:minor-bidi;}

Setting passwordless ssh root connection using dcli is fast and simple and will easy later to execute commands on all servers using this utility.

In order to do that you should have either:

DNS resolution to all Database and Storage nodes OR have them registered in /etc/hosts

1) Create a parameter file that contains all the server names you want to reach via dcli, tipically we have a cell_group for storage cells, a dbs_group for database servers and an all_group for both of them.

The parameter files will have only the server name, in short format

ie: all_group will have on an Exadata quarter rack:

dbnode1
dbnode2
cell1
cell2
cell3

2) As root user create ssh equivalence:

ssh-keygen   -t    rsa

3) Distribute the key to all servers

dcli -g ./all_group -l root -k -s '-o StrictHostKeyChecking=no'

4) check 

dcli -g all_group -l root hostname 

 

Complete information about the security fix availability should be reviewed, before applying the fix, in MOS DOC:

 Responses to common Exadata security scan findings (Doc ID 1405320.1)

The security fix is available for download from:

http://public-yum.oracle.com/repo/OracleLinux/OL5/latest/x86_64/getPackage/bash-3.2-33.el5_11.4.x86_64.rpm

The summary installation instructions are as follows:

1) Download getPackage/bash-3.2-33.el5_11.4.x86_64.rpm

2) Copy bash-3.2-33.el5_11.4.x86_64.rpm into /tmp at both database and storage nodes.

3) Remove rpm  exadata-sun-computenode-exact

rpm -e exadata-sun-computenode-exact

4) On compute nodes install bash-3.2-33.el5_11.4.x86_64.rpm using this command:

 rpm -Uvh /tmp/bash-3.2-33.el5_11.4.x86_64.rpm

5) On storage nodes  install bash-3.2-33.el5_11.4.x86_64.rpm using this command:

rpm -Uvh --nodeps /tmp/bash-3.2-33.el5_11.4.x86_64.rpm

6) Remove /tmp/bash-3.2-33.el5_11.4.x86_64.rpm from all nodes

As a side effect of applyin this fix,  during future upgrades on the database nodes, a warning will appear informing:

The "exact package" was not found and it will use minimal instead.

That's a normal and expected message and will not interfere with the upgrade. 

Complete information about the security fix availability should be reviewed, before applying the fix, in MOS DOC:

 Responses to common Exadata security scan findings (Doc ID 1405320.1)

The security fix is available for download from:

http://public-yum.oracle.com/repo/OracleLinux/OL5/latest/x86_64/getPackage/bash-3.2-33.el5_11.4.x86_64.rpm

The summary installation instructions are as follows:

1) Download getPackage/bash-3.2-33.el5_11.4.x86_64.rpm

2) Copy bash-3.2-33.el5_11.4.x86_64.rpm into /tmp at both database and storage nodes.

3) Remove rpm  exadata-sun-computenode-exact

rpm -e exadata-sun-computenode-exact

4) On compute nodes install bash-3.2-33.el5_11.4.x86_64.rpm using this command:

 rpm -Uvh /tmp/bash-3.2-33.el5_11.4.x86_64.rpm

5) On storage nodes  install bash-3.2-33.el5_11.4.x86_64.rpm using this command:

rpm -Uvh --nodeps /tmp/bash-3.2-33.el5_11.4.x86_64.rpm

6) Remove /tmp/bash-3.2-33.el5_11.4.x86_64.rpm from all nodes

As a side effect of applyin this fix,  during future upgrades on the database nodes, a warning will appear informing:

The "exact package" was not found and it will use minimal instead.

That's a normal and expected message and will not interfere with the upgrade. 

Exadata auto disk management is controlled by the parameter _AUTO_MANAGE_EXADATA_DISKS.

The default value for this parameter is TRUE.

When _AUTO_MANAGE_EXADATA_DISKS is enabled, Exadata automate the following disk operations:

If a griddisk becomes unavailable/available, ASM will OFFLINE/ONLINE it.
If a physicaldisk fails or its status change to predictive failure, for all griddisks built on it ASM will DROP FORCE the failed ones and DROP the ones with predictive failures.
If a flashdisk performance degrades, if there are griddisks built on it, they will be DROPPED FORCE in ASM.
If a physicaldisk is replaced, the celldisk and griddisks will be recreated and the griddisks will be automatically ADDED in ASM, if they were automatically dropped by ASM. If you manually drop the disks, that will not happen.
If a NORMAL, ONLINE griddisk is manually dropped, FORCE option should not be used, otherwise the disk will be automatically added back in ASM.
If a gridisk is inactivated, ASM will automatically OFFLINE it.
If a gridisk is activated, ASM will automatically ONLINED it.

There are some error conditions that may require to temporarily disable _AUTO_MANAGE_EXADATA_DISKS.

Details on MOS 1408865.1 - Exadata Auto Disk Management Add disk failing and ASM Rebalance interrupted with error ORA-15074.

Immediately after taking care of the problem _AUTO_MANAGE_EXADATA_DISKS should be set back to its default value of TRUE.

Full details on Auto disk management feature in Exadata (Doc ID 1484274.1)

Normal
0




false
false
false

EN-US
X-NONE
HE













MicrosoftInternetExplorer4














DefSemiHidden="true" DefQFormat="false" DefPriority="99"
LatentStyleCount="267">
UnhideWhenUsed="false" QFormat="true" Name="Normal"/>
UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>


















UnhideWhenUsed="false" QFormat="true" Name="Title"/>

UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>
UnhideWhenUsed="false" QFormat="true" Name="Strong"/>
UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>
UnhideWhenUsed="false" Name="Table Grid"/>

UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>
UnhideWhenUsed="false" Name="Light Shading"/>
UnhideWhenUsed="false" Name="Light List"/>
UnhideWhenUsed="false" Name="Light Grid"/>
UnhideWhenUsed="false" Name="Medium Shading 1"/>
UnhideWhenUsed="false" Name="Medium Shading 2"/>
UnhideWhenUsed="false" Name="Medium List 1"/>
UnhideWhenUsed="false" Name="Medium List 2"/>
UnhideWhenUsed="false" Name="Medium Grid 1"/>
UnhideWhenUsed="false" Name="Medium Grid 2"/>
UnhideWhenUsed="false" Name="Medium Grid 3"/>
UnhideWhenUsed="false" Name="Dark List"/>
UnhideWhenUsed="false" Name="Colorful Shading"/>
UnhideWhenUsed="false" Name="Colorful List"/>
UnhideWhenUsed="false" Name="Colorful Grid"/>
UnhideWhenUsed="false" Name="Light Shading Accent 1"/>
UnhideWhenUsed="false" Name="Light List Accent 1"/>
UnhideWhenUsed="false" Name="Light Grid Accent 1"/>
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>
UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>

UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>
UnhideWhenUsed="false" QFormat="true" Name="Quote"/>
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>
UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>
UnhideWhenUsed="false" Name="Dark List Accent 1"/>
UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>
UnhideWhenUsed="false" Name="Colorful List Accent 1"/>
UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>
UnhideWhenUsed="false" Name="Light Shading Accent 2"/>
UnhideWhenUsed="false" Name="Light List Accent 2"/>
UnhideWhenUsed="false" Name="Light Grid Accent 2"/>
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>
UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>
UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>
UnhideWhenUsed="false" Name="Dark List Accent 2"/>
UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>
UnhideWhenUsed="false" Name="Colorful List Accent 2"/>
UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>
UnhideWhenUsed="false" Name="Light Shading Accent 3"/>
UnhideWhenUsed="false" Name="Light List Accent 3"/>
UnhideWhenUsed="false" Name="Light Grid Accent 3"/>
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>
UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>
UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>
UnhideWhenUsed="false" Name="Dark List Accent 3"/>
UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>
UnhideWhenUsed="false" Name="Colorful List Accent 3"/>
UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>
UnhideWhenUsed="false" Name="Light Shading Accent 4"/>
UnhideWhenUsed="false" Name="Light List Accent 4"/>
UnhideWhenUsed="false" Name="Light Grid Accent 4"/>
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>
UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>
UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>
UnhideWhenUsed="false" Name="Dark List Accent 4"/>
UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>
UnhideWhenUsed="false" Name="Colorful List Accent 4"/>
UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>
UnhideWhenUsed="false" Name="Light Shading Accent 5"/>
UnhideWhenUsed="false" Name="Light List Accent 5"/>
UnhideWhenUsed="false" Name="Light Grid Accent 5"/>
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>
UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>
UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>
UnhideWhenUsed="false" Name="Dark List Accent 5"/>
UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>
UnhideWhenUsed="false" Name="Colorful List Accent 5"/>
UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>
UnhideWhenUsed="false" Name="Light Shading Accent 6"/>
UnhideWhenUsed="false" Name="Light List Accent 6"/>
UnhideWhenUsed="false" Name="Light Grid Accent 6"/>
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>
UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>
UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>
UnhideWhenUsed="false" Name="Dark List Accent 6"/>
UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>
UnhideWhenUsed="false" Name="Colorful List Accent 6"/>
UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>
UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>





/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:Arial;
mso-bidi-theme-font:minor-bidi;}

Exadata auto disk management is controlled by the parameter _AUTO_MANAGE_EXADATA_DISKS.

The default value for this parameter is TRUE.

When _AUTO_MANAGE_EXADATA_DISKS is enabled, Exadata automate the following disk operations:

If a griddisk becomes unavailable/available, ASM will OFFLINE/ONLINE it.
If a physicaldisk fails or its status change to predictive failure, for all griddisks built on it ASM will DROP FORCE the failed ones and DROP the ones with predictive failures.
If a flashdisk performance degrades, if there are griddisks built on it, they will be DROPPED FORCE in ASM.
If a physicaldisk is replaced, the celldisk and griddisks will be recreated and the griddisks will be automatically ADDED in ASM, if they were automatically dropped by ASM. If you manually drop the disks, that will not happen.
If a NORMAL, ONLINE griddisk is manually dropped, FORCE option should not be used, otherwise the disk will be automatically added back in ASM.
If a gridisk is inactivated, ASM will automatically OFFLINE it.
If a gridisk is activated, ASM will automatically ONLINED it.

There are some error conditions that may require to temporarily disable _AUTO_MANAGE_EXADATA_DISKS.

Details on MOS 1408865.1 - Exadata Auto Disk Management Add disk failing and ASM Rebalance interrupted with error ORA-15074.

Immediately after taking care of the problem _AUTO_MANAGE_EXADATA_DISKS should be set back to its default value of TRUE.

Full details on Auto disk management feature in Exadata (Doc ID 1484274.1)

Sometimes I have heard that Exalogic is just a bunch of servers connected using infiniband, something that you can easily build yourself at a lower cost.

That comments misses completely 2 things:

1) What is the idea behind an Oracle engineered system, and the back that Oracle provides for them 

2) What is Exalogic

This amazing 5 minute presentation explains Exalogic potential:

Oracle Exalogic Elastic Cloud

Sometimes I have heard that Exalogic is just a bunch of servers connected using infiniband, something that you can easily build yourself at a lower cost.

That comments misses completely 2 things:

1) What is the idea behind an Oracle engineered system, and the back that Oracle provides for them 

2) What is Exalogic

This amazing 5 minute presentation explains Exalogic potential:

Oracle Exalogic Elastic Cloud

There are 2 interesting new features on RAC 11.2.0.2.

The first is the cluster HAIP resource, that makes possible to have up to 4 redundant interconnects that will be automatically managed by the cluster for fail-over and load balancing.

 The second one is the Cluster Health Monitor. It was previously available as a utility that you can download and install, now is a resource on the cluster and will start to collect valuable OS statistics from the moment the Cluster is installed.

You can see details about both features on this file : HAIP and CHM 11.2.0.2 RAC Features

There are 2 interesting new features on RAC 11.2.0.2.

The first is the cluster HAIP resource, that makes possible to have up to 4 redundant interconnects that will be automatically managed by the cluster for fail-over and load balancing.

 The second one is the Cluster Health Monitor. It was previously available as a utility that you can download and install, now is a resource on the cluster and will start to collect valuable OS statistics from the moment the Cluster is installed.

You can see details about both features on this file : HAIP and CHM 11.2.0.2 RAC Features

Exadata is installed with the minimum set of rpm's required to make it work as a database server.In many cases you will need to install by yourself the rpms required to make available some specific functions, like FTP.Exadata is installed either with Oracle Enterprise Linux or Solaris Express. This instructions match the Linux distribution, and can be used on any RH compatible Linux, not only OEL on Exadata.You can find the rpm's on the Oracle Enterprise Linux Distribution Disk, downloadable from edelivery.oracle.comInstall the Following rpms:[root@exand02 rpms]# lsftp-0.17-35.el5.x86_64.rpm pam-rpms vsftpd-2.0.5-16.el5_4.1.x86_64.rpmlftp-3.7.11-4.el5.x86_64.rpm tftp-server-0.49-2.0.1.x86_64.rpmThe Command to Install[root@exand02 rpms]# rpm -Uivh vsftpd-2.0.5-16.el5_4.1.x86_64.rpm ftp-0.17-35.el5.x86_64.rpm lftp-3.7.11-4.el5.x86_64.rpmStart Service vsftpd[root@exand02 rpms]# service vsftpd startStarting vsftpd for vsftpd: [ OK ][root@exand02 rpms]# service vsftpd statusvsftpd (pid 9274) is running...Configure Automatic vsftp Start[root@exand02 rpms]# chkconfig vsftpd on[root@exand02 rpms]# chkconfig --list | grep vsftpdvsftpd 0:off 1:off 2:on 3:on 4:on 5:on 6:offecho "service vsftpd status" >> /etc/rc.local[root@exand02 rpms]# tail -2 /etc/rc.local########### END DO NOT REMOVE Added by Oracle Exadata ###########service vsftpd startEdit /etc/vsftpd.confSet the following parameters on vsftpd.conf#anonymous_enable=YES (changed to NO to allow Exadata users to ftp)anonymous_enable=NO#userlist_enable=YES (changed to NO to allow Exadata users to ftp)userlist_enable=NOTest[root@exand02 vsftpd]# ftp exand02Connected to exand02 (10.25.104.130).220 (vsFTPd 2.0.5)Name (exand02:root): oracle331 Please specify the password.Password:230 Login successful.Remote system type is UNIX.Using binary mode to transfer files.ftp> pwd257 "/home/oracle"ftp> ls227 Entering Passive Mode (10,25,104,130,85,192)150 Here comes the directory listing.drwxr-xr-x 3 1001 500 4096 May 20 19:47 localdrwxr----- 3 1001 500 4096 May 03 12:20 oradiag_oracle-rw-r--r-- 1 1001 500 1020 Jun 01 14:41 ~oraclec226 Directory send OK.ftp> bye221 Goodbye.