Manually apply archive logs waiting

RDBMS Version: 11.2.0.4

OS: RHEL 6.6

As I understand it, if I want to manually apply archive logs, I do the 2 steps.

But, how can I do watch DB to accept (add it as part of the eve DB) logs archiving transferred manually?

That is to say. How can force you standby DB to add these archiving logs to its control file?

Step 1. First stop the current recovery process (MRP) as

ALTER database recover managed standby database cancel;

Then transfer must all logs archiving of primary school next door waiting and apply manually using below command.

Step 2. recover a database on hold until cancel;

Hello

To do this manually, you must:

(a) manually transfer logs archived redo of primary site on backup site

(b) lets say to the backup site, you have this path ' / archives/database / ' and in this way, there are the archived redo logs

Then, in the backup site, you must catalog the logs archived redo with RMAN

RMAN > CATALOGUE START WITH "/ archives/database /";

change recover managed standby database disconnect log file using current;

ALTER database recover managed standby database disconnect;

(d) monitor the alerts log to see if this transferred manually and asking unregistered archived redo logs

Kind regards

Juan M

Tags: Database

Similar Questions

Best method to remove applied archive logs for the production and the DB in waiting
Dear all,

Two of my databases are 10gr 2 on Linux OS.

I have set up a database of pending for my production database. Logs apply and the size of the data file for the two databases is the same, if I compare.

I'm just confused about which method to use to remove applied log archiving of files from the production and standby databases.

the .dbf files are being moved from production to standby mode. I want to do it manually first and then automate for better understanding. I want to just make sure that the .dbf files can be deleted only used effect the process of production-standby.

Best regards, Imran
I have set up a database of pending for my production database. Logs apply and the size of the data file for the two databases is the same, if I compare.

I'm just confused about which method to use to remove applied log archiving of files from the production and standby databases.

For the removal of the archvies in production, better to use RMAN backup scripts,.

for the deletion archives pending check my comments thread below.

Deleting archives connects in standby mode

the .dbf files are being moved from production to standby mode. I want to do it manually first and then automate for better understanding. I want to just make sure that the .dbf files can be deleted only used effect the process of production-standby.

Be sure to what ever format archives, keep files archives other than data file locations. If you want you can delete production is there really no need backup archives on the primary?

Delete pending archive logs
Hello

My oracle database is 11.2.0.2 RDBMS RAC on RHEL 5. 6

We have recently established physics of the standby database. How to remove archive logs waiting for physical standby mode?
Hello;

There is a little different to do this. I would consider these notes:

How to ensure that RMAN is NOT delete archived logs that have not yet shipped to standby [394261.1 ID]

RMAN removes records of logs on the primary database not applied pending physical [ID 1324759.1]

Configure RMAN to purge the archivelogs after application on hold [728053.1 ID]

You can use an RMAN script to do this:
```
echo "Starting RMAN..."
$ORACLE_HOME/bin/rman target / catalog user/password@rcatalog << EOF

delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';

exit
EOF
```
Best regards

mseberg

archive log deletion pending
Hi all

I'm working on oracle database enterprise edition 10.2.0.4.I have created a database.the physical standby of the primary database name is prim and the standby database name Eve.He has 100 files of newspapers to archive are generating each size is 300 MB per day. I applied archive log political removal of watch on the primary database. So all the newspaper shifted and applied pending archive are deleted from primary. But my concern is the archive logs staggered into sleep mode. The archivelogs in the standby server must be deleted.how that it can be removed. Help, please
use RMAN to this effect, as you do in primaries.

It will make a backup if you need and delete the archivelogs.

Archiving logs not applied to sleep!
Hi guys,.

I'm implementing physical standby on windows 2003 server. I use oracle 10.2.0.4.0. I get the following error in my alert pending file
You cannot request the gap sequence

Here are the results of some queries:

SQL > SELECT PROCESS, STATUS, THREAD #, SEQUENCE #, BLOCK #, BLOCKS FROM V$ MANAGED_STANDBY;

STATUS OF PROCESS THREAD # SEQUENCE # BLOCK # BLOCKS
--------- ------------ ---------- ---------- ---------- ----------
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
Mr (FG) 1 10004 WAIT_FOR_GAP 0 0

SQL > select * from v$ archive_gap;
no selected line

SQL > select message from v$ dataguard_status;

Message
-------------------------------------------------------------
Arc0: Started archiving
Arc1: Started archiving
ARC2: Started archiving
ARC3: Started archiving
Arc4: Started archiving
ARC5: Started archiving
ARC6: Started archiving
ARC7: Started archiving
ARC8: Started archiving
ARC9: Started archiving
Arc0: become the "no FAL' ARCH

Message
-------------------------------------------------------------
Arc0: become the "no SRL" ARCH
Arc1: Become the heartbeat ARCH
Try to start inside the managed standby recovery process
MRP0: Background Managed Standby recovery started
Managed Standby recovery not using real time applies
Media, recovery waiting for thread 1 sequence 10004
Pick up the empty sequence in thread 1, sequence gap 10004-10017
FAL [client]: you cannot request the gap sequence
GAP - thread 1 sequence 10004-10017
2422302575 670594799 DBID branch
FAL [client]: all defined FAL servers have been tried.

Message
-------------------------------------------------------------
MRP0: Background Media Recovery cancelled with status 16037
MRP0: Stopping the process background Media Recovery
Managed recovery cancelled pending
Start of recovery media: managed standby recovery
Managed Standby recovery not using real time applies
Media, recovery waiting for thread 1 sequence 10004
Pick up the empty sequence in thread 1, sequence gap 10004-10017
FAL [client]: you cannot request the gap sequence
GAP - thread 1 sequence 10004-10017
2422302575 670594799 DBID branch
FAL [client]: all defined FAL servers have been tried.

SQL > SELECT THREAD #, SEQUENCE #, APPLIED TO V$ ARCHIVED_LOG
in case of application = 'YES '.

no selected line

##Modification in primary #.
* .log_archive_dest_2 = "SERVICE = STANDBY"
* .fal_client = "STUTEST".
* .fal_server = "STUSTANDBY".
* .log_archive_config = 'DG_CONFIG = (STUTEST, STUSTANDBY)'

##Modification on Eve #.
* .db_unique_name = "STANDBY".
* .log_archive_dest_2 = "SERVICE = STANDBY"
* .log_archive_dest_state_2 = 'ENABLE '.
*. Fal_server = STUTEST
*. Fal_client = STUSTANDBY
* .db_file_name_convert = "H:\ORACLE\ORADATA\STUTEST\",' I: \ORACLE\ORADATA\STUTEST\s_'
* .log_file_name_convert = a: \oracle\oradata\STUTEST\',: \oracle\oradata\STUTEST\s_'

Nore: I used RMAN to create the database on hold. Here's the brief steps

Here are the steps to accomplish the task:

Step 1: Back up the database that includes the backup of the data files, archivelogs and controlfile to standby
backup current controlfile to sleep;
Step 2: Move the backups to the server backup and restore of backup control file
Step 3: Change the database parameter files primary and standby
Step 4: Do the restore and recover on the backup database
Step 5: Put the database sleep in managed recovery mode

Thanks for the help guys!
jazz81,

If I were you I copy the archivelog 10119 Eve primary number and run the following command.
```
ALTER DATABASE REGISTER LOGFILE '/PATH_HERE/ARCH_10119.arch';
```
```
+This clause allows the registration of manually archived redo logs. The SQL statement syntax is:+

+ALTER DATABASE REGISTER [OR REPLACE] [PHYSICAL | LOGICAL] LOGFILE filespec;+
```
The database that you need to cancel the process MRP0, then re-run the MRP0 with the disconnection of the clause of session of the altar.

Ogan

Copy archive logs side Eve for manual resolution of gap
Version: 11.2 on RHEL 5.8
Watch type: physical standby

An excerpt from 11.2 Data guard Concepts and administration guide,

To manually correct the gap, one can copy primary eve archivelogs and register as below
```
SQL> ALTER DATABASE REGISTER LOGFILE '/physical_standby1/thread1_dest/arcr_1_7.arc';
SQL> ALTER DATABASE REGISTER LOGFILE '/physical_standby1/thread1_dest/arcr_1_8.arc';
SQL> ALTER DATABASE REGISTER LOGFILE '/physical_standby1/thread1_dest/arcr_1_9.arc';
```
Question1.
How is solved the gap once we register the archive above logs?

Question2.
We set LOG_ARCHIVE_DEST_1 physical standby? AFAIK, archive logs don't get generated in a physical standby
because the standby DBs ORLs are never used.
Hello
Rebel wrote:
Version: 11.2 on RHEL 5.8
Watch type: physical standby

An excerpt from 11.2 Data guard Concepts and administration guide,

To manually correct the gap, one can copy primary eve archivelogs and register as below
```
SQL> ALTER DATABASE REGISTER LOGFILE '/physical_standby1/thread1_dest/arcr_1_7.arc';
SQL> ALTER DATABASE REGISTER LOGFILE '/physical_standby1/thread1_dest/arcr_1_8.arc';
SQL> ALTER DATABASE REGISTER LOGFILE '/physical_standby1/thread1_dest/arcr_1_9.arc';
```
Question1.
How is solved the gap once we register the archive above logs?
Yes, you can save the newspapers archived on the eve of database, which is copied manually from the primary.
If you want to apply the archived redo logs, then you must start the recovery process - redo apply (MRP).

If you archived redo log in the primary, he's not neccasary primary copy manually.

If you have GAP and archived redo logs have in the primary, then it is enough to launch again apply.
When you start MRP, if you have gap then MRP request archived redo of the FAL Server (primary) and resolve the discrepancy.
It is the resolution of the automatic gap.

have you started with MRP?
```
select process from  v$managed_standby where process like 'MRP%';
-- if no row selected
alter database recover managed standby database disconnect from session;
or
alter database recover managed standby database using current logfile disconnect from session; -- real  time apply
```
>
>

Question2.
We set LOG_ARCHIVE_DEST_1 physical standby? AFAIK, archive logs don't get generated in a physical standby
because the standby DBs ORLs are never used.

Value by default is LOG_ARCHIVE_DEST_1 - is USE_DB_RECOVERY_FILE_DEST, that means if you are not ready to LOG_ARCHIVE_DEST_1,.
then all archived redo log store in the Flash recovery area.

Archvied redo log isn't genereted database pending, ORL, Srl, if you add standby recovery logs.
When you use protection MAX Performance mode and not added database SRL then sleep by using the BDL.

Concerning
Mr. Mahir Quluzade

Archiving logs apply frequency in Data Guard
Dear all,

How can we verify/set up the frequency archive newspapers should be applied to the Data Guard?

Version: 10 g 2; OS: Windows 2003 R2 (64-bit).
How we can configure the frequency of archive logs must be applied to the DG?

Erase the question once more what you're expecing, as I understand, it's...

It depends on the Redo genearation / Archive primary & network latency between primary databases & Eve.
There is a configuration, you can change in the primary to put options such as delay , net_timeout and so on.

consult this manual too.
http://download.Oracle.com/docs/CD/B28359_01/server.111/b28294/log_arch_dest_param.htm

DataGuard archiving log not applied
Hello

I met archive log apply errors in the physical standby database. Below are the errors.

SQL > SELECT SEQUENCE #, FIRST_TIME, NEXT_TIME, APPLIED from V$ ARCHIVED_LOG SEQUENCE ORDER #;

SEQUENCE # FIRST_TIM NEXT_TIME APP
---------- --------- --------- ---
10 24 AUGUST 11 NO. 24 AUG 11
10 24 AUGUST 11 NO. 24 AUG 11
11 AUGUST 24, 11 NO. 24 AUG 11
12 24 AUGUST 11 NO. 25 AUG 11
13 25 AUGUST 11 NO. 25 AUG 11
14-25 AUGUST 11 NO. 25 AUG 11

6 selected lines.

SQL > select database_role, open_mode from v$ database;

DATABASE_ROLE OPEN_MODE
---------------- ----------
FIRST READING WRITING

SQL > select message from v$ dataguard_status;

ARCs: Started archiving
CRAT: Started archiving
CJACBR: become the "no FAL' ARCH
CJACBR: become the "no SRL" ARCH
ARCm: Become the heartbeat ARCH

Message
--------------------------------------------------------------------------------
Again shipping customer logged in as PUBLIC
-User is valid
RFS [1]: assigned to the RFS 3389 process
RFS [1]: do not use real application clusters
LGWR: Error 16009 creation archivelog file "DBSOURCE.
LNS: Impossible to archive log 3 thread 1 sequence 15 (16009)
Again shipping customer logged in as PUBLIC
-User is valid
RFS [2]: assigned to the RFS 3393 process
RFS [2]: do not use real application clusters
FAL [server, ARCo]: error 16009 file creation remote archivelog 'DBSOURCE.

Message
--------------------------------------------------------------------------------
Again shipping customer logged in as PUBLIC
-User is valid
RFS [3]: assigned to the RFS 3397 process
RFS [3]: do not use real application clusters
Heartbeat PING [ARCm]: Unable to connect to the eve "DBSOURCE. The error is 16009.
Again shipping customer logged in as PUBLIC
-User is valid
RFS [4]: assigned to the RFS 3429 process
RFS [4]: do not use real application clusters
Heartbeat PING [ARCm]: Unable to connect to the eve "DBSOURCE. The error is 16009.

54 selected lines.

Of the primary alerts on DB log errors
Using the default value for the parameter STANDBY_ARCHIVE_DEST as/u01/app/oracle/oradata/DBSOURCE
Again shipping customer logged in as PUBLIC
-User is valid
RFS [1]: assigned to the RFS 3389 process
RFS [1]: do not use real application clusters
Errors in the /u01/app/oracle/diag/rdbms/dbsource/DBSOURCE/trace/DBSOURCE_rfs_3389.trc file:
ORA-16009: destination of the journal archive remote must be a database of the EVE
Game Aug 25 12:17:10 2011
Errors in the /u01/app/oracle/diag/rdbms/dbsource/DBSOURCE/trace/DBSOURCE_lns1_3349.trc file:
ORA-16009: destination of the journal archive remote must be a database of the EVE
LGWR: Error 16009 creation archivelog file "DBSOURCE.
LNS: Impossible to archive log 3 thread 1 sequence 15 (16009)
Game Aug 25 12:17:30 2011
Again shipping customer logged in as PUBLIC
-User is valid
RFS [2]: assigned to the RFS 3393 process
RFS [2]: do not use real application clusters
Errors in the /u01/app/oracle/diag/rdbms/dbsource/DBSOURCE/trace/DBSOURCE_rfs_3393.trc file:
ORA-16009: destination of the journal archive remote must be a database of the EVE

initDBSOURCE.ora params
DB_NAME = DBSOURCE
DB_UNIQUE_NAME = DBSOURCE
LOG_ARCHIVE_CONFIG = 'DG_CONFIG = (DBSOURCE, DBTARGET)'
LOG_ARCHIVE_DEST_1 =
"LOCATION = / u01/app/oracle/oradata/DBSOURCE"
VALID_FOR = (ALL_LOGFILES, ALL_ROLES)
DB_UNIQUE_NAME = DBSOURCE'
LOG_ARCHIVE_DEST_2 =
"SERVICE = DBSOURCE LGWR ASYNC
VALID_FOR = (ONLINE_LOGFILES, PRIMARY_ROLE)
DB_UNIQUE_NAME = DBTARGET'
LOG_ARCHIVE_DEST_STATE_1 = ENABLE
LOG_ARCHIVE_DEST_STATE_2 = ENABLE
REMOTE_LOGIN_PASSWORDFILE = EXCLUSIVE LOCK
LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
LOG_ARCHIVE_MAX_PROCESSES = 30

I have 1 more question. I copied all db files, control files, and archived logs of the remote db DBTARGET but with the standby control file I could mount the db in the remote server but the dbname is always DBSOURCE instead of DBTARGET.

I tried running NEST to change on the site of relief the dbname but it errored out with
Copyright (c) 1982, 2007, Oracle. All rights reserved.

Connected to database DBSOURCE (DBID = 977273159)

NEST-00131: control file is not current

Change of database name failed during validation - database is intact.

Could if apply the newspaper ceased due to the DBNAME is the same on the eve of primary and physical please help

Edited by: 880215 August 25, 2011 10:02
```
dbname is still DBSOURCE instead of DBTARGET
```
The database must be DBSOURCE on both. It's the same data in two different roles, role PRINCIPAL and ROLE of the day BEFORE.

Oracle, said by the DB_UNIQUE_NAME parameter.

What I have is copy the control file before on the basis of pending data down and then copy and rename the control file that are there.

Does make sense?

I have some notes here if it helps:

http://www.Visi.com/~mseberg/data_guard_on_oracle_11_step_by_step.html

Best regards

mseberg

Pull on the RMAN backup archive logs?

Environment:
Oracle 11.2.0.3 EE on Solaris
Physical standby
I have a gap of journal archive at the moment. The missing archive logs have been saved on the primary and have not yet been transferred to waiting due to some maintenance work performed on the standby server.
The database will be able to recognize that the missing archivelog files are in the RMAN backup files, restore them and send them to the update server standby for application?
If not, will it restore manually, copy them to the standby server and save them for their application?
Thanks a lot for your help!
-gary

Were the archivelogs deleted on the primary once they have been saved? If they have been deleted on the primary, then you can:

1 manually transfer the backup to forward files

2 replace the archivelog destination configured on the eve

3 restart the managed recovery on the standby process, and the computer should be able to detect and apply the missing archivelogs.

If they have not been deleted on the primary and are always available in the archivelog directory configured, then the process of Data Guard should be able to detect and automatically fix the gap.

If you have a long interval archivelogs missing and you use + ASM, you can also try to use an incremental backup to roll forward the database pending, this article provides a good step by step: the steps for Rolling forward a standby database using RMAN incremental backup. (Doc ID 836986.1)

Kind regards
Oscar

DataGuard archiving logs go?

Hi all
9i
OEL5
I'm following the dataguard configuration document.
One of the tasks is to run:
RMAN > backup filesperset remove all 10 ArchiveLog entry;
He created an output file > piece handle = / p01/oradata/PROD/dbs/06dlfmmt_1_1
Can it remove the archive logs.
My problem is, I want to still manually restore another set of database for replication so I still need that archive logs to be applied to this database 2 (non-dataguard).
Can I use this backup of archive logs merged to manually apply on my second instance?
Thank you very much
JC

Yes, controlfile of today can be used for backup of database of yesterday. However, if you have added new data files or tablespaces from backup, they would be reflected in the controlfile but not in the backup.

Hemant K Collette

Archive log list does not sequence of current journal is awaiting data base

Hi all
So I tried waiting for database physical installation in my local vm.
I apparently completed the Setup, but I am facing a problem which I cannot understand.
OS:-Linux 6.4
Oracle version: 12.1.0.2.0
primary data: ORA12C
backup database: ORASTD
Primary database: -.
SYS@ORA12C > list of archive logs;
Database log mode Archive Mode
Active AutoArchive
Archives/u01/app/oracle/fast_recovery_area of destination
More old sequence of journal online 14
Log sequence archive 16
Current log sequence 16
SYS@ORA12C > select name, database_role, controlfile_type from v$ database;
NAME DATABASE_ROLE CONTROL
--------- ---------------- -------
ORA12C CURRENT PRIMARY
SYS@ORA12C > select the sequence #, first_time, next_time, applied from v$ archived_log;
FIRST_TIM SEQUENCE NEXT_TIME # APPLIED
---------- --------- --------- ---------
4 15 APRIL 15 APRIL 16 15 NO.
4 15 APRIL 15 APRIL 16, 15 YES
5 16 APRIL 15 APRIL 16 15 NO.
5 16 APRIL 15 APRIL 16, 15 YES
6 16 APRIL 15 APRIL 16 15 NO.
6 16 APRIL 15 APRIL 16, 15 YES
7 16 APRIL 15 APRIL 16 15 NO.
7 16 APRIL 15 APRIL 16, 15 YES
8 16 APRIL 15 APRIL 16 15 NO.
8 16 APRIL 15 APRIL 16, 15 YES
9 16 APRIL 15 APRIL 16 15 NO.
FIRST_TIM SEQUENCE NEXT_TIME # APPLIED
---------- --------- --------- ---------
9-16 APRIL 15 APRIL 16, 15 YES
10 16 APRIL 15 APRIL 16 15 NO.
10-16 APRIL 15 APRIL 16, 15 YES
11 16 APRIL 15 APRIL 16 15 NO.
12 16 APRIL 15 APRIL 16 15 NO.
13 16 APRIL 15 APRIL 16 15 NO.
11-16 APRIL 15 APRIL 16, 15 YES
12-16 APRIL 15 APRIL 16, 15 YES
13-16 APRIL 15 APRIL 16, 15 YES
14 16 APRIL 15 APRIL 16 15 NO.
15 16 APRIL 15 APRIL 16 15 NO.
FIRST_TIM SEQUENCE NEXT_TIME # APPLIED
---------- --------- --------- ---------
15 16 APRIL 15 APRIL 16 15 NO.
14-16 APRIL 15 APRIL 16, 15 YES
Waiting for the database: -.
Select the sequence #, first_time, next_time, applied from v$ archived_log;
FIRST_TIM SEQUENCE NEXT_TIME # APPLIED
---------- --------- --------- ---------
4 15 APRIL 15 APRIL 16, 15 YES
5 16 APRIL 15 APRIL 16, 15 YES
6 16 APRIL 15 APRIL 16, 15 YES
7 16 APRIL 15 APRIL 16, 15 YES
8 16 APRIL 15 APRIL 16, 15 YES
9-16 APRIL 15 APRIL 16, 15 YES
10-16 APRIL 15 APRIL 16, 15 YES
11-16 APRIL 15 APRIL 16, 15 YES
12-16 APRIL 15 APRIL 16, 15 YES
13-16 APRIL 15 APRIL 16, 15 YES
15 16 APRIL 15 16 APRIL 15 IN-MEMORY
FIRST_TIM SEQUENCE NEXT_TIME # APPLIED
---------- --------- --------- ---------
14-16 APRIL 15 APRIL 16, 15 YES
SQL > select name, database_role, controlfile_type from v$ database;
NAME DATABASE_ROLE CONTROL
--------- ---------------- -------
PHYSICAL STANDBY ORA12C STANDBY
SQL > archive logs list;
Database log mode Archive Mode
Active AutoArchive
Archives/u01/app/oracle/fast_recovery_area of destination
More old sequence of journal online 0
Log sequence to archive 0
Current log sequence 0
Now, here's my question is why the sequence of current newspapers shows 0. I tested the datas
database primary eve happens again. I'm totally out of index.
I tried to find it on google but nothing could help me until now.
Any kind of help would be very appreciated.
Thank you
Soumya

Hello

I am also testing in Data Guard 12.1 configurations.

Oracle support response is "it seems therefore that this information be removed.

So is the best way to check on the database pending:

SQL > select thread #, max(sequence#) ' last day before Seq received. "

v $ archived_log val, v$ database vdb

where val.resetlogs_change # = vdb.resetlogs_change #.

Group thread # order by 1;

SQL > select thread #, max(sequence#) ' last day before Seq applied.

v $ archived_log val, v$ database vdb

where val.resetlogs_change # = vdb.resetlogs_change #.

and val.applied in ('YES', "IN-MEMORY")

Group thread # order by 1;

concerning

With RMAN for backup, but not with the archive logs
We run a 10.2.0.4 database and the rest 11.2.0.3. All databases are on RHEL 5.7.

Our backups are via RMAN, with the data files, controlfiles and spfile saved to disk, then each day, it is copied off site to a backup server.

My question is around logs archiving and RMAN.
Our current situation is:
-We do not save the logs to archive via RMAN. for example: backup of the list of the archivelog all; gives "specification does not match backups in the repository.
-We set the archive_lag_target so archiving logs is produced every 30 minutes.
-a cron job running on a remote server runs periodically to synchronize data (rsync server) the directory of archives with a remote control.
-daily archive logs on the server host are bzip. Purge of these newspapers is scheduled for more than 3 days rman 'window of recovery '.

I'm interested in feedback as to if our strategy around archiving logs is correct or not.

Should we be backup logs archiving via RMAN? Are there potential problems with our approach?
We just kept our backups in this way the DBA in the past want to see newspapers archived as opposed to it while a backupset.

Curious to know what others are doing.
Hello

Welcome to OTN!

Archivelogs with RMAN backup is a better option. When the archives are supported by RMAN, RMAN would be aware of the backup items which are required at the time of the recovery archives. You don't have to do it manually.

On the disk space, you can delete the archives once they were saved by RMAN.

RMAN > delete any backup archivelog entry;

This supports the archivelogs and then remove the archives from the disk.

If you have a dataguard configured, you can set the deletion policy 'applied on Eve', which removes the archives as and when they are applied to the database ensures there by the management of disk space again.

RMAN > configure archivelog political of deletion to applied pending;

RMAN-03009 and ORA-01858 everything by backing up archiving logs
Hello!

Since today, I get the above errors to backup the fra tape archiving logs. I tried the following: error ORA-01858 in RMAN during backup backupset format ' / test/rman/%U'
If I manually do the backup for a client, it works!

environment:
Server: windows 2008 standard server
Oracle: 10.2.0.4.0

configuration of RMAN:
CONFIGURE RETENTION POLICY TO THE 5 DAY RECOVERY WINDOW;
CONFIGURE BACKUP OPTIMIZATION
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFAPEX. ORA'; # by default

Error log:
Recovery Manager: Release 10.2.0.4.0 - Production on Thu Oct 1 04:30 2009

Copyright (c) 1982, 2007, Oracle. All rights reserved.

connected to target database: APEX (DBID = 1331326226)
connected to the recovery catalog database

RMAN > sql 'alter system archive log current;
2 > run {}
3 > #-> drive backup
4 > backup archivelog all;
5 > # FRA-> band
6 > allocate channel ch1 type 'sbt_tape '.
7 > PARMS = "BLKSIZE = 262144, ENV = (CvClientName = ora5neu, CvInstanceName = Instance001)"; "
8 > save the recovery area.
{9 >}
10 >
SQL statement: alter system archive log current

From backup 1st October 09
Current archived log
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = devtype 81 = DISK
skip the log file archive D:\FRA\APEX\ARCHIVELOG\2009_09_10\O1_MF_1_2720_5BKO9BOL_. ARC; already saved 1 time
...
skip the log file archive D:\FRA\APEX\ARCHIVELOG\2009_10_01\O1_MF_1_2981_5D7PZDXX_. ARC; already saved 1 time
channel ORA_DISK_1: from archive newspaper backupset
channel ORA_DISK_1: specification of archive log backup set
archive log entry thread = 1 sequence = 2733 recid = 2733 stamp = 697286083
archive log entry thread = 1 sequence = 2734 recid = 2734 stamp = 697293002
archive log entry thread = 1 sequence = 2735 recid = 2735 stamp = 697293004
archive log entry thread = 1 sequence = 2856 recid = 2856 stamp = 698142602
archive log entry thread = 1 sequence = 2857 recid = 2857 stamp = 698142603
archive log entry thread = 1 sequence = 2982 recid = 2982 stamp = 699078603
archive log entry thread = 1 sequence = 2983 recid = 2983 stamp = 699078605
channel ORA_DISK_1: starting piece 1 to October 1 09
channel ORA_DISK_1: finished piece 1 to October 1 09
piece handle = D:\FRA\APEX\BACKUPSET\2009_10_01\O1_MF_ANNNN_TAG20091001T043006_5D8520K4_. Tag BKP = comment TAG20091001T043006 = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:03
Backup finished on 1st October 09

From control file and SPFILE Autobackup 1st October 09
piece handle = D:\FRA\APEX\AUTOBACKUP\2009_10_01\O1_MF_S_699078626_5D8522W8_. Comment BKP = NONE
File control finished and SPFILE Autobackup to on 1 October 09

output channel: ORA_DISK_1
allocated channel: ch1
channel ch1: sid = 81 = SBT_TAPE devtype
channel ch1: CommVault Systems for Oracle: Version 7.0.0 (BUILD76)

From backup 1st October 09
specification does not match any data file copy in the repository
skip the log file archive D:\FRA\APEX\ARCHIVELOG\2009_09_10\O1_MF_1_2720_5BKO9BOL_. ARC; already saved 4 times
...
jump key 5203 backupset; already saved 1 time
channel ch1: from archive newspaper backupset
channel ch1: specification of archive log backup set
archive log entry thread = 1 sequence = 2982 recid = 2982 stamp = 699078603
archive log entry thread = 1 sequence = 2983 recid = 2983 stamp = 699078605
channel ch1: starting piece 1 to October 1 09
channel ch1: finished piece 1 to October 1 09
piece handle = i2kqm5vv_1_1 tag = comment TAG20091001T043031 = API 2.0, MMS Version 7.0.0.76 Version
channel ch1: complete set of backups, time: 00:00:16
entry count = 4670 stamp = 699064230 = creation_time backupset 1st October 09
channel ch1: starting piece 1 to October 1 09
RMAN-03009: failure of the backup command on channel ch1 at 2009-10-01 04:31:19
ORA-01858: a non-digit character was found here where was waiting for a digital
continue other job steps, not a not working will not re-run
entry count = 4672 stamp = 699078622 = creation_time backupset 1st October 09
channel ch1: starting piece 1 to October 1 09
channel ch1: backup D:\FRA\APEX\BACKUPSET\2009_10_01\O1_MF_ANNNN_TAG20091001T043006_5D8520K4_ piece. BKP
piece handle = i0kqm5uu_1_2 comment = API Version 2.0, Version MMS 7.0.0.76
channel ch1: finished piece 1 to October 1 09
channel ch1: complete set of backups, time: 00:00:07
entry count = 4673 stamp = 699078626 = creation_time backupset 1st October 09
channel ch1: starting piece 1 to October 1 09
output channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03009: failure of the backup command on channel ch1 at 01/10/2009 04:31:35
ORA-01858: a non-digit character was found here where was waiting for a digital

Complete recovery manager.

Thanks for your help!

Ciao,.
Christian
See my note of the Support of Oracle:

Subject: RMAN backup fails with RMAN-03009 ORA-01858 ORA-01861
DOC - ID: 744047.1 Type: PROBLEM
Modification date: 20 March 2009 status: MODERATE

This could be a NLS_DATE_FORMAT / NLS_LANG questioned.

Data Guard - RMAN removing archive log

Hello
I ' v DataGuard with physical standby.
I do a backup only on the primaries. Both sites have ther separate backup systems.
I ' v FRA and configured archivelog deletion with RMAN configuration:
on primary: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
standby: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;
It works fine but I think what if scenarios and I'v qestion on best practices for backup after the transition of role management. Let's say that for some reason, as i'v in switch mode sleep for a few days and the backup will be posible to watch (now primary) database. What would be the steps/reconfiguration appropriate to do?
1 should I reconfigure RMAN?
change of new primary to: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
change back to sleep again: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;
2. make full backup

Hello

1. you can refer to the oracle documentation: http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfb.htm#CHDCFHBG

section: "all archived Redo Log deletion policy."

Document provides the best algorithm to analysis of work

You can use the CONFIGURE ARCHIVELOG DELETION POLICY BACKED UP integer TIMES TO DEVICE TYPE command to allow a policy of removal of archived newspaper. This configuration specifies that archived newspapers are eligible for deletion only when the specified number of archived log backups exist on the specified device type.

If the deletion policy is configured with the BACKED UP integer TIMES clause, then a BACKUP ARCHIVELOG , the command copy newspapers, unless integer already exist on the specified device type backups. If integer are backups of logs, then the BACKUP ARCHIVELOG command ignores the newspapers. In this way, the deletion of archived newspaper policy works as a default NOT BACKED UP integer TIMES clause on the BACKUP ARCHIVELOG command. Note that you can override the deletion policy by specifying the FORCE option on the BACKUP command.

The deletion of archived newspaper policy has also options specific to an environment Data Guard. , then RMAN can delete logs after they have been applied to all destinations remote mandatory. If you specify SHIPPED TO STANDBY , for example, then RMAN can remove log files when they were transferred to all destinations of mandatory relief.

2. the paper provides good information, just to check and decide easily based on the functionality of the database role you can configure.

It will be useful.

-Thank you

Pavan Kumar N

can't understand why an extract of the database restore fails (missing archive logs)

Dear,
I'm completely back up my database ensures every night with following statement.
full backup AS BACKUPSET COMPRESSED ORCL_FULL_STBY format database tag ' / oradata/archive/fast_recovery_area/%d_%T_%s_%p_FULL_STBY' more tag ORCL_FULL_STBY archivelog delete all entries;
I wanted to check with 'restore... Preview' if my backup is good enough to restore the database from scratch.
result = failed!
Reason:
"any backup log archived for thread 1 with sequence 65 and YVERT departure from 49020676 found to restore."
I have read the documentation oracle and articles for days, but I did not understand that even though I take online backup yesterday if I want to restore my database today I still need archival newspapers last month?
can you please review my analysis and tell me where I am doing wrong?
for example a piece from my last backup;
Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
1008 full 199.25 M DISK 00:04:44 October 8, 15
BP key: 1010 situation: AVAILABLE Tablet: YES Tag: ORCL_FULL_STBY
Item name: / oradata/archive/fast_recovery_area/QIPDB1_20151008_1057_1_FULL_STBY
List of defined backup data files 1008
Name of file LV Type cash SNA cash time
---- -- ---- ---------- --------- ----
50570723 full 1 8 October 15 /oradata/data/qipdb1/system01.dbf
4 integer 50570723 8 October 15 /oradata/data/qipdb1/users01.dbf
as you can see "Cash SNA" is 50570723 so tells me that my understanding if restore these backups I need archived newspapers on top of the YVERT.
for me the best candidate is
Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
65,25 M 1004 00:01 DRIVE: 24 OCTOBER 8, 15
BP key: 1006 situation: AVAILABLE Tablet: YES Tag: ORCL_FULL_STBY
Part name: /oradata/archive/fast_recovery_area/QIPDB1_STBY/backupset/2015_10_08/o1_mf_annnn_ORCL_FULL_STBY_c1dkfw9k_.bkp
List of newspapers archived in backup set 1004
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 79 50310555 7 OCTOBER 15 50570723 8 OCTOBER 15

BUT out of "restore...". Preview' RMAN stil tells me that
any backup log archived for thread 1 with sequence 65 and YVERT departure from 49020676 found to restore
any backup log archived for thread 1 with sequence 66 and YVERT departure from 49020693 found to restore
any backup log archived for thread 1 with sequence 67 and YVERT departure from 49020696 found to restore
any backup log archived for thread 1 with sequence 68 and YVERT departure from 49020761 found to restore
any backup log archived for thread 1 with sequence 69 and YVERT departure from 49020836 found to restore
any backup log archived for thread 1 with sequence 70 and YVERT departure from 49020919 found to restore
any backup log archived for thread 1 with sequence 71 and YVERT departure from 49021021 found to restore
any backup log archived for thread 1 with sequence 72 and YVERT departure from 49155291 found to restore
any backup log archived for thread 1 with sequence 73 and YVERT departure from 49324912 found to restore
any backup log archived for thread 1 with sequence 74 and YVERT departure from 49498102 found to restore
When I look at V$ ARCHIVED_LOG I see seems indeed to these archived logs removed for cause of "more tag ORCL_FULL_STBY archivelog delete all entries ' that they have been deleetd after saving.
and because of my retention policy and script; I remove the logs also archived backups that are more than 2 days.
S SEQUENCE # FIRST_CHANGE # NEXT_CHANGE #.
- ---------- ------------- ------------
65 49020676 49020693 D
A 49020693 OF 49020676 65
D 68 49020761 49020836
66 49020693 49020696 D
67 49020696 49020761 D
69 49020836 49020919 D
70 49020919 49021021 D
49155291 49021021 71 D
72 49155291 49324912 D
D 73 49324912 49498102
74 49498102 49632131 D
I still don't understand why rman complains of the archived logs that are for an older sequence (SNA) as my last backup
because I was assuming that the concerned newspapers archived should have already applied to these files of data, right?
My final goal is to deliver below for the case that we have lost everything.
Run {}
restore the database;
recover the database;
}
Thanks in advance,
Halit

Hi guys,.

I found the root cause and workaround

RMAN-06025 - RMAN RESTORE DATABASE OVERVIEW to the backup site asks former newspaper (Doc ID 1599013.1)
```
CAUSE Checkpoint_change# standby controlfile not refreshed properly.  BUG 15876029 - RESTORE PREVIEW ASKING OLD ARCHIVE LOG IN STANDBY DATABASE  Closed as DUPLICATE of  BUG 8740124 - CURRENT STANDBY REDO LOG GROUP SHOULD BE INCLUDED IN THE DATABASE BACKUP BY RMAN SOLUTION  1) Workaround is to recreate the standby controlfile.  OR  2) upgrade to 11.2.0.4 or above where Bug 8740124  is fixed  OR  3) check for availability of patch 8740124
```

Manually apply archive logs waiting

Similar Questions

Maybe you are looking for