Why archive log is full so fast?

Hi All,
I have installed 10g RAC on RHEL4 using MSA1000 as a shared storage. and using ASM for database files and archive log files (external reduandancy) with RAID5. I have allocated 100GB for archive log files. database also created successfully with archive log enabled. After that i import 3 schemas in the RAC db each of 2GB size. The import was successful and when i try to connect the schema using Sqlplus it will "archive error". archive log space was full. i checked in asmcmd also, the 100GB fully occupied. My doubt is..How come the 100GB space is filled so fast?
Can anybody help me?
Thanks,
Praveen.

Hi Don,
No error, just code from an older release! Right ?
Not found any reference of the TIME column from V$LOG_HISTORY into the 8i and 9i doc. Maybe from Oracle 7 ?
Connected to:
Oracle8i Enterprise Edition Release 8.1.7.4.1 - Production
With the Partitioning option
JServer Release 8.1.7.4.1 - Production
SQL> select substr(time,1,5) day,
2 to_char(sum(decode(substr(time,10,2),'00',1,0)),'99') "00",
3 to_char(sum(decode(substr(time,10,2),'01',1,0)),'99') "01",
4 to_char(sum(decode(substr(time,10,2),'02',1,0)),'99') "02",
5 to_char(sum(decode(substr(time,10,2),'03',1,0)),'99') "03",
6 to_char(sum(decode(substr(time,10,2),'04',1,0)),'99') "04",
7 to_char(sum(decode(substr(time,10,2),'05',1,0)),'99') "05",
8 to_char(sum(decode(substr(time,10,2),'06',1,0)),'99') "06",
9 to_char(sum(decode(substr(time,10,2),'07',1,0)),'99') "07",
10 to_char(sum(decode(substr(time,10,2),'08',1,0)),'99') "08",
11 to_char(sum(decode(substr(time,10,2),'09',1,0)),'99') "09",
12 to_char(sum(decode(substr(time,10,2),'10',1,0)),'99') "10",
13 to_char(sum(decode(substr(time,10,2),'11',1,0)),'99') "11",
14 to_char(sum(decode(substr(time,10,2),'12',1,0)),'99') "12",
15 to_char(sum(decode(substr(time,10,2),'13',1,0)),'99') "13",
16 to_char(sum(decode(substr(time,10,2),'14',1,0)),'99') "14",
17 to_char(sum(decode(substr(time,10,2),'15',1,0)),'99') "15",
18 to_char(sum(decode(substr(time,10,2),'16',1,0)),'99') "16",
19 to_char(sum(decode(substr(time,10,2),'17',1,0)),'99') "17",
20 to_char(sum(decode(substr(time,10,2),'18',1,0)),'99') "18",
21 to_char(sum(decode(substr(time,10,2),'19',1,0)),'99') "19",
22 to_char(sum(decode(substr(time,10,2),'20',1,0)),'99') "20",
23 to_char(sum(decode(substr(time,10,2),'21',1,0)),'99') "21",
24 to_char(sum(decode(substr(time,10,2),'22',1,0)),'99') "22",
25 to_char(sum(decode(substr(time,10,2),'23',1,0)),'99') "23"
26 from v$log_history
27 group by substr(time,1,5);
group by substr(time,1,5)
ERROR at line 27:
ORA-00904: invalid column name
SQL> desc v$log_history
Name                                      Null?    Type
RECID                                              NUMBER
STAMP                                              NUMBER
THREAD#                                            NUMBER
SEQUENCE#                                          NUMBER
FIRST_CHANGE#                                      NUMBER
FIRST_TIME                                         DATE
NEXT_CHANGE#                                       NUMBER
SQL>
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
SQL> select substr(time,1,5) day,
2 to_char(sum(decode(substr(time,10,2),'00',1,0)),'99') "00",
3 to_char(sum(decode(substr(time,10,2),'01',1,0)),'99') "01",
4 to_char(sum(decode(substr(time,10,2),'02',1,0)),'99') "02",
5 to_char(sum(decode(substr(time,10,2),'03',1,0)),'99') "03",
6 to_char(sum(decode(substr(time,10,2),'04',1,0)),'99') "04",
7 to_char(sum(decode(substr(time,10,2),'05',1,0)),'99') "05",
8 to_char(sum(decode(substr(time,10,2),'06',1,0)),'99') "06",
9 to_char(sum(decode(substr(time,10,2),'07',1,0)),'99') "07",
10 to_char(sum(decode(substr(time,10,2),'08',1,0)),'99') "08",
11 to_char(sum(decode(substr(time,10,2),'09',1,0)),'99') "09",
12 to_char(sum(decode(substr(time,10,2),'10',1,0)),'99') "10",
13 to_char(sum(decode(substr(time,10,2),'11',1,0)),'99') "11",
14 to_char(sum(decode(substr(time,10,2),'12',1,0)),'99') "12",
15 to_char(sum(decode(substr(time,10,2),'13',1,0)),'99') "13",
16 to_char(sum(decode(substr(time,10,2),'14',1,0)),'99') "14",
17 to_char(sum(decode(substr(time,10,2),'15',1,0)),'99') "15",
18 to_char(sum(decode(substr(time,10,2),'16',1,0)),'99') "16",
19 to_char(sum(decode(substr(time,10,2),'17',1,0)),'99') "17",
20 to_char(sum(decode(substr(time,10,2),'18',1,0)),'99') "18",
21 to_char(sum(decode(substr(time,10,2),'19',1,0)),'99') "19",
22 to_char(sum(decode(substr(time,10,2),'20',1,0)),'99') "20",
23 to_char(sum(decode(substr(time,10,2),'21',1,0)),'99') "21",
24 to_char(sum(decode(substr(time,10,2),'22',1,0)),'99') "22",
25 to_char(sum(decode(substr(time,10,2),'23',1,0)),'99') "23"
26 from v$log_history
27 group by substr(time,1,5);
group by substr(time,1,5)
ERROR at line 27:
ORA-00904: "TIME": invalid identifier
SQL> desc v$log_history
Name                                      Null?    Type
RECID                                              NUMBER
STAMP                                              NUMBER
THREAD#                                            NUMBER
SEQUENCE#                                          NUMBER
FIRST_CHANGE#                                      NUMBER
FIRST_TIME                                         DATE
NEXT_CHANGE#                                       NUMBER
SQL> Well, Gints has already check the doc.
To be fair, I would agree that could be a nightmare to maintain a bunch of scripts through different release, but at least see the evidence, on that case, on the age of the scritp if it was tested a day.
Nicolas.
Message was edited by:
N. Gasparotto

Similar Messages

Archive log directory full

Hello all,
I had a problem where my archive log dir filled up last night and corrupted a datafile.
I haave tried to do an incomplete recovery until just before the directory filled.
When running this recovery I get errors:
RMAN-03022: compiling command: IRESTORE
RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: restore
RMAN-03002: failure during compilation of command
RMAN-03013: command type: IRESTORE
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 19 found to restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
I have Identified these datafiles as tmp, and rollback segment datafiles which I have not been backingup, because I didn't see the need to.
can anybody give advice on how to solve this issue.
Thanks,
Lenny

I ended up attempting a restore of the corrupt corrupt, and it worked. The database is up and running properly. Since I have done a full backup before releasing access to the company.
Thanks,
Lenny

Archive Log vs Full Backup Concept

Hi,
I just need some clarification on how backups and archive logs work. Lets say starting at 1PM I have archive logs 1,2,3,4,5 and then I perform a full backup at 6PM.
Then I resume generating archive logs at 6PM to get logs 6,7,8,9,10. I then stop at 11PM.
If my understanding is correct, the archive logs should allow me to restore oracle to a point in time anywhere between 1PM and 11PM. But if I only have the full backup then I can only restore to a single point, which is 6PM. Is my understanding correct?
Do the archive logs only get applied to the datafiles when the backup occurs or only when a restore occurs? It doesn't seem like the archive logs get applied on the fly.
Thanks in advance.

thelok wrote:
Thanks for the great explanation! So I can do a point in time restore from any time since the datafiles have last been written (or from when I have the last set of backed up datafiles plus the archive logs). From what you are saying, I can force the datafiles to be written from the redo logs (by doing a checkpoint with "alter set archive log current" or "backup database plus archivelog"), and then I can delete all the archive logs that have a SCN less than the checkpoint SCN on the datafiles. Is this true? This would be for the purposes of preserving disk space.Hi,
See this example. I hope this explain your doubt.
# My current date is 06-11-2011 17:15
# I not have backup of this database
# My retention policy is to have 1 backup
# I start listing archive logs.
RMAN> list archivelog all;
using target database control file instead of recovery catalog
List of Archived Log Copies
Key     Thrd Seq     S Low Time            Name
29      1    8       A 29-10-2011 12:01:58 +HR/dbhr/archivelog/2011_10_31/thread_1_seq_8.399.766018837
30      1    9       A 31-10-2011 23:00:30 +HR/dbhr/archivelog/2011_11_03/thread_1_seq_9.409.766278025
31      1    10      A 03-11-2011 23:00:23 +HR/dbhr/archivelog/2011_11_04/thread_1_seq_10.391.766366105
32      1    11      A 04-11-2011 23:28:23 +HR/dbhr/archivelog/2011_11_06/thread_1_seq_11.411.766516065
33      1    12      A 05-11-2011 23:28:49 +HR/dbhr/archivelog/2011_11_06/thread_1_seq_12.413.766516349
## See I have archive logs from time "29-10-2011 12:01:58" until "05-11-2011 23:28:49" but I dont have any backup of database.
# So I perfom backup of database including archive logs.
RMAN> backup database plus archivelog delete input;
Starting backup at 06-11-2011 17:15:21
## Note above RMAN forcing archive current log, this archivelog generated will be usable only for previous backup.
## Is not my case... I don't have backup of database.
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=159 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=8 recid=29 stamp=766018840
input archive log thread=1 sequence=9 recid=30 stamp=766278027
input archive log thread=1 sequence=10 recid=31 stamp=766366111
input archive log thread=1 sequence=11 recid=32 stamp=766516067
input archive log thread=1 sequence=12 recid=33 stamp=766516350
input archive log thread=1 sequence=13 recid=34 stamp=766516521
channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:15:23
channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:15:38
piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525 tag=TAG20111106T171521 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:16
channel ORA_DISK_1: deleting archive log(s)
archive log filename=+HR/dbhr/archivelog/2011_10_31/thread_1_seq_8.399.766018837 recid=29 stamp=766018840
archive log filename=+HR/dbhr/archivelog/2011_11_03/thread_1_seq_9.409.766278025 recid=30 stamp=766278027
archive log filename=+HR/dbhr/archivelog/2011_11_04/thread_1_seq_10.391.766366105 recid=31 stamp=766366111
archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_11.411.766516065 recid=32 stamp=766516067
archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_12.413.766516349 recid=33 stamp=766516350
archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_13.414.766516521 recid=34 stamp=766516521
Finished backup at 06-11-2011 17:15:38
## RMAN finish backup of Archivelog and Start Backup of Database
## My backup start at "06-11-2011 17:15:38"
Starting backup at 06-11-2011 17:15:38
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=+HR/dbhr/datafile/system.386.765556627
input datafile fno=00003 name=+HR/dbhr/datafile/sysaux.396.765556627
input datafile fno=00002 name=+HR/dbhr/datafile/undotbs1.393.765556627
input datafile fno=00004 name=+HR/dbhr/datafile/users.397.765557979
input datafile fno=00005 name=+BFILES/dbhr/datafile/bfiles.257.765542997
channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:15:39
channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:16:03
piece handle=+FRA/dbhr/backupset/2011_11_06/nnndf0_tag20111106t171539_0.269.766516539 tag=TAG20111106T171539 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:24
Finished backup at 06-11-2011 17:16:03
## And finish at "06-11-2011 17:16:03", so I can recovery my database from this time.
## I will need archivelogs (transactions) which was generated during backup of database.
## Note during backup some blocks are copied others not. The SCN is inconsistent state.
## To make it consistent I need apply archivelog which have all transactions recorded.
## Starting another backup of archived log generated during backup.
Starting backup at 06-11-2011 17:16:04
## So automatically RMAN force another "checkpoint" after backup finished,
## forcing archive current log, because this archivelog have all transactions to bring database in a consistent state.
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=14 recid=35 stamp=766516564
channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:16:05
channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:16:06
piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171604_0.272.766516565 tag=TAG20111106T171604 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
channel ORA_DISK_1: deleting archive log(s)
archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_14.414.766516565 recid=35 stamp=766516564
Finished backup at 06-11-2011 17:16:06
## Note: I can recover my database from time "06-11-2011 17:16:03" (finished backup full)
## until "06-11-2011 17:16:04" (last archivelog generated) that is my recover window in this scenary.
## Listing Backup I have:
## Archive Logs in backupset before backup full start - *BP Key: 40*
## Backup Full database in backupset - *BP Key: 41*
## Archive Logs in backupset after backup full stop - *BP Key: 42*
RMAN> list backup;
List of Backup Sets
===================
BS Key Size       Device Type Elapsed Time Completion Time
40      196.73M    DISK        00:00:15     06-11-2011 17:15:37
        *BP Key: 40*   Status: AVAILABLE Compressed: NO Tag: TAG20111106T171521
        Piece Name: +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525
List of Archived Logs in backup set 40
Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
1    8       766216     29-10-2011 12:01:58 855033     31-10-2011 23:00:30
1    9       855033     31-10-2011 23:00:30 896458     03-11-2011 23:00:23
1    10      896458     03-11-2011 23:00:23 937172     04-11-2011 23:28:23
1    11      937172     04-11-2011 23:28:23 976938     05-11-2011 23:28:49
1    12      976938     05-11-2011 23:28:49 1023057    06-11-2011 17:12:28
1    13      1023057    06-11-2011 17:12:28 1023411    06-11-2011 17:15:21
BS Key Type LV Size       Device Type Elapsed Time Completion Time
41      Full    565.66M    DISK        00:00:18     06-11-2011 17:15:57
        *BP Key: 41*   Status: AVAILABLE Compressed: NO Tag: TAG20111106T171539
        Piece Name: +FRA/dbhr/backupset/2011_11_06/nnndf0_tag20111106t171539_0.269.766516539
List of Datafiles in backup set 41
File LV Type Ckp SCN    Ckp Time            Name
1       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/system.386.765556627
2       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/undotbs1.393.765556627
3       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/sysaux.396.765556627
4       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/users.397.765557979
5       Full 1023422    06-11-2011 17:15:39 +BFILES/dbhr/datafile/bfiles.257.765542997
BS Key Size       Device Type Elapsed Time Completion Time
42      3.00K      DISK        00:00:02     06-11-2011 17:16:06
        *BP Key: 42*   Status: AVAILABLE Compressed: NO Tag: TAG20111106T171604
        Piece Name: +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171604_0.272.766516565
List of Archived Logs in backup set 42
Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
1    14      1023411    06-11-2011 17:15:21 1023433    06-11-2011 17:16:04
## Here make sense what I trying explain
## As I don't have backup of database before of my Last backup, all archivelogs generated before of my backup full is useless.
## Deleting what are obsolete in my env, RMAN choose backupset 40 (i.e all archived logs generated before my backup full)
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
*Backup Set           40*     06-11-2011 17:15:37
Backup Piece       40     06-11-2011 17:15:37 +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525
Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525 recid=40 stamp=766516523
Deleted 1 objectsIn the above example, I could before starting the backup run "delete archivelog all" because they would not be needed, but to show the example I follow this unnecessary way. (backup archivelog and delete after)
Regards,
Levi Pereira
Edited by: Levi Pereira on Nov 7, 2011 1:02 AM

Why archived log of an instance got created in another instance?

Hi All,
It is a 2 nodes RAC. I found that there are archived log of instance#1 created in instance#2. It is strange. Do you have any idea?
instance#1
[oracle@server1 dbs]$ ls -l /appl/erp/arch/orcl/
total 1501340
-rw-r----- 1 oracle erpdba 49469952 Jan 17 09:33 1_781_715695404.arc
-rw-r----- 1 oracle erpdba 50551808 Jan 17 09:34 1_782_715695404.arc
-rw-r----- 1 oracle erpdba     1024 Jan 17 09:39 1_785_715695404.arc
-rw-r----- 1 oracle erpdba 49051648 Jan 17 10:00 1_786_715695404.arc
-rw-r----- 1 oracle erpdba 83065344 Jan 17 10:00 2_615_715695404.arc
-rw-r----- 1 oracle erpdba 51148800 Jan 17 10:01 1_787_715695404.arc
-rw-r----- 1 oracle erpdba     1024 Jan 17 10:01 2_616_715695404.arc
-rw-r----- 1 oracle erpdba 48924672 Jan 17 10:01 1_788_715695404.arc
-rw-r----- 1 oracle erpdba 48935424 Jan 17 10:01 1_789_715695404.arc
-rw-r----- 1 oracle erpdba 23964160 Jan 17 10:06 1_790_715695404.arc
-rw-r----- 1 oracle erpdba 51796480 Jan 17 10:07 1_791_715695404.arc
-rw-r----- 1 oracle erpdba 52080640 Jan 17 10:08 1_792_715695404.arc
-rw-r----- 1 oracle erpdba 51973120 Jan 17 10:09 1_793_715695404.arcinstance#2
[oracle@server2 dbs]$ ls -l /appl/erp/arch/orcl/
total 1501340
-rw-rw---- 1 oracle erpdba 101348352 Jan 16 15:46 2_605_715695404.arc
-rw-rw---- 1 oracle erpdba 101351424 Jan 16 16:05 2_606_715695404.arc
-rw-rw---- 1 oracle erpdba 101347840 Jan 16 16:06 2_607_715695404.arc
-rw-r----- 1 oracle erpdba 101350400 Jan 16 16:55 2_596_715695404.arc
-rw-rw---- 1 oracle erpdba   3522560 Jan 16 18:13 2_609_715695404.arc
-rw-rw---- 1 oracle erpdba 47719424 Jan 17 09:33 2_610_715695404.arc
-rw-rw---- 1 oracle erpdba      7168 Jan 17 09:33 2_611_715695404.arc
-rw-rw---- 1 oracle erpdba   5175296 Jan 17 09:34 1_783_715695404.arc
-rw-rw---- 1 oracle erpdba   6170112 Jan 17 09:34 2_612_715695404.arc
-rw-rw---- 1 oracle erpdba 50551808 Jan 17 09:34 1_782_715695404.arc
-rw-rw---- 1 oracle erpdba      1024 Jan 17 09:34 1_784_715695404.arc
-rw-rw---- 1 oracle erpdba 102879232 Jan 17 09:36 2_613_715695404.arc
-rw-rw---- 1 oracle erpdba 103360512 Jan 17 09:38 2_614_715695404.arcRegards,
nww

Hi Salman,
I don't know. I just modified your SQL a bit as below.
select inst_id, name, thread#, sequence#, first_time from gv$archived_log
where first_time like '16-JAN-13%'
and sequence# between 605 and 793
order by FIRST_TIME ;I tried again with the follow SQL. Do you know what's going on? The FIRST_TIME changed?
select inst_id, name, thread#, sequence#, first_time from gv$archived_log
where first_time >= trunc(sysdate-1)
and sequence# between 605 and 793
order by FIRST_TIME ;
   INST_ID NAME                                          THREAD# SEQUENCE# FIRST_TIM
         2                                                     1        770 16-JAN-13
         2 ORCLSB                                              1        770 16-JAN-13
         1 ORCLSB                                              1        770 16-JAN-13
         1                                                     1        770 16-JAN-13
         1                                                     1        771 16-JAN-13
         2                                                     1        771 16-JAN-13
         1 ORCLSB                                              1        771 16-JAN-13
         2 ORCLSB                                              1        771 16-JAN-13
         2 ORCLSB                                              1        772 16-JAN-13
         1                                                     1        772 16-JAN-13
         2                                                     1        772 16-JAN-13
         1 ORCLSB                                              1        772 16-JAN-13
         1                                                     2        605 16-JAN-13
         2                                                     2        605 16-JAN-13
         2 ORCLSB                                              2        605 16-JAN-13
         1 ORCLSB                                              2        605 16-JAN-13
         1                                                     2        606 16-JAN-13
         2                                                     2        606 16-JAN-13
         1 ORCLSB                                              2        606 16-JAN-13
         2 ORCLSB                                              2        606 16-JAN-13
         2 ORCLSB                                              2        607 16-JAN-13
         2                                                     2        607 16-JAN-13
         1                                                     2        607 16-JAN-13
         1 ORCLSB                                              2        607 16-JAN-13
         1 ORCLSB                                              2        608 16-JAN-13
         2 ORCLSB                                              2        608 16-JAN-13
         1                                                     2        608 16-JAN-13
         2                                                     2        608 16-JAN-13
         2 ORCLSB                                              1        773 16-JAN-13
         2                                                     1        773 16-JAN-13
         1 ORCLSB                                              1        773 16-JAN-13
         1                                                     1        773 16-JAN-13
         2                                                     1        774 16-JAN-13
         1 ORCLSB                                              1        774 16-JAN-13
         2 ORCLSB                                              1        774 16-JAN-13
         1                                                     1        774 16-JAN-13
         2 ORCLSB                                              2        609 16-JAN-13
         1 ORCLSB                                              2        609 16-JAN-13
         1                                                     2        609 16-JAN-13
         2                                                     2        609 16-JAN-13
         1 ORCLSB                                              1        775 16-JAN-13
         1                                                     1        775 16-JAN-13
         2                                                     1        775 16-JAN-13
         2 ORCLSB                                              1        775 16-JAN-13
         2                                                     2        610 16-JAN-13
         1 ORCLSB                                              2        610 16-JAN-13
         1                                                     2        610 16-JAN-13
         2 ORCLSB                                              2        610 16-JAN-13
         2 ORCLSB                                              1        776 16-JAN-13
         2                                                     1        776 16-JAN-13
         1 ORCLSB                                              1        776 16-JAN-13
         1                                                     1        776 16-JAN-13
         2 ORCLSB                                              1        777 17-JAN-13
         1                                                     1        777 17-JAN-13
         1 ORCLSB                                              1        777 17-JAN-13
         2                                                     1        777 17-JAN-13
         1                                                     1        778 17-JAN-13
         1 ORCLSB                                              1        778 17-JAN-13
         2                                                     1        778 17-JAN-13
         2 ORCLSB                                              1        778 17-JAN-13
         2                                                     2        611 17-JAN-13
         1 ORCLSB                                              2        611 17-JAN-13
         2 ORCLSB                                              2        611 17-JAN-13
         1                                                     2        611 17-JAN-13
         2 ORCLSB                                              1        779 17-JAN-13
         1                                                     1        779 17-JAN-13
         1 ORCLSB                                              1        779 17-JAN-13
         2                                                     1        779 17-JAN-13
         2 ORCLSB                                              1        780 17-JAN-13
         2                                                     1        780 17-JAN-13
         1 ORCLSB                                              1        780 17-JAN-13
         1                                                     1        780 17-JAN-13
         1                                                     2        612 17-JAN-13
         1 ORCLSB                                              2        612 17-JAN-13
         2                                                     2        612 17-JAN-13
         2 ORCLSB                                              2        612 17-JAN-13
         1 ORCLSB                                              1        781 17-JAN-13
         1                                                     1        781 17-JAN-13
         2                                                     1        781 17-JAN-13
         2 ORCLSB                                              1        781 17-JAN-13
         1                                                     1        782 17-JAN-13
         2                                                     1        782 17-JAN-13
         2                                                     1        783 17-JAN-13
         1                                                     1        783 17-JAN-13
         2 ORCLSB                                              1        783 17-JAN-13
         1 ORCLSB                                              1        783 17-JAN-13
         1 ORCLSB                                              1        784 17-JAN-13
         1                                                     1        784 17-JAN-13
         2                                                     1        784 17-JAN-13
         2 ORCLSB                                              1        784 17-JAN-13
         2                                                     2        613 17-JAN-13
         1                                                     2        613 17-JAN-13
         1 ORCLSB                                              2        613 17-JAN-13
         2 ORCLSB                                              2        613 17-JAN-13
         2                                                     2        614 17-JAN-13
         1                                                     2        614 17-JAN-13
         1 ORCLSB                                              2        614 17-JAN-13
         2 ORCLSB                                              2        614 17-JAN-13
         2 ORCLSB                                              2        615 17-JAN-13
         1                                                     2        615 17-JAN-13
         1 ORCLSB                                              2        615 17-JAN-13
         2                                                     2        615 17-JAN-13
         1 ORCLSB                                              1        785 17-JAN-13
         1                                                     1        785 17-JAN-13
         2                                                     1        785 17-JAN-13
         2 ORCLSB                                              1        785 17-JAN-13
         2 ORCLSB                                              1        786 17-JAN-13
         2                                                     1        786 17-JAN-13
         1 ORCLSB                                              1        786 17-JAN-13
         1                                                     1        786 17-JAN-13
         2                                                     1        787 17-JAN-13
         1 ORCLSB                                              1        787 17-JAN-13
         2 ORCLSB                                              1        787 17-JAN-13
         1                                                     1        787 17-JAN-13
         1 ORCLSB                                              2        616 17-JAN-13
         2 ORCLSB                                              2        616 17-JAN-13
         1                                                     2        616 17-JAN-13
         2                                                     2        616 17-JAN-13
         2                                                     1        788 17-JAN-13
         1 ORCLSB                                              1        788 17-JAN-13
         1                                                     1        788 17-JAN-13
         2 ORCLSB                                              1        788 17-JAN-13
         2 ORCLSB                                              1        789 17-JAN-13
         1                                                     1        789 17-JAN-13
         1 ORCLSB                                              1        789 17-JAN-13
         2                                                     1        789 17-JAN-13
         1 ORCLSB                                              1        790 17-JAN-13
         1                                                     1        790 17-JAN-13
         2                                                     1        790 17-JAN-13
         2 ORCLSB                                              1        790 17-JAN-13
         1                                                     1        791 17-JAN-13
         1 ORCLSB                                              1        791 17-JAN-13
         2 ORCLSB                                              1        791 17-JAN-13
         2                                                     1        791 17-JAN-13
         1                                                     1        792 17-JAN-13
         1 ORCLSB                                              1        792 17-JAN-13
         2 ORCLSB                                              1        792 17-JAN-13
         2                                                     1        792 17-JAN-13
         2 ORCLSB                                              1        793 17-JAN-13
         2                                                     1        793 17-JAN-13
         1 ORCLSB                                              1        793 17-JAN-13
         1                                                     1        793 17-JAN-13
         1 ORCLSB                                              2        617 17-JAN-13
         1                                                     2        617 17-JAN-13
         2                                                     2        617 17-JAN-13
         2 ORCLSB                                              2        617 17-JAN-13
         2 ORCLSB                                              2        618 17-JAN-13
         1 /appl/erp/arch/ORCL/2_618_715695404.arc             2        618 17-JAN-13
         1 ORCLSB                                              2        618 17-JAN-13
         2 /appl/erp/arch/ORCL/2_618_715695404.arc             2        618 17-JAN-13
         2 /appl/erp/arch/ORCL/2_619_715695404.arc             2        619 17-JAN-13
         1 /appl/erp/arch/ORCL/2_619_715695404.arc             2        619 17-JAN-13
         2 /appl/erp/arch/ORCL/2_620_715695404.arc             2        620 17-JAN-13
         1 /appl/erp/arch/ORCL/2_620_715695404.arc             2        620 17-JAN-13
         2 /appl/erp/arch/ORCL/2_623_715695404.arc             2        623 17-JAN-13
         1 /appl/erp/arch/ORCL/2_622_715695404.arc             2        622 17-JAN-13
         1 /appl/erp/arch/ORCL/2_623_715695404.arc             2        623 17-JAN-13
         1 /appl/erp/arch/ORCL/2_621_715695404.arc             2        621 17-JAN-13
         2 /appl/erp/arch/ORCL/2_621_715695404.arc             2        621 17-JAN-13
         2 /appl/erp/arch/ORCL/2_622_715695404.arc             2        622 17-JAN-13
         2 /appl/erp/arch/ORCL/2_624_715695404.arc             2        624 17-JAN-13
         1 /appl/erp/arch/ORCL/2_624_715695404.arc             2        624 17-JAN-13
162 rows selected.BTW, what are those records having blank name?
Regards,
nww

Archive Log file size

I am using Oracle database 9.2.0.1.0, My OS is Linux AS4 Update version.
My database is in archive log mode, the archive file size generated on disk is 100 MB. I want to monitor the reason that why the size of redo generated is too big.
Kindly suggest.
Regards

Archived log file size will always be the same size as redo log or less than the redo log size (but never bigger than redo log size)
ARCHIVE_LAG_TARGET is the reason (apart from manual archiving ALTER SYSTEM ARCHIVE LOG CURRENT/ALL) why you see archived logs with lesser size than redo log
why archive log file size constanly change?

Full Backups, Level 0 Backups, and Archived Logs

We have an active Oracle server and a standby Oracle server. We keep the standby database up to date with a cron script. The script tells the active database to do 'alter system switch logfile;'. We then rsync the archived logs to our standby server and have rman apply them.
This works everyday except Monday (of course!) and it only recently started failing on Mondays. The only change was that our Sunday backups used to be 'Full' backups but are now 'level 0' backups. Ever since that change, the first attempt to apply the archived logs to the standby server after the level 0 is taken on the active server gives us something like this:
ORA-00308: cannot open archived log
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60519_%u_.arc'
ORA-27037: unable to obtain file status
Of course, the file is not there and doesn't exist on the active server either. And of course, the nightly level1 backups fo not give us problems applying archived logs to the standby database the rest of the week.
The only way I know to recover from this is to apply the level 0 backup or take a new level 0 and apply it. After that, all subsequent archive logs just work. Any idea why changing from Full to Level 0 would break this? The Oracle docs insist that a Level 0 is identical to a Full except that level 1s can reference them as parents. This simply cannot be true based on what I'm seeing! I really want to keep the level 0 backups in play if possible. Level 1 cumulatives wont be useful without them.

Here are the RMAN settings:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/102/dbs/snapcf_ORCL.f'; # default
I'm not sure how changing ARCHIVELOG BACKUP COPIES would help. Can you give me a little more information about how that setting comes into play in this situation?
I actually don't want an archive deletion policy here. We have this done in script three days after the needed archive logs have been applied. Is it possible that the we're deleting archivelogs too soon? Would we ever need to reach back in time to previously applied archive logs to apply new ones?
The %u does resolve, but this message isn't showing it. Here is that same log entry plus a few previous entries that show it does resolve.
ORA-00279: change 1284618956 generated at 04/13/2012 15:30:05 needed for thread
1
ORA-00289: suggestion :
/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60518_%u_.arc
ORA-00280: change 1284618956 for thread 1 is in sequence #60518
ORA-00278: log file
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_13/o1_mf_1_60517_7rjzox
0l_.arc' no longer needed for this recovery
ORA-00279: change 1284618958 generated at 04/13/2012 15:30:05 needed for thread
1
ORA-00289: suggestion :
/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60519_%u_.arc
ORA-00280: change 1284618958 for thread 1 is in sequence #60519
ORA-00278: log file
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_13/o1_mf_1_60518_7rjzox
0x_.arc' no longer needed for this recovery
ORA-00308: cannot open archived log
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60519_%u_.ar
c'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

Recovery using Full BCV backup & archive logs

Hello DBA's ,
I have Last Sunday's Full BCV (Buisness Copy Volume) backup (i.e. ..... the tablespaces were taken into Backup mode then Sync the BCV, then split the BCV , take the backup of BCV and take the tabespaces in normal mode in short what we call as HOT BACKUP ........ ) & also I am taking only archive log & control file backup Daily.
Now I want to Run my database on Different Server using the above FULL BCV & daily backed up Archive logs & Control file.
Kindly update me- Can I go for following recovery steps for above scenario.
1) Install ORACLE software on new server.
2) Restore the last Sunday's FULL BCV (Hot backup)
3) Restore the archive log from last Sunday's Full BCV backup.
4) Restore the latest backed up control file.
5) Mount the database.
6) Recover the database using backed up control file & archive logs.
7) Open the database with RESETLOGS option.
Please Guide me whether I can Fully Recover/Start database on this new server using above steps. ---OR---- " Are there any more files except data files that need to be backed up daily after Full BCV ? " ---OR ---- More suggestions are Welcome.
I want to test this scenario bcz.
a) I can't afford daily BCV due to lack of storage with current retention given by buisness.
b) I can't afford long time taken by RMAN for backup & recovery, as it disturbs my other backup shedules, also RTO should be very low as per my buisness requirement.
c) Currently we are not thinking for any another Backup options.
OS platform -- SOLARIS 10
Database version -- ORACLE 9i/10g
Atul.

Hello everybody ....
Actually I am doing the above scenario practically and I am facing the problem that when I am applying my archive logs using backup controlfile until cancel, the recovery completes upto the available Archive logs/sequence. But it throws the following error along with it ......
ORA-00279: change 7001791222 generated at 01/13/2008 07:23:42 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9623_601570270.dbf
ORA-00280: change 7001791222 for thread 1 is in sequence #9623
ORA-00278: log file '/oracle/EPR/oraarch/1_9622_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 7001816252 generated at 01/13/2008 12:53:05 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9624_601570270.dbf
ORA-00280: change 7001816252 for thread 1 is in sequence #9624
ORA-00278: log file '/oracle/EPR/oraarch/1_9623_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/oracle/EPR/oraarch/1_9624_601570270.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
SQL> SQL> SQL> SQL> SQL> SQL> SQL>
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
So, I opened my database using Last (Sunday's) full hot backup only and it opens successfully without applying any archives.
Now, my question is... why my database doesn't open with OPEN RESETLOGS option when I am recovering it using command " RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE; "
I want to recover my database upto Saturday then What should I do ?
Please help me out !
Atul.

Incomplete Recovery Fails using Full hot backup & Archive logs !!

Hello DBA's !!
I am doing on Recovery scenario where I have taken One full hot backup of my Portal Database (EPR) and Restored it on New Test Server. Also I restored Archive logs from last full hot backup for next 6 days. Also I restored the latest Control file (binary) to their original locations. Now, I started the recovery scenario as follows....
1) Installed Oracle 10.2.0.2 compatible with restored version of oracle.
2) Configured tnsnames.ora, listener.ora, sqlnet.ora with hostname of Test server.
3) Restored all Hot backup files from Tape to Test Server.
4) Restored all archive logs from tape to Test server.
5) Restored Latest Binary Control file from Tape to Test Server.
6) Now, Started recovery using following command from SQL prompt.
SQL> recover database until cancel using backup controlfile;
7) Open database after Recovery Completion using RESETLOGS option.
Now in Above scenario I completed steps upto 5) successfully. But when I execute the step 6) the recovery completes with Warning : Recovery completed but OPEN RESETLOGS may throw error " system file needs more recovery to be consistent " . Please find the following snapshot ....
ORA-00279: change 7001816252 generated at 01/13/2008 12:53:05 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9624_601570270.dbf
ORA-00280: change 7001816252 for thread 1 is in sequence #9624
ORA-00278: log file '/oracle/EPR/oraarch/1_9623_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/oracle/EPR/oraarch/1_9624_601570270.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
SQL> SQL> SQL> SQL> SQL> SQL> SQL>
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
Let me know What should be the reason behind recovery failure !
Note : I tried to Open the database using Last Full Hot Backup only & not applying any archives. Then Database Opens successfully. It means my Database Installation & Configuration is OK !
Please Let me know why my Incomplete Recovery using Archive logs Goes Fail ?
Atul Patil.

oh you made up a new thread so here again:
there is nothing wrong.
You restored your backup, archives etc.
you started your recovery and oracle applyed all archives but the archive
'/oracle/EPR/oraarch/1_9624_601570270.dbf'
does not exist because it represents your current online redo log file and that is not present.
the recovery process cancels by itself.
the solution is:
restart your recovery process with:
recover database until cancel using backup controlfile
and when oracle suggests you '/oracle/EPR/oraarch/1_9624_601570270.dbf'
type cancel!
now you should be able to open your database with open resetlogs.

Staging server archive log full

Hi ,
i have encountered my staging server having archive log full which i do not understand.
i hope anyone can help clarify my doubts
Production server : oracle 10G , RedHat
Staging Server : oracle 10G , runnings on windows
source server : DB2
the staging server is simply a link between the Production server & db2
i am running my procedures on the production server which is getting db2's data via the staging server thru dblink
i have encountered the error : ORA-00257 : archiver error : connect internal only, until freed when i ran some recovery which involved some 20M to 40M records being loaded at the same time
what i do not understand is why would the Oracle running on windows have its archive log full when it's just a link betw the production and db2
pls advise
tks & rgds

Just go to the archivl log destination and delete some/all of the archive logs then I think the problem will be resolved.
OR
connect to RMAN then run
run {
allocate channel ch1 device type disk;
backup format '/u04/rman_backup/RMAN_ARCH_<%s:%t:%p>.bkp' archivelog all delete input;
It will take the backup of your all archivelog and then delete the archive logs from your current archive log directory.
Regards
Asif Kabir

Why the flashback log'size smaller than the archived log ?

hi, all . why the flashback log'size smaller than the archived log ?

Lonion wrote:
hi, all . why the flashback log'size smaller than the archived log ?Both are different.
Flash logs size depends on parameter DB_FLASHBACK_RETENTION_TARGET , how much you want to keep.
Archive log files is dumped file of Online redo log files, It can be either size of Online redo log file size or less depending on online redo size when switch occurred.
Some more information:-
Flashback log files can be created only under the Flash Recovery Area (that must be configured before enabling the Flashback Database functionality). RVWR creates flashback log files into a directory named “FLASHBACK” under FRA. The size of every generated flashback log file is again under Oracle’s control. According to current Oracle environment – during normal database activity flashback log files have size of 8200192 bytes. It is very close value to the current redo log buffer size. The size of a generated flashback log file can differs during shutdown and startup database activities. Flashback log file sizes can differ during high intensive write activity as well.
Source:- http://dba-blog.blogspot.in/2006/05/flashback-database-feature.html
Edited by: CKPT on Jun 14, 2012 7:34 PM

When creating a tablespace why should we enable LOGGING when a database is already on ARCHIVE LOG mode

Question :
When creating a tablespace why should we enable LOGGING when a database is already on ARCHIVE LOG mode ?
Example:
Create Tablespace
CREATE SMALLFILE TABLESPACE "TEST_DATA"
LOGGING
DATAFILE '+DG_TEST_DATA_01(DATAFILE)' SIZE 10G
AUTOEXTEND ON NEXT 500K MAXSIZE 31000M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
LOGGING: Generate redo logs for creation of tables, indexes and partitions, and for subsequent inserts. Recoverable
Are they not logged and not recoverable if we do not enable LOGGING? What is that ARCHIVELOG mode does?

What is that ARCHIVELOG Mode Does?
Whenever your database is in archive log mode , Oracle will backup the redo log files in the form of Archives so that we can recover the database to the consistent state in case of any failure.
Archive logging is essential for production databases where the loss of a transaction might be fatal.
Why Logging?
Logging is safest method to ensure that all the changes made at the tablespace will be captured and available for recovery in the redo logs.
It is just the level at which we defines:
Force Logging at DB level
Logging at Tablespace Level
Logging at schema Level
Before the existence of FORCE LOGGING, Oracle provided logging and nologging options. These two options have higher precedence at the schema object level than the tablespace level; therefore, it was possible to override the logging settings at the tablespace level with nologging setting at schema object level.

Archive The Log When Full Disabled

Currently I'm having problem in setting up auto archive log for "Applications and Services Logs > Microsoft > Windows > Application Server - Applications > Debug", because the option is disabled (I've disabled the log to setup the properties).
Please take a look screenshot below:
How to choose "Archive the log when full, do not overwrite events"? Thanks in advance.

Hi ,
"How to choose "Archive the log when full, do not overwrite events"?"
Generally , you need to enable logging then you can choose the action after the log size is reached .
If this machine is domain joined , you can edit the domain policy on DC :
computer configuration \windows settings \security settings \event log
The Retention method for event log policy settings determine the wrapping method for the application, security, and system logs .
Best Regards
Elton JI
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
I've tried to enable the log and make the maximum size reached, but I still can't choose automatically archive log:
and also take a look a screenshot below, it is a different type of event (Operational) and it shows us that I can choose Archive the log when full without activating it and make it reach its maximum log size:
How to solve this issue? Thanks in advance.

Why size of archive log file increasing in merge clause

my database is running in archive log mode.
someone is running oracle merge statement. still it is running.
He will issue commit after the operation.
in that period redolog file increasing now.
my question is why size of archive log file increasing with redolog file.
i know that after commit archive log file should generate.(may be it is wrong).
please suggest........
Edited by: 855516 on Mar 13, 2012 11:18 AM

855516 wrote:
my database is running in archive log mode.
someone is running oracle merge statement. still it is running.
He will issue commit after the operation.
in that period redolog file increasing now.
my question is why size of archive log file increasing with redolog file.
i know that after commit archive log file should generate.(may be it is wrong). No this is not correct that after commit archive log will generate....You know merge statement causes the insert (if data not present already) or update if database is present.. Obviously these operation will generate lots of redo if the amount of data been processed is high.
If you feel that this operation is causing excessive of redo then root cause analysis should be done...
For that use Logminer (excellent tool to provide segment level breakdown of redo size). V$logmnr_contens has columns redo block and redo byte address associated with the current redo
change
There are some gudlines in order to reduce redos( which may vary in any environment)
1) check if there are unwanted indexes being used in tables which are refereed in merge. If yes then remove those could bring down the redo
2) Use global temporary tables to reduce redo (if there is a need to keep data only temporarily in a session)
3) Use nologging if possible (but see its implications)
Hope this helps

When occurs crash recovery,why use active online redo log not archived log?

If current redo log had archived, but it's still 'ACTIVE'. As we all know, archived log is just an archived copy of the current redo log which is still 'ACTIVE', they have the same data. But why use active online redo log not archived log for crash recovery?(I think, if crash recovery can use archived log, then whether the online redo log is 'ACTIVE' or not, it can be overwritten)
Quote:
Re: v$log : How redo log file can have a status ACTIVE and be already archived?
Hemant K Chitale
If your instance crashes, Oracle attempts Instance Recovery -- reading from the Online Redo Logs. It doesn't need ArchiveLogs for Instance Recovery.
TanelPoder
Whether the log is already archived or not doesn't matter here, when the instance crashes, Oracle needs some blocks from that redolog. Archivelog is just an archived copy of the redolog, so you could use either the online or achive log for the recovery, it's the same data in there (Oracle reads the log/archivelog file header when it tries to use it for recovery and validates whether it contains the changes (RBA range) in it what it needs).

Aman.... wrote:
John,
Are you sure that the instance recovery (not the media recovery) would be using the archived redo logs? Since the only thing that would be lost is the isntance, there wouldn't be any archived redo log generated from the Current redo log and the previous archived redo logs, would be already checkpointed to the data file, IMHO archived redo logs won't participate in the instance recovery process. Yep, shall watch the video but tomorrow .
Regards
Aman....
That's what I said. Or meant to say. If Oracle used archivelogs for instance recovery, it would not be possible to recover in noarchive log mode. So recovery relies exclusively on the online log.
Sorry I wasted your time, I'll try to be less ambiguous in future

How to Recover database from old backup and full archive log file

Hi Oracle expert!
I met problem when restore my oracle database.
In my case:
- My database version: 10.2.0.2
- I have a database full backup (01-Nov)
- I have all Archived log file from (01-Nov -> 05-Nov)
- My database drop in 05-Nov with disk error (no datafile, no redo..).
- I have no any RMAN backup from (01-Nov -> 05-Nov)
How can i restore my database to 05-Nov?
Thanks

user10280724 wrote:
Hi Chinar.
When i used RMAN flow as your step, but i met the problem!
- After recover database i select sequence#, applied from v$archived_log;
--> it apply newest archived log that i had.
- but when I select Data from table created between 01-Nov to 05-Nov, it not found!
Not the same way the step:
SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL?
It apply newest the same archived log i had table created between 01-Nov to 05-Nov.
How can i do with RMAN to recover my table?That is not possible,if your all available archive logs applied using rman or through sqlplus(recover database using backup controlfile until cancel) and one of these logs contain your table then there are not any problems.So there are not any difference between recovery using rman and user managed(using sqlplus),but there main matter is applying all archive logs.So first check through rman list copy of archivelog all or list backup of archivelog all and identify there in rman repository is any information or not about these logs.

Why archive log is full so fast?

Similar Messages

Maybe you are looking for