Scn in redologs and controlfile

Hi
The checkpoint scn in datafile headers are updated after checkpoint.
How about redologs and controlfile?
As far I read from the docs
scn's are written to redo logs continuously, it should also stored in controlfile continuesly(every commit) so that controlfile will know where redochain ends ..
Is that right?

Hi,
The checkpoint scn in datafile headers are updated after checkpoint.
Yes. By CKPT process.
scn's are written to redo logs continuously
Yes, by LGWR every COMMIT IMMEDIATE.
+ it should also stored in controlfile continuesly(every commit) so that controlfile will know where redochain ends ..+
Even if it is in controlfile then it is NOT updated every commit.
Bartek

Similar Messages

Checkpoint scn in redolog and controlfile

Hi
The checkpoint scn in datafile headers are updated after checkpoint.
How about redologs and controlfile?
As far I read from the docs
scn's are written to redo logs continuously (every commit), it should also stored in controlfile continuesly(every commit) so that controlfile will know where redochain ends ..
Is that right?

Pascal Nouma wrote:
Yes Aman, I read it.
As I said,
I learned that scn is incremented in controlfile and datafile after checkpoint.
However still have doubts about redologs..No, that's what my doubt is. If you have read the thread thoroughly, it explains that in the redo logs, there is open/close SCN. And I have shown its behavior too there. SCN is nothing but a time stamp(see Hans's reply also for the explanation, in the thread too , I have posted one) and as redologs contain nothing but transactions, each one would be having its starting and ending SCN(the article posted by Hans goes into great length to show it) . The files would have the high and low scn. I would suggest that you reread the thread one more time and come back with a more detailed question. I am not still sure that what is your doubt regarging the scn in the redologs. Control file's mechanism or data files's mechanism are different as the writes happen at certain events while redo logs are constantly being fliushed with the minimum frequency of 3seconds. So things are not really alike and its not good to compare bit by bit all the aspects in every file IMHO.
HTH
Aman....

SCN in redologs

Hi
The scn of the controlfile and datafile headers updated after checkpoint,
How about the SCN in redologs, Are they updated after every checkpoint or every commit ?

Dear scofield!
You can find a very interesting article about "Checkpointing in Oracle" at the following site:
[http://www.vldb.org/conf/1998/p665.pdf]
Yours sincerely
Florian W.

Scn of redologs

Hi
I know that when I start the database the scn of controlfile,datafile headers and redologs
shoud be same.
I can compare scn of datafiles from v$datafile_header
Control file from v$datafile
redolog from v$log
For example:
sys@XE> select CHECKPOINT_CHANGE# from v$datafile;
CHECKPOINT_CHANGE#
4344269
4344269
4344269
4344269
sys@XE> select first_Change# from v$log;
FIRST_CHANGE#
4341385
4341016
My database is up at the moment and above confirms that redolog scn is behind than controlfile and datafile.
What I want to ask is,
When I shutdown the database and restore old redologs and create a controlfile with noresetlogs option
It fails with:
ORA-01229: data file 4 is inconsistent with logs.
How can oracle understand if the current online redologs are consistent or not?
As I showed above, the redo scn is already behind while the db is up.
It should compare something else..

Oracle does check the redo logs. There is more information in the redo logs (and datafile headers, for that matter) than you can see in V$LOG or V$DATAFILE_HEADER.
e.g. I see :
SQL> select checkpoint_change# from v$datafile;
CHECKPOINT_CHANGE#
          13491047
          13491047
          13491047
          13491047
          13491047
          13491047
          13491047
          13491047
8 rows selected.
SQL> select group#, first_change# from v$log;
    GROUP# FIRST_CHANGE#
         1      13487614
         2      13488637
         3      13489762
SQL>But if I take a dump of the Group#3 log file, I can see :
Last redo scn: 0x0000.00cddcd0 (13491408)Hemant K Chitale
http://hemantoracledba.blogspot.com

How Can I Restore database from datafiles, control,redolog and parameter

Hi there,
The scenario is Database Server is down, meaning that OS has been corrupted, data files and other files can be retrieved from the hard drive. Database is not is archivelog mode, No full backup of the database is available. Only Full DMP Backup is there. I have imported the full dmp backup but is seems like it could not import all of it. Specially some of the Packages and triggers are missing or invalid(does not compile successfully). May be dump backup has been corrupted.
Now Can I restore all data with other objects(views,packages,triggers)in different server and different database if I can copy all datafiles, controlfiles, redolog and other parameter files? Please reply with solutions
Hasan Al Mamun
Programmer
Bangladesh Bank.
Dhaka, Bangladesh

pgoel wrote:
Yes, Create same directory structure on new server and copy all datafiles, controlfiles, redolog and other parameter files at new location and re-start the database again.OP has stated that db in not in archivelog mode and no full backup has been taken. If the database crashed while open, recovery using what you have described is impossible AFAIK (unless Consulting gets involved).
Srini

Took backup of data files and controlfile but not archive file db is 11g xe

took backup of data files and controlfile but not redo file db is 11g xe r2..was trying complete shut backup,..missed redo..
anyway to restore the db back..
I had failed to backup redo log file..
db was shut...properly
any info highly appreciated.
cheers
Edited by: zycoz100 on Feb 27, 2013 4:42 AM

A controlfile create is a fairly trivial task, for either a cold backup or hot backup scenario. Well, its an easy task after you've done the process a few times.
If you have a healthy oracle instance running any place else, preferably at 11gR2, or even a 10g instance can work as an example, get a system connection and do an `alter database backup controlfile to trace;` and the instance will create a new trace file with all SQL commands needed to rebuild the controlfile in the instance trace directory.
Have a look at the trace file, a `show parameter diag` reveals the diagnostic_dest parameter, look for the "trace" directory under that folder, for the latest *trc file. In 10g its `show parameter dump` and the trace file goes straight to the user_dump_dest directory, no digging required.

On RESETLOGS and CONTROLFILE restore

Friends,
Do we have to always open the database with RESETLOGS option after a controlfile restore from nomount with RMAN? If so then what is the reason?
Thanks much.

Fadai,
As soon as you restore a controlfile the information in the controlfile is no longer in sync with the information in the datafile headers.
When you open a database it has to be in sync.
The purpose of resetlogs is:
Whatever is in the datafiles is OK, forget about the info in the controlfile, and SYNC datafile headers and controlfile.
Otherwise you wouldn't be able to open the database.
Hth
Sybrand Bakker
Senior Oracle DBA

Applying redolog and archivelog

hi,
people always say complete recovery is when u apply all redo log and archive log..
well i am confused when making a backup...how to apply redolog and archive log..
suppose i restore a backup ,. how do i apply the archive and redolog...
thnx for the help//

Hi,
well i am confused when making a backup...how to apply redolog and archive logwhen taking backup why to apply redologs? You are backing up, NOT Recovering.
suppose i restore a backup ,. how do i apply the archive and redolog...If it is a cold backup .NO need of applying anything.
For More INFO Read ORACLE CONECPTS MANUALS at tahiti.oracle.com
Regards!

PERFORMING FULL RECOVERY WHEN THE RECOVERY CATALOG AND CONTROLFILE ARE LOST

제품 : RMAN
작성날짜 : 2002-05-30
PERFORMING FULL RECOVERY WHEN THE RECOVERY CATALOG AND CONTROLFILE ARE LOST
===========================================================================
PURPOSE
Recovery Catalog와 Controlfile이 손상되었을 때 Oracle9i의 new feature인
Controlfile Autobackup을 이용하여 full recovery를 수행하는 방법을 알아본다
EXPLANATION
Catalog와 Controlfile이 모두 손상되었을 경우 full recovery를 수행할 수 있도록
하기 위해 oracle9i부터 Controlfile Autobackup이라는 New feature를 제공한다.
이 Feature가 활성화되면 RMAN은 자동으로 특정 형식(specific format)으로
controlfile을 backup한다 나중에 RMAN은 Recovery catalog를 access하지 않고도
이 backup을 인식할 수 있다. 이 형식은 "%F"라는 variable을 포함하는데
이 variable은 중요한 정보인 DATABASE ID를 포함하고 있다.
이것은 다음과 같은 CONFIGURE 명령을 사용하여 Turn-on 될 수 있다.
RMAN> configure controlfile autobackup on;
활성화시킨 후에 controlfile autobackup의 format을 변경할 수 있다. 그러나
이것은 반드시 variable "%F"를 포함해야만 한다. 그렇지 않으면 다음과 같은 Error
를 만나게 된다.
RMAN> configure controlfile autobackup format for
2> device type disk to 'c:\backups\%U';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00579: the following error occurred at 01/31/2002 11:57:21
RMAN-03002: failure during compilation of command
RMAN-03013: command type: configure
RMAN-06492: controlfile autobackup format "c:\backups\%U" must specify a "%F"
format specifier
%F 는 RMAN이 recovery catalog 없이 backup piece를 인식하도록 Key이다.
이 Feature가 활성화 된 후에 RMAN은 BACKUP 명령을 수행할 때마다 controlfile에
대해서 별도의 backup을 수행한다. 이전에는, controlfile 은 오직 system
tablespace가 backup되는 경우에만 자동으로 backup되었다.
Database Backup은 아래와 같은 log를 출력한다.
RMAN> backup database;
Starting backup at 31-JAN-02
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=12 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\ORADATA\PROD\SYSTEM01.DBF
input datafile fno=00002 name=C:\ORACLE\ORADATA\PROD\UNDOTBS01.DBF
input datafile fno=00005 name=C:\ORACLE\ORADATA\PROD\EXAMPLE01.DBF
input datafile fno=00006 name=C:\ORACLE\ORADATA\PROD\INDX01.DBF
input datafile fno=00008 name=C:\ORACLE\ORADATA\PROD\USERS01.DBF
input datafile fno=00003 name=C:\ORACLE\ORADATA\PROD\CWMLITE01.DBF
input datafile fno=00004 name=C:\ORACLE\ORADATA\PROD\DRSYS01.DBF
input datafile fno=00007 name=C:\ORACLE\ORADATA\PROD\TOOLS01.DBF
channel ORA_DISK_1: starting piece 1 at 31-JAN-02
channel ORA_DISK_1: finished piece 1 at 31-JAN-02
piece handle=C:\BACKUPS\01DFKAIH_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:56
Finished backup at 31-JAN-02
Starting Control File Autobackup at 31-JAN-02
piece handle=C:\BACKUPS\C-4159396170-20020131-00 comment=NONE
Finished Control File Autobackup at 31-JAN-02
Note:
Controlfile backup은 backup의 끝에서 수행된다.
그리고 이 backup piece name의 두번째 string은 dbid이다(4159396170)
Current controlfile이 database와 함께 손실되고 Recovery catalog도 손상되어
사용할 수 없게 되었을 때 controlfile autobackup이 controlfile을 restore하기
위해 사용될 수 있다. restore된 controlfile은 db를 mount하고 datafile들을
restore하기 위해 사용될 수 있다.
Controlfile autobackup을 이용하여 full recovery를 수행하기 위해서는 아래와
같은 과정을 수행하면 된다.
1. Target instance를 위한 new init.ora를 생성한다. backup이 있다면 이것을
사용할 수 있다.
2. Startup nomount your new instance.
3. RMAN은 시작하나 어떤 connect statement도 수행하지 않는다.
4. RMAN prompt상에서 DBID를 설정한다. 만약 DBID를 모르면 controlfile autobackup
의 이름으로부터 이것을 알 수 있다.
RMAN> set dbid=4159396170;
5. Dbid를 설정한 후에 nomount로 startup한 target instance에 connect한다.
RMAN> connect target /
6. 만약에 backup이 disk상에 있고 controlfile autobackup을 non-default location
으로 지정하였다면 파일을 다음과 같은 위치로 옮겨 놓는다
ON UNIX : ORACLE_HOME/dbs
ON WINDOWS: ORACLE_HOME/database
RMAN은 controlfile autobackup을 찾기 위해 위 directory를 검색한다.
만약 controlfile autobackup location을 바꾸지 않으면 위 directory안에
backup이 생성되게 된다.
만약에 backup이 tape에 있다면 restore시 channel과 device를 기술하기 위해서
run block을 사용해야 한다. database가 mount되어 있지 않기 때문에
default device와 channel을 설정할 수 없다.
RMAN> run { allocate channel c_1 type 'sbt_tape'
parms "ENV=(NB_ORA_SERV=rm-wgt)";
restore controlfile from autobackup;}
7. Restore the controlfile:
RMAN> restore controlfile from autobackup;
8. Mount the database from the restored controlfile:
RMAN> alter database mount;
9. Restore datafiles:
RMAN> restore database;
10. file들을 restore한 후에 recovery를 수행할 수 있다.
이때 current online redo log가 없고 또한 backup controlfile을 사용하기
때문에 incomplete recovery를 수행해야 한다. 이를 수행하기 위해서는
"UNTIL TIME"을 설정해야 하고 open시에는 resetlogs를 사용해야 한다.
RMAN> set until time=<time stamp>;
RMAN> recover database;
RMAN> alter database open resetlogs;
REFERENCE DOCUMENT
NOTE:174623.1

BACKUP Command Behavior
ON
If the backup includes datafile 1, then RMAN does not automatically include the current control file in the datafile backup set. Instead, RMAN writes the control file and server parameter file to a separate autobackup piece.
Note: The autobackup occurs regardless of whether the BACKUP or COPY command explicitly includes the current control file, for example, BACKUP DATABASE INCLUDE CURRENT CONTROLFILE.
OFF
If the backup includes datafile 1, then RMAN automatically includes the current control file and server parameter file in the datafile backup set. RMAN does not create a separate autobackup piece containing the control file and server parameter file.
BUT Dear Mohammed,
It is not working accordingly. what I did is :-
1. I switched off the AUTOBACKUP
2. Then I took whole database backup, that means it included File # 1
3. But according to above it is going to include autobackup of controlfile and spfile in the same backupset .
4. But when I asked it to restore controlfile from autobackup it said NO AUTOBACKUP FOUND.
COULD YOU PLEASE HELP ME ONCE AGAIN DEAR.
If it works accroding to above then it should have my Autobackup.
Regards
Harpreet Singh

Redolog and checkpoint problems

Hi!
We are working on Oracle 10.2.0.3.0 Standard Edition on a Windows 2003 Server platform.
We are facing the following two problems:
Problem 1:
Thread 1 cannot allocate new log, sequence 953
Checkpoint not complete
Current log# 4 seq# 952 mem# 0: R:\ORANT\ORADATA\ITBMED4\REDOLOG\REDO04A.LOG
Current log# 4 seq# 952 mem# 1: S:\ORANT\ORADATA\ITBMED4\REDOLOG\REDO04B.LOG
Thu Jun 07 07:11:53 2007
Thread 1 advanced to log sequence 953
Current log# 1 seq# 953 mem# 0: R:\ORANT\ORADATA\ITBMED4\REDOLOG\REDO01A.LOG
Current log# 1 seq# 953 mem# 1: S:\ORANT\ORADATA\ITBMED4\REDOLOG\REDO01B.LOG
The database is not very active and there are 4 redo log files each of 50 MB in size. We have implemented this at several customers but only one customer gets this error.
After an 'ALTER SYSTEM CHECKPOINT' followed by a log switch, the error disappears from the alert log but then again appears after a few more log switches.
Other points of concern are that the archived logs are not the same size as the redo logs (before we did the log switch exercise).
The layout on the server is:
Disk 1: Oracle installation and data files
Disk 2: redo log files
Disk 3: redo log files
Disk 4: Archived logs
What is the solution to this problem?
Problem 2:
The second problem is that the OS timestamp of the redo log files does not change. It remains the same as the date on which we migrated the database from 8i to 10g.
Regards,
Aniruddha

Yes, I had a look at this Metalink note. I reproduce the relevant information for discussion below:
This message indicates that Oracle wants to reuse a redo log file, but
the current checkpoint position is still in that log. In this case, Oracle must
wait until the checkpoint position passes that log. Because the
incremental checkpoint target never lags the current log tail by more than 90%
of the smallest log file size, this situation may be encountered if DBWR writes
too slowly, or if a log switch happens before the log is completely full,
or if log file sizes are too small.
I do not feel that this is related to the size of the log file as we do not get this problem at any other customer which have larger activity. Under what conditions can the log switch happen before the log is completely full other than purposefully switching the log file?

What would you think if SCN hides points and displays only your badges and current level?

Hi
After recent change or improvement I must say, in SCN gamification and points system I just came up with an idea that what if SCN hides points completely and calculate and maintain them just they way they are being calculated now?
With this you'll be able to see reputation of users just with their badges (Answer Hero, Story Teller, Thought Leader etc) and their levels (Diamond, Gold, Topaz etc). Would you like that reputation system or this one with points showing with every name.? Please share your thoughts and views.
Thank$

Hi JP
Thank you for being part of this discussion and sharing your views. As you can see there are users with different opinions and its good that we have multiple thoughts on it.
When I post a question and get responses from users and if I like someone's response I always visit his profile and see his badges/level/points and area of expertise. It gives me an idea about his potential and increases my trust level. There are many users who sometimes give foolish suggestions without knowing anything. Some users respond just for the sake of points and they give irrelevant answers. If we see badges and points it gives us or at least me a trust level on poster. This is the reason that reputation system is mandatory for this type of forums.
It doesn't mean newbies can't post good and valuable posts. There can be a newbie who has tons of knowledge and years of experience but he is new in SCN. Exceptions are always there but if we see as a whole you must be agreed that newbies post basic or sometimes irrelevant posts mostly.
As you said points give us a barometer and sometimes this barometer can be misused specially when you are near to get some next level. You must have seen in car racings that driver boosts up speed to his maximum in last lap of race. When a user sees he needs just 300/400 points to reach next level (Topaz/Emerald) etc he can use tricks to get points. If we have only levels and badges and points are being calculating at background users will be contributing positively without curse of points.
This is what I believe in.
Thank$

SCN in blocks and datafile headers

When CKPT updates datafiles headers with the new SCN is it also updates the datafiles blocks with the new SCN ?
Thank you,
Micheal.

imran khan wrote:
The SCN are not stored the datafile blocks in fact it stores the SCNs in terms of bitmaps..Cheers!An absolutely wrong statement! How you think that the transaction within a block would come to know that its committed or not if there is no SCN stored in the block?
See below the dump of a block and also the SCN info recorded in it,
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select header_file, header_block from dba_segments where segment_name='EMP'
2 ;
HEADER_FILE HEADER_BLOCK
          4          234
SQL> select blocks from dba_segments where segment_name='EMP' and owner='SCOTT';
    BLOCKS
         8
SQL> alter session set tracefile_identifier=myblockd;
Session altered.
SQL> alter system dump datafile 4 block 235;
System altered.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Windows XP Version V5.1 Service Pack 2
CPU                 : 2 - type 586
Process Affinity    : 0x0x00000000
Memory (Avail/Total): Ph:437M/2045M, Ph+PgF:1335M/3428M, VA:1663M/2047M
Instance name: orcl
Redo thread mounted by this instance: 1
Oracle process number: 30
Windows thread id: 4596, image: ORACLE.EXE (SHAD)
*** 2011-08-21 17:40:49.781
*** SESSION ID:(16.6) 2011-08-21 17:40:49.781
*** CLIENT ID:() 2011-08-21 17:40:49.781
*** SERVICE NAME:(SYS$USERS) 2011-08-21 17:40:49.781
*** MODULE NAME:(sqlplus.exe) 2011-08-21 17:40:49.781
*** ACTION NAME:() 2011-08-21 17:40:49.781
Start dump data blocks tsn: 4 file#:4 minblk 235 maxblk 235
Block dump from cache:
Dump of buffer cache at level 4 for tsn=4, rdba=16777451
Block dump from disk:
buffer tsn: 4 rdba: 0x010000eb (4/235)
scn: 0x0000.002c106e seq: 0x05 flg: 0x04 tail: 0x106e0605
frmt: 0x02 chkval: 0xed5f type: 0x06=trans data
Hex dump of block: st=0, typ_found=1There is for sure, a block level SCN that oracle maintains .
Aman....

..... Redolog and Recovery

Hi all,
Again focusing on the basics, May i know that when a system crashes/ or any power failure, How oracle recognise that a transaction has been commited or not?
One way i think is that oracle assigns a SCN to all commited transactions but not to the uncommited transaction. Is this true?
Or may be that Checkpoint Update the headers of all files and include SCN of the latest commited transaction only?
Kindly highlight
Thanks alot

Yes, And this Tom discussion would add value of your thinking See How hare krishna Alok

Rman restore spfile and controlfile issue

I have a backup of a db-test on another server....
The backup contains autobackup.tar, backupset.tar, controlfile.txt,
dba_rman_local_ueadbs2_TEST_2007_01_03.log, initTEST.txt, listener.ora,
o1_mf_s_610888673_2sq471ln_.bkp,orapwTEST, snapcf_TEST.f,tnsnames.ora
Using rman, I would like to create a new db-test on the server where i
have the backups....
I ve created the neccessary paths required for the on the new sever...
The problem is with the autobackup which cannot be located in the backup...
Checkout the rman prompt:
RMAN> set DBID = 1858659026
executing command: SET DBID
RMAN> startup nomount;
startup failed: ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file
'/u01/app/oracle/product/10.1.0/db_1/dbs/initTEST.ora'
trying to start the Oracle instance without parameter files ...
Oracle instance started
Total System Global Area 88080384 bytes
Fixed Size 1300928 bytes
Variable Size 68953664 bytes
Database Buffers 16777216 bytes
Redo Buffers 1048576 bytes
RMAN> run {
2> set controlfile autobackup format for device type disk to
'/hostbackups/oracle/TEST/%F';
3> restore spfile from autobackup maxseq 200 maxdays 100;
4> restore controlfile from autobackup maxseq 200 maxdays 100;
5> startup force mount
6> }
executing command: SET CONTROLFILE AUTOBACKUP FORMAT
using target database controlfile instead of recovery catalog
Starting restore at 05-JAN-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=29 devtype=DISK
channel ORA_DISK_1: looking for autobackup on day: 20070105
channel ORA_DISK_1: looking for autobackup on day: 20070104
channel ORA_DISK_1: looking for autobackup on day: 20070103
channel ORA_DISK_1: looking for autobackup on day: 20070102
channel ORA_DISK_1: looking for autobackup on day: 20070101
channel ORA_DISK_1: looking for autobackup on day: 20061231
channel ORA_DISK_1: looking for autobackup on day: 20061230
channel ORA_DISK_1: looking for autobackup on day: 20061229
channel ORA_DISK_1: looking for autobackup on day: 20061228
channel ORA_DISK_1: looking for autobackup on day: 20061227
channel ORA_DISK_1: looking for autobackup on day: 20061226
channel ORA_DISK_1: looking for autobackup on day: 20061225
channel ORA_DISK_1: looking for autobackup on day: 20061224
channel ORA_DISK_1: looking for autobackup on day: 20061223
channel ORA_DISK_1: looking for autobackup on day: 20061222
channel ORA_DISK_1: looking for autobackup on day: 20061221
channel ORA_DISK_1: looking for autobackup on day: 20061220
channel ORA_DISK_1: looking for autobackup on day: 20061219
channel ORA_DISK_1: looking for autobackup on day: 20061218
channel ORA_DISK_1: looking for autobackup on day: 20061217
channel ORA_DISK_1: looking for autobackup on day: 20061216
channel ORA_DISK_1: looking for autobackup on day: 20061215
channel ORA_DISK_1: looking for autobackup on day: 20061214
channel ORA_DISK_1: looking for autobackup on day: 20061213
channel ORA_DISK_1: looking for autobackup on day: 20061212
channel ORA_DISK_1: looking for autobackup on day: 20061211
channel ORA_DISK_1: looking for autobackup on day: 20061210
channel ORA_DISK_1: looking for autobackup on day: 20061209
channel ORA_DISK_1: looking for autobackup on day: 20061208
channel ORA_DISK_1: looking for autobackup on day: 20061207
channel ORA_DISK_1: looking for autobackup on day: 20061206
channel ORA_DISK_1: looking for autobackup on day: 20061205
channel ORA_DISK_1: looking for autobackup on day: 20061204
channel ORA_DISK_1: looking for autobackup on day: 20061203
channel ORA_DISK_1: looking for autobackup on day: 20061202
channel ORA_DISK_1: looking for autobackup on day: 20061201
channel ORA_DISK_1: looking for autobackup on day: 20061130
channel ORA_DISK_1: looking for autobackup on day: 20061129
channel ORA_DISK_1: looking for autobackup on day: 20061128
channel ORA_DISK_1: looking for autobackup on day: 20061127
channel ORA_DISK_1: looking for autobackup on day: 20061126
channel ORA_DISK_1: looking for autobackup on day: 20061125
channel ORA_DISK_1: looking for autobackup on day: 20061124
channel ORA_DISK_1: looking for autobackup on day: 20061123
channel ORA_DISK_1: looking for autobackup on day: 20061122
channel ORA_DISK_1: looking for autobackup on day: 20061121
channel ORA_DISK_1: looking for autobackup on day: 20061120
channel ORA_DISK_1: looking for autobackup on day: 20061119
channel ORA_DISK_1: looking for autobackup on day: 20061118
channel ORA_DISK_1: looking for autobackup on day: 20061117
channel ORA_DISK_1: looking for autobackup on day: 20061116
channel ORA_DISK_1: looking for autobackup on day: 20061115
channel ORA_DISK_1: looking for autobackup on day: 20061114
channel ORA_DISK_1: looking for autobackup on day: 20061113
channel ORA_DISK_1: looking for autobackup on day: 20061112
channel ORA_DISK_1: looking for autobackup on day: 20061111
channel ORA_DISK_1: looking for autobackup on day: 20061110
channel ORA_DISK_1: looking for autobackup on day: 20061109
channel ORA_DISK_1: looking for autobackup on day: 20061108
channel ORA_DISK_1: looking for autobackup on day: 20061107
channel ORA_DISK_1: looking for autobackup on day: 20061106
channel ORA_DISK_1: looking for autobackup on day: 20061105
channel ORA_DISK_1: looking for autobackup on day: 20061104
channel ORA_DISK_1: looking for autobackup on day: 20061103
channel ORA_DISK_1: looking for autobackup on day: 20061102
channel ORA_DISK_1: looking for autobackup on day: 20061101
channel ORA_DISK_1: looking for autobackup on day: 20061031
channel ORA_DISK_1: looking for autobackup on day: 20061030
channel ORA_DISK_1: looking for autobackup on day: 20061029
channel ORA_DISK_1: looking for autobackup on day: 20061028
channel ORA_DISK_1: looking for autobackup on day: 20061027
channel ORA_DISK_1: looking for autobackup on day: 20061026
channel ORA_DISK_1: looking for autobackup on day: 20061025
channel ORA_DISK_1: looking for autobackup on day: 20061024
channel ORA_DISK_1: looking for autobackup on day: 20061023
channel ORA_DISK_1: looking for autobackup on day: 20061022
channel ORA_DISK_1: looking for autobackup on day: 20061021
channel ORA_DISK_1: looking for autobackup on day: 20061020
channel ORA_DISK_1: looking for autobackup on day: 20061019
channel ORA_DISK_1: looking for autobackup on day: 20061018
channel ORA_DISK_1: looking for autobackup on day: 20061017
channel ORA_DISK_1: looking for autobackup on day: 20061016
channel ORA_DISK_1: looking for autobackup on day: 20061015
channel ORA_DISK_1: looking for autobackup on day: 20061014
channel ORA_DISK_1: looking for autobackup on day: 20061013
channel ORA_DISK_1: looking for autobackup on day: 20061012
channel ORA_DISK_1: looking for autobackup on day: 20061011
channel ORA_DISK_1: looking for autobackup on day: 20061010
channel ORA_DISK_1: looking for autobackup on day: 20061009
channel ORA_DISK_1: looking for autobackup on day: 20061008
channel ORA_DISK_1: looking for autobackup on day: 20061007
channel ORA_DISK_1: looking for autobackup on day: 20061006
channel ORA_DISK_1: looking for autobackup on day: 20061005
channel ORA_DISK_1: looking for autobackup on day: 20061004
channel ORA_DISK_1: looking for autobackup on day: 20061003
channel ORA_DISK_1: looking for autobackup on day: 20061002
channel ORA_DISK_1: looking for autobackup on day: 20061001
channel ORA_DISK_1: looking for autobackup on day: 20060930
channel ORA_DISK_1: looking for autobackup on day: 20060929
channel ORA_DISK_1: looking for autobackup on day: 20060928
channel ORA_DISK_1: no autobackup in 100 days found
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 01/05/2007 09:25:59
RMAN-06172: no autobackup found or specified handle is not a valid copy or
piece
RMAN> exit
what could be the reason why the autobackup is not found?
Cheers..
Kenny.

I have a backup of a db-test on another server....
The backup contains autobackup.tar, backupset.tar,
controlfile.txt,
dba_rman_local_ueadbs2_TEST_2007_01_03.log,
initTEST.txt, listener.ora,
o1_mf_s_610888673_2sq471ln_.bkp,orapwTEST,
snapcf_TEST.f,tnsnames.oraAre the backups and the control file autobackup tared? Have you un-tared the files?

Drop dbf file and then recover - possible?

We have to 'startup mount' our database and then
1. alter database datafile ....12.dbf offline
2. recover using backupcontrolfile until cancel.
Can we do this on oracle 9.1.7

Hi,
I am not sure if I have understood the question.
Here is my translation of my understanding:
- you have dropped a datafile and do not have a backup, right?
- you want to recover the lost datafile, right?
My question now is:
- how did you drop the file?
1. did you remove it on OS level?
2. did you drop the tablespace?
Here the possible answers:
=> 1: if you "just" removed the file from the OS it is no problem to recreate it and recover it, under the condition that you have all the redologs archived or online which contain all the changes applied to the db since the creation of the lost datafile. Oracle will know the creation change number for the file and will be able to create a new one. It works like this:
SQL > ALTER DATABASE CREATE DATAFILE '<name of your lost file>';
SQL> RECOVER DATAFILE '<name of your lost file>' -- number of the file is also possible
SQL > ALTER DATABASE DATAFILE '<name of your lost file> ONLINE;
=> 2: if you have dropped teh entire database by DROP TABLESPACE ... INCLUDING CONTENTES AND DATAFILES; it is a little more tricky. Now you first need a controlfile which still contains the talespace information, because the tablesapce has been removed from the controlfile with the drop stsatement. And you can only recover what is in the controlfile. So you need a backup of the old controlfile, either a binary controlfile backup or a backup from a trace controlfile backup.
In this case you must shutdown the db and startup with a backup controlfile. You must restore the entire db from backup and recover incomplete, which means loss of data!
You must recover the whole db to a point in time short before the drop tablespace. YOu can find the timestamp for the drop tablespace in the alertSID.log file.
The first thing you do is to take a full backup of the entire db including redologs and controlfile, just in case you make a mistake in order to be able to get back to where you started!!!
Then resore db from backup.
Then:
SQL> RECOVER DATABASE UNTIL TIME <timestamp> USING BACKUP CONTROLFILE;
Then you must open teh database with RESETLOGS:
SQL> ALTER DATABASE OPEN RESETLOGS;
The next thing you do is check if you met the point in time you wanted and then TAKE A NEW BACKUP OF THE ENTIRE DATABASE, because you do not have ya valid backup any more now. It is a new database you have, at least a new incarnation.
Let me know if this was helpfull or if I have completely misunderstood your question.
Good luck,
Lutz

Scn in redologs and controlfile

Similar Messages

Maybe you are looking for