I tried that too. But did it not help. here is the ouput. executing command: SET NEWNAME
executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME allocated channel: c1 channel c1: sid=10 devtype=DISK allocated channel: c2 channel c2: sid=11 devtype=DISK allocated channel: c3 channel c3: sid=12 devtype=DISK Starting restore at 17-SEP-02 released channel: c1 released channel: c2 released channel: c3 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 09/17/2002 10:29:13 RMAN-06026: some targets not found - aborting restore RMAN-06100: no channel to restore a backup or copy of datafile 8 RMAN-06100: no channel to restore a backup or copy of datafile 7 RMAN-06100: no channel to restore a backup or copy of datafile 6 RMAN-06100: no channel to restore a backup or copy of datafile 5 RMAN-06100: no channel to restore a backup or copy of datafile 4 RMAN-06100: no channel to restore a backup or copy of datafile 3 RMAN-06100: no channel to restore a backup or copy of datafile 2 RMAN-06100: no channel to restore a backup or copy of datafile 1 --- DENNIS WILLIAMS <[EMAIL PROTECTED]> wrote: > Johnson > Their explanation doesn't make sense to me. I > have had RMAN fail to get > the backup piece, and the error message is very > clear. > Just in case the SET NEWNAME is somehow affecting > the recovery, you might > take them out just to see what happens. I would also > have moved the ALLOCATE > CHANNEL below the SET NEWNAME, rather than opening a > new set of channels, > but then I haven't used SET NEWNAME. I just had my > Unix sys admin create > mount points named the same as the mount points on > the production system. > Perhaps someone can post an RMAN recovery script > that includes a SET > NEWNAME, so you can compare. You might also post > your recovery script, that > might clarify something. > Also, this is Oracle 9.2, and most of my RMAN > practice has been on Oracle > 8.1.6. > Another thought for a test is to backup the > production control file > separately and then place it where it is needed, > rather than have RMAN > recover it. I'm just wondering whether you are > getting some side-effect from > the successful control file recovery. > > Dennis Williams > DBA > Lifetouch, Inc. > [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > > -----Original Message----- > From: Johnson Poovathummoottil > [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 17, 2002 9:16 AM > To: DENNIS WILLIAMS; '[EMAIL PROTECTED]' > Subject: RE: RMAN restore to another node > > > They are alluding it to a possibilty that RMAN > cannot > find the backup piece and just before showing the > error it realeasing channels and that releasing > channels per se does not point to any problem. > > --- DENNIS WILLIAMS <[EMAIL PROTECTED]> wrote: > > Johnson - Did Oracle Support offer any theories on > > why the RMAN channels > > were being spontaneously released? Is Oracle > Support > > looking into this as a > > possible bug, and you are just checking to see > > whether anyone else has > > experienced this behavior? > > > > Dennis Williams > > DBA > > Lifetouch, Inc. > > [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> > > > > > > -----Original Message----- > > From: Johnson Poovathummoottil > > [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, September 17, 2002 9:02 AM > > To: DENNIS WILLIAMS; '[EMAIL PROTECTED]' > > Cc: '[EMAIL PROTECTED]' > > Subject: RE: RMAN restore to another node > > > > > > Oracle support too pointed to that. I tested with > > allocating 3 more channnels after 'set newname'. > But > > no change. They were released. and same error > > followed. > > > > --- DENNIS WILLIAMS <[EMAIL PROTECTED]> > wrote: > > > Johnson > > > From what I read of your trace file, the > > channels > > > are being released, > > > presumably just before you need them. Do you > have > > > that explicitly coded in > > > your RMAN recovery script, or are they being > > > released for another reason. My > > > immediate response is that maybe the problem > lies > > in > > > why those channels are > > > being released. Can you move your channel > commands > > > after the SET NEWNAME > > > commands? > > > > > > Dennis Williams > > > DBA > > > Lifetouch, Inc. > > > [EMAIL PROTECTED] > > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > -----Original Message----- > > > From: Johnson Poovathummoottil > > > [mailto:[EMAIL PROTECTED]] > > > Sent: Tuesday, September 17, 2002 9:23 AM > > > To: Multiple recipients of list ORACLE-L > > > Subject: RMAN restore to another node > > > > > > > > > Hi all, > > > > > > I am stuck on this restore for two days and > Oracle > > > support seems to offering little help. > > > > > > I seem to be doing everything according to > manuals > > > and > > > metalink notes but am not able to do the > restore. > > > > > > The case is I am restoring a database to another > > > node. > > > I have successfully restore the control file but > > > when > > > I tried to restore the database I get > > > RMAN-06100: no channel to restore a backup or > copy > > > of > > > datafile 1 > > > for every datafile. > > > > > > I am inserting the RMAN trace . I would > appreciate > > > if > > > someone can lead in the right direction. > > > Recovery Manager: Release 9.2.0.1.0 - Production > > > > > > Copyright (c) 1995, 2002, Oracle Corporation. > All > > > rights reserved. > > > > > > ORACLE_HOME = /opt/Apps/oracle/product/9.2.0 > > > System name: SunOS > > > Node name: EdwDev > > > Release: 5.8 > > > Version: Generic_108528-15 > > > Machine: sun4u > > > > > > Starting with debugging turned off > > > > > > connected to target database: DB01 (not mounted) > > > using target database controlfile instead of > > > recovery > > > catalog > > > > > > RMAN> > > > executing command: SET DBID > > > > > > RMAN> 2> 3> 4> > > > allocated channel: ci > > > channel ci: sid=10 devtype=DISK > > > > > > Starting restore at 17-SEP-02 > > > > > > channel ci: restoring controlfile > > > channel ci: restore complete > > > replicating controlfile > > > input filename=/extracts1/DB01_temp/ctrl1.ctl > > > output filename=/extracts1/DB01_temp/ctrl2.ctl > > > output filename=/extracts1/DB01_temp/ctrl3.ctl > > > Finished restore at 17-SEP-02 > > > released channel: ci > > > > > > RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> > 14> > > > 15> > > > 16> > > > allocated channel: c1 > > > channel c1: sid=10 devtype=DISK > > > > > > allocated channel: c2 > > > channel c2: sid=11 devtype=DISK > > > > > > allocated channel: c3 > > > channel c3: sid=12 devtype=DISK > > > > > > executing command: SET NEWNAME > > > > > > executing command: SET NEWNAME > > > > === message truncated === __________________________________________________ Do you Yahoo!? Yahoo! News - Today's headlines http://news.yahoo.com -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Johnson Poovathummoottil INET: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] (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).
