Thanks to everyone for your help. I finally was able to complete the RMAN
disaster recovery! I am backing up to NFS-mounted disk, which is
subsequently copied to tape. Oracle 8.1.6 on Compaq Tru64. Here is what I
learned:
1. Even if you use the RMAN catalog to back up your database, you can
recov
Thanks Jim. This morning I did something close to what you describe. I just
did
run {
allocate channel d1 type disk;
restore database;
}
Same result. It recovers the same set of files and hangs. At least this
rules out a lot of things like the time format of time. Now I'm thinking
maybe I should
Thanks Ruth. Actually the controlfile keeps records for quite a few backups.
I actually don't care about rolling forward. In a disaster recovery I will
probably only have the level zero backup from tape.
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Frid
And that is why you have to use the controlfile from the time of the backup.
Your current constrolfile doesn't know about back then, You can then roll
forward to whenever you want.
HTH,
Ruth
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Thursday
James
Will try your suggestion. I dodged the problem you describe with the control
file. I couldn't get RMAN to create the controlfile without the database
being mounted, so I've just been doing a backup controlfile. Thanks for the
ideas.
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
---
Dennis,
Try this:
sql> startup mount;
sql> exit
rman target sys/password nocatalog
then,
run {
allocate channel d1 type disk;
restore database;
recover database until cancel;
alter database open resetlogs;
}
Is you're controlfile coming from the RMAN backup set ora are you
copying i
Oops, I forgot to clarify that I have the production database in archivelog
mode, but the recovery database not in archivelog mode.
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Thursday, August 15, 2002 5:08 PM
To: '[EMAIL PROTECTED]'
James
I think
James
I think you may have put your finger on a possible misconception of mine.
Here is my situation/understanding.
- On production,
- Archive logging.
- RMAN backup to disk without shutting the database down.
- Not using RMAN to backup the archive logs.
- Disaster reco
I was thinking along those same lines...set your NLS_DATE_FORMAT
environment variable, for example, to '-MM-DD:HH24:MI:SS' and then use
a matching format in your script: set until time '2002-02-03:03:30:59';
This format is what I use.
Debi
At 01:13 PM 8/15/2002 -0800, James Howerton wro
Dennis,
Annother thought, I had similar hang problems while trying to clone a
database to annother box. I can't remember exactly what I did, it was
too long ago. I set the until time in a different format than you are
using.
run {
set until time '03-FEB-2002 03:30:59';
allocate channel d1typ
Dennis,
This is just a wild guess and I'm probably wrong but I saw in you're
original post this DB was not in archivelog mode, try putting it in
archivelog mode and running the restore again???
...JIM...
>>> [EMAIL PROTECTED] 8/15/02 2:58:31 PM >>>
Okay, I implemented everyone's comments and re
Ruth - You suggested using a backup controlfile. What I have been doing is
some time after the RMAN backup creates the backup set, I do a alter
database backup controlfile to "file", and use that. Does that sound okay to
you?
I really don't care when it recovers to, I'm just trying to perform a
Okay, I implemented everyone's comments and re-executed the RMAN recovery.
Here is what I did and the results.
1. Action: Removed "alter database open resetlogs" from the run statement.
Result: No change.
2. Action: Added trace=1 to the allocate channel command.
Result: No trace file is pr
Robert, Tim, Mladen, Bruce - Thanks for the excellent suggestions. I will
try them today.
Bruce - Yes, you have an excellent memory. Not only for the Metalink note,
but recalling my posting from a month ago. I was pulled into some other
projects and just now getting back to this one, trying the l
You have to use the backup controlfile to do a point-in-time recovery that
is prior to the current time. This may be your probelm.
Ruth
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Thursday, August 15, 2002 12:28 AM
> The problem is probably
This reminded me of a Metalink note I once found.
Dennis - you might want to look at Note:145624.1 (RMAN: Resolving an RMAN Hung Job)
for some more hints & information.
Tim - the note mentions the debug command line parameter but doesn't show the
"trace=1" phrase so its good to learn tha
The problem is probably in the "RESETLOGS" part. Do you have many large log files?
If you do, your instance is trying to initialize them all. Take a look at the system
monitor and observe the CPU consumption. If it is large, you have a problem. If it
isn't,
use sar -b 5 50 or something alike and
Call RMAN from command-line as follows:
rman nocatalog log= debug trace=
Both the "logfilename" and "tracefilename" should have copious amounts of
output, which can provide a clue.
When you allocate the channel, make sure to add the phrase "trace=1" to the
end of the ALLOCATE command. This
Robert - Thanks a million. I'll get started on that tomorrow. Yep, I figured
I'd made some type of novice error which is why I posted the commands I'm
using.
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Wednesday, August 14, 2002 4:33 PM
To: Multiple re
There is a bug in 8.1.6 that is fixed in 8.1.7:
1164440 The RMAN command "release channel" reports RMAN-20020 if there are
"set until" and "alter database open reset logs" commands in the same "run"
block.
While this isn't exactly like your problem, it might be related. So, I'd
remove the last
I am trying to perform an RMAN disaster recovery task. While I use an RMAN
catalog to make backups, I am trying to recover using just the control file
information.
Oracle 8.1.6, Compaq/HP Tru64
I start RMAN with
rman target sys/password nocatalog
then,
startup mount
run {
set until ti
21 matches
Mail list logo
