part 7. Database software install

Database Install
As a reminder how to use winscp:

• you need to know the public dns address of the newly image. This is easy to get from hybdridfox. Place the cursor over the running image, press the right button and a set of choices apprears. One of them is “Copy public DNS name to clipboard”.
• Add private key (ppk file)
• and root as user
• You can save the profile and give it some meaningful name

My DB install files were named V17530-01_1of2.zip and V17530-01_2of2.zip. I moved them with winscp as user oracle.

Move them to the stage directory and unzip them. You need to log in as user oracle so the username and group of extracted files is oracle and oinstall.
# unzip V17530-01_1of2.zip
# unzip V17530-01_2of2.zip
This created a number of directories under the /u01/stage directory.
Make directory where to install db and change owner. I created directory /u01/app
#cd /u01
#mkdir app
#chown oracle:oninstall appStart xming server on windows so you can have display of xprograms like the install progam and create a connection again to the linux image (disconnect and connect again)

Start the install program from the database subdirectory
#cd database
#./runInstaller.sh
This starts the database install program. I wanted to install first the sw only and then create the db as separate step. You mileage may vary.

Starting installation

I had a friend by as I am not really a DBA and he prefers to install SW first and then create the database

Single Server install for test environment

Languages - I accepted default; English

 Version of DB - I went with enterprise edition

Next the install program asks where to install the sw. I accepted the default which was /u01/app/oracle as the location. The installer will create the needed directory.
Next the group for SYSDBA

There is a really nice feature that the db install program does all types of checks about needed rpm packages and kernel parameters. It seemed that running the oracle-validated rpm had not cleared all issues.

The install program shows what issues are open and you can press the fix and check again button to clear the issues automatically. The installer has created a script that you must execute as root to appl the fixes

[root@localhost u01]# cd /tmp/CVU_11.2.0.1.0_oracle/

[root@localhost CVU_11.2.0.1.0_oracle]# ./runfixup.sh

Response file being used is :./fixup.response

Enable file being used is :./fixup.enable

Log file location: ./orarun.log

Setting Kernel Parameters...

kernel.sem = 250 32000 100 128

fs.file-max = 6815744

net.ipv4.ip_local_port_range = 9000 65500

net.core.rmem_default = 262144

net.core.wmem_default = 262144

net.core.rmem_max = 4194304

net.core.wmem_max = 1048576

fs.aio-max-nr = 1048576

uid=59895(oracle) gid=501(oinstall) groups=501(oinstall)

[root@localhost CVU_11.2.0.1.0_oracle]#

If you have not managed to run the Oracle-validated script as described earlier, you have to manually download the missing packages and install them as described earlier. In that case your screen would look like this:

The last remaining issue for me was that there was not enough swap space and the install program could not fix this.

Add swap space

I created new volume of 10G with hybridfox and attached it to the running image (waiting until it was fully attached); back to terminal window

I partitioned the disk with fdisk. With fdisk I created just one partition (meaning all data is on the first one) similarly to the other fdisk commands earlier.

[root@localhost CVU_11.2.0.1.0_oracle]# fdisk /dev/vdd

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel

Building a new DOS disklabel. Changes will remain in memory only,

until you decide to write them. After that, of course, the previous

content won't be recoverable.

The number of cylinders for this disk is set to 20805.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

   (e.g., DOS FDISK, OS/2 FDISK)

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): n

Command action

   e   extended

   p   primary partition (1-4)

p

Partition number (1-4): 1

First cylinder (1-20805, default 1):

Using default value 1

Last cylinder or +size or +sizeM or +sizeK (1-20805, default 20805):

Using default value 20805

Created the swap space with:

# mkswap /dev/vdd1

Edited fstab so that the swap space is automatically mounted. This is the final contents of the fstab file after adding swap space:

/dev/vda1               /                       ext3    defaults        0 0

tmpfs                   /dev/shm                tmpfs   defaults        0 0

devpts                  /dev/pts                devpts  gid=5,mode=620  0 0

sysfs                   /sys                    sysfs   defaults        0 0

proc                    /proc                   proc    defaults        0 0

/dev/vda2               /mnt                    ext2    defaults        0 0

/dev/vda3               swap                    swap    defaults        0 0

LABEL=u01               /u01                    ext3    defaults        0 0

/dev/vdc1               /u02                    ext3    defaults        0 0

/dev/vdd1               swap                    swap    defaults        0 0

And finally enabled the swap space with:

#Swapon /dev/vdd1

Now I could proceed with DB install. Summary page is shown:

 

Finish button starts the actual installation of sw.

Install program has created scripts to run as root to add additional stuff.

[root@localhost CVU_11.2.0.1.0_oracle]# cd /u01/app/oraInventory/

[root@localhost oraInventory]# ./orainstRoot.sh

Changing permissions of /u01/app/oraInventory.

Adding read,write permissions for group.

Removing read,write,execute permissions for world.

        

Changing groupname of /u01/app/oraInventory to oinstall.

The execution of the script is complete.

Second command fails as I did not have /opt on my system. This is the outut

[root@localhost dbhome_1]# pwd

/u01/app/oracle/product/11.2.0/dbhome_1

[root@localhost dbhome_1]# ./root.sh

Running Oracle 11g root.sh script...

The following environment variables are set as:

    ORACLE_OWNER= oracle

    ORACLE_HOME=  /u01/app/oracle/product/11.2.0/dbhome_1

Enter the full pathname of the local bin directory: [/usr/local/bin]:

   Copying dbhome to /usr/local/bin ...

   Copying oraenv to /usr/local/bin ...

   Copying coraenv to /usr/local/bin ...

Creating /etc/oratab file...

Entries will be added to the /etc/oratab file as needed by

Database Configuration Assistant when a database is created

Finished running generic part of root.sh script.

Now product-specific root actions will be performed.

Finished product-specific root actions.

/bin/mkdir: cannot create directory `/opt/ORCLfmap': No such file or directory

/bin/mkdir: cannot create directory `/opt/ORCLfmap/prot1_64': No such file or direct   ory

/bin/mkdir: cannot create directory `/opt/ORCLfmap/prot1_64/bin': No such file or di   rectory

/bin/mkdir: cannot create directory `/opt/ORCLfmap/prot1_64/etc': No such file or di   rectory

/bin/mkdir: cannot create directory `/opt/ORCLfmap/prot1_64/log': No such file or di   rectory

/bin/cp: cannot create regular file `/opt/ORCLfmap/prot1_64/bin': No such file or di   rectory

/bin/cp: cannot create regular file `/opt/ORCLfmap/prot1_64/bin': No such file or di   rectory

/bin/chmod: cannot access `/opt/ORCLfmap/prot1_64/bin/fmputl': No such file or direc   tory

/bin/chmod: cannot access `/opt/ORCLfmap/prot1_64/bin/fmputlhp': No such file or dir   ectory

/bin/cp: cannot create regular file `/opt/ORCLfmap/prot1_64/etc': No such file or di   rectory

[root@localhost dbhome_1]#

Just created /opt and re-ran.

[root@localhost dbhome_1]# mkdir /opt

[root@localhost dbhome_1]# ./root.sh

Running Oracle 11g root.sh script...

The following environment variables are set as:

    ORACLE_OWNER= oracle

    ORACLE_HOME=  /u01/app/oracle/product/11.2.0/dbhome_1

Enter the full pathname of the local bin directory: [/usr/local/bin]:

The file "dbhome" already exists in /usr/local/bin.  Overwrite it? (y/n)

[n]: y

   Copying dbhome to /usr/local/bin ...

The file "oraenv" already exists in /usr/local/bin.  Overwrite it? (y/n)

[n]: y

   Copying oraenv to /usr/local/bin ...

The file "coraenv" already exists in /usr/local/bin.  Overwrite it? (y/n)

[n]: y

   Copying coraenv to /usr/local/bin ...

Entries will be added to the /etc/oratab file as needed by

Database Configuration Assistant when a database is created

Finished running generic part of root.sh script.

Now product-specific root actions will be performed.

Finished product-specific root actions.

[root@localhost dbhome_1]#

And now we have the SW installed and can move to create the DB.