How to split BCV and open oracle ASM database

How to split BCV and open oracle ASM database

All

Linux Articles / All 47 Views comments

BCV (Enterprise Continuance Quantity ) is the goal quantity for EMC Symmetrix TimeFinder/Mirror course of. When a BCV is absolutely synchronized with a knowledge gadget, the BCV is separated or cut up, thus turns into out there to a number for backup or different host processes. Briefly, a BCV cut up is a tool to be a clone of one other system. Earlier than you employ BCV cut up as oracle backup, it is advisable to slender down what's contained on the backed up volumes. You need to use BCV cut up to backup solely asm disks along with rdbms datafiles, redologs, and controlfiles. BCV cut up of the GRID_HOME won't work.

Everytime you use BCV cut up, the method of cloning consists of the next levels:

  1. Set up Grid Infrastructure software program on the vacation spot.
  2. Mount bcv cut up volumes and verify entry to the disks.
  3. Convey up asm occasion and mount disk teams.
  4. Deliver up rdbms occasion and recuperate the database.

1. INSTALL GRID INFRASTRUCTURE SOFTWARE ON THE DESTINATION

The Oracle model ought to match on supply and vacation spot servers. Even when you have a RAC setup on the supply finish, you possibly can set up a standalone grid model on the vacation spot.

2. MOUNT BCV SPLIT VOLUMES AND CHECK ACCESS TO THE DISKS

1. When you encounter issues mounting BCV cut up, contact EMC.
http://www.emc.com
http://www.emc.com/collateral/software program/white-papers/h5550-backup-oracle-symmetrix-netwrk-powernsap-wp.pdf

2. After BCV cut up is mounted on the vacation spot, ensure that the software program proprietor (oracle or grid relying on the model) has full entry to the disks. For that use kfod utility. We will simulate the disk discovery from the working system degree, utilizing device kfod. ($ORACLE_HOME/bin). The execution syntax is:

$ kfod asm_diskstring='/dev/rdsk/*' disks=all

or

$ kfod asm_diskstring='dev/oracleasm/disks/*' disks=all

or

$ kfod asm_diskstring='ORCL:*' disks=all

Instance of syntax:

$ cd $ORACLE_HOME/bin
$ kfod disks=all
$ kfod standing=TRUE dscvgroup=TRUE asm_diskstring='/dev/xvd*' disks=all
$ kfod standing=TRUE dscvgroup=TRUE asm_diskstring='/dev/rhdisk*' disks=all
$ kfod standing=TRUE dscvgroup=TRUE asm_diskstring='/dev/emcpower*' disks=all

the place asm_diskstring is your legitimate path to the disks.

three. Verify disk permissions, supply and vacation spot ought to match. proprietor:group of the cloned disks have to be owned by the ASM OS consumer.

four. If kfod output obtain the subsequent error that might point out that the candidate uncooked units aren't accessible at OS degree by the grid or oracle OS customers, subsequently ASM or ASM instruments will be unable to detect or use it till this drawback is fastened:

ORA-15025: couldn't open disk "/dev/rdsk/c3t60080E500017CAA8000006954EEA57CDd0s0"
SVR4 Error: 13: Permission denied

In such case please join as oracle or grid OS consumer and confirm you possibly can learn and write utilizing the dd OS command as comply with on the uncooked units as comply with:

$ id
$ dd if=/dev/null of=/dev/rdsk/c3t60080E500017CAA8000006954EEA57CDd0s0 bs=8192 rely=12800

If dd reviews the identical issues then you will need to interact your OS and Storage help to right the entry on the disks/uncooked units to the grid and oracle OS customers. Don't proceed to the subsequent step till kfod utility returns right entry to the disks. Output can be just like the next (consumer and group ought to match on the supply and vacation spot)

$ kfod asm_diskstring='/dev/rhdisk*' disks=all
--------------------------------------------------------------------------------
 Disk          Measurement Path                                     Consumer     Group
================================================================================
   1:     102400 Mb /dev/rhdisk2                             grid   asmadmin
   2:     102400 Mb /dev/rhdisk3                             grid   asmadmin
   three:     102400 Mb /dev/rhdisk4                             grid   asmadmin
   four:     102400 Mb /dev/rhdisk5                             grid   asmadmin
--------------------------------------------------------------------------------
ORACLE_SID ORACLE_HOME                                                          
================================================================================
      +ASM /u01/app/grid/product/11.2.zero/grid   

or

$ kfod asm_diskstring='/dev/rhdisk*' disks=all
--------------------------------------------------------------------------------
 Disk          Measurement Path                                     Consumer     Group
================================================================================
   1:     102400 Mb /dev/rhdisk2                             oracle   dba
   2:     102400 Mb /dev/rhdisk3                             oracle   dba
   three:     102400 Mb /dev/rhdisk4                             oracle   dba
   four:     102400 Mb /dev/rhdisk5                             oracle   dba
--------------------------------------------------------------------------------
ORACLE_SID ORACLE_HOME                                                          
================================================================================
      +ASM /u01/app/grid/product/11.1.zero/grid   

three. BRING UP ASM INSTANCE AND MOUNT DISKGROUPS

Under are examples for 11gR2 Standalone (non-RAC). Word that CRS and ASM are collectively in 11gR2 vs. 10g or 11gR1 so clusterware processes need to be up first.

1. Set setting. For instance:

$ export ORACLE_HOME=/oracle/ora11g/11.2.zero/grid
$ export PATH=$ORACLE_HOME/bin:$PATH
$ export ORACLE_SID=+ASM

or

$ . oraenv
ORACLE_SID = +ASM

2. Verify if clusterware assets are up as root:

# cd [Grid Home]/bin
# ./crsctl standing useful resource -t

If has, ora.cssd useful resource is offline, manually begin it.

# ./crsctl begin has
# ./crsctl begin useful resource ora.cssd
# ./crsctl standing useful resource -t

three. Startup ASM and mount ORA_CRS disk group, the place ORA_CRS is the disk group identify. One of many choices to do it utilizing pfile and never spfile. If CRS is up, you could possibly startup utilizing spfile which is saved inside asm.

SQL> startup nomount ;
SQL> alter diskgroup ORA_CRS mount ;

As root startup crsd:

# crsctl begin useful resource ora.crsd -init

As soon as they're began, attempt to manually mount all diskgroups which might be presently seen on this server .

SQL> alter diskgroup [DG] mount ;

four. In case you get spile errors, then you'll want to create/recreate the SPFILE for ASM. The default is to start out asm with out pfile or spfile, so it's a quite common drawback. Use additional care regarding the asm_diskstring parameter because it impacts the invention of the voting disks. Confirm the earlier settings utilizing the ASM alert go online the supply the place you took BCV cut up.

Put together a pfile (e.g. /tmp/asm_pfile.ora) with the ASM startup parameters – these might differ from the instance under. If unsure seek the advice of the ASM alert log because the ASM occasion startup ought to listing all non-default parameter values. Please notice the final startup of ASM (in step 2 by way of CRS begin) won't have used an SPFILE, so a startup previous to the lack of the CRS disk group would have to be situated.

*.asm_power_limit=1
*.diagnostic_dest='/u01/app/oragrid'
*.instance_type='asm'
*.large_pool_size=12M
*.remote_login_passwordfile='EXCLUSIVE'

Now the SPFILE could be created utilizing this PFILE:

$ sqlplus / as sysasm
SQL> create spfile='+CRS' from pfile='/YOUR_LOCATION/asm_pfile.ora';
File created.
SQL> startup nomount ;
SQL> alter diskgroup ORA_CRS mount ;

As root startup crsd:

# crsctl begin useful resource ora.crsd -init

5. Verify state of disks:

SQL> set linesize 200
SQL> column path format a45
SQL> column identify format a20
SQL> column failgroup format a15
SQL> choose group_number, disk_number, mount_status, header_status, state, failgroup, identify, path from v$asm_disk;

If the disks present as Member, then it is best to have the ability to mount diskgroups.

6. As soon as all right disks present as MEMBER, you possibly can mount diskgroups which might be presently seen on this server .

SQL> alter diskgroup  mount ;
SQL> choose group_number, identify, state, sort, total_mb, free_mb from v$asm_diskgroup;

7. Verify that asm is up and that right values are acknowledged for asm_disksgroups and asm_diskstring.

SQL> choose * from v$occasion;
SQL> present parameter asm;

four. BRING UP RDBMS INSTANCE AND RECOVER THE DATABASE

1. ASM is up, diskgroups are mounted, now you're able to open the database. Begin listener from the Grid residence.

$ lsnrctl begin
$ lsnrctl standing

2. Set setting to level to your database house (which ought to already be put in or cloned):

$ export ORACLE_HOME=/oracle/ora11g/11.2.zero/db_home
$ export PATH=$ORACLE_HOME/bin:$PATH
$ export ORACLE_SID=YOUR_DB_SID

or

$ . oraenv
ORACLE_SID = YOUR_DB_NAME

three. Begin database.

$ sqlplus / as sysdba
SQL> startup

four. Verify that the earlier command truly opened the database:

SQL> choose identify, open_mode from v$database;

NAME      OPEN_MODE
--------- --------------------
YOUR_DB_NAME  READ WRITE

Comments