Steps to Relink 12c Grid

Relinking the 12c Grid 

In this Practice have have used 2 Nodes with the Hp-ux Itanium as the O/S with the 12c grid and 12c database with The standard cluster .. Before starting the re linking process we need to stop all the cluster services running in all the Nodes ..check the CRS and make sure that the crs had been in all the Nodes

Step 1  Unlock the grid infrastructure 

We need to unlock all the nodes in the grid infrastructure to perform the relink .. the unlocking can be done by the O/S root user ..before unlock the grid make sure that all the services had been  stopped correctly
As the root user navigate to the GRID_HOME/crs/install directory and run the command  perl rootcrs.pl -unlock  In all the nodes
Node1
root @ db01/prod01/oracle/12.1.0/12.1.0/grid/crs/install >perl rootcrs.pl -unlock
Using configuration parameter file: ./crsconfig_params
2014/06/29 11:50:07 CLSRSC-347: Successfully unlock /prod01/oracle/12.1.0/12.1.0/grid
root @ db01./prod01/oracle/12.1.0/12.1.0/grid/crs/install >
Node2
root @ db02/prod01/oracle/12.1.0/12.1.0/grid/crs/install >perl rootcrs.pl -unlock
Using configuration parameter file: ./crsconfig_params
2014/06/29 11:53:39 CLSRSC-347: Successfully unlock /prod01/oracle/12.1.0/12.1.0/grid
root @ db02/prod01/oracle/12.1.0/12.1.0/grid/crs/install >

Step 2 Relink for the grid owner[O/S]
Switch the user to the grid owner and set the environment variable for ORACLE_HOME and path for the grid user and navigate to ORACLE_HOME/bin and execute the command relink all in all the nodes 
Node1
oragrid @ db01/home/oragrid >echo $ORACLE_HOME
/prod01/oracle/12.1.0/12.1.0/grid

oragrid @ db01/prod01/oracle/12.1.0/12.1.0/grid/bin >relink all

writing relink log to: /prod01/oracle/12.1.0/12.1.0/grid/install/relink.log

Node2

oragrid @ db02/prod01/oracle/12.1.0/12.1.0/grid >echo $ORACLE_HOME

/prod01/oracle/12.1.0/12.1.0/grid

oragrid @ db01/prod01/oracle/12.1.0/12.1.0/grid/bin >relink all

writing relink log to: /prod01/oracle/12.1.0/12.1.0/grid/install/relink.log

Once the Re-link is done check the relink.log to find where any discard or any error Messages if there are error or discard messages fix the problem and move to next step .. else Proceed to the next step 

Step 3 Rootadd and rootcrs execution

Once the relink command had been successfully completed then we need to run the rootadd and rootcrs  again from the o/s root user

Run the rootadd_rdbms.sh from the GRID_HOME/rdbms/install as the root user run the command on all the nodes of the grid
Node1

root @ db01/prod01/oracle/12.1.0/12.1.0/grid/rdbms/install >pwd

/prod01/oracle/12.1.0/12.1.0/grid/rdbms/install

root @ db01/prod01/oracle/12.1.0/12.1.0/grid/rdbms/install >./rootadd_rdbms.sh

Node2

root @ db02/prod01/oracle/12.1.0/12.1.0/grid/rdbms/install >pwd

/prod01/oracle/12.1.0/12.1.0/grid/rdbms/install

root @ db02/prod01/oracle/12.1.0/12.1.0/grid/rdbms/install >./rootadd_rdbms.sh

After the execution of the rootadd_rdbms.sh we need to execute the perl rootcrs.pl -patch  it will start the all the Custer services .. we need to execute this command in all the nodes in the cluster
Node1

root @ db01/prod01/oracle/12.1.0/12.1.0/grid/crs/install >perl rootcrs.pl -patch

Using configuration parameter file: ./crsconfig_params

CRS-4123: Starting Oracle High Availability Services-managed resources

CRS-2672: Attempting to start 'ora.mdnsd' on 'db01'

CRS-2672: Attempting to start 'ora.evmd' on 'db01'

CRS-2676: Start of 'ora.mdnsd' on 'db01' succeeded

CRS-2676: Start of 'ora.evmd' on 'db01' succeeded

CRS-2672: Attempting to start 'ora.gpnpd' on 'db01'

CRS-2676: Start of 'ora.gpnpd' on 'db01' succeeded

CRS-2672: Attempting to start 'ora.gipcd' on 'db01'

CRS-2676: Start of 'ora.gipcd' on 'db01' succeeded

CRS-2672: Attempting to start 'ora.cssdmonitor' on 'db01'

CRS-2676: Start of 'ora.cssdmonitor' on 'db01' succeeded

CRS-2672: Attempting to start 'ora.cssd' on 'db01'

CRS-2672: Attempting to start 'ora.diskmon' on 'db01'

CRS-2676: Start of 'ora.diskmon' on 'db01' succeeded

CRS-2789: Cannot stop resource 'ora.diskmon' as it is not running on server 'db01'

CRS-2676: Start of 'ora.cssd' on 'db01' succeeded

CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'db01'

CRS-2672: Attempting to start 'ora.ctssd' on 'db01'

CRS-2676: Start of 'ora.ctssd' on 'db01' succeeded

CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'db01' succeeded

CRS-2672: Attempting to start 'ora.asm' on 'db01'

CRS-2676: Start of 'ora.asm' on 'db01' succeeded

CRS-2672: Attempting to start 'ora.storage' on 'db01'

CRS-2676: Start of 'ora.storage' on 'db01' succeeded

CRS-2672: Attempting to start 'ora.crsd' on 'db01'

CRS-2676: Start of 'ora.crsd' on 'db01' succeeded

CRS-6023: Starting Oracle Cluster Ready Services-managed resources

CRS-6017: Processing resource auto-start for servers: db01

CRS-2672: Attempting to start 'ora.scan1.vip' on 'db01'

CRS-2672: Attempting to start 'ora.ons' on 'db01'

CRS-2672: Attempting to start 'ora.db01.vip' on 'db01'

CRS-2672: Attempting to start 'ora.db02.vip' on 'db01'

CRS-2672: Attempting to start 'ora.cvu' on 'db01'

CRS-2676: Start of 'ora.cvu' on 'db01' succeeded

CRS-2676: Start of 'ora.scan1.vip' on 'db01' succeeded

CRS-2672: Attempting to start 'ora.LISTENER_SCAN1.lsnr' on 'db01'

CRS-2676: Start of 'ora.db02.vip' on 'db01' succeeded

CRS-2676: Start of 'ora.db01.vip' on 'db01' succeeded

CRS-2672: Attempting to start 'ora.LISTENER.lsnr' on 'db01'

CRS-2672: Attempting to start 'ora.LISTENER_OMPRD.lsnr' on 'db01'

CRS-2676: Start of 'ora.ons' on 'db01' succeeded

CRS-2672: Attempting to start 'ora.scan3.vip' on 'db01'

CRS-2672: Attempting to start 'ora.scan2.vip' on 'db01'

CRS-2676: Start of 'ora.LISTENER_OMPRD.lsnr' on 'db01' succeeded

CRS-2676: Start of 'ora.LISTENER.lsnr' on 'db01' succeeded

CRS-2676: Start of 'ora.LISTENER_SCAN1.lsnr' on 'db01' succeeded

CRS-2676: Start of 'ora.scan3.vip' on 'db01' succeeded

CRS-2672: Attempting to start 'ora.LISTENER_SCAN3.lsnr' on 'db01'

CRS-2676: Start of 'ora.scan2.vip' on 'db01' succeeded

CRS-2672: Attempting to start 'ora.LISTENER_SCAN2.lsnr' on 'db01'

CRS-2676: Start of 'ora.LISTENER_SCAN3.lsnr' on 'db01' succeeded

CRS-2676: Start of 'ora.LISTENER_SCAN2.lsnr' on 'db01' succeeded

CRS-2672: Attempting to start 'ora.omprd.db' on 'db01'

CRS-2676: Start of 'ora.omprd.db' on 'db01' succeeded

CRS-6016: Resource auto-start has completed for server db01

CRS-6024: Completed start of Oracle Cluster Ready Services-managed resources

CRS-4123: Oracle High Availability Services has been started.

Oracle Clusterware active version on the cluster is [12.1.0.1.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [0].

Node2

root @ db02.oasiserp.com/prod01/oracle/12.1.0/12.1.0/grid/crs/install >perl rootcrs.pl -patch

Using configuration parameter file: ./crsconfig_params
CRS-4123: Starting Oracle High Availability Services-managed resources
CRS-2672: Attempting to start 'ora.mdnsd' on 'db02'
CRS-2672: Attempting to start 'ora.evmd' on 'db02'
CRS-2676: Start of 'ora.evmd' on 'db02' succeeded
CRS-2676: Start of 'ora.mdnsd' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'db02'
CRS-2676: Start of 'ora.gpnpd' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.gipcd' on 'db02'
CRS-2676: Start of 'ora.gipcd' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'db02'
CRS-2676: Start of 'ora.cssdmonitor' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'db02'
CRS-2672: Attempting to start 'ora.diskmon' on 'db02'
CRS-2676: Start of 'ora.diskmon' on 'db02' succeeded
CRS-2789: Cannot stop resource 'ora.diskmon' as it is not running on server 'db02'
CRS-2676: Start of 'ora.cssd' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'db02'
CRS-2672: Attempting to start 'ora.ctssd' on 'db02'
CRS-2676: Start of 'ora.ctssd' on 'db02' succeeded
CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'db02'
CRS-2676: Start of 'ora.asm' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.storage' on 'db02'
CRS-2676: Start of 'ora.storage' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.crsd' on 'db02'
CRS-2676: Start of 'ora.crsd' on 'db02' succeeded
CRS-6017: Processing resource auto-start for servers: db02
CRS-2672: Attempting to start 'ora.ons' on 'db02'
CRS-2673: Attempting to stop 'ora.db02.vip' on 'db01'
CRS-2672: Attempting to start 'ora.ASMNET1LSNR_ASM.lsnr' on 'db02'
CRS-2673: Attempting to stop 'ora.LISTENER_SCAN1.lsnr' on 'db01'
CRS-2677: Stop of 'ora.LISTENER_SCAN1.lsnr' on 'db01' succeeded
CRS-2673: Attempting to stop 'ora.scan1.vip' on 'db01'
CRS-2677: Stop of 'ora.db02.vip' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.db02.vip' on 'db02'
CRS-2677: Stop of 'ora.scan1.vip' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.scan1.vip' on 'db02'
CRS-2676: Start of 'ora.db02.vip' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.LISTENER.lsnr' on 'db02'
CRS-2672: Attempting to start 'ora.LISTENER_OMPRD.lsnr' on 'db02'
CRS-2676: Start of 'ora.scan1.vip' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.LISTENER_SCAN1.lsnr' on 'db02'
CRS-2676: Start of 'ora.ASMNET1LSNR_ASM.lsnr' on 'db02' succeeded
CRS-2676: Start of 'ora.ons' on 'db02' succeeded
CRS-2676: Start of 'ora.LISTENER_SCAN1.lsnr' on 'db02' succeeded
CRS-2676: Start of 'ora.LISTENER.lsnr' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'db02'
CRS-2676: Start of 'ora.LISTENER_OMPRD.lsnr' on 'db02' succeeded
CRS-2676: Start of 'ora.asm' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.omprd.db' on 'db02'
CRS-2676: Start of 'ora.omprd.db' on 'db02' succeeded
CRS-6016: Resource auto-start has completed for server db02
CRS-6024: Completed start of Oracle Cluster Ready Services-managed resources
CRS-4123: Oracle High Availability Services has been started.
Oracle Clusterware active version on the cluster is [12.1.0.1.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [0].
Step 4

check the cluster now all the services should be up automatically
root @ db01/prod01/oracle/12.1.0/12.1.0/grid/bin >./crs_stat -t -v

Name           Type           R/RA   F/FT   Target    State     Host

----------------------------------------------------------------------

ora....SM.lsnr ora....er.type 0/5    0/     ONLINE    ONLINE    db01

ora.DATA.dg    ora....up.type 0/5    0/     ONLINE    ONLINE    db01

ora.FLASH.dg   ora....up.type 0/5    0/     ONLINE    ONLINE    db01

ora....ER.lsnr ora....er.type 0/5    0/     ONLINE    ONLINE    db01

ora....RD.lsnr ora....er.type 0/5    0/     ONLINE    ONLINE    db01

ora....N1.lsnr ora....er.type 0/5    0/0    ONLINE    ONLINE    db02

ora....N2.lsnr ora....er.type 0/5    0/0    ONLINE    ONLINE    db01

ora....N3.lsnr ora....er.type 0/5    0/0    ONLINE    ONLINE    db01

ora.asm        ora.asm.type   0/5    0/0    ONLINE    ONLINE    db01

ora.cvu        ora.cvu.type   0/5    0/0    ONLINE    ONLINE    db01

ora....SM1.asm application    0/5    0/0    ONLINE    ONLINE    db01

ora....01.lsnr application    0/5    0/0    ONLINE    ONLINE    db01

ora....01.lsnr application    0/5    0/0    ONLINE    ONLINE    db01

ora.db01.ons   application    0/3    0/0    ONLINE    ONLINE    db01

ora.db01.vip   ora....t1.type 0/0    0/0    ONLINE    ONLINE    db01

ora....SM2.asm application    0/5    0/0    ONLINE    ONLINE    db02

ora....02.lsnr application    0/5    0/0    ONLINE    ONLINE    db02

ora....02.lsnr application    0/5    0/0    ONLINE    ONLINE    db02

ora.db02.ons   application    0/3    0/0    ONLINE    ONLINE    db02

ora.db02.vip   ora....t1.type 0/0    0/0    ONLINE    ONLINE    db02

ora.gns        ora.gns.type   0/5    0/0    ONLINE    ONLINE    db01

ora.gns.vip    ora....ip.type 0/0    0/0    ONLINE    ONLINE    db01

ora....network ora....rk.type 0/5    0/     ONLINE    ONLINE    db01

ora.oc4j       ora.oc4j.type  0/1    0/2    OFFLINE   OFFLINE

ora.omprd.db   ora....se.type 0/2    0/1    ONLINE    ONLINE    db01

ora.ons        ora.ons.type   0/3    0/     ONLINE    ONLINE    db01

ora.scan1.vip  ora....ip.type 0/0    0/0    ONLINE    ONLINE    db02

ora.scan2.vip  ora....ip.type 0/0    0/0    ONLINE    ONLINE    db01

ora.scan3.vip  ora....ip.type 0/0    0/0    ONLINE    ONLINE    db01

Creating RCU for ADF Development

Creating the Rcu for ADF development 

Once the ADF Development  had  been installed then we can start the RCU  for the database
before start configuration of the domain .. The RCU will create the seeded schema which will be used for the different services of the middleware

We had used 12c database with the Oracle Linux six for this Practice 

Step 1
Navigate to the middle ware home and from the oracle_common and bin and start the rcu

Step 2
Click next to proceed to the next page

Step 3

There are three options which gives more flexibility for a person to run

[1]system load and product load   only run by the user who has the dba privileges

[2]Prepare Scripts for System Load -- it will create the script which contains all the schema  we need to provide the script to the person who has the sysdba privileges and execute the script

once the system load is done by the dba then the non dba can run the product load  

in this practice we are selecting the system Load and Product load

Step 4

Provide the database credentials for

Legends

Host name :Host name of the database Server

Port           :Database Port Number

Service Name: Database Service name

User name   : SYS

Password    :SYS password for the database [while creating the database for the adf create the orapw<instance_name> password for the sys] to connect remotely 

Role             :SYSDBA

Once  the database details are provide the prerequisite check start it process and all the prerequisite check is successful click ok to proceed 

Step 5

Select the necessary components which is need to be installed 

Step 6

Provide the password for sachems which is newly created 

Step 7

Step 8

Click the Create Button to Create the Schema for the Database

Installing Weblogic 12c on Linux 6

Installing Weblogic 12c Server on Linux 6

In this Practice we are going to install the weblogic server 12c in the oracle Linux 6.4 we had gone through the steps which will install the binary and later we need to create the Domain separately --

Prerequisites for installing webogic 12c on linux 6 

[1] Installing the required Java
Download the latest java which is certified to work with the webloigc 12c java 1.7_60 [which is the latest update of java 7 series] is certified to work with the 12c.. . For Linux the java 1.7 is available in the rpm as well as in the tar file .. Download the rpm and install the java
Download the JDK for linux for the oracle website
http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html

[root@omoicfin ~]# cd /tmp
[root@omoicfin tmp]# ll jdk*
-rw-r-----. 1 root root 126841508 Jun 24 21:36 jdk-7u60-linux-x64.rpm
[root@omoicfin tmp]# yum install /tmp/jdk-7u60-linux-x64.rpm

Once the java is installed then it will be available in the
[root@omoicfin java-1.7.0]# pwd
/usr/lib/java-1.7.0

[2]Create the user and groups for the weblogic in O/S

Create the weblogic owner  and the group as we had created the database user name and group previously for the weblogic user use the same primary group which is used for the database

[root@omoicfin ]# useradd -g oinstall -G oinstall , dba oraadf

[root@omoicfin ]# id oraadf
uid=54322(oraadf) gid=54321(oinstall) groups=54321(oinstall),54322(dba)

In O/s we have create the mount point /u02/app/oracle for install the weblogic server

Assign the newly create the weblogic user to own the mount point which the weblogic is going to be installed 

[root@omoicfin ]# chown -R oraadf:oinstall /u02/app/oracle

[root@omoicfin ]# chmod -R g+w /u02/app/oracle

[3]Set the Java Home to the latest Java Installed 

We need to Set the java home to the latest java which is installed  or the defalut java which comes with the OEL will be taken
[root@omoicfin java-1.7.0]# java -version
java version "1.7.0_09-icedtea"
OpenJDK Runtime Environment (rhel-2.3.4.1.0.1.el6_3-x86_64)
OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)

For setting the correct java for the weblogic add the JAVA_HOME env variable in the adfuser .bash_profile

export JAVA_HOME=/usr/java/jdk1.7.0_60

export PATH=$JAVA_HOME/bin:$PATH

log out and login and check the java version 

[oraadf@omoicfin ~]$ java -version

java version "1.7.0_60"

Java(TM) SE Runtime Environment (build 1.7.0_60-b19)

Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)

[oraadf@omoicfin ~]$

Step 1 
Start the Weblogic installer in the Linux by using the java which had been installed  according to the weblogic server requirements
login to the weblogic owner [o/s user which is created  for weblogic]and execute the command
java -jar  wls_121200.jar 

Invoke the Weblogic installer in the Linux 

This command will invoke the weblogic installer

Click Next to proceed to the Next Page

Step 2
Provide the Oracle Middle ware location home  where the s binaries will be installed

Step 3

Select the Installation type which we need to install if you want to proceed with the complete installation with the examples then select complete

 Step 4
Check the prerequisite check and make sure the prerequisite check completes successfully

Step 5
If the Server is connected with the internet then provide the metalink details

 Step 6
Check the installation summary and save the configuration file for the reference

Step 7
Check the installation progress and once the installation Process reaches  100% and then click next

 Step 8

Once  the Installation completes then if you want to go the configuration wizard then click the check box and click the finish button it will  take to the configuration screen or you can use the configh .sh  for configuration of the domains

The weblogic Binaries had been installed successfully .. next step is to proceed to the Domain configuration 

Converting 12c ASM to Flex ASM

Converting ASM to 12c FLEX ASM 

Converting the 12c non flex ASM to flex ASM
In this practice we had upgraded the 11gr2 grid to the 12c ..we can do the upgraed from 11g to 12c with the traditional asm and  once the upgrade is complete then we can convert the non flex asm to flex asm.
[Note] Once the ASM converted to flex ASM  then we cant convert back to the traditional ASM
 In 12c Both the asm types of asm are supported
As with out flex asm like the traditional asm we can run one asm instance in each RAC nodes ..  when we use the flex asm  the asm instance will be running in one node [or cordiality  which is set by us]
Here there are two different concepts introduced in the 12c.. Flex cluster's and Flex ASM both are different components  of  12c we can have flex asm with out flex cluster .. but enabling the flex cluster we need to have the flex asm enabled
The advantage of the flex ASM  we can separately have one instance for ASM and then it will communicate with all the RAC nodes and treat them as the client .. not like the traditional ASM that it is mandatory to have one asm instance running in all the RAC nodes
In this practice we have two cluster nodes running with the two asm instance .. once we finish the conversion we have one asm instance communication with the two database instance

Step 1
check the Mode of the ASM in the  12c
ASMCMD> lsdg
State    Type    Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
MOUNTED  EXTERN  N        1024   4096  4194304    819136   167912                0          167912              0             Y  DATA/
MOUNTED  EXTERN  N        1024   4096  4194304    511968   324560                0          324560              0             N  FLASH/

ASMCMD> showclustermode

ASM cluster : Flex mode disabled

ASMCMD>

oragrid @ db01/home/oragrid >asmcmd showclustermode
ASM cluster : Flex mode disabled

Step 2
Check the current ASM details before starting the conversion 

oragrid @ db01/home/oragrid >srvctl status asm -detail
ASM is running on db02,db01

ASM is enabled.

root @ db02/prod01/oracle/12.1.0/12.1.0/grid/bin >./srvctl status asm -detail
ASM is running on db02,db01

ASM is enabled.

oragrid @ db01/home/oragrid >srvctl config asm

ASM home: /prod01/oracle/12.1.0/12.1.0/grid

Password file:

ASM listener: LISTENER

oragrid @ db02./home/oragrid >srvctl config asm

ASM home: /prod01/oracle/12.1.0/12.1.0/grid

Password file:

ASM listener: LISTENER

Run the below query to find the attached ASM in each Node of the RAC 

SQL> SELECT instance_name, db_name, status FROM V$ASM_CLIENT;

INSTANCE_NAME                                                    DB_NAME  STATUS

---------------------------------------------------------------- -------- ------------

+ASM1                                                              +ASM       CONNECTED

OMPRD1                                                           OMPRD    CONNECTED

OMPRD1                                                           OMPRD    CONNECTED

SQL> SELECT instance_name, db_name, status FROM V$ASM_CLIENT;

INSTANCE_NAME                                                    DB_NAME  STATUS

---------------------------------------------------------------- -------- ------------

+ASM2                                                              +ASM     CONNECTED

OMPRD2                                                           OMPRD    CONNECTED

OMPRD2                                                           OMPRD    CONNECTED

Step 3

Changing compatibility mode of the ASM

Before starting the conversion of the asm to flex asm we need to Change the compatibility mode of the disk group to the 12 to enable the new features of the 12c 

Go to the Disk group tab through the asmca and select the disk group which we need to change the compatibility and select the edit attributes 

we can change the compatibility in two methods by using the asmca and by using the command line 

check the asm compatibility ASM the database compatibility  of the 12 c.. the default value will be displayed in the screen we need to update to the necessary values 

Query also to check the compatibility values of the asm diskgroup

SQL> SELECT name AS diskgroup, substr(compatibility,1,12) AS asm_compat,

     substr(database_compatibility,1,12) AS db_compat FROM V$ASM_DISKGROUP;

DISKGROUP                      ASM_COMPAT   DB_COMPAT

------------------------------ ------------ ------------

FLASH                          11.2.0.0.0   10.1.0.0.0

DATA                           11.2.0.0.0   10.1.0.0.0

Query to check the ASM disk group attributes 

SQL> SELECT SUBSTR(dg.name,1,12) AS diskgroup, SUBSTR(a.name,1,24) AS name,

  2       SUBSTR(a.value,1,24) AS value, read_only FROM V$ASM_DISKGROUP dg,

  3       V$ASM_ATTRIBUTE a WHERE dg.name = 'DATA' AND dg.group_number = a.group_number

  4       AND a.name NOT LIKE '%template%';

DISKGROUP    NAME                     VALUE                    READ_ON

------------ ------------------------ ------------------------ -------

DATA         disk_repair_time                       3.6h                       N

DATA         au_size                                     4194304                Y

DATA         access_control.umask               066                        N

DATA         access_control.enabled             FALSE                   N

DATA         cell.smart_scan_capable            FALSE                   N

DATA         compatible.rdbms                     10.1.0.0.0                N

DATA         compatible.asm                         11.2.0.0.0               N

DATA         sector_size                                1024                       Y

8 rows selected.

SQL>SELECT SUBSTR(dg.name,1,12) AS diskgroup, SUBSTR(a.name,1,24) AS name,   

  2       SUBSTR(a.value,1,24) AS value, read_only FROM V$ASM_DISKGROUP dg,

  3       V$ASM_ATTRIBUTE a WHERE dg.name = 'FLASH' AND dg.group_number = a.group_number

  4       AND a.name NOT LIKE '%template%';

DISKGROUP    NAME                     VALUE                    READ_ON

------------ ------------------------ ------------------------ -------

FLASH        disk_repair_time         3.6h                     N

FLASH        access_control.enabled   FALSE                    N

FLASH        cell.smart_scan_capable  FALSE                    N

FLASH        compatible.rdbms         10.1.0.0.0               N

FLASH        compatible.asm           11.2.0.0.0               N

FLASH        sector_size              1024                     Y

FLASH        au_size                  4194304                  Y

FLASH        access_control.umask     066                      N

8 rows selected.

change the compatibility version to the 12.1.0.0.0 in the asm compatibility column  and click ok to save the new value for the disk group 

once we are changing the compatibility mode in the asm then we can degrade the compatibility mode .. make sure that all the clients which is using the disk group is accessing by the 12.1 asm

In the manual command lime method we can give the below command with the appropriate attribute to change the value  

as we had already change the DATA disk group attribute by using the asmca now for the FLASH we can change by using the command line

SQL> ALTER DISKGROUP FLASH SET ATTRIBUTE 'compatible.asm' = '12.1';

Diskgroup altered.

SQL>  SELECT name AS diskgroup, substr(compatibility,1,12) AS asm_compat,

     substr(database_compatibility,1,12) AS db_compat FROM V$ASM_DISKGROUP;  2

DISKGROUP                      ASM_COMPAT   DB_COMPAT

------------------------------ ------------ ------------

FLASH                          12.1.0.0.0   10.1.0.0.0

DATA                           12.1.0.0.0   10.1.0.0.0

check the spfile is placed in the disk group before starting the conversion 

SQL> show parameter spfile

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

spfile                               string      +DATA/ommprod-cluster/asmparam

                                                 eterfile/registry.253.828933955

Step 4

Converting non flex asm to flex asm

start the asmca and check the asm instance page which has the information about the number for asm instance which is currently available in the cluster  

Step 5

clink the convert to oracle flex asm  a new pop up window will display the lan interconnects which can be used  for the  flex asm 

Select appropriate lan interconnect which had been configured as the cluster interconnect ip and verify the asm listener port the default port is 1521 and if needed we can change the port  

Step 6

Create the password file for the ASM  instance .. as the new feature of the 12c now the password files can be kept  in the disk groups in common so the asm clients can access the ASM 

we can create the new password file are we can use the existing password file as the input file and create the new password file in the disk group  which can be accessed by all asm clients 

Step 7

Moving the ASM password file into the Disk group 

orapwd input_file='/prod01/oracle/12.1.0/12.1.0/grid/dbs/orapwASM' file='+DATA/ASM/orapw+ASM' asm=y

oragrid @ db01/prod01/oracle/12.1.0/12.1.0/grid/dbs >0/grid/dbs/orapw+ASM' file='+DATA/ASM/orapw+ASM' asm=y                                      <
/usr/lib/hpux64/dld.so: Unable to find library 'libocrb12.so'.
Killed

Set the  LD_LIBRARY_PATH to access the particular library .. this error is caused due to the environment variable set up

oragrid @ db01/prod01/oracle/12.1.0/12.1.0/grid/lib >ll libocrb12.so

-rw-r--r--   1 root       oinstall   3808144 Dec 18  2013 libocrb12.so

set the LD_LIBRARY_PATH to $ORACLE_HOME/lib  or GRID_HOME/lib according to the home env variable  and try the command

If the compatibility Mode is not set as per Step 3 then this error occurs  .. when we upgrade the asm the default compatibility  of the ASM is set to the version before the upgrade we need to change the version to the 12.1 to enable the flex asm

oragrid @ db01/home/oragrid >orapwd input_file='/prod01/oracle/12.1.0/12.1.0/grid/dbs/orapw+ASM' file='+DATA/ASM/orapwASM' asm=y

OPW-00010: Could not create the password file.

ORA-15056: additional error message

ORA-15221: ASM operation requires compatible.asm of 12.1.0.0.0 or higher

ORA-06512: at line 4

All the ASM disk groups should be set to  the compatible mode to 12.1.0.0.0 the default compatible mode for the ASM is 11.2.0.0 we need to change the compatible mode to 12 as the password file can be store in the disk group was introduced in 12  

follow the previous steps  in Step 3 to change the comparability mode for the disk groups before moving the password file 

Create a new directory named ASM in the disk group which is going to store the password file 

oragrid @ db01/home/oragrid >asmcmd

ASMCMD> cd DATA

ASMCMD> ls

OMPRD/

ommprod-cluster/

spfileomprd.ora

ASMCMD> mkdir ASM

ASMCMD> ls

ASM/

OMPRD/

ommprod-cluster/

spfileomprd.ora

ASMCMD> exit

oragrid @ db01/home/oragrid >orapwd input_file='/prod01/oracle/12.1.0/12.1.0/grid/dbs/orapw+ASM' file='+DATA/ASM/orapwASM' asm=y

oragrid @ db01/home/oragrid >

check the newly create  password file by using the asmcmd

ASMCMD> ls -lt

Type      Redund  Striped  Time             Sys  Name

                                            Y    PASSWORD/

PASSWORD  UNPROT  COARSE   JUN 17 16:00:00  N    orapwasm => +DATA/ASM/PASSWORD/pwdasm.362.850494523

Now we can retry the conversion process to convert the asm to the Flex ASM
Once the password file is moved to the Disk group then we can resume the conversion of the ASM 

 

Step 8

Running the converttoFlexASM.sh script 

oragrid @ db01/prod01/oracle/12.1.0/oragrid/cfgtoollogs/asmca/scripts >ll
total 2
-rwxr-xr-x   1 oragrid    oinstall       530 Jun 17 16:39 converttoFlexASM.sh
oragrid @ db01/prod01/oracle/12.1.0/oragrid/cfgtoollogs/asmca/scripts >

Running the converttoFlexASM.sh script 

root @ db01.oasiserp.com/prod01/oracle/12.1.0/12.1.0/grid/bin >cd /prod01/oracle/12.1.0/oragrid/cfgtoollogs/asmca/scripts
root @ db01.oasiserp.com/prod01/oracle/12.1.0/oragrid/cfgtoollogs/asmca/scripts >./converttoFlexASM.sh
CRS-2673: Attempting to stop 'ora.crsd' on 'db01'
CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on 'db01'
CRS-2673: Attempting to stop 'ora.omprd.db' on 'db01'
CRS-2673: Attempting to stop 'ora.LISTENER_OMPRD.lsnr' on 'db01'
CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on 'db01'
CRS-2673: Attempting to stop 'ora.LISTENER_SCAN1.lsnr' on 'db01'
CRS-2677: Stop of 'ora.LISTENER_OMPRD.lsnr' on 'db01' succeeded
CRS-2677: Stop of 'ora.LISTENER.lsnr' on 'db01' succeeded
CRS-2673: Attempting to stop 'ora.db01.vip' on 'db01'
CRS-2677: Stop of 'ora.LISTENER_SCAN1.lsnr' on 'db01' succeeded
CRS-2673: Attempting to stop 'ora.scan1.vip' on 'db01'
CRS-2677: Stop of 'ora.omprd.db' on 'db01' succeeded
CRS-2673: Attempting to stop 'ora.DATA.dg' on 'db01'
CRS-2673: Attempting to stop 'ora.FLASH.dg' on 'db01'
CRS-2677: Stop of 'ora.DATA.dg' on 'db01' succeeded
CRS-2677: Stop of 'ora.FLASH.dg' on 'db01' succeeded
CRS-2673: Attempting to stop 'ora.asm' on 'db01'
CRS-2677: Stop of 'ora.asm' on 'db01' succeeded
CRS-2673: Attempting to stop 'ora.ASMNET1LSNR_ASM.lsnr' on 'db01'
CRS-2677: Stop of 'ora.scan1.vip' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.scan1.vip' on 'db02'
CRS-2677: Stop of 'ora.db01.vip' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.db01.vip' on 'db02'
CRS-2677: Stop of 'ora.ASMNET1LSNR_ASM.lsnr' on 'db01' succeeded
CRS-2676: Start of 'ora.scan1.vip' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.LISTENER_SCAN1.lsnr' on 'db02'
CRS-2676: Start of 'ora.LISTENER_SCAN1.lsnr' on 'db02' succeeded
CRS-2676: Start of 'ora.db01.vip' on 'db02' succeeded
CRS-2673: Attempting to stop 'ora.ons' on 'db01'
CRS-2677: Stop of 'ora.ons' on 'db01' succeeded
CRS-2673: Attempting to stop 'ora.net1.network' on 'db01'
CRS-2677: Stop of 'ora.net1.network' on 'db01' succeeded
CRS-2792: Shutdown of Cluster Ready Services-managed resources on 'db01' has completed
CRS-2677: Stop of 'ora.crsd' on 'db01' succeeded
CRS-2673: Attempting to stop 'ora.ctssd' on 'db01'
CRS-2673: Attempting to stop 'ora.evmd' on 'db01'
CRS-2673: Attempting to stop 'ora.storage' on 'db01'
CRS-2677: Stop of 'ora.storage' on 'db01' succeeded
CRS-2673: Attempting to stop 'ora.asm' on 'db01'
CRS-2677: Stop of 'ora.ctssd' on 'db01' succeeded
CRS-2677: Stop of 'ora.asm' on 'db01' succeeded
CRS-2673: Attempting to stop 'ora.cluster_interconnect.haip' on 'db01'
CRS-2677: Stop of 'ora.evmd' on 'db01' succeeded
CRS-2677: Stop of 'ora.cluster_interconnect.haip' on 'db01' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'db01'
CRS-2677: Stop of 'ora.cssd' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.evmd' on 'db01'
CRS-2676: Start of 'ora.evmd' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'db01'
CRS-2676: Start of 'ora.cssdmonitor' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'db01'
CRS-2672: Attempting to start 'ora.diskmon' on 'db01'
CRS-2676: Start of 'ora.diskmon' on 'db01' succeeded
CRS-2676: Start of 'ora.cssd' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.ctssd' on 'db01'
CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'db01'
CRS-2676: Start of 'ora.ctssd' on 'db01' succeeded
CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'db01'
CRS-2676: Start of 'ora.asm' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.storage' on 'db01'
CRS-2676: Start of 'ora.storage' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.crsd' on 'db01'
CRS-2676: Start of 'ora.crsd' on 'db01' succeeded
Cluster bounced in node db01
CRS-2673: Attempting to stop 'ora.crsd' on 'db02'
CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on 'db02'
CRS-2673: Attempting to stop 'ora.LISTENER_OMPRD.lsnr' on 'db02'
CRS-2673: Attempting to stop 'ora.LISTENER_SCAN3.lsnr' on 'db02'
CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on 'db02'
CRS-2673: Attempting to stop 'ora.LISTENER_SCAN2.lsnr' on 'db02'
CRS-2673: Attempting to stop 'ora.cvu' on 'db02'
CRS-2677: Stop of 'ora.LISTENER_OMPRD.lsnr' on 'db02' succeeded
CRS-2677: Stop of 'ora.LISTENER_SCAN3.lsnr' on 'db02' succeeded
CRS-2673: Attempting to stop 'ora.scan3.vip' on 'db02'
CRS-2677: Stop of 'ora.LISTENER.lsnr' on 'db02' succeeded
CRS-2677: Stop of 'ora.LISTENER_SCAN2.lsnr' on 'db02' succeeded
CRS-2673: Attempting to stop 'ora.scan2.vip' on 'db02'
CRS-2677: Stop of 'ora.scan3.vip' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.scan3.vip' on 'db01'
CRS-2677: Stop of 'ora.scan2.vip' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.scan2.vip' on 'db01'
CRS-2676: Start of 'ora.scan3.vip' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.LISTENER_SCAN3.lsnr' on 'db01'
CRS-2676: Start of 'ora.scan2.vip' on 'db01' succeeded
CRS-2672: Attempting to start 'ora.LISTENER_SCAN2.lsnr' on 'db01'
CRS-2673: Attempting to stop 'ora.omprd.db' on 'db02'
CRS-2673: Attempting to stop 'ora.db02.vip' on 'db02'
CRS-2677: Stop of 'ora.db02.vip' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.db02.vip' on 'db01'
CRS-2677: Stop of 'ora.omprd.db' on 'db02' succeeded
CRS-2673: Attempting to stop 'ora.DATA.dg' on 'db02'
CRS-2673: Attempting to stop 'ora.FLASH.dg' on 'db02'
CRS-2677: Stop of 'ora.DATA.dg' on 'db02' succeeded
CRS-2676: Start of 'ora.LISTENER_SCAN3.lsnr' on 'db01' succeeded
CRS-2677: Stop of 'ora.FLASH.dg' on 'db02' succeeded
CRS-2673: Attempting to stop 'ora.asm' on 'db02'
CRS-2677: Stop of 'ora.asm' on 'db02' succeeded
CRS-2673: Attempting to stop 'ora.ASMNET1LSNR_ASM.lsnr' on 'db02'
CRS-2676: Start of 'ora.LISTENER_SCAN2.lsnr' on 'db01' succeeded
CRS-2677: Stop of 'ora.ASMNET1LSNR_ASM.lsnr' on 'db02' succeeded
CRS-2676: Start of 'ora.db02.vip' on 'db01' succeeded
CRS-2677: Stop of 'ora.cvu' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.cvu' on 'db01'
CRS-2676: Start of 'ora.cvu' on 'db01' succeeded
CRS-2673: Attempting to stop 'ora.ons' on 'db02'
CRS-2677: Stop of 'ora.ons' on 'db02' succeeded
CRS-2673: Attempting to stop 'ora.net1.network' on 'db02'
CRS-2677: Stop of 'ora.net1.network' on 'db02' succeeded
CRS-2792: Shutdown of Cluster Ready Services-managed resources on 'db02' has completed
CRS-2677: Stop of 'ora.crsd' on 'db02' succeeded
CRS-2673: Attempting to stop 'ora.ctssd' on 'db02'
CRS-2673: Attempting to stop 'ora.evmd' on 'db02'
CRS-2673: Attempting to stop 'ora.storage' on 'db02'
CRS-2677: Stop of 'ora.storage' on 'db02' succeeded
CRS-2673: Attempting to stop 'ora.asm' on 'db02'
CRS-2677: Stop of 'ora.ctssd' on 'db02' succeeded
CRS-2677: Stop of 'ora.asm' on 'db02' succeeded
CRS-2673: Attempting to stop 'ora.cluster_interconnect.haip' on 'db02'
CRS-2677: Stop of 'ora.cluster_interconnect.haip' on 'db02' succeeded
CRS-2677: Stop of 'ora.evmd' on 'db02' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'db02'
CRS-2677: Stop of 'ora.cssd' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.evmd' on 'db02'
CRS-2676: Start of 'ora.evmd' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'db02'
CRS-2676: Start of 'ora.cssdmonitor' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'db02'
CRS-2672: Attempting to start 'ora.diskmon' on 'db02'
CRS-2676: Start of 'ora.diskmon' on 'db02' succeeded
CRS-2676: Start of 'ora.cssd' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.ctssd' on 'db02'
CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'db02'
CRS-2676: Start of 'ora.ctssd' on 'db02' succeeded
CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'db02'
CRS-2676: Start of 'ora.asm' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.storage' on 'db02'
CRS-2676: Start of 'ora.storage' on 'db02' succeeded
CRS-2672: Attempting to start 'ora.crsd' on 'db02'
CRS-2676: Start of 'ora.crsd' on 'db02' succeeded
Cluster bounced in node db02
root @ db01.oasiserp.com/prod01/oracle/12.1.0/oragrid/cfgtoollogs/asmca/scripts >
Once the script is completed  then  once stop the cluster in all the nodes and start the cluster   we need to do this step because some time while bouncing the cluster there may be one or two proces which remains as zombi process .. so once you shutdown all the cluster . and check and conform no process exists from previous session and then start the cluster

Step 8 

Changing the cardinality of the FLEX ASM

we can set the cardinality of the asm according to the number of nodes
For two nodes  we  set the cardinality as one so asm will be running in one instance  and all the database instance will be communications with this asm instance
oragrid @ db01/home/oragrid >srvctl modify asm -count 1

oragrid @ db01home/oragrid >srvctl config asm
ASM home: /prod01/oracle/12.1.0/12.1.0/grid
Password file: +DATA/ASM/orapwasm
ASM listener: LISTENER
ASM instance count: 1
Cluster ASM listener: ASMNET1LSNR_ASM
oragrid @ db01.oasiserp.com/home/oragrid >

Query's to check the client connections in the FLEX ASM





SQL> SELECT instance_name, db_name, status FROM V$ASM_CLIENT;

INSTANCE_NAME                                                    DB_NAME  STATUS
---------------------------------------------------------------- -------- ------------
+ASM1                                                            +ASM     CONNECTED
OMPRD1                                                           OMPRD    CONNECTED
OMPRD1                                                           OMPRD    CONNECTED
OMPRD2                                                           OMPRD    CONNECTED
OMPRD2                                                           OMPRD    CONNECTED

SQL>

SQL>  select group_number,instance_name,status from gv$asm_client where DB_NAME='+ASM';

GROUP_NUMBER INSTANCE_NAME                                                    STATUS
------------ ---------------------------------------------------------------- ------------
           1 +ASM1                                                            CONNECTED


SQL> select distinct i.instance_name asm_instance_name, c.instance_name client_instance_name, c.db_name, c.status from gv$instance i, gv$asm_client c where i.inst_id=c.inst_id;

ASM_INSTANCE_NAM CLIENT_INSTANCE_NAME                                             DB_NAME  STATUS
---------------- ---------------------------------------------------------------- -------- ------------
+ASM1            +ASM1                                                            +ASM     CONNECTED
+ASM1            OMPRD1                                                           OMPRD    CONNECTED
+ASM1            OMPRD2                                                           OMPRD    CONNECTED


oragrid @ db01/home/oragrid >asmcmd lsct data
DB_Name  Status     Software_Version  Compatible_version  Instance_Name  Disk_Group
+ASM     CONNECTED        12.1.0.1.0          12.1.0.1.0  +ASM1          DATA
OMPRD    CONNECTED        12.1.0.1.0          11.2.0.0.0  OMPRD1         DATA
OMPRD    CONNECTED        12.1.0.1.0          11.2.0.0.0  OMPRD2         DATA


oragrid @ db01/home/oragrid >asmcmd lsct flash
DB_Name  Status     Software_Version  Compatible_version  Instance_Name  Disk_Group
OMPRD    CONNECTED        12.1.0.1.0          11.2.0.0.0  OMPRD1         FLASH
OMPRD    CONNECTED        12.1.0.1.0          11.2.0.0.0  OMPRD2         FLASH

SQL> select INST_ID,GROUP_NUMBER, INSTANCE_NAME, DB_NAME, INSTANCE_NAME||':'||DB_NAME client_id,
STATUS from gv$asm_client where DB_NAME = 'OMPRD';  2

   INST_ID GROUP_NUMBER INSTANCE_NAME        DB_NAME  CLIENT_ID                                                                 STATUS
---------- ------------ -------------------- -------- ------------------------------------------------------------------------- ------------
         1            1 OMPRD1               OMPRD    OMPRD1:OMPRD                                                              CONNECTED
         1            2 OMPRD1               OMPRD    OMPRD1:OMPRD                                                              CONNECTED
         1            1 OMPRD2               OMPRD    OMPRD2:OMPRD                                                              CONNECTED
         1            2 OMPRD2               OMPRD    OMPRD2:OMPRD                                                              CONNECTED

SQL> select INSTANCE_NUMBER,INSTANCE_NAME,STATUS, HOST_NAME from v$instance;

INSTANCE_NUMBER INSTANCE_NAME        STATUS       HOST_NAME
--------------- -------------------- ------------ ----------------------------------------------------------------
              1 +ASM1                STARTED      db01<domain>.com


IN this Above Practice we have converted  the flex ASM with out flex Cluster ..

FLEX ASM with out Flex Cluster

It is not mandatory to change the cluster to flex cluster  for converting the asm to flex asm with the standard cluster  oracle Flex asm can be used 

Note:-once you have converted the non flex asm to flex asm then you cant go back normal asm
          For enabling the flex cluster it is mandatory that ASM should be in FLEX ASM
          we can run the Flex ASM with out flex cluster

Upgrade 11.2.0.3 cluster to 12.1.0 cluster

Upgrading 11gr2 grid to 12c Grid

We have two node 11.2.0.3 Rac database with the 11.2.0.3 grid as the environment for this Practice The 11.2.0.3 can be directly upgrade to 12c as the out box box upgrade by creating the new grid_home for 12c   . The O/s we are using in this practice is hp-ux 11.31 for Itanium Servers'

Step 1

Check the cluster status before starting the upgrade and make sure the necessary services are running
oragrid @ db01/prod01/oracle/11.2.0/grid/bin >./crs_stat -t -v
Name           Type           R/RA   F/FT   Target    State     Host
----------------------------------------------------------------------
ora.DATA.dg    ora....up.type 0/5    0/     ONLINE    ONLINE    db01
ora.FLASH.dg   ora....up.type 0/5    0/     ONLINE    ONLINE    db01
ora....ER.lsnr ora....er.type 0/5    0/     ONLINE    ONLINE    db01
ora....RD.lsnr ora....er.type 0/5    0/     ONLINE    ONLINE    db01
ora....N1.lsnr ora....er.type 0/5    0/0    OFFLINE   OFFLINE
ora.asm        ora.asm.type   0/5    0/     ONLINE    ONLINE    db01
ora.cvu        ora.cvu.type   0/5    0/0    ONLINE    ONLINE    db02
ora....SM1.asm application    0/5    0/0    ONLINE    ONLINE    db01
ora....01.lsnr application    0/5    0/0    ONLINE    ONLINE    db01
ora....01.lsnr application    0/5    0/0    ONLINE    ONLINE    db01
ora.db01.gsd   application    0/5    0/0    OFFLINE   OFFLINE
ora.db01.ons   application    0/3    0/0    ONLINE    ONLINE    db01
ora.db01.vip   ora....t1.type 0/0    0/0    ONLINE    ONLINE    db01
ora....SM2.asm application    0/5    0/0    ONLINE    ONLINE    db02
ora....02.lsnr application    0/5    0/0    ONLINE    ONLINE    db02
ora....02.lsnr application    0/5    0/0    ONLINE    ONLINE    db02
ora.db02.gsd   application    0/5    0/0    OFFLINE   OFFLINE
ora.db02.ons   application    0/3    0/0    ONLINE    ONLINE    db02
ora.db02.vip   ora....t1.type 0/0    0/0    ONLINE    ONLINE    db02
ora.gsd        ora.gsd.type   0/5    0/     OFFLINE   OFFLINE
ora....network ora....rk.type 0/5    0/     ONLINE    ONLINE    db01
ora.oc4j       ora.oc4j.type  0/1    0/2    OFFLINE   OFFLINE
ora.omprd.db   ora....se.type 0/2    0/1    ONLINE    ONLINE    db01
ora.ons        ora.ons.type   0/3    0/     ONLINE    ONLINE    db01
ora.scan1.vip  ora....ip.type 0/0    0/0    OFFLINE   OFFLINE

Step 2

Download the  below Software binaries for the  oracle cloud

Step 3

Minor Number for Device files 

check the async value in all nodes of the grid and if the async value differs then change to the suitable value

The recommended values for the async in hp-ux are  101 0x4 [or] 101 0x104
We can use the command  /sbin/mknod to change the value to the async device file
move the old file to different name and create the new file with the desired values
Node1

root @ db01/prod01/oracle >mv /dev/async /dev/async_old_db01

root @ db01./prod01/oracle >/sbin/mknod /dev/async c 101 0x104

Node2

root @ db02./prod01/oracle >mv /dev/async /dev/async_old_db02

root @ db02/prod01/oracle >/sbin/mknod /dev/async c 101 0x104

Step 4
Running the cluster verify and checking the SCAN

Run the cluster verify command  with the parameter value as per to verify the values before upgrade and check the scan listener 

Check all the O/S Prerequisites by using the cluster verify command
If you have configured the scan listener in 11g by adding the host name with one ip in 12c it is mandatory to have DNS configuration with three ip's
reconfigure the scan listener with the three ip's after making the necessary changed in the DNS if the Sacn  existing meets the requirement then we can go head oraprod @ db01/prod01/oracle/11.2.0/grid/bin >srvctl config scan
SCAN name: ommprod-cluster-scan, Network: 1
Subnet IPv4: 192.168.5.0/255.255.255.0/lan0
Subnet IPv6:
SCAN 0 IPv4 VIP: <ip_address>
SCAN name: ommprod-cluster-scan, Network: 1
Subnet IPv4: 192.168.5.0/255.255.255.0/lan0
Subnet IPv6:
SCAN 1 IPv4 VIP: <ipaddress>
SCAN name: ommprod-cluster-scan, Network: 1
Subnet IPv4: 192.168.5.0/255.255.255.0/lan0
Subnet IPv6:
SCAN 2 IPv4 VIP: <ip_address>
oraprod @ db01/prod01/oracle/11.2.0/grid/bin >srvctl status scan
SCAN VIP scan1 is enabled
SCAN VIP scan1 is running on node db01
SCAN VIP scan2 is enabled
SCAN VIP scan2 is running on node db02
SCAN VIP scan3 is enabled
SCAN VIP scan3 is running on node db01

Step 5

Backup the OCr disk' and  unset the env variables .. shutdown the database before upgrade of cluster

root @ db01.oasiserp.com/prod01/oracle/11.2.0/grid/bin >./ocrconfig -manualbackup
check the ocr's status by using the ocrcheck and you can check the list of backup files also by using the ocrcheck
Shutdown the database before starting the upgrade of the grid
Unset all the env variables which is pointing to the old location of the grid home
Set the new grid home and patch to start the run installer .. if OUI has Problems with the Host name not found then set the env variable as ORACLE_HOSTNAME ..

Step 6

upgrading the 11gr2 grid to 12c 

start the OUI 

Step7

skip or provide the MOS credentials

Step8
Select the upgrade the grid infrastructure to upgrade the existing 11.2.0.3 grid to the 12 c 

Step 9
Select the Preferred Language

Step10

Select the Node which need to be upgraded in our env e have two node cluster and we had selected both the nodes
As we are in the Process of upgrade the User equivalence between the two nodes had been existing  in the environment

Step 11

Select the necessary groups for OAASM [asmadmin] , ASMDBA [asmdba] ASM operator [asmoper]

Step12
Select the Oracle base and the oracle home for the new grid installation we are doing the out of box installation and specify the new location instead of the old software location

Step13

we can provide the root password to run the  root configuration scripts instead of manual running in each nodes -e decided to run as manual and skipped this page

if you want to run the root scripts automatically then skip this page and follow the steps from 13a ,13b

Step 13A

 we can provide the root password for running the scripts

Step 13B

Once the root password is provide and we had many nodes you can combine the nodes into a batch processing to run the root script here we had to nodes combined to single batch and the batch will be running the sequence if the large number of nodes are present

Step 14

check the Prerequisite and fix the warnings before staring to process

check the async value and set to appropriate value check the step 3 kernel warnings can be fixed by running the fix script or by using the kctune in hp-ux or changing manually  the kernel values according to  recommendations

Step 14 B

Once the all the values are fixed and then you will get the response file page 

save the response file and start the installation

Step 15

Once the GUI installtion is completed in both the nodes then you will pop up prompting for run the rootupgrade.sh script from the grid home form all the Nodes 

Once the rootupgrade.sh had been completed in both the nodes the installation is completed and the grid service's will be up

Check the ASM  and check the asm disk which had been attached

oragrid @ db01/prod01/oracle/12.1.0/12.1.0/grid >sqlplus

SQL*Plus: Release 12.1.0.1.0 Production on Fri Mar 14 10:04:04 2014

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

Enter user-name: sys as sysasm

Enter password:

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

With the Real Application Clusters and Automatic Storage Management options

SQL> set line 300

SQL> select name, header_status, path from v$asm_disk;

NAME                           HEADER_STATU PATH

------------------------------ ------------ ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

DATA_0000                      MEMBER       /dev/vg_data1/rlv_data1

DATA_0001                      MEMBER       /dev/vg_data2/rlv_data2

DATA_0002                      MEMBER       /dev/vg_data3/rlv_data3

DATA_0003                      MEMBER       /dev/vg_data4/rlv_data4

FLASH_0000                     MEMBER       /dev/vg_flash1/rlv_flash1

FLASH_0001                     MEMBER       /dev/vg_flash2/rlv_flash2

6 rows selected.

oragrid @ db01.oasiserp.com/prod01/oracle/12.1.0/12.1.0/grid >asmcmd

ASMCMD> lsdg

State    Type    Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name

MOUNTED  EXTERN  N        1024   4096  4194304    819136   167912                0          167912              0             Y  DATA/

MOUNTED  EXTERN  N        1024   4096  4194304    511968   340428                0          340428              0             N  FLASH/

ASMCMD>

 Step 16

Conform the software version's in both the nodes the 11.2.0.3 database is compitable with the 12.1cluster so we can start the database and verify before we start the upgrade of the database to 12.1

Node 1

root @ db01/prod01/oracle/12.1.0/12.1.0/grid/bin >./olsnodes -s
db01 Active
db02 Active
root @ db01/prod01/oracle/12.1.0/12.1.0/grid/bin >./crsctl query crs softwareversion
Oracle Clusterware version on node [db01] is [12.1.0.1.0]
root @ db01/prod01/oracle/12.1.0/12.1.0/grid/bin >./crsctl query crs activeversion
Oracle Clusterware active version on the cluster is [12.1.0.1.0]
root @ db01/prod01/oracle/12.1.0/12.1.0/grid/bin >

Node2
root @ db02/prod01/oracle/12.1.0/12.1.0/grid/bin >./crsctl query crs softwareversion
Oracle Clusterware version on node [db02] is [12.1.0.1.0]
root @ db02./prod01/oracle/12.1.0/12.1.0/grid/bin >./olsnodes -s
db01 Active
db02 Active
root @ db02prod01/oracle/12.1.0/12.1.0/grid/bin >./crsctl query crs activeversion
Oracle Clusterware active version on the cluster is [12.1.0.1.0]
root @ db02/prod01/oracle/12.1.0/12.1.0/grid/bin >