Redolog resizing at dataguard environment

 Steps 01: Stop/Shutdown standby database
===========================================

SQL> Alter database recover managed standby database cancel;
SQL> Shutdown immediate;

 Steps 02: delete redolog file and standby file using rm command in standby side
====================================================================================


Steps: 3. Drop online redologfiles in primary database
========================================================
SQL> alter system switch logfile;
SQL> alter system checkpoint;
SQL> alter database drop logfile group 1;

SQL> ALTER DATABASE ADD LOGFILE GROUP 1 ('/oradata1/redo1/redo01a.log',
'/oradata1/redo2/redo01b.log') SIZE 300M;

SQL> alter database drop logfile group 2;


SQL> ALTER DATABASE ADD LOGFILE GROUP 2 ('/oradata1/redo1/redo02a.log',
'/oradata1/redo2/redo02b.log') SIZE 300M;

SQL> alter database drop logfile group 3;


SQL> ALTER DATABASE ADD LOGFILE GROUP 3 ('/oradata1/redo1/redo03a.log',
'/oradata1/redo2/redo03b.log') SIZE 300M;

SQL> alter database drop logfile group 4;

SQL> ALTER DATABASE ADD LOGFILE GROUP 4 ('/oradata1/redo1/redo04a.log',
'/oradata1/redo2/redo04b.log') SIZE 300M;

==========================================================================================

Steps 04:  Drop standby logs in primary database and add standby logs in primary

SQL> ALTER DATABASE DROP STANDBY LOGFILE GROUP 5;

SQL> ALTER DATABASE DROP STANDBY LOGFILE GROUP 6;

SQL> ALTER DATABASE DROP STANDBY LOGFILE GROUP 7;

SQL> ALTER DATABASE DROP STANDBY LOGFILE GROUP 8;

SQL> ALTER DATABASE DROP STANDBY LOGFILE GROUP 9;


===========================================================================================

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 5 ('/oradata1/redo1/standbyredo05a.log',
'/oradata1/redo2/standbyredo05b.log') SIZE 300M;

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 6 ('/oradata1/redo1/standbyredo06a.log',
'/oradata1/redo2/standbyredo06b.log') SIZE 300M;

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 7 ('/oradata1/redo1/standbyredo07a.log',
'/oradata1/redo2/standbyredo07b.log') SIZE 300M;

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 8 ('/oradata1/redo1/standbyredo08a.log',
'/oradata1/redo2/standbyredo08b.log') SIZE 300M;

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 9 ('/oradata1/redo1/standbyredo09a.log',
'/oradata1/redo2/standbyredo09b.log') SIZE 300M;

Steps 05:  create standby controlfile- and move it on standby db side
===========================================================================================

SQL> alter database create standby controlfile as '/oradata1/standby01.ctl';

Move Control file to standby remote destination
============================
Steps 06: Startup standby database--
============================

SQL> startup nomount

SQL> alter database mount standby database;

SQL> alter database recover managed standby database disconnect from session

Steps 07:  Open read-only mode and real-time redo apply
========================================================
SQL> startup
SQL> alter database recover managed standby database disconnect using current logfile;

RMAN backup at NFS mount point

RMAN backup at NFS mount point

To take rman backup at NFS mount point on Linux Platform from Oracle Database 11.2 add few rule:

Listing of required NFS options for 11.2.0.2 RMAN disk backup directory

The following NFS options must be specified for 11.2.0.2 RMAN disk backup directory:
Mount Options for Linux systems

Single Instance NFS Mount Options
---------------------------------
Mount options for Oracle Binaries

rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,tcp

Mount options for Oracle Datafiles

rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,tcp


RAC NFS Mount options
---------------------

Mount options for Oracle Binaries

rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp, vers=3,timeo=600, actimeo=0


Mount options for Oracle Datafiles

rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,noac,forcedirectio, vers=3,suid

The above values are starting recommendations as a starting point you can tune further
as required. To test which value of rsize/wsize is optimal for your system you can run
the testing outlined below.

First, we'll try transfers of 16384 blocks of 16k each from a unique file called /dev/zero
(when you read it, it's all zeroes, put out very quickly) to the test file. The time it takes to do this is our measure. From the client, command:

time dd if=/dev/zero of=/<mounted partition>/testfile bs=16k count=16384



MOS Note : ID 1117597.1