I want to make a clean copy on a second machine of an ever running database.
Therefore, i enter
alter tablespace XXX begin backup;
for all tablespaces, copy the datafiles to the second machine, and after
alter tabaespace XXX end backup;
for all tablespaces, too.
Then i enter
alter database backup controlfile to 'newctl.sql';
Now i edit this file: removing the head, strike out "reuse", change "noresetlogs" to "resetlogs", and delete the last three statements. Finally, i copy this to the second machine.
The archive-redologs are also copied to this machine (including initXXXX.ora).
Now, on the second machine, with the oracle-software-installati
Now the following:
connect internal
@newctl.sql
alter database open resetlogs;
now the Message "ora-01195" occurs:
online backup of file 1 needs more recovery to be consistent.
I try to find out the last SCN of all datafiles:
select to_char(max(checkpoint_cha
... gives me an number YYY.
now:
recover database until change YYY using backup controlfile;
But this will result in the same.
If i use more archivelogs to recover ("recover until cancel..."), the most time it will work (perhaps 80%).
If i rename the latest online-redolog to an archivelog, there were never problems, and the database was up-to-date.
Are the problem the active rollback segments?
Or unfinished transactions (means this the same?)
Or "uncommited" data inserted during the backup phase?
Sure, i can make some log switches (=checkpoint) and copy the last archivelogs. But if i try to keep this instances in sync?
The last chance i can see, is to copy the controlfiles and online-redologs ONLINE two times, compare these, and if they're identical, it shoud be '(a bit) consistent'.
Or i freeze the oracle processes (which means the same as if the system hangs) and copy the online-redologs and controlfiles then.
Any tips/solutions!
Thanks.
PS: I don't have not more than 75 Question Points. If iv'e got 500, i would give so much.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
You are correct. Sometimes you have to apply the latest redo log. I also agree with dbrowser, that you should switch logs before you want to recover. This will archive the latest redo log and then you will not need to apply the latest redo log.
Here are the steps:
1. switch logfile.
2. archive controlfile to trace.
3. for each tablespace:
3a. take tablespace in backup mode. (begin backup)
3b. copy all files for the tablespace
3c. end backup on tablespace.
4. switch logfile.
5. wait for the logfile to be archived.
6. copy controlfile trace file, all datafiles and all archive log files between steps 1 and 5 to the backup server or another server.
7. Layout the datafiles as you wish and modify controlfile accordingly.
8. login as internal
9. start instance in nomount mode.
10. create controlfile with resetlogs. change database name if necessary.
11. recover database until CANCEL.
12. after you have applied all redo log files, enter CANCEL.
13. open database with resetlogs option.
When you backup datafile finished,you must switch logfile.during backup datafile,database is running and add redo log to logfile.
online backup is not consistent and arch log finished it.during backup,database consistent need online redo log to check consistent.
alter method,you create your controlfile noresetlog and open is noresetlog and apply online redo log.Of course,if database is running when you copy online redolog,the recover oper will often fail.
Please update and finalize this old, open question. Please:
1) Award points ... if you need Moderator assistance to split points, comment here with details please or advise us in Community Support with a zero point question and this question link.
2) Ask us to delete it if it has no value to you or others
3) Ask for a refund so that we can move it to our PAQ at zero points if it did not help you but may help others.
EXPERT INPUT WITH CLOSING RECOMMENDATIONS IS APPRECIATED IF ASKER DOES NOT RESPOND.
Thanks,
** Mindphaser - Community Support Moderator **
P.S. Click your Member Profile, choose View Question History to go through all your open and locked questions to update them.
Thanks, Dan.
I finalized this today and will monitor it in the event an adjustment is needed.
Points have been split.
Points for afkapur -> http://www.experts-exchang
Moondancer - EE Moderator
Business Accounts
Answer for Membership
by: dbrowerPosted on 2001-07-10 at 05:38:12ID: 6269044
You need to switch log files immediately after the point in time that you want to recover to. I believe that this will give you the last change that you are looking for