When using the DBCA tool under Oracle 11gR2 64-bit on Windows 2008, and trying to specify ASM as the file storage, the following error is encountered:
“grid infrastructure or clusterware home not found”
The DBCA tool must be run as Administrator, even if the account you are using is already an Administrator privileged account.
If you launch DBCA from the command line, the CMD executable must be launched with the Run As Administrator option.
In this blog post, we are going to rename the Linux host name of an existing Oracle 11gR2 system. We can also use this technique to change the IP address of our host.
Host renames are a useful technique in virtualized environments, where vCenter may be used to clone entire hosts including the Oracle databases installed on them. This technique will also work with physical hosts should you wish to simply rename an existing Oracle host.
In this blog post, we are going to silently install Oracle 11.2.0.3 64-bit on RedHat 6.0 using VMWare Workstation 8.
This install demonstration is going to use the silent install mode for all components. At least within the guest VM, at no point will we use a GUI for the install. We will need to use the VMWare GUI to create the VM, install the OS and add disks.
With the increasing use of VMWare, many organizations are looking to automate the deployment of Oracle database environments for development, test or validation. And increasingly DBAs are being tasked with automating the provisioning process.
You installed the Grid Infrastructure using the silent software-only option:
./runInstaller -silent -force -responseFile $HOME/grid.rsp
When you try to create the ASM instance and a diskgroup, the asmca command fails with:
Error while detecting Oracle Grid Infrastructure. ASMCA needs Oracle Grid Infrastructure to configure ASM.
This is because the CRS components still need to be configured, you can do this as the root user as follows:
[root@localhost ~]# $ORACLE_HOME/perl/bin/perl -I \ $ORACLE_HOME/perl/lib -I \ $ORACLE_HOME/crs/install $ORACLE_HOME/crs/install/roothas.pl Using configuration parameter file: /u01/app/11.2.0/grid/crs/install/crsconfig_params Creating trace directory LOCAL ADD MODE Creating OCR keys for user 'oracle', privgrp 'oinstall'.. Operation successful. LOCAL ONLY MODE Successfully accumulated necessary OCR keys. Creating OCR keys for user 'root', privgrp 'root'.. Operation successful. CRS-4664: Node localhost successfully pinned. Adding Clusterware entries to upstart localhost 2013/01/10 15:06:48 /u01/app/11.2.0/grid/cdata/localhost/backup_20130110_150648.olr Successfully configured Oracle Grid Infrastructure for a Standalone Server
Once this is done, the asmca command can be run successfully.
In this blog post, we are going to install Oracle 11.2.0.3 64-bit on CentOS 6.3 using VMware Workstation 8. Given that Oracle no longer offers ASMLib for non Oracle branded Linux, we are going to use UDEV rules to manage the disk presentation to ASM.
In my 10-part post on installing Oracle RAC on VMware Workstation I deliberately used an excessive number of screen shots to guide readers through the process. This time I am going to assume you are already comfortable with the Oracle GUI installers, and will skip over excess details to condense this down into a single blog post.
Hybrid Columnar Compression is one of the new features that Oracle has been touting to persuade DBAs on the virtues of their Exadata and ZFSSA storage solutions.
As stated in my bio, I currently get paid by EMC, but this blog post is not another critique of Oracle sales massaging technical numbers on the assumption that you can use HCC for OLTP loads.
Rather, this is a USE AT YOUR OWN RISK method to explore what HCC can and cannot do. Using this method will render your databases unsupported by Oracle and you must NOT do this on any production or mission critical system. Please note I accept no responsibility for anyone destroying critical data from trying any of this.
You may find the scsi_id command returns a null result in CentOS 6 or RHEL 6 on VMware.
[root@localhost ~]# scsi_id -g -u -d /dev/sdb [root@localhost ~]#
The problem here is that VMware Workstation does not provide unique SCSI identifiers to the virtual SCSI devices. We need to modify the VMX file to make this happen by adding the following directive:
disk.EnableUUID = "TRUE"
Restart the VM and now the scsi_id command should work:
[root@localhost ~]# scsi_id -g -u -d /dev/sdb 36000c2980c56d98cc5150a0ac103058d
You are installing 11gR2 11.2.0.1 Grid Infrastructure on Red Hat 6, CentOS 6 or similar Linux operating system, and right at the very end of the process, the root.sh script blows up with a really odd error:
[root@localhost oraInventory]# cd /u01/app/oracle/product/11.2.0/db_1 [root@localhost db_1]# ./root.sh Running Oracle 11g root.sh script...
Time Required: 60 minutes
Class Materials:
Next we are going to install the Oracle Grid Infrastructure software.
The Grid Infrastructure will provide the Cluster software that allows the RAC nodes to communicate, as well as the ASM software to manage the shared disks.
To begin, download the zip file from the Oracle software download website and unzip on Orpheus. Make sure you are logged into Orpheus as the oracle user so that oracle owns the unzipped files.
Time Required: 20 minutes
Class Materials:
Next we will install the ASMLib drivers that simplify management of ASM on Linux.
ASMLib is an interface between block devices presented to Linux, and the Oracle ASM software that executes as the Oracle user.
the gruffdba 