Alejandro Vargas

Subscribe to Alejandro Vargas feed
Oracle Blogs
Updated: 10 hours 50 min ago

After motherboard change on BDA server eth0 network interface is missing

Sun, 2018-07-15 03:55

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.
 

Categories: DBA Blogs

How to replace old Exadata storage cells with the new X7-2 storage cells, without downtime

Fri, 2018-06-15 03:32

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.

X7-2 hardware

 

 

 

 

 

 

 

 

 

 

 

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.

 

 

 

 

Categories: DBA Blogs

How to setup passwordless ssh in Exadata using dcli

Sun, 2014-10-05 03:57

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 

Categories: DBA Blogs

How to setup passwordless ssh in Exadata using dcli

Sun, 2014-10-05 03:57

 




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 



 

Categories: DBA Blogs

Bash security fix made available for Exadata

Sun, 2014-10-05 03:29

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. 


Categories: DBA Blogs

Bash security fix made available for Exadata

Sun, 2014-10-05 03:29

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. 







Categories: DBA Blogs

Exadata Parameter _AUTO_MANAGE_EXADATA_DISKS

Wed, 2012-10-17 11:50
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)
Categories: DBA Blogs

Exadata Parameter _AUTO_MANAGE_EXADATA_DISKS

Wed, 2012-10-17 11:50



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)

Categories: DBA Blogs

Oracle Engineered Systems, Amazing Exalogic

Thu, 2012-09-27 03:36

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


Categories: DBA Blogs

Oracle Engineered Systems, Amazing Exalogic

Thu, 2012-09-27 03:36

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



Categories: DBA Blogs

RAC11.2.0.2 redundant interconnect and the Cluster Health Monitor

Mon, 2012-01-09 15:54

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

Categories: DBA Blogs

RAC11.2.0.2 redundant interconnect and the Cluster Health Monitor

Mon, 2012-01-09 15:54


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

Categories: DBA Blogs

Configuring FTP on Exadata

Sun, 2011-07-24 23:30
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.
Categories: DBA Blogs

Configuring FTP on Exadata

Sun, 2011-07-24 23:30

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

Install the Following rpms:

[root@exand02 rpms]# ls
ftp-0.17-35.el5.x86_64.rpm pam-rpms
vsftpd-2.0.5-16.el5_4.1.x86_64.rpm
lftp-3.7.11-4.el5.x86_64.rpm tftp-server-0.49-2.0.1.x86_64.rpm

The 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.rpm

Start Service vsftpd

[root@exand02 rpms]# service vsftpd start
Starting vsftpd for vsftpd: [ OK ]
[root@exand02 rpms]# service vsftpd status
vsftpd (pid 9274) is running...

Configure Automatic vsftp Start

[root@exand02 rpms]# chkconfig vsftpd on

[root@exand02 rpms]# chkconfig --list | grep vsftpd
vsftpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off

echo "service vsftpd status" >> /etc/rc.local

[root@exand02 rpms]# tail -2 /etc/rc.local
########### END DO NOT REMOVE Added by Oracle Exadata ###########
service vsftpd start

Edit /etc/vsftpd.conf

Set 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=NO

Test

[root@exand02 vsftpd]# ftp exand02

Connected to exand02 (10.25.104.130).
220 (vsFTPd 2.0.5)
Name (exand02:root): oracle
331 Please specify the password.
Password:
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.

ftp> pwd
257 "/home/oracle"

ftp> ls
227 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 local
drwxr----- 3 1001 500 4096 May 03 12:20 oradiag_oracle
-rw-r--r-- 1 1001 500 1020 Jun 01 14:41 ~oraclec
226 Directory send OK.

ftp> bye
221 Goodbye.

Categories: DBA Blogs

11.2.0.2 Creating a Standby or a Clone Database using Rman Duplicate From Active Database

Sun, 2011-07-24 03:20
There are a few things on 11.2.0.2 that you need to take into account to create a standby database or a clone database from an Active Database using Duplicate database command. Points 2, 9 and 10 of this document contains the details I’ve found I needed to change in order to get the clone or duplicate for standby running smoothly on this release:The steps required to complete the task are: 1)

Create a parameter file for the clone or standby

2)

add the following 3 parameters to the standby or clone database parameter file, even if the paths are identical on both the source and standby or clone servers: *._compression_compatibility='11.2.0' *.db_file_name_convert=('trg_path','aux_path'…) *.log_file_name_convert=('trg_path','aux_path'…) 3)

Copy the passwordfile from the source database to the clone or standby Oracle_Home/database folder or $Oracle_Home/dbs on Linux/Uniux.

4)

Configure the network on the clone or standby server so that you can connect to the database

5)

Startup nomount the clone or standby database

6)

Add a tnsnames.ora entry to the clone or standby on your source database server

7)

Check that you can connect to the clone or standby database as sysdba

8)

On the Primary server connect to the source database and clone or standby database (auxiliary) using RMAN >rman target / auxiliary sys/@prodcl Recovery Manager: Release 11.2.0.2.0 - Production on Sun Jul 24 15:49:25 2011 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. connected to target database: PROD (DBID=8114723455) connected to auxiliary database: PRODCL (not mounted)

9)

Use the following syntax to duplicate to a clone (use as many channels as CPU’s you may dedicate): run { allocate channel c1 type disk; allocate auxiliary channel cr1 type disk; duplicate target database to 'prodcl' from active database nofilenamecheck; } 10)

Use the following syntax to duplicate for standby (use as many channels as CPU’s you may dedicate): run { allocate channel c1 type disk; allocate auxiliary channel cr1 type disk; duplicate target database for standby from active database nofilenamecheck; }
Categories: DBA Blogs

11.2.0.2 Creating a Standby or a Clone Database using Rman Duplicate From Active Database

Sun, 2011-07-24 03:20

There are a few things on 11.2.0.2 that you need to take into account to create a standby database or a clone database from an Active Database using Duplicate database command.

Points 2, 9 and 10 of this document contains the details I’ve found I needed to change in order to get the clone or duplicate for standby running smoothly on this release:

The steps required to complete the task are:

1) Create a parameter file for the clone or standby

2) add the following 3 parameters to the standby or clone database parameter file, even if the paths are identical on both the source and standby or clone servers:

*._compression_compatibility='11.2.0'
*.db_file_name_convert=('trg_path','aux_path'…)
*.log_file_name_convert=('trg_path','aux_path'…)

3) Copy the passwordfile from the source database to the clone or standby Oracle_Home/database folder or $Oracle_Home/dbs on Linux/Uniux.

4) Configure the network on the clone or standby server so that you can connect to the database

5) Startup nomount the clone or standby database

6) Add a tnsnames.ora entry to the clone or standby on your source database server

7) Check that you can connect to the clone or standby database as sysdba

8) On the Primary server connect to the source database and clone or standby database (auxiliary) using RMAN

>rman target / auxiliary sys/@prodcl

Recovery Manager: Release 11.2.0.2.0 - Production on Sun Jul 24 15:49:25 2011

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

connected to target database: PROD (DBID=8114723455)
connected to auxiliary database: PRODCL (not mounted)

9) Use the following syntax to duplicate to a clone (use as many channels as CPU’s you may dedicate):

run {
allocate channel c1 type disk;
allocate auxiliary channel cr1 type disk;
duplicate target database to 'prodcl' from active database nofilenamecheck;
}

10) Use the following syntax to duplicate for standby (use as many channels as CPU’s you may dedicate):

run {
allocate channel c1 type disk;
allocate auxiliary channel cr1 type disk;
duplicate target database for standby from active database nofilenamecheck;
}

Categories: DBA Blogs

RAC, ASM and Linux Forum, May 18, 2011: EXADATA Production Customers updates

Sun, 2011-05-08 08:11

Exadata is changing the world of Database Performance, on this forum we will have two EXADATA Production Customers updates.

75 million Customer Telecom Turkcell will be represented by Ferhat Sengonul, Senior OS Administrator, DBA, and Datawarehouse Project Leader, that led Exadata implementation and scale out to their actual 3 full, 24 database nodes, Exadata racks.

Ferhat will present his experience with a very large Data-Warehouse in Exadata, including online high performance reporting, VLDB backup and recovery best practices and upgrading from a traditional 11 racks (1 Sun M9000 Sparc 7; 10 storage racks 250 TB uncompressed) datawarehouse to a full rack and then to multiple racks. We will hear also about his consolidation project of all datawarehouse databases in Exadata.

Golden Pages, the first Consolidation on Exadata project implemented in Israel will be presented by Shimi Nahum, Senior DBA and Exadata Project Leader. Shimi will tell us about the challenges the Exadata environment presented to him as a DBA and how he faced them, and the impact of using Oracle Exadata to consolidate multiple Customer databases, including Siebel and ERP databases.

A practical dive into the technology will be presented by Oracle's Ophir Manor, the responsible for the several POC's being run by different Israeli Customers.

And finally I will tell about the experiences from the field, installing and implementing Exadata at different Customers around the world.

Exadata is radically changing the rules and expectations a DBA can have of an Oracle Database; this first hand experiences promise to be one of the most interesting conferences in Israel this year.

The conference will be held on May 18 at the Sharon Conference Center 09 starting at 14:00

REGISTRATION: ILOUG RAC, ASM and Linux Forum Registration,

SCHEDULE:

14:00 – 14:30

Registration

14:30 – 14:40

Welcome

14:40 – 15:25

Shimi Nahum, Dapei Zahab, Senior Oracle DBA, responsible of the Exadata project.

The first production Oracle Exadata in Israel, challenges for the DBA, speedup impact of Exadata on the end Customer

15:25 – 16:15

Ferhat Sengönül, Senior OS and DBA Turkcell, Responsible for the DW project

A very large Data-Warehouse in Exadata, the migration process, backup and recovery strategies, scaling up from 1 Exadata rack to 3

16:15 – 16:30

Refreshments Break

16:30 – 17:15

Ofir Manor. Oracle Senior Sales Consultant and Exadata Expert.

Preparing the IT infrastructure for Exadata. Lifetime maintenance procedures.

17:15 – 17:45

Alejandro Vargas, Oracle Principal Support Consultant and EMEA Exadata Core Team Member.

Inside the Oracle Database Machine, secrets about the configuration, install and support procedures

17:45 – 18:15

Questions and Answers
Categories: DBA Blogs

RAC, ASM and Linux Forum, May 18, 2011: EXADATA Production Customers updates

Sun, 2011-05-08 08:11

Exadata is changing the world of Database Performance, on this forum we will have two EXADATA Production Customers updates.

75 million Customer Telecom Turkcell will be represented by Ferhat Sengonul, Senior OS Administrator, DBA, and Datawarehouse Project Leader, that led Exadata implementation and scale out to their actual 3 full, 24 database nodes, Exadata racks.

Ferhat will present his experience with a very large Data-Warehouse in Exadata, including online high performance reporting, VLDB backup and recovery best practices and upgrading from a traditional 11 racks (1 Sun M9000 Sparc 7; 10 storage racks 250 TB uncompressed) datawarehouse to a full rack and then to multiple racks. We will hear also about his consolidation project of all datawarehouse databases in Exadata.

Golden Pages, the first Consolidation on Exadata project implemented in Israel will be presented by Shimi Nahum, Senior DBA and Exadata Project Leader. Shimi will tell us about the challenges the Exadata environment presented to him as a DBA and how he faced them, and the impact of using Oracle Exadata to consolidate multiple Customer databases, including Siebel and ERP databases.

A practical dive into the technology will be presented by Oracle's Ophir Manor, the responsible for the several POC's being run by different Israeli Customers.

And finally I will tell about the experiences from the field, installing and implementing Exadata at different Customers around the world.

Exadata is radically changing the rules and expectations a DBA can have of an Oracle Database; this first hand experiences promise to be one of the most interesting conferences in Israel this year.

The conference will be held on May 18 at the Sharon Conference Center 09 starting at 14:00

REGISTRATION: ILOUG RAC, ASM and Linux Forum Registration,

SCHEDULE:

14:00 – 14:30 Registration

14:30 – 14:40 Welcome

14:40 – 15:25 Shimi Nahum, Dapei Zahab, Senior Oracle DBA, responsible of the Exadata project.

The first production Oracle Exadata in Israel, challenges for the DBA, speedup impact of Exadata on the end Customer

15:25 – 16:15 Ferhat Sengönül, Senior OS and DBA Turkcell, Responsible for the DW project

A very large Data-Warehouse in Exadata, the migration process, backup and recovery strategies, scaling up from 1 Exadata rack to 3

16:15 – 16:30 Refreshments Break

16:30 – 17:15 Ofir Manor. Oracle Senior Sales Consultant and Exadata Expert.

Preparing the IT infrastructure for Exadata. Lifetime maintenance procedures.

17:15 – 17:45 Alejandro Vargas, Oracle Principal Support Consultant and EMEA Exadata Core Team Member.

Inside the Oracle Database Machine, secrets about the configuration, install and support procedures

17:45 – 18:15 Questions and Answers
Categories: DBA Blogs

How to Install the Oracle-Validated rpm Using a Local Repository

Tue, 2010-11-23 23:20

One of the steps required to install Oracle on Linux is to Install all the Linux packages, rpm's, needed by Oracle, and their dependencies. That is followed by creating the Oracle user account and groups and setup the parameters for the kernel.

All of these tasks can be automatized by installing a single rpm that is distributed by Oracle, the Oracle-Validated rpm.

On the Oracle Enterprise Linux 5.5 distribution disk it is included the Oracle-Validated rpm and also the ASMLib related rpms.

The rpm can be installed as part of the Linux install process, as explained on Sergio Leunissen post from 2009

Another option, if you have your server connected to the Internet, is to run the install using Yum; it will install the oracle-validated rpm and download all required dependencies.

Yet another option, if you don't have access to the Internet, is to setup a local or NFS mounted repository that contains all rpm's included on the Linux distribution disk.

In this post I'm including an example of the steps required to setup a local rpm repository and install the Oracle-Validated rpm and it's dependencies from it:

How to Install The Oracle-Validated rpm From a Local Repository

Categories: DBA Blogs

How to Install the Oracle-Validated rpm Using a Local Repository

Tue, 2010-11-23 23:20

One of the steps required to install Oracle on Linux is to Install all the Linux packages, rpm's, needed by Oracle, and their dependencies. That is followed by creating the Oracle user account and groups and setup the parameters for the kernel.

All of these tasks can be automatized by installing a single rpm that is distributed by Oracle, the Oracle-Validated rpm.

On the Oracle Enterprise Linux 5.5 distribution disk it is included the Oracle-Validated rpm and also the ASMLib related rpms.

The rpm can be installed as part of the Linux install process, as explained on Sergio Leunissen post from 2009

Another option, if you have your server connected to the Internet, is to run the install using Yum; it will install the oracle-validated rpm and download all required dependencies.

Yet another option, if you don't have access to the Internet, is to setup a local or NFS mounted repository that contains all rpm's included on the Linux distribution disk.

In this post I'm including an example of the steps required to setup a local rpm repository and install the Oracle-Validated rpm and it's dependencies from it:

How to Install The Oracle-Validated rpm From a Local Repository

Categories: DBA Blogs

Pages