Oracle Grid Infrastructure 11.2.0.3.0 Download

09.01.2020 admin

On this post, i am going to show you how to install a single instance Oracle Database 11g release 2 with ASM using Oracle Enterprise Linux 6x86_64 and role separation.

Oracle Grid Infrastructure Software Download
How To Install Oracle Grid Infrastructure
Oracle Grid Infrastructure Overview
Oracle Grid Infrastructure 11.2.0.3.0 Download Pc

In order to setup the environment you will need:

D How to Upgrade to Oracle Grid Infrastructure 11 g Release 2. If you are completing a patch update of Oracle Clusterware or Oracle ASM, then after you download the patch software and before you start to patch or upgrade your software installation, review the Patch Set Release Notes that accompany the patch to determine if your system meets. Where can I find grid 11.2.0.3 for download. I can see the version for 11.2.0.1 on the grid infrastructure download page. But there is no reference to the newer version. I am attempting to build a 2 node RAC database running on a UEK 6.3 os.

The Oracle Database 11g Software (11.2.0.3). LINK
The Oracle Grid Infrastructure 11g Software (11.2.0.3). LINK
The Oracle Linux 6.3 x86_64 installation CD/ISO. LINK
A Virtual Machine/ Server with x86_64 support

Note: You will need your OTN login in order to download the products. If you don’t have one, go ahead and register.

I am going to use Oracle Virtual Box to setup the lab. Here are the details for the VM.

Name: oralab1
RAM: 3.5 GB
Hostname: oralab1.localdomain
Ip: 192.168.10.151/255.255.255.0 gw 192.168.10.1
Nics: 1 bridged adapter
Disks: 1 * 54 GB, 3 * 9 GB

We are going to make the installation in the following order.

Installing and configuring the Operating system.
Installing Oracle Grid Infrastructure and ASM.

Let’s Begin

PART I – Installing and configuring Oracle Enterprise Linux 6 x86_64

Once you create your VM/Server and downloaded your Linux media, boot your VM/Server to begin the installation.

Once the anaconda installer loads up, click next to begin

Select your preferred language and keyboard

Select your type for storage and continue

Setup your hostname and network interfaces and continue

Choose your time zone

Choose your root password

Select your type of installation and continue.

Next you will be prompted to choose which type of server installation you want. Here I prefer to select a custom installation to select only the packages that i need.

In the next screen select all the required packages that you need, at least include:

Desktop Environment
X Server
Administration tools
Oracle 11g Preinstall package and the AsmLib driver

Once you’re done with the packages, click next to begin the installation

Click reboot to finish

When the operating system reboots, you will need to complete the setup as follows

You could create the grid user here. I prefer to do it later, click Forward to continue

Select your time to continue

Click Finnish

Now you will need to login using the root user. This is because the oracle user created by the Oracle Preinstall package does not have password. Log on and set it up

Disable the firewall. Go go System/Administration/Firewall

Depending on your environment edit your network interface as follows.

Edit your hosts file hosts file with your hostname and ip.

Reload your network as follows

Install your virtual box guest additions. This will not be necessary if you’re on a physical server or VmWare.

Create the necessary directories and the grid user.

Set the necessary permissions

Edit the file ‘/home/grid/.bash_profile’ and add the following lines to set up the grid user environment

Edit the file ‘/home/oracle/.bash_profile’ and add the following lines to set up the oracle user environment

Shutdown your system and add the necessary disks to be used as ASM disks. In this case I’ll created 3 disks

Startup you system and configure you ASM driver as the root user

Check if your disks are available

It’s time to setup the disks. As you saw in the previous screenshot, i have three additional disks named (/dev/sdb, /dev/sdc, /dev/sdd ) we need to partition each disks in order to make them available for ASM. We will use fdisk to partition them, here is the order you’ll have to follow.

fdisk /dev/sdb
n,p,1,1,w
fdisk /dev/sdc
n,p,1,1,w
fdisk /dev/sdd
n,p,1,1,w

Here is how it looks like:

Let’s check again our disks. You will notice that 3 more devices appear, those are the partition we created.

Next let’s disable SELinux as follows ‘vi /etc/selinux/config’

Create your ASM disks as follows

oracleam createdisk ‘DISK1’ /dev/sdb1

oracleam createdisk ‘DISK2’ /dev/sdc1

oracleam createdisk ‘DISK3’ /dev/sdd1

At this point we will have our server ready for the grid infrastructure installation.

PART II – Installing Oracle Grid Infrastructure 11.2.0.3 and ASM

In this installation we will use role separation of duties; we will proceed as the grid user who’s going to be the GRID_HOME owner

If you have downloaded all the files required, unzip the file p10404530_112030_Linux-x86-64_3of7.zip as follows

After unzipping the file, you will have a folder called “grid”. Start the installer with ./runInstaler

Skip the software updates

Select the option for a standalone server as shown in the picture

Select you languages

Create one diskgroup called DATA with disks ( DISK1, DISK2 ) with external redundancy a shown.

Specify a password for sys and asmsnmp accounts

Leave the default groups and continue

Choose the paths to de ORACLE_BASE and ORACLE_HOME

Note: 11.0.3 in the path, should be 11.2.3 if you follow OFA or you can choose whatever you want in your ORACLE_HOME path

Specify for inventory

Next the installer will perform a check on your server as shown

If the installer finds that something is not right with your server, it will tell you to run some fixup scripts. Run them as root until your good

Once ready continue with the installation

During the installation you will prompted to run two scripts a root user, run them to continue

After the installation ends click close to finnish

To verify the installation just execute the command “crsctl status resource –t” as grid user

And with sqlplus

At this point we have our Oracle Restart and ASM in place.

PART III – Installing the Database Software and creating the Database

Now we are going to install the database software as the oracle user. Unzip all the files required as follows

You’ll have a folder called “database” let’s get inside and ejecute the oracle installer with “./runInstaller”

If you have toy Oracle Support credencials put them in place and continue.

Skip Sofware updates if you want and continue

Select install software only and continue

Select Single instance Database installation and continue

Select your language and continue

Select enterprise Edition or the one you prefer and continue

Choose your ORACLE_BASE and ORACLE_HOME

Review your installation and click install to proceed

As the installation goes on, you will need to execute a script as the root user

At the end of the installation you will see something like this.

Now let’s create our database with dbca. As the oracle user execute the dbca

Select create a database

Select your template, this time we’re going to select general purpose

Write your Global database name and sid

Choose to configure the enterprise manager

Write in the passwords for the administrative users

Choose the storage for your database. Select ASM and write the name of your diskgroup.

Specify your asm credentials

Choose to enable or not archiving and the FRA for you database. This time we are not going to set it up. NOT RECOMMENDED IN PRODUCCTION SYSTEM.

Adjust your memory settings as you want or leave the defaults

Next review your database storage. You don’t really need yo modify anything here.

On the summary screen click “OK” to begin the creation of the database

At the end you will see a summary of the database you just created

Let’s verify

Done! We now have a fully functional single database instance using ASM for storage over Oracle Linux 6.

Good Luck!

Emmanuel

Advertisements

Half a year ago, my colleague Remco wrote an article on auto starting the listener and the databases after a host reboot. As usual with Oracle, there are several solutions. In a previous job, I learned to appreciate Oracle Grid infrastructure to do the same. And then some more.

Oracle Grid Infrastructure can be downloaded and used for free. It serves many purposes, especially for ASM and RAC,but as it turns out, it can be installed as ‘software only’ and still serve a purpose known as Oracle Restart.

So why not use the old familiar dbstart and dbstop scripts?

Here’s why: Data Guard. Many applications, including Weblogic Connection Pools, use a long connection string that contains host name and service name of both (or more) instances of a Data Guard installation. Suppose host A with instance Prim represents the primary database. Now suppose the application wants to connect to the host A and SID Prim but it can’t get a connection immediately through the listener (this actually might happen more often than you think). The application will behave as expected, which is to look for host B with SID Prim. That might very well exist, but since that instance is a standby instance, it will answer with a connection refused. And that often is worse than not finding an instance at all.

What we want is to connect to a service rather than to a SID. Services are completely customizable per instance. So why not have a service that only exists if the database is a primary database?

This mechanism exists for years already and used to be taken care of by using triggers, activating the service upon opening the database. Remember, a standby database doesn’t open, so that particular service won’t be started.

Doesn’t it? Not in the past, but now we have active standby. Oops, there’s an unwanted service.

Grid Infrastructure allows you to start services depending on the role of the database: Primary, Physical Standby, Logical Standby or Snapshot Standby.

It also enables you to automatically start the database and listener upon host startup.

It even enables you to immediately and automatically start processes when they crash. Try killing process pmon for instance. That’s basically killing your instance. You’d have to discover this happened and then restart your database manually using sqlplus.

With this new software, it will be detected automatically and restart your database before you noticed it was down.

Time to show how it’s done.

Download the Oracle Grid software and have it available at your host.

[oracle@oraclelinux6 grid]$ ./runInstaller

The options are pretty clear. Choose the last one and click Next.

No comment needed.

I still prefer the familiar oinstall group and for this example it’s not important anyway since we won’t be using ASM.

Click Next.

Depending on your choices you might get one or more warnings. You can safely ignore them.

This is the Oracle default. Make sure you at least have /u01/app, owned by oracle:oinstall.

I highly recommend using these Oracle default directories, it makes life easier at so many levels.

Adobe cs6 crack milkman hat how to. You get to use the bottom coming Neill Corlett's network to give the Quick off port.

Click Next.

Oracle Grid Infrastructure Software Download

Issues will occur. Investigate and fix them, or check Ignore All if you are sure of what you are doing. Personally I don’t need swap on a database server so at least that one I ignore. And in this particular case, I didn’t solve the resolv.conf issue either.

Click Install.

An overview of the choices you made. Check them and Click Install.

Now the software will be installed which might take up anything between 1 and 20 minutes. When it’s finished you’ll see the next screen:

Open an extra terminal as user root and execute the script /u01/app/11.2.0/grid/root.sh

Look at the output. It should contain the lines

This is the most tricky part: even if you think you’ve met all requirements, you might very well run into errors. Luckily it’s quite well documented on the interweb.

Once done, click Finish in the main screen and the screen will close. You are done installing.

Next, we create a database with dbca. You can also use grid control to do so. Once you filled out all parameters and start creating the database, notice there is a line in the progress window, stating

Registering database with Oracle Restart

And now for the real thing.

The main reason we installed Grid infrastructure is a feature called Oracle Restart. It can be checked and configured using the command ‘srvctl’. Let’s explore its possibilities.

First, check which databases are controlled by Oracle Restart

There’s one database registered by Oracle restart, our just created orcl.

How To Install Oracle Grid Infrastructure

Let’s check out this database:

The original goal of installing Grid infrastructure was to automatically start the database upon starting or rebooting the host.

So I rebooted (not visible here) and checked:

Good, that worked.

I also claimed that it would start the listener automatically. Has it done so?

That’s disappointing. Or is it? Maybe we should add the listener (default name LISTENER) to the srvctl configuration and start it:

Pity, it doesn’t show the listener. But it might be there:

I’ve rebooted the host at this time and sure enough, both the listener and the database started automatically.

Film serial rusesc online. Oct 24, 2014 Biata Anastasia (serial rusesc) - Episodul 2 Med Tracker. Unsubscribe from Med Tracker? Film Pistruiatul - 1973 (toate episoadele) - Duration: 5:22:27.

Oracle Grid Infrastructure Overview

So, we’ve met our target: both the listener and the database started without any human intervention. But it would be a shame to stop now since there are many more options in Oracle Restart. One in particular I mentioned in my introduction.

As we all know, or should know, one should connect to a database using a service, not to a SID. Let’s take another look at the Oracle Restart configuration of this specific database:

The last line, Services, is empty. Now we’ll add a service with the name ‘production’. As you can see we need to tell to which database this service should refer:

Look at the last parameter, -l PRIMARY. This tells Oracle Restart that this service should be started only if the database_role is PRIMARY. Redundant for a standalone database but in case of a dataguard configuration this is critical: The service ‘production’ will only be available if the server is the primary server. A standby server will never be reachable through this service name.

At the standby host you can add this same service on the standby database configuration. The service will only be started if that standby database becomes the primary database and that’s exactly what we want.

Okay, start the service and check: