Guenadi N Jilevski's Oracle BLOG

Oracle RAC, DG, EBS, DR and HA DBA BLOG

RMAN configuration for backup & recovery with Oracle RAC ( 10gR2, 11gR1, 11gR2)

RMAN configuration for backup & recovery with Oracle RAC ( 10gR2, 11gR1, 11gR2)

Oracle RAC database like a single database needs a backup & recovery strategy to protect against media failure. Oracle RAC architecture has shared control files, data files, redo logs and spfile (recommended). Archive logs that are generated by each RAC instance thread are either in a local file system on each node or on a shared storage (ASM, CFS, NFS). The existence of archive logs generated by instances’ threads and their type of location (shared or non-shared among all instances) determines the specifics for Oracle RAC backup and recovery.

In a single instance database an instance can access all data files and the backup and archive log destination. While performing backup the backup location is accessible. While performing a restore or recovery the backup location and the archive location are also available.

There are two most common Oracle RAC configurations

  1. Shared Oracle ASM, CFS or NFS for data files and archive logs and backups in FRA. All components are shared by all instances. Each instance can perform backup and restore/recovery.
  2. Local archive NFS mounted to all other cluster nodes. The accessibility of the backup location from the RAC instance determines how backup and restore take place. That is what determines which instance can perform backup and restore.

For Oracle RAC and FRA setup make sure that both DB_RECOVERY_DEST and DB_RECOVERY_DEST_SIZE have same values across all cluster instances.

In Oracle RAC each instance can access the data files but might or might not access the backups and all archive log destinations. Having a shared location for archiving allows all instances to access the archive logs of the remaining cluster database instances. Having a shared location for the backup also makes backups accessible for all instances. The location and the type of the location (shared/non-shared) of the following below components determine how complicated is the RAC rman backup & restore setup.

  • Archive log destinations for each instance’s thread
  • Backup locations

For shared archive logs and a shared location of the backups there is no need to specify an explicit connect for each channel starting with Oracle 10gR2 onwards.

Starting with Oracle RAC 9i rman had to be configured by explicitly configuring a channel connecting to a specific instance. The purpose was to

  1. Balance between instances for parallelism for backup and recovery.
  2. Accessing locally configured archive log destinations. Only when connecting explicitly to an instance an archive log destination can be backed up and restored if it is on a NON-shared location. Also a local backup on the node can be done. Only the node doing the backup can restore.

CONFIGURE CHANNEL 1 DEVICE TYPE sbt CONNECT = ‘SYS/oracle@trgt1’;

CONFIGURE CHANNEL 2 DEVICE TYPE sbt CONNECT = ‘SYS/oracle@trgt2’;

An explicit connection to an instance allows a backup on a location accessible by the node where is the instance. For non-shared archive destinations this is the only option. In Oracle 9i an explicit connection also allows to run a backup in parallel in channels across each RAC instance.

Example for 3 node cluster (this set up is valid all the way toOracle 11.2)

CONFIGURE DEFAULT DEVICE TYPE TO sbt;

CONFIGURE DEVICE TYPE sbt PARALLELISM 3;

CONFIGURE CHANNEL 1 DEVICE TYPE sbt CONNECT = ‘SYS/oracle@trgt1’;

CONFIGURE CHANNEL 2 DEVICE TYPE sbt CONNECT = ‘SYS/oracle@trgt2’;

CONFIGURE CHANNEL 3 DEVICE TYPE sbt CONNECT = ‘SYS/oracle@trgt3’;

Starting from Oracle 10gR2 rman was enhanced to benefit from dynamic parallelism. That is, RMAN can be configured for automatic load balancing. This configuration is still valid in 11gR2. Note that there is no need to explicitly specify a channel with connect clause. The one time configuration as below is sufficient to perform a backup and recovery.

CONFIGURE DEVICE TYPE [disk | sbt] PARALLELISM number of channels;

Here specify the number of channels that can be used for the backup and restore. The configuration introduced in 9i is still applicable up to 11gR2 ( 10gR2, 11gR1, 11gR2).

To configure channels to use a specific channel as in Oracle 9i perform the one time configuration

CONFIGURE CHANNEL DEVICE TYPE sbt CONNECT ‘SYS/change_on_install@node1’

CONFIGURE CHANNEL DEVICE TYPE sbt CONNECT ‘SYS/change_on_install@node2’

After this one-time configuration step, you can issue the BACKUP or RESTORE commands. In addition, you can use the PARMS command in this example to set vendor-specific parameters.

Note: Explicit channel allocation to a specific instance requires that all instances to be either mounted all open, otherwise the rman produces an error.

Oracle RAC ( 10gR2, 11gR1, 11gR2) can perform the following operations in parallel :

  • Parallel instance recovery: Controlled by parameter RECOVERY_PARALLELISM. Set to 1 or 0 for serial operation.
  • Parallel archive log apply: alter database recover or RMAN recover has a clause of nonparallel. The level or parallelism is dependent on the number of CPUs.
  • Parallel backup and restore: controlled by the number of channels.
  • Parallelism while merging incremental backups determine by the number of channels.

For Oracle RAC also make sure the LOG_ARCHIVE_FORMAT includes

  • Thread: %t or %T
  • Sequence: %s or %S
  • Reset log identifier: %r or %R

RMAN can be used either from command line or through OEM. RMAN can access raw devices, ASM, CFS, NFS, local file system, block devices. For 11Gr2 ( raw and block devices are deprecated). For 11gR1 raw is deprecated.

Configuring RMAN Snapshot control file location

Staring from Oracle 10gR2 and into 11gR2 a snapshot control file location needs to be specified.

The location is stored as a persistent configuration and therefore needs to be the same on all nodes that are to perform backup. That is, all nodes need to have the same location ( full path name and file name).

The snapshot control file is created only during backup in the following cases.

  • To re-synchronize the recovery catalog from a read-consistent control file during backup.
  • If a backup of the control file is done.

The snapshot file does not need to be globally available.

To determine the snapshot file location issue.

SHOW SNAPSHOT CONTROLFILE NAME;

To change the snapshot file location issue.

CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘$ORACLE_HOME/dbs/scf/snap_prod.cf’;

To delete a snapshot file location change the location and delete the old one.

CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘new_name’;

DELETE COPY OF CONTROLFILE;

The location can be a raw device, block device, ASM , CFS , local file system or supported NFS.

Configure control file and SPFILE autobackup.

For Oracle RAC 10gR2, 11gR1 and 11gR2 configure control file and SPFILE autobackup and specify the autobackup location. The location should be available from all cluster nodes.

At RMAN prompt issue ‘CONFIGURE CONTROLFILE AUTOBACKUP ON;’ to automatically backup the controlfile and SPFILE whenever issue any backup or copy commend.

Issue at RMAN prompt CONFIGURE CONTROLFILE AUTOBACKUP FORMAT DOR DEVICE TYPE DISK TO ‘+DATA’; to specify autobackup location.

Crosschecking on Multiple Oracle RAC Nodes

When crosschecking on multiple nodes make sure that all backups are shared and can be accessed by every node in the cluster. This way every node can perform a backup and every node can be used for crosscheck and restore. Otherwise you must provide channels on multiple modes using explicit connect in the channel specification in CONFIGURE CHANNEL RMAN command. If a backup is not accessible due to channel not configured for the node to access the backup after crosscheck the backups are marked as EXPIRED in the RMAN repository.

There a several RMAN backup configurations for a Oracle RAC database with FRA

  • Network backup server accessible from all nodes of a RAC cluster with FRA.
  • Local backup appliance connected to a server of a RAC cluster with FRA.
  • Local backup appliances connected to each server of a RAC cluster with FRA.
  • Local backup appliances connected to each server of a RAC cluster without FRA and with local archiving.

Network backup server accessible from all nodes of a RAC cluster with FRA

In this configuration each node can initiate a backup and the backup is shared. The archive log destination is also shared. The channel configuration can be as show below , where N is the desired level of parallelism. Every node can be used for restore and recovery.

RMAN>CONFIGURE DEVICE TYPE SBT PARALLELISM N;

RMAN>CONFIGURE DEFAULT DEVICE TYPE SBT;

RMAN>backup database;

Local backup appliance connected to a server of a RAC cluster with FRA

In this configuration a backup appliance is attached to one node. All archive redo log file and FRA data is shared among all nodes. The node with the backup appliance can perform the backup and restore/recovery.

RMAN>CONFIGURE DEVICE TYPE SBT PARALLELISM 1;

RMAN>CONFIGURE DEFAULT DEVICE TYPE SBT;

RMAN>backup database;

Backup appliances connected to each server of a RAC cluster with FRA

In this configuration there is a backup appliance attached to each node. Each node of the cluster can access all backups and archive logs in the FRA. Using the specified below set up each node can perform backup and restore. For simplicity it is assumed that it is a two node cluster.

RMAN>CONFIGURE DEVICE TYPE SBT PARALLELISM 2;

RMAN>CONFIGURE DEFAULT DEVICE TYPE SBT;

RMAN>CONFIGURE CHANNEL 1 DEVICE TYPE SBT CONNECT ‘SyS/PASWD@n1’;

RMAN>CONFIGURE CHANNEL 2 DEVICE TYPE SBT CONNECT ‘SyS/PASWD@n2’;

RMAN>backup database

Local backup appliances connected to each server of a RAC cluster without FRA and with local archiving

In this configuration there is one backup appliance connected to each node of the cluster. Each node performs a backup to the local backup devices and backups archived logs that are generated on the instance running on the node. Backup and restore can be initiated from each node of the cluster but each node backup and restores only the local archive logs.

RMAN>CONFIGURE DEVICE TYPE SBT PARALLELISM 2;

RMAN>CONFIGURE DEFAULT DEVICE TYPE SBT;

RMAN>CONFIGURE CHANNEL 1 DEVICE TYPE SBT CONNECT ‘SyS/PASWD@n1’;

RMAN>CONFIGURE CHANNEL 2 DEVICE TYPE SBT CONNECT ‘SyS/PASWD@n2’;

RMAN>backup database;

Instance affinity

In Oracle RAC an instance of a RAC database can access some files faster than others. This is referred to as an instance affinity. RMAN recognizes it and backup files using the channels that are allocated to the instance that the files have affinity to.

July 8, 2011 - Posted by | oracle

15 Comments »

  1. It’s clear but still needs to fix: “RNAN” should be “RMAN”

    Regards

    Gokhan

    Comment by Gokhan Atil | July 8, 2011 | Reply

    • Correct. I agree.

      Comment by gjilevski | July 8, 2011 | Reply

  2. In a multi node RAC, do you need to backup the archive logs from EACH and EVERY node? Would backing up archivelogs from just ONE node sufficient?

    Tony

    Comment by Tony Fernandes | August 4, 2011 | Reply

    • Hi Tony,

      If the archive logs are shared as in case of FRA than you can backup them all fom one only node. You can use every one node for restore.

      If the the archive locations on the nodes are not shared you can backup them all from any one node using the extended channel allocation with explicit connect. The isue is how to make them available for restore and recovery (NFS comes useful).

      You can use one node for the backup. The channel configuration will address cases where archive logs are not shared or shared.

      Make sure you have all backups and archive logs available for restore and recovery.

      Answer is :

      In a multi node RAC, do you need to backup the archive logs from EACH and EVERY node? No,

      Would backing up archivelogs from just ONE node sufficient?Yes,depends on the configuration of the channel. Make sure archivelogs are available for restore & recovery.

      Regards

      Comment by gjilevski | August 4, 2011 | Reply

  3. Hi ,
    Can you please explain the following scenario ?

    I have two RAC nodes and I am running a back on both the RAC nodes using connect ‘@node[1-2]. If one node goes down what will happen to the backup pieces it was writing. Is there any failover mechanism for this problem and Can the surviving node rman process can take over this job?

    Can you please advice ?

    Many Thanks
    Viddya

    Comment by Viddyasagar CS | August 5, 2011 | Reply

    • Hello Viddya,

      The backup failed and rman does not record it. Thus, you will need to re-run it. RMAN never records a backup that is incomplete in the repository be it a controlfile or rman catalog. There is no failover.

      CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
      CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT ‘SYS/sys1@RAC10G1’;
      CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT ‘SYS/sys1@RAC10G2’;

      RAC10G1 =
      (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = raclinux1-vip)(PORT = 1521))
      (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = RAC10G)
      (INSTANCE_NAME = RAC10G1)
      )
      )

      RAC10G =
      (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = raclinux1-vip)(PORT = 1521))
      (ADDRESS = (PROTOCOL = TCP)(HOST = raclinux2-vip)(PORT = 1521))
      (LOAD_BALANCE = yes)
      (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = RAC10G)
      )
      )

      RMAN> show all;

      using target database control file instead of recovery catalog
      RMAN configuration parameters are:
      CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
      CONFIGURE BACKUP OPTIMIZATION OFF; # default
      CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
      CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
      CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO ‘%F’; # default
      CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
      CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
      CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
      CONFIGURE MAXSETSIZE TO UNLIMITED; # default
      CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
      CONFIGURE ENCRYPTION ALGORITHM ‘AES128’; # default
      CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
      CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘/u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_RAC10G1.f’; # default

      RMAN>

      RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
      CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT ‘SYS/sys1@RAC10G1’;
      CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT ‘SYS/sys1@RAC10G2’;

      new RMAN configuration parameters:
      CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
      new RMAN configuration parameters are successfully stored

      RMAN>
      new RMAN configuration parameters:
      CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT ‘*’;
      new RMAN configuration parameters are successfully stored

      RMAN>
      new RMAN configuration parameters:
      CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT ‘*’;
      new RMAN configuration parameters are successfully stored

      RMAN> show all;

      RMAN configuration parameters are:
      CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
      CONFIGURE BACKUP OPTIMIZATION OFF; # default
      CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
      CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
      CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO ‘%F’; # default
      CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
      CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
      CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
      CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT ‘*’;
      CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT ‘*’;
      CONFIGURE MAXSETSIZE TO UNLIMITED; # default
      CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
      CONFIGURE ENCRYPTION ALGORITHM ‘AES128’; # default
      CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
      CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘/u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_RAC10G1.f’; # default

      RMAN>

      RMAN> backup database plus archivelog;

      Starting backup at 05-AUG-11
      current log archived
      allocated channel: ORA_DISK_1
      channel ORA_DISK_1: sid=144 instance=RAC10G1 devtype=DISK
      allocated channel: ORA_DISK_2
      channel ORA_DISK_2: sid=136 instance=RAC10G2 devtype=DISK
      channel ORA_DISK_1: starting archive log backupset
      channel ORA_DISK_1: specifying archive log(s) in backup set
      input archive log thread=1 sequence=2 recid=2 stamp=757481615
      channel ORA_DISK_1: starting piece 1 at 05-AUG-11
      channel ORA_DISK_2: starting archive log backupset
      channel ORA_DISK_2: specifying archive log(s) in backup set
      input archive log thread=1 sequence=3 recid=3 stamp=757481775
      input archive log thread=1 sequence=4 recid=5 stamp=757551146
      input archive log thread=1 sequence=5 recid=6 stamp=757555849
      input archive log thread=1 sequence=6 recid=8 stamp=757560453
      input archive log thread=1 sequence=7 recid=10 stamp=757648268
      input archive log thread=1 sequence=8 recid=12 stamp=757716393
      input archive log thread=1 sequence=9 recid=13 stamp=757723408
      input archive log thread=1 sequence=10 recid=16 stamp=758406561
      input archive log thread=1 sequence=11 recid=17 stamp=758406850
      channel ORA_DISK_2: starting piece 1 at 05-AUG-11
      channel ORA_DISK_1: finished piece 1 at 05-AUG-11
      piece handle=+DATADG/rac10g/backupset/2011_08_05/annnf0_tag20110805t203422_0.296.758406865 tag=TAG20110805T203422 comment=NONE
      channel ORA_DISK_1: backup set complete, elapsed time: 00:00:16
      channel ORA_DISK_2: finished piece 1 at 05-AUG-11
      piece handle=+DATADG/rac10g/backupset/2011_08_05/annnf0_tag20110805t203422_0.297.758406865 tag=TAG20110805T203422 comment=NONE
      channel ORA_DISK_2: backup set complete, elapsed time: 00:00:16
      channel ORA_DISK_1: starting archive log backupset
      channel ORA_DISK_1: specifying archive log(s) in backup set
      input archive log thread=2 sequence=1 recid=1 stamp=757481544
      input archive log thread=2 sequence=2 recid=4 stamp=757481722
      input archive log thread=2 sequence=3 recid=7 stamp=757558822
      input archive log thread=2 sequence=4 recid=9 stamp=757561798
      input archive log thread=2 sequence=5 recid=11 stamp=757648507
      input archive log thread=2 sequence=6 recid=14 stamp=757723409
      input archive log thread=2 sequence=7 recid=15 stamp=758406558
      input archive log thread=2 sequence=8 recid=18 stamp=758406852
      channel ORA_DISK_1: starting piece 1 at 05-AUG-11
      channel ORA_DISK_1: finished piece 1 at 05-AUG-11
      piece handle=+DATADG/rac10g/backupset/2011_08_05/annnf0_tag20110805t203422_0.298.758406881 tag=TAG20110805T203422 comment=NONE
      channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
      Finished backup at 05-AUG-11

      Starting backup at 05-AUG-11
      using channel ORA_DISK_1
      using channel ORA_DISK_2
      channel ORA_DISK_1: starting full datafile backupset
      channel ORA_DISK_1: specifying datafile(s) in backupset
      input datafile fno=00001 name=+DATADG/rac10g/datafile/system.256.757479967
      input datafile fno=00006 name=+DATADG/rac10g/datafile/undotbs2.268.757480275
      input datafile fno=00004 name=+DATADG/rac10g/datafile/users.259.757479969
      channel ORA_DISK_1: starting piece 1 at 05-AUG-11
      channel ORA_DISK_2: starting full datafile backupset
      channel ORA_DISK_2: specifying datafile(s) in backupset
      input datafile fno=00003 name=+DATADG/rac10g/datafile/sysaux.257.757479969
      input datafile fno=00005 name=+DATADG/rac10g/datafile/example.267.757480099
      input datafile fno=00002 name=+DATADG/rac10g/datafile/undotbs1.258.757479969
      channel ORA_DISK_2: starting piece 1 at 05-AUG-11
      RMAN-00571: ===========================================================
      RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
      RMAN-00571: ===========================================================
      RMAN-00601: fatal error in recovery manager
      RMAN-03004: fatal error during execution of command
      ORA-12521: TNS:listener does not currently know of instance requested in connect descriptor
      [oracle@raclinux1 admin]$

      After

      [oracle@raclinux2 ~]$ ps -ef | grep pmon
      grid 5294 1 0 20:27 ? 00:00:00 asm_pmon_+ASM2
      oracle 5897 1 0 20:30 ? 00:00:00 ora_pmon_RAC10G2
      oracle 6066 1 0 20:30 ? 00:00:00 ora_pmon_RACDB2
      oracle 6472 5205 0 20:34 pts/2 00:00:00 grep pmon
      [oracle@raclinux2 ~]$ kill -9 5897
      [oracle@raclinux2 ~]$ ps -ef | grep pmon
      grid 5294 1 0 20:27 ? 00:00:00 asm_pmon_+ASM2
      oracle 6066 1 0 20:30 ? 00:00:00 ora_pmon_RACDB2
      oracle 6507 5205 0 20:34 pts/2 00:00:00 grep pmon
      [oracle@raclinux2 ~]$

      Comment by gjilevski | August 5, 2011 | Reply

    • Hello Viddya,

      As I said the backup will fail and there will be no failover.

      CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
      CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT ‘SYS/sys1@RAC10G’;
      CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT ‘SYS/sys1@RAC10G’;

      RAC10G =
      (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = raclinux1-vip)(PORT = 1521))
      (ADDRESS = (PROTOCOL = TCP)(HOST = raclinux2-vip)(PORT = 1521))
      (LOAD_BALANCE = yes)
      (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = RAC10G)
      )
      )

      RMAN> backup database plus archivelog;

      Starting backup at 05-AUG-11
      current log archived
      using target database control file instead of recovery catalog
      allocated channel: ORA_DISK_1
      channel ORA_DISK_1: sid=148 instance=RAC10G2 devtype=DISK
      allocated channel: ORA_DISK_2
      channel ORA_DISK_2: sid=136 instance=RAC10G1 devtype=DISK
      channel ORA_DISK_1: starting archive log backupset
      channel ORA_DISK_1: specifying archive log(s) in backup set
      input archive log thread=1 sequence=2 recid=2 stamp=757481615
      channel ORA_DISK_1: starting piece 1 at 05-AUG-11
      channel ORA_DISK_2: starting archive log backupset
      channel ORA_DISK_2: specifying archive log(s) in backup set
      input archive log thread=1 sequence=3 recid=3 stamp=757481775
      input archive log thread=1 sequence=4 recid=5 stamp=757551146
      input archive log thread=1 sequence=5 recid=6 stamp=757555849
      input archive log thread=1 sequence=6 recid=8 stamp=757560453
      input archive log thread=1 sequence=7 recid=10 stamp=757648268
      input archive log thread=1 sequence=8 recid=12 stamp=757716393
      input archive log thread=1 sequence=9 recid=13 stamp=757723408
      input archive log thread=1 sequence=10 recid=16 stamp=758406561
      input archive log thread=1 sequence=11 recid=17 stamp=758406850
      input archive log thread=1 sequence=12 recid=21 stamp=758407495
      input archive log thread=2 sequence=1 recid=1 stamp=757481544
      channel ORA_DISK_2: starting piece 1 at 05-AUG-11
      channel ORA_DISK_1: finished piece 1 at 05-AUG-11
      piece handle=+DATADG/rac10g/backupset/2011_08_05/annnf0_tag20110805t204504_0.303.758407507 tag=TAG20110805T204504 comment=NONE
      channel ORA_DISK_1: backup set complete, elapsed time: 00:00:09
      channel ORA_DISK_1: starting archive log backupset
      channel ORA_DISK_1: specifying archive log(s) in backup set
      input archive log thread=2 sequence=2 recid=4 stamp=757481722
      input archive log thread=2 sequence=3 recid=7 stamp=757558822
      input archive log thread=2 sequence=4 recid=9 stamp=757561798
      input archive log thread=2 sequence=5 recid=11 stamp=757648507
      input archive log thread=2 sequence=6 recid=14 stamp=757723409
      input archive log thread=2 sequence=7 recid=15 stamp=758406558
      input archive log thread=2 sequence=8 recid=18 stamp=758406852
      input archive log thread=2 sequence=9 recid=19 stamp=758406947
      input archive log thread=2 sequence=10 recid=20 stamp=758407494
      channel ORA_DISK_1: starting piece 1 at 05-AUG-11
      channel ORA_DISK_1: finished piece 1 at 05-AUG-11
      piece handle=+DATADG/rac10g/backupset/2011_08_05/annnf0_tag20110805t204504_0.305.758407517 tag=TAG20110805T204504 comment=NONE
      channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
      channel ORA_DISK_2: finished piece 1 at 05-AUG-11
      piece handle=+DATADG/rac10g/backupset/2011_08_05/annnf0_tag20110805t204504_0.304.758407507 tag=TAG20110805T204504 comment=NONE
      channel ORA_DISK_2: backup set complete, elapsed time: 00:00:12
      Finished backup at 05-AUG-11

      Starting backup at 05-AUG-11
      using channel ORA_DISK_2
      using channel ORA_DISK_1
      RMAN-00571: ===========================================================
      RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
      RMAN-00571: ===========================================================
      RMAN-03002: failure of backup plus archivelog command at 08/05/2011 20:45:22
      RMAN-10038: database session for channel ORA_DISK_1 terminated unexpectedly

      RMAN>

      After

      [oracle@raclinux2 ~]$ ps -ef | grep pmon
      grid 5294 1 0 20:27 ? 00:00:00 asm_pmon_+ASM2
      oracle 6066 1 0 20:30 ? 00:00:00 ora_pmon_RACDB2
      oracle 6617 1 0 20:35 ? 00:00:00 ora_pmon_RAC10G2
      oracle 7230 5205 0 20:44 pts/2 00:00:00 grep pmon
      [oracle@raclinux2 ~]$ kill -9 6617
      [oracle@raclinux2 ~]$

      Comment by gjilevski | August 5, 2011 | Reply

  4. Hi.

    I am planning a 4-node 11Gr2 RAC cluster and on each node i have two NICs for the public network and another two NICs for the private interconnect network. In assigning IPs for the private interconnect, i have read that IPMP or other related technologies are no longer required in 11GR2. Can i just assign 2 IPs, one for each NIC, for the private network interfaces?

    Thanks.
    Stephen.

    Comment by Stephen Agbodza | August 26, 2011 | Reply

    • Hello Stephen,

      Assuming you are on Oracle 11.2.0.2 you can go ahead.

      Look at

      11gR2 Grid Infrastructure Redundant Interconnect and ora.cluster_interconnect.haip [ID 1210883.1]

      Solaris IPMP and Trunking for the cluster interconnect in Oracle Grid Infrastructure 11g Rel. 2 [ID 1069584.1]

      11.2.0.2 and above
      Started from 11.2.0.2, as Redundant Interconnect is supported natively by Oracle Clusterware, it’s not recommended to configure IPMP for cluster interconnect anymore; please refer to note 1210883.1 for more details.

      Regards,

      Guenadi Jilevski

      Comment by gjilevski | August 26, 2011 | Reply

      • Hi Guenadi,

        Thanks for your reply. I will definitely take a look at the references you provided.
        Will let you know how it goes.
        Thanks again.

        Stephen.

        Comment by Stephen | September 3, 2011

  5. how about Standerd oracle where you can’t have multiple channel?

    Comment by ishams | September 19, 2011 | Reply

    • Hi,

      Officially , If you look at

      ‘Oracle Clusterware and Oracle Real Application Clusters
      Administration and Deployment Guide
      10g Release 2 (10.2)
      B14197-15’

      ‘If you are using the Oracle Database 10g Standard Edition,
      then you must use ASM for storing all of the database files.’

      This is supposed to mean that a FRA DG and a data DG. No need for parallelism if using FRA in SE.

      Regards,

      Comment by gjilevski | September 19, 2011 | Reply

    • Hi,

      In SE you will not have parallelism for backup and recovery with rman.

      Regards,

      Comment by gjilevski | September 21, 2011 | Reply

  6. Website Trackback Link…

    […]the time to read or visit the content or sites we have linked to below the[…]…

    Trackback by Buy Facebook Fans | December 27, 2011 | Reply

  7. Howdy! I could have sworn I’ve visited your blog before but
    after going through some of the articles I realized it’s new to me.
    Anyways, I’m definitely delighted I stumbled upon it and I’ll be bookmarking it and checking back often!

    Comment by refrigerator repair Slidell | July 19, 2014 | Reply


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: