SUN ORACLEWORLD: RMAN full backup on Standby (RAC) and Restoration on new server as primary (Standalone)

RMAN full backup on Standby (RAC) and Restoration on new server as primary (Standalone)

Requirement – Take RMAN full consistent backup on standby RAC database and then restore this consistent RMAN full backup on to the test server and open the restored database in READ WRITE mode.

Scenario and consideration –

1) Migration from one server to another

2) RAC to single instance

3) ASM to file system

4) Standby to Primary

Task involved in this activity-

Stop recovery on standby database.
Take RMAN full backup on standby database.
Start recovery on standby database.
Transfer backup piece to the target server.
Restore rman backup and open database in READ WRITE mode.
Perform post restoration activities.

We have NOT made any changes to production and standby side. We have performed restoration on test server.

1 Stop recovery on standby database.

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

Crosscheck MRP process is not running on standby database and then proceed with next step.

2 RMAN full backup on standby RAC database.

Take rman full backup on standby database. Below are the script details which were used to take the RMAN full backup on standby database.

$ nohup sh rman_l0_bkp.sh &

$ cat rman_l0_bkp.sh

export ORACLE_SID=mystd1

export ORACLE_HOME=/oracle/app/oracle/product/11.2.0/dbhome_1;

/oracle/app/oracle/product/11.2.0/dbhome_1/bin/rman target / CMDFILE=/backup/rman_bkp/RMAN_BKP_TEST/rman_l0_bkp.rcv log=/backup/rman_bkp/RMAN_BKP_TEST/rman_l0_bkp.log

$cat rman_l0_bkp.rcv

run{

allocate channel c1 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

allocate channel c2 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

allocate channel c3 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

allocate channel c4 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

allocate channel c5 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

allocate channel c6 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

allocate channel c7 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

allocate channel c8 type disk format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U';

backup AS COMPRESSED BACKUPSET full database tag bkp_level_0 format '/backup/rman_bkp/RMAN_BKP_TEST/FULL_mystd_%U' database;

backup controlfile format '/backup/rman_bkp/RMAN_BKP_TEST/control_mystd_%U';

release channel c1;

release channel c2;

release channel c3;

release channel c4;

release channel c5;

release channel c6;

release channel c7;

release channel c8;

}

Start the recovery process on standby database after successful completion of RMAN full backup.

# Background redo apply. Control is returned to the session once the apply process is started.

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

3. Transfer this RMAN full backup to target server .

Use ftp or scp to transfer the backup to target server. Crosscheck the backup piece and it’s size on source and target server.

4. Restoration of RMAN backup on target server .

Create a PFILE for the single instance database using the production/standby RAC parameter file.

a. please modify the following parameters depending on the directory structure of the new host: audit_file_dest, background_dump_dest, control_files, core_dump_dest, log_archive_dest_1, user_dump_dest etc

b. remove RAC specific parameters such as cluster_database_instances, cluster_database etc

c. for the parameter undo_tablespace, mention any one undo tablespace name

Starting from 10g it is NOT mandatory to copy the RMAN backup pieces to exactly the same location on the new host as the production location.

Below is sample init.ora file used for this activity. Please make the modification according to your application requirements.

*._optim_peek_user_binds=FALSE

*.audit_file_dest='/oracle/app/oracle/admin/myprod/adump'

*.audit_sys_operations=FALSE

*.audit_trail='NONE'

*.cluster_database=false

*.compatible='11.2.0.0.0'

*.control_files='/database/data/myprod/controlfile/contol01.ctl','/database/data/myprod/controlfile/control02.ctl'

*.db_block_checking='TRUE'

*.db_block_checksum='TYPICAL'

*.db_block_size=8192

*.db_create_file_dest='/database/data/myprod/datafile'

*.db_domain=''

*.db_name='myprod'

*.diagnostic_dest='/oracle/app/oracle'

*.dispatchers='(PROTOCOL=TCP) (SERVICE=myprodXDB)'

*.dml_locks=800

*.job_queue_processes=10

*.log_archive_dest_1='location=/database/data/myprod/archive'

*.log_archive_format='%t_%s_%r.arc'

*.log_archive_max_processes=6

*.memory_target=0

*.nls_length_semantics='CHAR'

*.open_cursors=1000

*.optimizer_capture_sql_plan_baselines=FALSE

*.optimizer_features_enable='10.2.0.4'

*.optimizer_index_cost_adj=100

myprod.pga_aggregate_target=52428800

*.processes=350

*.query_rewrite_enabled='FALSE'

*.remote_login_passwordfile='EXCLUSIVE'

*.resource_limit=TRUE

*.sec_case_sensitive_logon=FALSE

*.session_cached_cursors=150

*.sessions=5280

*.sga_max_size=4g

#*.sga_max_target=4g

*.standby_file_management='AUTO'

*.undo_retention=7200

myprod.undo_tablespace='UNDOTBS1'

create spfile from initmyprod.ora

SQL> CREATE SPFILE FROM PFILE=’/path/initmyprod.ora’;

Use the spfile created above to STARTUP NOMOUNT the database on the new host

bash-2.05b$ sqlplus "/ as sysdba"

SQL*Plus: Release 11.2.0.4.0 Production on Tue Dec 27 09:53:45 2016

Connected to an idle instance.

SQL>

SQL> startup nomount;

ORACLE instance started.

Total System Global Area 4275781632 bytes

Fixed Size 2253216 bytes

Variable Size 4211084896 bytes

Database Buffers 50331648 bytes

Redo Buffers 12111872 bytes

SQL>

Now invoke RMAN and restore the controlfile specifying the location where the controlfile

piece is transferred on this new server. You can mount the database once the controlfile

is restored successfully.

RMAN> restore controlfile from '/database/RMAN/RMAN_BKP_TEST/control_mystd_msroess4_1_1’;

Starting restore at 27-DEC-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK

channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
output filename= /database/data/myprod/controlfile/contol01.ctl

output filename= /database/data/myprod/controlfile/control02.ctl

Finished restore at 27-DEC-16

RMAN>

RMAN> alter database mount;

database mounted
released channel: ORA_DISK_1

SQL> select name, open_mode,log_mode, database_role, controlfile_type from v$database;

NAME OPEN_MODE LOG_MODE DATABASE_ROLE CONTROL

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

MYPROD MOUNTED ARCHIVELOG PHYSICAL STANDBY STANDBY

You can skip this step if you have restored the RMAN backup pieces to exactly the

same location they were backed up on production. If this is not the case then you

need to catalog the RMAN backup pieces to make RMAN aware of thier new location

on the new host. Note that CATALOG BACKUPPIECE command is available only starting from

10g.

RMAN> catalog start with '/database/RMAN/RMAN_BKP_TEST';

searching for all files that match the pattern /database/RMAN/RMAN_BKP_TEST

List of Files Unknown to the Database

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

File Name: /database/RMAN/RMAN_BKP_TEST/FULL_mystd_mlroeq5e_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/FULL_mystd_mmroeq5e_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/FULL_mystd_mnroeq5f_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/FULL_mystd_moroeq5f_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/FULL_mystd_mproeq5f_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/FULL_mystd_mqroeq5g_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/FULL_mystd_mrroeq5g_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/control_mystd_msroess4_1_1

File Name: /database/RMAN/RMAN_BKP_TEST/nohup.out

File Name: /database/RMAN/RMAN_BKP_TEST/rman_l0_bkp.log

Do you really want to catalog the above files (enter YES or NO)? YES

cataloging files...

cataloging done

List of Cataloged Files

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