Converting ASM to 12c FLEX ASM
Converting the 12c non flex ASM to flex ASMIn 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.
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=yoragrid @ 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
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
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/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 nodesFor 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 >
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
No comments:
Post a Comment