As the root user, configure oracleasm by using the command

oracleasm configure -i

and answer the prompts as shown in the screenshot.

Initialize the asmlib with the oracleasm init command. This command loads the oracleasm module and mounts the oracleasm filesystem.

Use the oracleasm createdisk <diskname> <device_name> command to create the ASM disk label for each disk.

In this tutorial name the disks DATA1, DATA2, DATA3, and DATA4 as shown in the screenshot.

Check that the disk are visible using the oracleasm listdisks command.

Check the the disks are mounted in the oracleasm filesystem with the command

ls -l /dev/oracleasm/disks

Open a terminal window as the OS user named oracle. This is the user that will own the Grid Infrastructure Installation. Change directories to the location that the clusterware software is staged.

cd /stage/clusterware/Disk1

Start the installer with the command

./runInstaller

On the first screen of the installer, select Install and Configure Grid Infrastructure for a Standalone Server. Click Next.

On the Select Product Languages screen, select the languages that should be supported in this installation. For this tutorial click the Move All button to select all the available languages. Click Next.

On the CreateASMDiskGroup screen,

• Set Redundancy to External
• Select the disks: ORCL:DATA1, ORCL:DATA2, and ORCL:DATA3.
• Click Next

On the Specify ASM Password page,

• Select 'Use same passwords for these accounts'
• Enter your password
• Confirm the password
• Click Next

On the Privileged Operating System Groups page,set each group to dba.

Note: these groups do not allow for job role separation. For this tutorial the database DBA and ASM administrator are assumed to be the same person, or have all the same privileges. A warning will appear. Click Yes.

On the Specify Installation Location page, the location of the database home will be shown

• Set the Software Location to /u01/app/grid/product/11.2.0/grid.
• Set the Oracle Base to /u01/app/grid
• Click Next

Note: the Grid infrastructure must be installed in a separate home directory from the database

The Perform Prerequisite Check page appears and completes the checks.

You may receive a failed RunLevel. This is ok. Select the Ignore All check box and click Next.

On the Summary page, the installation settings are shown. Click Finish to complete the installation.

The setup page shows the install progress.

• The Execute Configuration Scripts page asks you to execute a configuration script as the root user.

• Open a terminal window.
• connect as the root user. Use the su - root command to become the root user as shown in the screenshot.

• Copy the script name, /u01/app/grid/product/11.2.0/grid/root.sh, from the Execute Configuration Scripts page into to the terminal window and execute.

• When the script has completed, Click OK in the Execute Configuration Scripts page.

When the Finish page appears, with the message "The installation of Oracle Grid Infrastructure for single Server was successful", click Close

To manage the ASM instance in Enterprise Manager Database Control. you must configure the ASM Instance as a target. When you configure the ASM target, you must provide the port for the ASM listener. The Grid Infrastructure installs a listener by default on port 1521, and configures the ASM instance to use this listener. In this tutorial the database is already installed and has a listener configured on port 1521, the Grid Infrastructure places a listener on port 1522 and the ASM instance is registered with the grid listener.

In a terminal window as the oracle OS user, start EM database control with the command. If the console is already running the command will return "An instance of Oracle Enterprise Manager 11g Database Control is already running."

emctl start dbconsole

View the EM database control home page. Invoke the browser and enter the URL

https://host01.example.com:1158/em

When the login page appears enter:

• User: SYS
• Password: <your_password>
• Connect as: SYSDBA

The database instance home page appears: notice that the ASM target is absent from the expected position below Listener in the leftmost column.

Configure the ASM Target in EM database control.

1. Click the Server tab.
2. On the Server page, click Migrate to ASM.

On the Migrate Database to ASM : ASM Instance page, configure the ASM instance as a target.

• Change the Target name to +ASM.example.com
• Change Database Home to the ASM Home: /u01/app/grid/product/11.2.0/grid
• Enter the SYS password
• Change Port to: 1522
• In Host Credentials section enter Username: oracle,and the Password
• Click Continue

On the Migrate Database To ASM: Migration Options page click Cancel.

Create a tablespace named test with datafile named test01.dbf in the DATA diskgroup of the ASM instance

1. On the Server page, in the Storage section, click Tablespaces

2. On the Tablespaces page, click Create.

3. On the Create Tablespace page,

• enter Name: TEST
• Click Add

4. On the Add Datafile page

• Enter File Name: test01.dbf
• Enter File Directory: +DATA
• Click Continue

5. On the Create Tablespace page, click OK.

6. On the Tablespaces page confirm that the TEST tablespace has been created. Enter TEST in the search field and click Go.

7. The tablespace was created and is in the list.

In a terminal window as the oracle OS user stop, and restart EM database control with the commands.

emctl stop dbconsole

emctl start dbconsole

View the EM database instance home page, use the URL

https: host01.example.com:1158/em

Confirm that the ASM instance is now listed as a target.

Close your browser.

Stop EM database control with

emctl stop dbconsole

Determine which components are running. The pgrep -lf <string> command work well for this.

• Use pgrep -lf orcl to see the orcl instance processes

• Use pgrep -lf ASM to see the +ASM instance processes

• Use pgrep -lf tns to see the listeners

Shutdown the database instance with

sqlplus / as sysdba

SQL> shutdown immediate

SQL> exit

Stop the listener with the command

lsnrctl stop

In a terminal window as the oracle user, set the environment to user the ASM home with . oraenv and enter the ORACLE_SID +ASM when prompted.

In the same terminal window, shutdown the ASM instance

sqlplus / as sysasm

SQL> shutdown immediate

SQL> exit

In the same terminal window, stop the listener that was configured for the ASM instance with the command:

lsnrctl stop

The standard OBE environment automatically starts the database with the dbora service. The dbora service may not exist if you downloaded this OBE and configured your own environment. As the root user, remove the dbora service with the command:

su - root

chkconfig --del dbora

Use the --list option to determine if the dbora service is configured

chkconfig --list dbora

Now that all the Oracle related processes are stopped reboot the machine

In a terminal window as the root use the reboot command

reboot

Connect to the machine and Login

As the oracle user are any of the Oracle related processes running. Use the pgrep -lf command to check. The listener started from the database home directory is the only Oracle related process running

pgrep -lf orcl

pgrep -lf ASM

pgrep -lf tns

Enable Oracle restart to automatically start the registered components with the crsctl command This command must be run from the grid ORACLE_HOME directory (this is the same directory as the ASM home). You can set this by running oraenv as shown below and setting the ORACLE_SID to +ASM.

. oraenv

crsctl enable has

Attempt to start Oracle Restart with the crsctl utility. This fails because the ohasd process is already running. It was configured to restart automatically at boot time during the grid Infrastructure installation.

crsctl start has

Remove the grid infrastructure listener from the Oracle Restart configuration with the following command:

srvctl remove listener -l LISTENER

Change the name of the grid infrastructure listener. The default name LISTENER cannot be the same as the database listener if both listeners will be registered with Oracle Restart.

Edit the grid infrastructure listener.ora file at /u01/app/grid/product/11.2.0/grid/network/admin/listener.ora

vi /u01/app/grid/product/11.2.0/grid/network/admin/listener.ora

Change the name LISTENER to LISTENERASM.

Save the file

Add the grid infrastructure listener to the Oracle Restart configuration with the following command:

srvctl add listener -l LISTENERASM -p "TCP:1522" -o $ORACLE_HOME

Reconfigure the asm database in Oracle Restart to have a dependencies on the LISTENERASM. Use the commands listed below. Check the current configuration then modify it using the values shown in the configuration. Be sure to use your spfilename.

srvctl config asm

srvctl remove asm

srvctl add asm -l LISTENERASM -p +data/spfile.ora

srvctl config asm

Start the oracle grid components: listener, and asm, and then check that the +ASM instance and the LISTENERASM are running. Since they are configured in Oracle Restart, use the single command

srvctl start asm

pgrep -lf ASM

pgrep -lf tns

Start the oracle database components: listener, database instance and EM database control.

Change the environment to use the orcl instance ORACLE_HOME with

. oraenv

Start the listener with

lsnrctl start LISTENER

Start the database with

sqlplus / as sysdba

SQL> startup

SQL> exit

Start EM database control with

emctl start dbconsole

Enable Oracle Restart for the orcl database instance

Start EM database control at URL https://host01.example.com:1158/em

Navigate to the database home page.

In the High Availability section click the Disabled link for Oracle Restart

On the Specify Host Credentials page enter Username: oracle and Password:oracle

On the Confirmation: Register Database page, observe the command that will be executed, and then click Continue.

On the Database Home page, Oracle Restart now shows Enabled.

Register the database listener with Oracle Restart.

On the Database Home page, in the General section click the Listener name.

 

On the Listener: Listener_host01.example.com page, click the Disabled link for Oracle Restart.

 

On the Confirmation: Register Listener page observe the command to be executed.

srvctl add listener -l LISTENER -p TCP:1521 -o /u01/app/oracle/product/11.2.0/dbhome_1

Click Continue.

The Processing page appears, then the Listener Home page. The listener is now Enabled for Oracle Restart.

In a terminal window as the oracle OS user, start the database with the command

srvctl start database -d orcl

22.

As the root user reboot the machine with the command

su - root

reboot

Observe the oracle components that are started automatically with the pgrep commands:

pgrep -lf tns

pgrep -lf ASM

pgrep -lf orcl

Check the EM database control status with the command

emctl status dbconsole

Because the EM database is not included in Oracle Restart, it must be started manually.

The SPFILE for an ASM instance is in use anytime the ASM instance is active. The SPFILE can be copied with the spcopy command while the Instance is active. The spcopy command does not change which copy of the SPFILE is being used. The spmove command changes the Oracle Restart configuration so that the target SPFILE will be used on the next startup, and attempts to delete the source SPFILE. To move the SPIFLE the ASM instance must be stopped, this implies all instances using the ASM diskgroups must also be stopped

Stop the database, and asm diskgroup, with the srvctl command;

srvctl stop database -d orcl

srvctl stop diskgroup -g DATA

Check the configuration of the asm instance, determine the current location of the SPFILE using the command

srvctl config asm

Move the SPFILE for the ASM instance out of the ASM file. The SPFILE for ASM is created in the ASM diskgroup by default with the Grid Infrastructure installation. To move the SPFILE out of the ASM diskgroup and into filesystem , use the ASMCMD command spmove. The ASMCMD utility requires that the ASM environment is set.

. oraenv

asmcmd

ASMCMD> spmove +DATA/spfile.ora /u01/app/grid/product/11.2.0/grid/dbs/spfile+ASM.ora

Stop and restart the ASM instance to use the SPFILE in the new location. Use the ASMCMD commands shutdown and startup.

ASMCMD> shutdown

ASMCMD> startup

ASMCMD> mount DATA

Retrieve the location of the SPFILE registered in Oracle Restart with the spget command.

ASMCMD> spget

ASMCMD> exit

Using SQL*Plus commands, find the current location of the SPFILE. Connect to the ASM instance "as SYSASM"

sqlplus / as SYSASM

SQL> select sys_context('sys_cluster_properties','asm_spfile') from dual;

Move the SPFILE into the ASM diskgroup using SQL*Plus command

SQL> create SPFILE = '+DATA/spfile.ora' from memory;

Restart the ASM instance to use the new SPFILE.

SQL> shutdown immediate

SQL> startup

SQL> select sys_context('sys_cluster_properties','asm_spfile') from dual;

SQL> exit

Restart the orcl instance, and restore the status with the command

srvctl start database -d orcl

In a terminal window as the oracle user, and environment set to the orcl instance, stop EM database control and deconfigure with

/home/oracle/wkdir/gi_inst/deconfigem.sh

Remove objects stored in ASM from database instance orcl.

/home/oracle/wkdir/gi_inst/rmasmobj.sh

Run the deinstall_gi.sh script remove the database and the database listener from the Oracle Restart configuration.

/home/oracle/wkdir/gi_inst/deinstall_gi.sh

You will recieve 4 prompts.

The first is "Specify all Oracle Restart enabled listeners that are to be de-configured [LISTENERASM]:" Enter carriage return.

The second is :"De-configuring ASM will drop all the diskgroups and it's contents at cleanup time. This will affect all of the databases and ACFS that use this ASM instance(s).
If you want to retain the existing diskgroups or if any of the information detected is incorrect, you can modify by entering 'y'. Do you want to modify above information (y|n) [n]: " Enter carriage return

The third is: "Do you want to continue (y - yes, n - no)? [n]:" Enter y.

You will be prompted to run one or more scripts as root to complete the deinstallation. When prompted open a terminal and use the su - root command to become root. cut and paste the command from the deinstall script window to the root window and execute.

As the root user run the following script

su - root

/home/oracle/wkdir/gi_inst/cleanup_root.sh

exit

As the oracle OS user, reconfigure EM database control with the command:

/home/oracle/wkdir/gi_inst/reconfigem.sh