RE: RMAN restore on another server

From: DENNIS WILLIAMS <DWILLIAMS_at_LIFETOUCH.COM>
Date: Fri, 05 Dec 2003 14:29:26 -0800
Message-ID: <F001.005D8F4B.20031205142926@fatcity.com>

Brian - First, congratulations on performing what seems pretty close to a disaster recovery test. I don't know the specific answer to your problem, so I'll ask a couple of questions related to hard points I encountered, and maybe that will strike a cord.

You say you connected to your existing RMAN catalog? How does the catalog know to recover this new database and not the one it backed up? Maybe it is confused. I found it much simpler to recover from the controlfile even if I used the catalog to perform the backup. Also in a true disaster, you may not have your RMAN catalog unless you have another tape. If you can recover from the single tape with the RMAN backup, then your offsite tape could get you up and running.
Are the backup pieces in the same path as you backed them up? I don't think that is your problem because that usually gives a clear error.
Are you using NFS? I encountered a problem with NFS very similar to your symptoms. My sys admin assumed there would be only a connection or two over NFS, so left some stuff default. Come to find out RMAN opens a bunch of connections.

Sorry, but that is all my brain can think up on Friday.

Dennis Williams
DBA
Lifetouch, Inc.
dwilliams_at_lifetouch.com

-----Original Message-----
Sent: Friday, December 05, 2003 4:14 PM
To: Multiple recipients of list ORACLE-L

Goal: To restore the database from RMAN backup on a different server by means of moving the backup pieces and logs over to the new machine and use Rman to unpack the database files.
Strategy: To restore the database from the RMAN backup pieces into a new directory locations on the machine and extract the control file and startup the database.

Some of the steps to setup the new machine.

1) Install oracle 8i
2) install the patch 4.0
3) copy .profile over
4) duplicated the Admin directories for the database to be restored
5) created a big mount  /u02/vssppln/ point for all the datafiles and

controlfiles and so on
6) Created a backup mount point to store the RMAN backup pieces and archivelogs

7) moved the backup pieces and archivelogs to the new machine
8) Setup and confirm connectivity to Rman catalog
9) No mount the database to be on the new machine

10) Launch the Rman command
rman cmdfile=restore_dbsid.rman trace=restore_dbsid.log

Problem... I run this restore from Rman backup...but it gets to processing the command and gets to the "RMAN-03022: compiling command: set " and just hangs...adding another line every 1/2 hour or so...

Anybody seen this or have ideas? I talked to one guy who did have this but couldn't remember the solution. This is the first time doing this so I might be missing something simple..

Here is the command in operation

==> rman cmdfile=restore_dbsid.rman trace=restore_dbsid.nohup_log

Recovery Manager: Release 8.1.7.4.0 - Production

RMAN>
RMAN> connect catalog rman81740/depart_at_ltsprcat <mailto:rman81740/depart_at_ltsprcat>

2> 
3> connect target /
4> 
5> 
6> 
7> run
8> 
9> {
10> 
11> allocate channel disk_channel1 type disk ;
12> 
13> sql 'alter session set NLS_DATE_FORMAT="YYYY-MM-DD HH24:MI:SS"';
14> set until time = '2003-12-02 05:50:00';
15> 
16>  set newname for datafile 1 to
17> '/u02/vssppln/system01.dbf';
18> 
19>  set newname for datafile 2 to
20> '/u02/vssppln/rbs01.dbf';
21> 
22>  set newname for datafile 3 to
23> '/u02/vssppln/rbs02.dbf';
24> 
25>  set newname for datafile 4 to
26> '/u02/vssppln/AIMFACT01.dbf';
27> 
28>  set newname for datafile 5 to
29> '/u02/vssppln/AIMFACT_INDEX01.dbf';
30> 
31>  set newname for datafile 6 to
32> '/u02/vssppln/AIMFACT101.dbf';
33> 
34>  set newname for datafile 7 to
35> '/u02/vssppln/AIMFACT102.dbf';
36> 
37>  set newname for datafile 8 to
38> '/u02/vssppln/aimfact1_index01.dbf';
39> 
40>  set newname for datafile 9 to
41> '/u02/vssppln/aimfact1_index02.dbf';
42> 
43>  set newname for datafile 10 to
44> '/u02/vssppln/aimfact1_index03.dbf';
45> 
46>  set newname for datafile 11 to
47> '/u02/vssppln/aimfact1_index04.dbf';
48> 
49>  set newname for datafile 12 to
50> '/u02/vssppln/aimfact201.dbf';
51> 
52>  set newname for datafile 13 to
53> '/u02/vssppln/aimfact202.dbf';
54> 
55>  set newname for datafile 14 to
56> '/u02/vssppln/aimfact2_index01.dbf';
57> 
58>  set newname for datafile 15 to
59> '/u02/vssppln/aimfact2_index02.dbf';
60> 
61>  set newname for datafile 16 to
62> '/u02/vssppln/aimfact2_index03.dbf';
63> 
64>  set newname for datafile 17 to
65> '/u02/vssppln/aimfact2_index04.dbf';
66> 
67>  set newname for datafile 18 to
68> '/u02/vssppln/aimstruct01.dbf';
69> 
70>  set newname for datafile 19 to
71> '/u02/vssppln/aimstruct_index01.dbf';
72> 
73>  set newname for datafile 20 to
74> '/u02/vssppln/aimstruct101.dbf';
75> 
76>  set newname for datafile 21 to
77> '/u02/vssppln/aimstruct1_index01.dbf';
78> 
79>  set newname for datafile 22 to
80> '/u02/vssppln/aimwork01.dbf';
81> 
82>  set newname for datafile 23 to
83> '/u02/vssppln/mipsdata01.dbf';
84> 
85>  set newname for datafile 24 to
86> '/u02/vssppln/mipsindex01.dbf';
87> 
88>  set newname for datafile 25 to
89> '/u02/vssppln/mipsdata101.dbf';
90> 
91>  set newname for datafile 26 to
92> '/u02/vssppln/mipsdata1_index01.dbf';
93> 
94>  set newname for datafile 27 to
95> '/u02/vssppln/mipsdata201.dbf';
96> 
97>  set newname for datafile 28 to

98> '/u02/vssppln/nipsdata2_index01.dbf'; 99>

100>  set newname for datafile 29 to
101> '/u02/vssppln/tools01.dbf';
102> 
103>  set newname for datafile 30 to
104> '/u02/vssppln/users01.dbf';
105> 
106>  set newname for datafile 31 to
107> '/u02/vssppln/AIMINDEX01.dbf';
108> 
109>  set newname for datafile 32 to
110> '/u02/vssppln/aimfact1_index05.dbf';
111> 
112>  set newname for datafile 33 to
113> '/u02/vssppln/aimfact2_index05.dbf';
114> 
115> 
116> restore database;
117> 
118> restore controlfile to '/u02/vssppln/restored_cf.ctl';
119> 
120> mount database;
121> 
122> switch datafile all;
123> 
124> release channel disk_channel1;
125> }
126> 
127>

RMAN-06008: connected to recovery catalog database

RMAN-06006: connected to target database: vssppln (not mounted)

RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: disk_channel1
RMAN-08500: channel disk_channel1: sid=10 devtype=DISK

RMAN-03022: compiling command: sql
RMAN-06162: sql statement: alter session set NLS_DATE_FORMAT="YYYY-MM-DD HH24:MI:SS"
RMAN-03023: executing command: sql

RMAN-03022: compiling command: set

(and it slowly keeps spitting out these "RMAN-03022: compiling command: set " )

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: DENNIS WILLIAMS
  INET: DWILLIAMS_at_LIFETOUCH.COM

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Received on Fri Dec 05 2003 - 16:29:26 CST