Delete logs archive > 1 day

Hi all

RHEL5

I posted a thread here on how to remove the log archiving liked only 1 day for both PRIMARY and standby database.

But I don't find it anymore

Is it possible to search all the contents of my son using Keywork "delete archive logs?

Thank you all,

Hello;

You old thread:

Remove the archivelogs and old backups

Best regards

mseberg

Tags: Database

Similar Questions

Delete log archiving

Hi friends,

I use oracle 10.2.0.1 on windows xp.

11/05/2009 I give:
RMAN > backup database;

Completed successfully.

On 02/08/2010 I give:

RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
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 'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFORCL.ORA'; # default

RMAN> run
2> {
3> backup database;
4> BACKUP ARCHIVELOG ALL DELETE INPUT;
5> }

Finished backup at 08-FEB-10

On 02/10/2010 I give: (with the same parameters of RMAN from 02/08/2010)

run
{
ARCHIVELOG backup all;
overlap archivelog all;
remove expired archivelog all;
}

...
...
In the end, there were:

output channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 133 devtype = DISK
specification does not match any newspaper archive in the recovery catalog

I give you today (26/02/2010):

RMAN> show all;

RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
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 'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFORCL.ORA'; # default

RMAN> run
2> {
3> backup archivelog all;
4> crosscheck archivelog all;
5> delete expired archivelog all;
6> }

..
..
Crosschecked 153 objects


released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=157 devtype=DISK
specification does not match any archive log in the recovery catalog

RMAN> BACKUP ARCHIVELOG ALL DELETE INPUT;
input archive log thread=1 sequence=627 recid=593 stamp=710249727
input archive log thread=1 sequence=628 recid=595 stamp=710411997
..
..

Finished backup at 26-FEB-10

But the location of archive (5 files, and arch2 = 50 = arch1) files are still there. Can I delete these files from OS commands.

In C:\oracle\product\10.2.0\flash_recovery_area\ORCL, there are 405. ARC files is also available. I can remove them too; because I took the backup of all archive logs? Location of the Archive previous was FRA, but now I take archives at 2 different locations i.e. d:\orcl\arch1 and d:\orcl\arch2.

Thanking you,
Nisha

Why not look at the file names (indicating the sequence numbers) and timestamps and make a decision on your own?

And go ahead: take MORE FREQUENT backups. And copy your backups on the server. If you lose the discs/storage, you lose the backup and the database!

Hemant K Collette

Published by: Hemant K grapple on February 26, 2010 16:53

Applied deletion logs archiving on standby DB
Hello:

I need help in the construction of this shell script to me. We have databases of production on oracle 9i (9.2.0.8) on solaris 9 OS. Each of these databases have a physical standby (same configuration as the primary) all pending databases are on the same node. At the moment I have to hand, check the location of archive and remove the logs that are already applied to the system. I want to eliminate this manual activity to automate this. I have the primary DB on a daily and weekly backup RMAN. (Not sure WHAT RMAN has any command to meet my needs).

The shell (BASH) script should do the following.

1. the source of the oraenv file

2. connect to the database.

3. get the number # from the last applied log.

4. store in a variable.

5. go the archives directory and delete all files up to the number #, we are at step 3.

6. the connection to the database next and repeat the same thing.

I have very little experience with shell scripts and no help from the team would be really useful

Kind regards

BMP
Bala,

Here is an example, (read comments) you may need to extend this to fit your needs, but it should work as is and change the shell (regardless of shelll you use).
```
#!/bin/ksh
typeset username=$1
function readSqlstmt {
  typeset stmt=$1

  echo "
    set feedback off
    set verify off
    set heading off
    set pagesize 0
    whenever sqlerror exit 1
    whenever oserror exit 2
    $stmt;
    exit
  " |  sqlplus -S "/as sysdba" >> test.log
}

# You can remove this killpid function from the script or comment out
function killpid {
killpidsql=killpid.sql

sqlplus -s "/as sysdba" << ENDOFSQL >> test.log
whenever sqlerror exit 1
whenever oserror exit 2
SET pagesize 0
SET verify   off
SET feedback off

SPOOL ${killpidsql}
  SELECT 'ALTER system kill session ''' || s.sid || ',' || s.serial# || ''';'
  FROM v\$session s, v\$process p
  WHERE s.paddr = p.addr AND s.status = 'INACTIVE';
SPOOL OFF
#@${killpidsql}
ENDOFSQL
}

readSqlstmt "SELECT name from v\$archived_log WHERE applied = 'YES'"  | while read u
do
    echo $u
    # Here you can print first to see if you are getting the correct list
    # then you can simply remove
    #
    # rm $u
done
```
Concerning

Size of the huge log archive
I have 5 redo log files. Each is 4 GB. There are huge transactions (1800-2000 per second). So we have every hour 5-6 journal of the switches. So all the hours of archives journal 20 to 24 GB and daily increase in size, the size 480 GB.

I had planned to take an incremental backup of level 1 and level 0 per week daily with the option delete log archiving 'sysdate-1 '.

But we have little storage if, it is impossible to the sphere 480 GB per day and take backup of these 480 GB for 7 days (480 * 7) GB = 4 TB. How can I correct this situation? Help, please.
1 disk is cheap
2 the onus on those who "Advanced" application
3 you can use Log Miner to check what is happening.

You need to this address with application developers and/or clients and/or buy the disc.
There are no other solutions.

-----------
Sybrand Bakker
Senior Oracle DBA

Published by: sybrand_b on July 16, 2012 11:11

Data Guard archive political deletion log

Hi all
I configured the data guard with 2 bases Eve in oracle 11g.
I want to use rman to delete archives on all servers.
I have configured no FRA, no recovery catalog.
My question is:
If I delete waiting til sequence # 1627 and on primary sequence til = # = 1620 or vice versa this would cause problems for Data Guard.
I say delete until the different sequences # on primary and standby cause problems for synchronization?
Thank you

So if I understand delete archivelog to sysdate - or delete archivelog all completed before sysdate n is not the archivelog deletion policy you put on RMAN?

She depends on it. The note was made at the base of the MOS document how ensure that RMAN is NOT delete archived logs that have not yet shipped to standby mode (Doc ID 394261.1)

Delete archivelog to sysdate - depends on all of the deletion policy. If the deletion policy is set on "applied pending all", then it does not delete the archives, if they are not applied on the day before. If the deletion policy is set to none, then it does not check if the archive is applied on the eve and deletes them directly.

Last Archive generated on primary:

SYS@oraprim > select max(sequence#) from v$ archived_log;

MAX(SEQUENCE#)

--------------

114

Last check-in applied in mode ensures:

SYS@orastb > select max(sequence#) from v$ archived_log in case of application = 'YES ';

MAX(SEQUENCE#)

--------------

109

Delete policy set to NONE on primary:

RMAN > show archivelog deletion policy;

using the control file of the target instead of recovery catalog database

RMAN settings for database with db_unique_name ORAPRIM are:

CONFIGURE THE NONE ARCHIVELOG DELETION POLICY;

RMAN > delete archivelog until 'sysdate;

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID = 60 type of device = DISK

List copies of newspapers archived to database with db_unique_name ORAPRIM

=====================================================================

Thrd Seq S key low time

------- ---- ------- - ---------

110-1-214 A JANUARY 13, 16

Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_110.318.901050727

216-1-111 A JANUARY 13, 16

Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_111.317.901050731

217-1-112 A JANUARY 13, 16

Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_112.316.901050731

113. OF 1 219 A 13 JANUARY 16

Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_113.315.901050733

222 1 114 A JANUARY 13, 16

Name: +FRA/oraprim/archivelog/2016_01_13/thread_1_seq_114.314.901050737

You sure you want to delete the items above (enter YES or NO)? NO.

It is the removal of primary archives that have not yet been applied on the eve.

Delete policy 'APPLIES ON STANDBY ALL' value on the primary:

RMAN > show archivelog deletion policy;

RMAN settings for database with db_unique_name ORAPRIM are:

CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

RMAN > delete archivelog until 'sysdate;

output channel: ORA_DISK_1

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID = 60 type of device = DISK

RMAN-08120: WARNING: log archived not deleted, not yet applied watch

Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_110.318.901050727 thread = 1 sequence = 110

RMAN-08120: WARNING: log archived not deleted, not yet applied watch

Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_111.317.901050731 thread = 1 sequence = 111

RMAN-08120: WARNING: log archived not deleted, not yet applied watch

Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_112.316.901050731 thread = 1 sequence = 112

RMAN-08120: WARNING: log archived not deleted, not yet applied watch

Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_113.315.901050733 thread = 1 sequence = 113

RMAN-08120: WARNING: log archived not deleted, not yet applied watch

Archive log file name=+FRA/oraprim/archivelog/2016_01_13/thread_1_seq_114.314.901050737 thread = 1 sequence = 114

It checks if the archive has been applied on the day before. As the 110 to 114 sequence is not applied in the waiting, the archives are not deleted on the primary.

Hope that gives you a clear picture of how it works.

-Jonathan Rolland

RMAN-08120: WARNING: log archived not deleted, not yet applied watch
I get RMAN-08120: WARNING: journal archived not deleted, not yet applied watch on primaries
but when I run under query, I get the same result of primary and backup

SQL > select max(sequence#) from v$ archived_log;

MAX(SEQUENCE#)
--------------
44051

SQL >

Eve is a log switch behind only!
Hello;

If RMAN tries to remove an archive which is not yet applied in standby log, you see the RMAN-08120

It's a good thing. As long as you don't have any archives for days on standby, you probably don't have a problem.

What are your RMAN settings for the database of the day before?

MetaLink Note: 361182.1 can help too. Or Note 1079953.1

Your main, make sure that:
```
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
```
Please consider closing some of your old issues to clean up the forum.

Best regards

mseberg

RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

Hi Oracle Community,
I have a few databases (11.2.0.4 POWER 2 block and 12.1.0.2) with Data Guard. Back up this database with RMAN to ribbons, only on the primaries.
During the backup, sometimes I got RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure
By reason of this global warning to backup status is "COMPLETED WITH WARNINGS". Is it possible to remove this warning, or perhaps change RMAN configuration to avoid the appearance of this warning?
Concerning
J

Where is the problem on these warnings? If you do not want to see such warnings, why not simply to perform the removal of the archivelogs in a separate step? For example:
```
RMAN> backup database plus archivelog;
RMAN> delete noprompt archivelog all completed before 'sysdate-1';
```

Find the archive logs generated per day (for 7.3.4 database)?
I use a query like the one below to determine the average amount archives logs generated per day for a database for a month:

Select sum (GB_USED_PER_DAY) count (GB_USED_PER_DAY) in (SELECT
To_char(completion_time,'YYYY-mm-DD') completion_date,
round (SUM (block_size *(blocks+1)) / 1024 / 1024 / 1024, 2) GB_USED_PER_DAY
V $ archived_log
WHEN TRUNC (completion_time) BETWEEN
TRUNC(SYSDATE-30) AND TRUNC (SYSDATE)
GROUP OF TO_CHAR(completion_time,'YYYY-MM-DD')
order by 1 desc);

This query does not work on Oracle 7.3.4 database. Anyone know how I can calculate average archive generation of newspapers per day for Oracle 7.3.4?

Thanks in advance!
Select substr(first_time,1,8), round (sum (bytes) /(1024*1024)) MB of v$ log group by substr (first_time, 1, 8);

How long should we keep logs archived in the comic book?

11.2.0.4 DB Oracle Linux 6.5

We have a database whose archive generation is as follows.

Average of generation of archive log: 400 GB/day

Max log generation: 900 GB/day

Archive log diskgroup size: 4 TB

Backup strategy: we take full backups on Monday and Wednesday and Level1 for the rest of the days.

-----------------

Sunday-> level 0 backup

Monday-> level 1 backup

Tuesday-> level 1 backup

Wednesday-> level 0 backup

Thursday-> level 1 backup

Friday-> level 1 backup

Saturday-> level 1 backup

Both Level0 and Level1 scripts have MORE ARCHIVELOG; (without a clause to DELETE all THE ENTRIES )

We have archiveLog backup script that runs at 10:00 and 16:00 which does not REMOVE all ENTRIES either.

We serve the archivelogs of Level0 and Level1 backup scripts, with the following command

delete noprompt archivelog until 'SYSDATE -2";

Question1. What is the industry standard to keep (retention period), archiving within DB logs? Is there a 'formula' / rule for this? When a restore, recovery lose us not a lot of time restore backup media archivelogs. That's why we stay 2 days now archivelog within the DB.

Question2. We have 4 TB of space to store the archivelogs in this particular PB. With 900 GB Max generation arch daily newspapers, we can keep safe the last 3 days of the archivelogs. Right? I mean, is there a possibility of hitting the terrible archiver error if we increase the shelf life of the archive logs using the delete noprompt archivelog until 'SYSDATE -3';

N ° DELETE OBSOLETE removes old newspapers also all the log_archive_dest.

I could be wrong, but this is the first I hear of this and on a quick scan, I found no support in that either rman reference or guide the user to rman. Could cite your source?

DELETE OBSOLETE is not the same thing as REMOVE EXPIRES.

-EDIT

Never mind. I found it.

DELETE

OBSOLETE

Removes backups of data files and copies stored in the repository RMAN which are obsolete, in other words, is no longer required (see example 2-66). RMAN also deletes the log of the obsolete filesand archived redo log backups.

RMAN determines what backups and copies of data files are no longer needed, which in turn determines what records (and backups of logs) are no longer needed. RMAN considers that the creation of a data file as a backup to decide which connects to keep.

Post edited by: EdStevens

Historically, I saved my archivelogs with the option to DELETE the ENTRIES, I never had reason to notice or question this behavior... a rman DELETE OBSOLETE reach out to the archivelogs themselves. Thinking maybe it was related to the maintenance of the FRA, I just tried a little test in two ways... archivlogs wrote to FRA and archivelogs writes destined for non - FRA. Of course, anyway DELETE OBSOLETE also deleted real archivelogs. I don't know that I'll change my procedures as well, but it is good to know.

I learned something new today. Can I go home now?

Purge logs archiving on things primary and Standby and for Data Guard RMAN

Hi, I saw a couple of orders in regard to the purge archive records in a Data Guard configuration.
Set UP the STRATEGY of SUPPRESSION of ARCHIVE to SHIPPED to All RELIEF;
Set UP the STRATEGY of ARCHIVELOG DELETION to APPLIED on All RELIEF;
Q1. The above only removes logs archiving to the primary or primary and Standby?
Q2. If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?
I also saw
CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED;
Q3. That what precedes, and once again it is something that you re primary side?
I saw the following advice in the manual of Concepts of data protection & Admin
Configure the DB_UNIQUE_NAME in RMAN for each database (primary and Standby) so RMAN can connect remotely to him
Q4. Why would I want my primary ro connect to the RMAN Repository (I use the local control file) of the standby? (is this for me to say define RMAN configuration settings in the Standby) manual
Q5. Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?
Q6. If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?
Q7. Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?
Q8. What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?
Any idea greatly appreciated,
Jim

The above only removes logs archiving to the primary or primary and Standby?

When CONFIGURE you a deletion policy, the configuration applies to all destinations archive

including the flash recovery area. BACKUP - ENTRY DELETE and DELETE - ARCHIVELOG obey this configuration, like the flash recovery area.

You can also CONFIGURE an archived redo log political suppression that newspapers are eligible for deletion only after being applied to or transferred to database backup destinations.

If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

Its a configuration, it will not erase by itself.

If you want to use FRA for the automatic removal of the archivelogs on a database of physical before you do this:

1. make sure that DB_RECOVERY_FILE_DEST is set to FRA - view parameter DB_RECOVERY_FILE_DEST - and - setting DB_RECOVERY_FILE_DEST_SIZE

2. do you have political RMAN primary and Standby set - CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON ALL STANDBY;

If you want to keep archives more you can control how long keep logs by adjusting the size of the FRA

Great example:

http://emrebaransel.blogspot.com/2009/03/delete-applied-archivelogs-on-standby.html

All Oracle is worth a peek here:

http://emrebaransel.blogspot.com/

That what precedes, and once again it is something that you re primary side?

I would never use it. I always had it put it this way:

CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

I would use only 'BACKED UP' for the data protection system. Usually it tell oracle how many times to back up before removing.

Why would I want my primary ro connect to the RMAN Repository?

Because if you break down, you want to be able to backup there, too.

Also if it remains idle for awhile you want.

Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

Always use a database of catalog RMAN with Data Guard.

If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

Same answer as 5, use a catalog database.

Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

Same answer as 5, use a catalog database.

What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

I think cron is still, but they all work. I like cron because the database has a problem at work always reports its results.

Best regards

mseberg

Summary

Always use a database with RMAN catalog.

Always use CRF with RMAN.

Always set the deletion «To APPLY ON ALL STANDBY» policy

DB_RECOVERY_FILE_DEST_SIZE determines how long to keep the archives with this configuration.

Post edited by: mseberg

Log archiving
Dear experts,

I have to test the size of the log archive every transaction. the next step needs to be done for this test

1 running dml scripts in bulk
2 need to find how the size of the log file archive created on the archive location.

based on what we have to give the stats that particular transaction generated as much redo log file from archive. can you please provide the script to do this. Thanks in advance.
Oragg wrote:
Dear experts,

I have to test the size of the log archive every transaction. the next step needs to be done for this test

1 running dml scripts in bulk
2 need to find how the size of the log file archive created on the archive location.

based on what we have to give the stats that particular transaction generated as much redo log file from archive. can you please provide the script to do this. Thanks in advance.

Lets assume that you have loaded data for 1 day or 1 hour as below
```
alter session set nls_date_format = 'YYYY-MM-DD HH24';

select
  trunc(COMPLETION_TIME,'HH24') TIME,
   SUM(BLOCKS * BLOCK_SIZE)/1024/1024 SIZE_MB
from
  V$ARCHIVED_LOG
group by
  trunc (COMPLETION_TIME,'HH24') order by 1;
```

Logs archiving for the RAC ASM basics

Hello

I have a question about logs archiving on the ASM database located on a RAC. I created a database orcl who has orcl1 instance on node1 and orcl2 on Node2. For the backup of this database, I enabled for the database to archivelog.

After a few transactions and backups, I noticed that there are two sets of archiving logs created on each node in the folder $ORACLE_HOME/dbs. In node 1, it starts with arch1_ * and node2 is arch2_ *.

IWhy is it creates logs archiving on local disks, in which she should ideally create disks asm which is shared between the nodes. My backup application fails with journal archive not found error, because it searches newspaper archives in the other node.

All entries on this will be useful.

Amith

Hello

I have a question about logs archiving on the ASM database located on a RAC. I created a database orcl who has orcl1 instance on node1 and orcl2 on Node2. For the backup of this database, I enabled for the database to archivelog.

After a few transactions and backups, I noticed that there are two sets of archiving logs created on each node in the folder $ORACLE_HOME/dbs. In node 1, it starts with arch1_ * and node2 is arch2_ *.

I believe that it is missing from your configuration database and Oracle uses the default location. (i.e. your "$ORACLE_HOME/dbs")

ARCHIVELOG must focus on a shared domain.

You need the parameter config below:

SQL> show parameter db_recovery_file
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest                string
db_recovery_file_dest_size           big integer

Or location of default config:

SQL> show parameter log_archive_dest

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest                     string

IWhy is it creates logs archiving on local disks, in which she should ideally create disks asm which is shared between the nodes. My backup application fails with journal archive not found error, because it searches newspaper archives in the other node.

To resolve this problem see this example:

SQL> show parameter recover

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest                string
db_recovery_file_dest_size           big integer 1

SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /u01/app/oracle/product/10.2.0/db_1/dbs/
Oldest online log sequence     2
Next log sequence to archive   3
Current log sequence           3
SQL>

SQL> alter system set db_recovery_file_dest_size=20G scope=both sid='*';

System altered.

SQL> alter system set db_recovery_file_dest='+FRA' scope=both sid='*';

System altered.

SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     5
Next log sequence to archive   6
Current log sequence           6
SQL>

With RMAN

RMAN> CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT 'sys/oracle@db10g1';

new RMAN configuration parameters:
CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT '*';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete

RMAN>  CONFIGURE CHANNEL 2  DEVICE TYPE DISK CONNECT  'sys/oracle@db10g2';

new RMAN configuration parameters:
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT '*';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete

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
------- ---- ------- - --------- ----
1       1    3       A 28-FEB-11 /u01/app/oracle/product/10.2.0/db_1/dbs/arch1_3_744216789.dbf
2       2    2       A 27-FEB-11 /u01/app/oracle/product/10.2.0/db_1/dbs/arch2_2_744216789.dbf

RMAN> crosscheck archivelog all;

allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=127 instance=db10g1 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=135 instance=db10g2 devtype=DISK
validation succeeded for archived log
archive log filename=/u01/app/oracle/product/10.2.0/db_1/dbs/arch1_3_744216789.dbf recid=1 stamp=744292116
Crosschecked 1 objects

validation succeeded for archived log
archive log filename=/u01/app/oracle/product/10.2.0/db_1/dbs/arch2_2_744216789.dbf recid=2 stamp=743939327
Crosschecked 1 objects

RMAN> backup archivelog all delete input;

Starting backup at 28-FEB-11
current log archived
using channel ORA_DISK_1
using channel ORA_DISK_2
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=3 recid=1 stamp=744292116
channel ORA_DISK_1: starting piece 1 at 28-FEB-11
channel ORA_DISK_2: starting archive log backupset
channel ORA_DISK_2: specifying archive log(s) in backup set
input archive log thread=2 sequence=2 recid=2 stamp=743939327
channel ORA_DISK_2: starting piece 1 at 24-FEB-11
channel ORA_DISK_1: finished piece 1 at 28-FEB-11
piece handle=+FRA/db10g/backupset/2011_02_28/annnf0_tag20110228t120354_0.265.744293037 tag=TAG20110228T120354 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=/u01/app/oracle/product/10.2.0/db_1/dbs/arch1_3_744216789.dbf recid=1 stamp=744292116
channel ORA_DISK_2: finished piece 1 at 24-FEB-11
piece handle=+FRA/db10g/backupset/2011_02_24/annnf0_tag20110228t120354_0.266.743940249 tag=TAG20110228T120354 comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:00:03
channel ORA_DISK_2: deleting archive log(s)
archive log filename=/u01/app/oracle/product/10.2.0/db_1/dbs/arch2_2_744216789.dbf recid=2 stamp=743939327
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=4 recid=4 stamp=744293023
input archive log thread=2 sequence=3 recid=3 stamp=743940232
channel ORA_DISK_1: starting piece 1 at 28-FEB-11
channel ORA_DISK_1: finished piece 1 at 28-FEB-11
piece handle=+FRA/db10g/backupset/2011_02_28/annnf0_tag20110228t120354_0.267.744293039 tag=TAG20110228T120354 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=+FRA/db10g/archivelog/2011_02_28/thread_1_seq_4.264.744293023 recid=4 stamp=744293023
archive log filename=+FRA/db10g/archivelog/2011_02_24/thread_2_seq_3.263.743940231 recid=3 stamp=743940232
Finished backup at 28-FEB-11

Starting Control File and SPFILE Autobackup at 28-FEB-11
piece handle=+FRA/db10g/autobackup/2011_02_28/s_744293039.263.744293039 comment=NONE
Finished Control File and SPFILE Autobackup at 28-FEB-11

SQL> alter system archive log current;

System altered.

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
------- ---- ------- - --------- ----
5       1    5       A 28-FEB-11 +FRA/db10g/archivelog/2011_02_28/thread_1_seq_5.264.744293089
6       2    4       A 24-FEB-11 +FRA/db10g/archivelog/2011_02_24/thread_2_seq_4.268.743940307

RMAN> CONFIGURE CHANNEL 1 DEVICE TYPE DISK CLEAR;

old RMAN configuration parameters:
CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT '*';
old RMAN configuration parameters are successfully deleted

RMAN> CONFIGURE CHANNEL 2 DEVICE TYPE DISK CLEAR;

old RMAN configuration parameters:
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT '*';
old RMAN configuration parameters are successfully deleted

RMAN> exit

Recovery Manager complete.

Kind regards
Levi Pereira

Published by: Levi Pereira on February 28, 2011 12:16

My emails are deleted after a few days. If I read them everyday I can miss important messages.

My emails are deleted after a few days. If I do not consider my inbox every day I can miss important messages.

E-mail address is removed from the privacy *.

Hi Marion,.

The most likely cause is that you have a setting that is configured to do this in your e-mail program or in your online account. I recommend that to start with your email provider to see if they can help you with this problem (as it's probably something in these settings, or they may be able to find the settings in the program that you are using if it's one they know). If they can help or saying is not your online account settings, then we need to know the version of Windows you use, e-mail program, (name and version) you are using, or the browser you use to access the account. With this, we can help you with the problem or refer you to experts that specialize in what you use.

Thanks and good luck!

Reg apply log archiving after the transfer of data files
Hi all

That I reinstalled the main server of the D-Drive E-reader data files using the command line.
```
C:\>Move <source_path> <destination_path>
```
The redo logs for the move operation will apply on the eve of the database?
In addition, what happens if the data files are moved manually in the primary database (i.e. without using the command prompt)?

Thank you
Madhu
See this doc. Keyword search Rename a data file in the primary database

http://docs.Oracle.com/CD/B28359_01/server.111/b28294/manage_ps.htm#i1034172

Also, you need to update primary database controlfile if some moment of the file made...

And also close this thread

Reg apply log archiving after the transfer of data files

As it would help in the forum of maintenance to clean.

delete the archive logs after cold backup?
Hi all
my database is in archivelog mode, I do COLD backup every night, can I just remove the archive logs after I do my cold backup, because there is no need of them, as the closed DB should have all the info in the archived papers

and archive connected is needed only during the day, if a sudden power outage that happened.

Thank you very much
The ArchiveLogs allow you RollForward a backup restored to a specific point in time.

Assuming that stop you your database at 23:00 (2300) every night and backup up to 11 h 45 (2345) tracks...

Significant transactions entered between 15:00 and 16:00 on Friday, but a person deleted by mistake the lines (or some other lines) at 17:00

your current backup strategy of "restoration" of the database only allows 23:00 Thursday night. If you also back up your archivelogs (in this case, the backup of Friday night would the archivelogs), you restore Thursday night backup 'cold' and "rollforward" by publishing a RECOVER database with the HELP of BACKUP CONTROLFILE until 16:00 Friday.

Delete logs archive &gt; 1 day

Similar Questions

Maybe you are looking for

Delete logs archive > 1 day