Dennis,
I have been admiring you from far. Thank you so much to reply to my email.
The renamed data file has been tested and there is no corruption of any
kind. The nightly physical and logical backups were successful completed
with no error. However, I got an ora-19502 error when I
Anne
What version of Oracle is this?
Okay, you renamed a production database file 10 days ago. Since then,
has Oracle been able to use this file? Can you export the table that is
stored on this file without error? Have you examined your RMAN backup log to
ensure this file is specifically
Anne
Gee, things must appear better from Texas! Thanks for the comment.
The only other thing I can suggest is to have your network administrator
take a careful look at any connection settings. I'm sorry I can't be more
specific, but we had a situation where the network/system administrator
Title: Message
Dear
List, I have renamed a datafile in a production
databaseten days ago. I have no error to back up this database
but I cannotduplicate/recover this database since. I
am getting ora-19502 write error on this file. Please
advise.
Many
thanks,
1. I have configured RMAN for controlfile autobackup, so that every DB
backup produces a backup of the controlfiles and spfile as well. With
these, I can easily recover from a loss of every single database file.
I can't imagine why anyone wouldn't do it this way (reponses invited).
2.
I'm now working on the problem of restoring a database
from one server to another, with different directory
locations and names. ( on Windoze )
I've got the syntax down, but there's something missing
in the Veritas docs, and I'm not quite there yet.
Guess I'll have to call Veritas support
Timothy
I will tell you what I've figured out. Perhaps someone else can
provide additional information.
1. Some people have reported success in extracting the control file from the
RMAN backup. I got stuck on the issue that RMAN wouldn't function unless the
target instance was up with
Hi Timothy , I am guessing about the following answers, and I work on
9.2.0.1.0 but anyway here goes :
(1) How do I recover from a RMAN backup to disk if I have lost all the
original database files (control files, data files and redo logs)
In nomount
First run SET DBID
SET UNTIL SEQUENCE number
--- Layzee DBA [EMAIL PROTECTED] wrote:
Hi DBA's
I am in the process of establishing Crash Recovery
scenarios using RMAN and i came across one situation
wherein i am able to recover a tbs having (non
system
tbs) rbs in it using svrmgrl but the same damn thing
does not work with
Rachel,
Did you ever determine if the unix crossmount or such to be the complete
problem?
Did the Rman backup turn out to be ok after all- no corruptions?
Ever find out if they run validate command?
Thanks Rachel,
Brian Spears
-Original Message-
Sent: Monday, March 03,
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
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 it
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]
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,
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:
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
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 in
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
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
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
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
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
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
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
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
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
alter
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
Call RMAN from command-line as follows:
rman nocatalog log=logfilename debug trace=tracefilename
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
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
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 that.
30 matches
Mail list logo