Oracle Rman Advanced Recovery Overview (iv) tablespace point-in-time recovery

Ii. Manual implementation of TSPITR

Oracle supports creating its own helper instances for Tspitr. You can also use the manual tspitr to complete the failed automatic Tspitr operation. First, the steps listed in the previous preparation phase are still applied, then you must prepare the secondary instance and then perform the TSPITR process.

3.2.1 Prepare Auxiliary Instance

First, you need to start and run the secondary instance. A secondary instance is just a temporary instance of the Rman used to perform tspitr. The secondary instance must reside in the same machine as the target database and cannot perform any type of DML on the secondary instance.

Before starting Tspitr, you need to prepare a secondary instance. The same as a normal database instance.

Windows Oracle 10G CREATE database manually

Http://blog.csdn.net/tianlesoftware/archive/2009/10/17/4680230.aspx

Create a new database manually under Linux

Http://blog.csdn.net/tianlesoftware/archive/2009/10/17/4680213.aspx

Let's assume that the secondary instance name created is test. Action steps are as follows:

(1) Create password file

C:>orapwd File=d:/app/administrator/product/11.2.0/dbhome_1/database/pwdtest.ora Password=admin

(2) Create service

C:/>oradim-new-sid TEST

Oradim is the name of the tool that created the instance,-new indicates the execution of the new instance,-delete indicates that the instance was deleted,-sid the name of the specified case.

(3) Create a parameter file

The parameter file for the secondary database differs from the parameter file used by the target database. Some of the parameters that should be added to the secondary instance are the following table:

Name of parameter

Optional or required

Description

Db_name

Optional

The same name as the target database

Lock_name_space

Must select

differs from the unique name of the other database name on the system where the secondary instance is created.

Db_file_name_convert

Optional

When you restore a data file in a secondary database with Rman, this parameter is used to define a set of file naming transformation patterns for these data files. It can replace the Rman configure Auxname command.

Log_file_name_convert

Optional

When you restore redo logs in a secondary database with Rman, this parameter defines a set of command conversion modes for these redo logs. It can replace the Rman set newnameml.

Control_files

Necessary

This parameter defines the name and location of the secondary instance control file. The name of the secondary instance control file should be different from the other control file names already in place in the lock.

Remote_login_passwordfile

Optional/Necessary

Used to allow Rman to connect to the secondary database through the Oracle networking service. A current password file is required. If you want to connect to the secondary database locally, you do not need to set this parameter.

Compatible

Necessary

Must be the same as the target database settings

Db_block_size

Optional/Necessary

If this parameter is set on the target database, it must also be set to the same parameter value in the secondary database.

We put all the auxiliary instances into the F:/test directory, and the secondary instance parameters are as follows:

Db_name=bl

Db_unique_name=test

db_block_size=8192

db_cache_size=8388608

Timed_statistics=true

shared_pool_size=110m

large_pool_size=1m

compatible=11.2.0.0.0

Background_dump_dest=f:/test

Core_dump_dest=f:/test

User_dump_dest=f:/test

Control_files=f:/test/control01.ctl

Db_create_file_dest=f:/test

log_file_name_convert= (' D:/app/administrator/oradata/bl ', ' f:/test ');

Save the parameter as Inittest.ora, and store it under f:/test/.

(4) Start auxiliary instance and check network connectivity

C:/users/administrator.daviddai>set Oracle_sid=test

C:/users/administrator.daviddai>sqlplus/nolog

Sql*plus:release 11.2.0.1.0 Production on Thursday July 8 15:52:17 2010

Copyright (c) 1982, Oracle. All rights reserved.

Sql> Conn/as SYSDBA

You are connected to an idle routine.

sql> startup Nomount pfile= ' F:/test/inittest.ora ';

Ora-32006:background_dump_dest initialization parameter has been deprecated

Ora-32006:user_dump_dest initialization parameter has been deprecated

The ORACLE routine has started.

Total System Global area 163221504 bytes

Fixed Size 1373236 bytes

Variable Size 146803660 bytes