Copy archive logs side Eve for manual resolution of gap
Version: 11.2 on RHEL 5.8Watch 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 standbyAn 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
Tags: Database
Similar Questions
-
Windows script to copy archive logs to another location
Hi all
I need windows script that will copy created 'Archive logs' from the default location to another location using "Time stamp".
"Time Stamp" means, the script will copy the active logs based on time current system - (less) 1 hour.
If the script will copy all archive logs that got packed before 1 hour and not the current one, or who is currently used by the database.
Is it a on a such a script of any third-party tool
Version of database 11g R2 =
Operating system = Windows 2008
Please guide me on the same.
Thank you and best regards,user592598 wrote:
In the box of SAN, there is not enough space available to store the archive logs, until the storage space is full so we need to 'MOVE' the archive logs to another location.This solution try us on a temporary basis only.
Published by: user592598 on May 26, 2010 21:46
So do the location where you want to copy your FRA archivelogs, use rman backup the archivelogs and remove them when saved.
-
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.dbfas 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 isTime 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_.bkpList 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 thatany 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 restoreWhen 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 DI 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,
HalitHi 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
-
Archiving log / nologging / direct path insert
Could you please confirm if the following are true or correct me if my interpretation is wrong:
Log mode archive 1) and logging is necessary to deal with the media recovery; It was not necessary for the recovery of the instance.
(2) IF the insert is no. APPEND mode, redo is generated, even if the table is in nologging mode and database is in log noachive mode. This recovery is necessary for recovery of the instance.
(3) direct path insert ignore cancel the generation and can jump redo generation if the object is in nologging mode.
Thank you.
In case if it is relevant, I'm using Oracle 11.2.0.3.(1) Yes, archive logs is required for media recovery.
2 and 3) even if the table is in nologging mode, it generates little recovery data dictionary and index maintenance. After a reboot of a failure - Oracle reads the online redo logs and replay any what transaction it finds in there. It's the little "roll forward." The binary redo information are used to re-read everything that did not get written to the data files. This review included refreshing the information for CANCELLATION (UNDO is protected by roll forward).After the restoration has been applied, the database is generally available for use now - and restore begins. For any transaction that was being processed when the instance failed - we have to revert his changes, roll back. We do this by treating the cancellation of all uncommitted transactions.
The database is now fully recovered.
Also read he following link
http://docs.Oracle.com/CD/B19306_01/server.102/b14220/startup.htm
http://asktom.Oracle.com/pls/asktom/f?p=100:11:0:P11_QUESTION_ID:5280714813869 -
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;
-
Problem with the archive log when you use RMAN for backup and restore (11g 2)
Hello world
Please help me solve this problem.
I'm just beginner in Oracle Database (11 g 2). Today, I had a problem, I tried to back up and restore my db by RMAN. I delete all the files in /u01/app/oracle/oradata/orcl / * , then I restore them easily, but the point is I have a table, I can restore Hungarian, but cannot restore anything ranks in it (something wrong with step restore database). I'll tell the detail below.
-First, I create a 'Day' with command table create table hr.day (varchar (20)) day. Then I backup complete by this:run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_FULL_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 0 tag 'DB_FULL' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_FULL' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}
D ' other hand, I have insert 'Monday' to table. then do an incremental backup by this:run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_INC_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 1 tag 'DB_INC' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_INC' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}Repeat 7 times (Monday-> Saturday). And I got these files:
[oracle@rac ~]$ ls -l /u01/backup/
total 400280
-rw-r----- 1 oracle oinstall 10158080 Jan 20 07:23 c-1428943247-20160120-01
-rw-r----- 1 oracle oinstall 10158080 Jan 20 08:04 c-1428943247-20160120-02
-rw-r----- 1 oracle oinstall 10158080 Jan 20 08:05 c-1428943247-20160120-03
-rw-r----- 1 oracle oinstall 10158080 Jan 20 08:06 c-1428943247-20160120-04
-rw-r----- 1 oracle oinstall 10158080 Jan 20 08:08 c-1428943247-20160120-05
-rw-r----- 1 oracle oinstall 10158080 Jan 20 08:08 c-1428943247-20160120-06
-rw-r----- 1 oracle oinstall 10158080 Jan 20 08:09 c-1428943247-20160120-07
-rw-r----- 1 oracle oinstall 10158080 Jan 20 08:32 c-1428943247-20160120-08
-rw-r----- 1 oracle oinstall 296337408 Jan 20 07:23 DB_FULL_ORCL_20160120_s89_p1
-rw-r----- 1 oracle oinstall 1130496 Jan 20 07:23 DB_FULL_ORCL_20160120_s90_p1
-rw-r----- 1 oracle oinstall 2266624 Jan 20 07:23 DB_FULL_ORCL_20160120_s91_p1
-rw-r----- 1 oracle oinstall 4073984 Jan 20 07:23 DB_FULL_ORCL_20160120_s92_p1
-rw-r----- 1 oracle oinstall 11201536 Jan 20 07:23 DB_FULL_ORCL_20160120_s93_p1
-rw-r----- 1 oracle oinstall 1130496 Jan 20 08:05 DB_INC_ORCL_20160120_s100_p1
-rw-r----- 1 oracle oinstall 146944 Jan 20 08:05 DB_INC_ORCL_20160120_s101_p1
-rw-r----- 1 oracle oinstall 884736 Jan 20 08:06 DB_INC_ORCL_20160120_s103_p1
-rw-r----- 1 oracle oinstall 1130496 Jan 20 08:06 DB_INC_ORCL_20160120_s104_p1
-rw-r----- 1 oracle oinstall 82432 Jan 20 08:06 DB_INC_ORCL_20160120_s105_p1
-rw-r----- 1 oracle oinstall 294912 Jan 20 08:07 DB_INC_ORCL_20160120_s107_p1
-rw-r----- 1 oracle oinstall 1130496 Jan 20 08:07 DB_INC_ORCL_20160120_s108_p1
-rw-r----- 1 oracle oinstall 18944 Jan 20 08:08 DB_INC_ORCL_20160120_s109_p1
-rw-r----- 1 oracle oinstall 155648 Jan 20 08:08 DB_INC_ORCL_20160120_s111_p1
-rw-r----- 1 oracle oinstall 1130496 Jan 20 08:08 DB_INC_ORCL_20160120_s112_p1
-rw-r----- 1 oracle oinstall 131584 Jan 20 08:08 DB_INC_ORCL_20160120_s113_p1
-rw-r----- 1 oracle oinstall 647168 Jan 20 08:09 DB_INC_ORCL_20160120_s115_p1
-rw-r----- 1 oracle oinstall 1130496 Jan 20 08:09 DB_INC_ORCL_20160120_s116_p1
-rw-r----- 1 oracle oinstall 8704 Jan 20 08:09 DB_INC_ORCL_20160120_s117_p1
-rw-r----- 1 oracle oinstall 2203648 Jan 20 08:04 DB_INC_ORCL_20160120_s95_p1
-rw-r----- 1 oracle oinstall 1130496 Jan 20 08:04 DB_INC_ORCL_20160120_s96_p1
-rw-r----- 1 oracle oinstall 1899008 Jan 20 08:04 DB_INC_ORCL_20160120_s97_p1
-rw-r----- 1 oracle oinstall 327680 Jan 20 08:05 DB_INC_ORCL_20160120_s99_p1And
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
80 B 0 A DISK 20-JAN-16 1 1 YES DB_FULL
81 B 0 A DISK 20-JAN-16 1 1 YES DB_FULL
82 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_FULL
83 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_FULL
84 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_FULL
85 B F A DISK 20-JAN-16 1 1 NO TAG20160120T072332
86 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
87 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
88 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_INC
89 B F A DISK 20-JAN-16 1 1 NO TAG20160120T080440
90 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
91 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
92 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_INC
93 B F A DISK 20-JAN-16 1 1 NO TAG20160120T080545
94 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
95 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
96 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_INC
97 B F A DISK 20-JAN-16 1 1 NO TAG20160120T080657
98 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
99 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
100 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_INC
101 B F A DISK 20-JAN-16 1 1 NO TAG20160120T080801
102 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
103 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
104 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_INC
105 B F A DISK 20-JAN-16 1 1 NO TAG20160120T080844
106 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
107 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
108 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_INCMy configuration of rman:
RMAN> show all;
RMAN configuration parameters for database with db_unique_name ORCL are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/backup/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/u01/backup/backup_df%t_s%s_s%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome/dbs/snapcf_orcl.f'; # default- Thirdly, i removed all file in /u01/app/oracle/oradata/orcl/*. then restore control file from the newest backup control file (saturday backup) + restore database. Seem nothing's wrong here.
RMAN> restore controlfile from '/u01/backup/c-1428943247-20160120-08';
Starting restore at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=18 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=20 device type=DISK
channel ORA_DISK_2: skipped, AUTOBACKUP already found
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:09
output file name=/u01/app/oracle/oradata/orcl/control01.ctl
output file name=/u01/app/oracle/flash_recovery_area/orcl/control02.ctl
Finished restore at 20-JAN-16
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
released channel: ORA_DISK_2
RMAN> restore database;
Starting restore at 20-JAN-16
Starting implicit crosscheck backup at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=20 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=18 device type=DISK
Crosschecked 29 objects
Finished implicit crosscheck backup at 20-JAN-16
Starting implicit crosscheck copy at 20-JAN-16
using channel ORA_DISK_1
using channel ORA_DISK_2
Finished implicit crosscheck copy at 20-JAN-16
searching for all files in the recovery area
cataloging files...
no files cataloged
using channel ORA_DISK_1
using channel ORA_DISK_2
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl/users01.dbf
channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_FULL_ORCL_20160120_s89_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_FULL_ORCL_20160120_s89_p1 tag=DB_FULL
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:15
Finished restore at 20-JAN-16-Fourth, the problem here, I got the database;
.. .every oky until this line...starting media recovery
channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=15
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_INC_ORCL_20160120_s117_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_INC_ORCL_20160120_s117_p1 tag=ARCL_BKP_INC
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u01/app/oracle/flash_recovery_area/ORCL/archivelog/2016_01_20/o1_mf_1_15_c9xsyx9k_.arc thread=1 sequence=15
unable to find archived log
archived log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/20/2016 08:50:22RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 1205841
The error said that it is impossible to find the archived log thread = 1 sequence = 1. Then I check it with this command always there (oh, I'm wrong?)RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
82 2.16M DISK 00:00:00 20-JAN-16
BP Key: 82 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_FULL
Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s91_p1
List of Archived Logs in backup set 82
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 1 1154833 20-JAN-16 1177422 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
83 3.88M DISK 00:00:00 20-JAN-16
BP Key: 83 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_FULL
Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s92_p1
List of Archived Logs in backup set 83
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 1 1162729 20-JAN-16 1188784 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
84 10.68M DISK 00:00:01 20-JAN-16
BP Key: 84 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_FULL
Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s93_p1
List of Archived Logs in backup set 84
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 2 1177422 20-JAN-16 1201833 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
88 1.81M DISK 00:00:01 20-JAN-16
BP Key: 88 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC
Piece Name: /u01/backup/DB_INC_ORCL_20160120_s97_p1
List of Archived Logs in backup set 88
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 3 1201833 20-JAN-16 1204844 20-JAN-16
1 4 1204844 20-JAN-16 1204893 20-JAN-16
1 5 1204893 20-JAN-16 1204958 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
92 143.00K DISK 00:00:00 20-JAN-16
BP Key: 92 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC
Piece Name: /u01/backup/DB_INC_ORCL_20160120_s101_p1
List of Archived Logs in backup set 92
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 6 1204958 20-JAN-16 1205034 20-JAN-16
1 7 1205034 20-JAN-16 1205253 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
96 80.00K DISK 00:00:00 20-JAN-16
BP Key: 96 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC
Piece Name: /u01/backup/DB_INC_ORCL_20160120_s105_p1
List of Archived Logs in backup set 96
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 8 1205253 20-JAN-16 1205354 20-JAN-16
1 9 1205354 20-JAN-16 1205433 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
100 18.00K DISK 00:00:00 20-JAN-16
BP Key: 100 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC
Piece Name: /u01/backup/DB_INC_ORCL_20160120_s109_p1
List of Archived Logs in backup set 100
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 10 1205433 20-JAN-16 1205519 20-JAN-16
1 11 1205519 20-JAN-16 1205559 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
104 128.00K DISK 00:00:00 20-JAN-16
BP Key: 104 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC
Piece Name: /u01/backup/DB_INC_ORCL_20160120_s113_p1
List of Archived Logs in backup set 104
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 12 1205559 20-JAN-16 1205624 20-JAN-16
1 13 1205624 20-JAN-16 1205739 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
108 8.00K DISK 00:00:00 20-JAN-16
BP Key: 108 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC
Piece Name: /u01/backup/DB_INC_ORCL_20160120_s117_p1
List of Archived Logs in backup set 108
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 14 1205739 20-JAN-16 1205796 20-JAN-16
1 15 1205796 20-JAN-16 1205840 20-JAN-16
If i ignore it and open the database, just my table in full backup come back but rows was not restored. I'm sure the problem is my archive log backup but i don't know how to solve it. Plz help me.Sorry for a long post.
> 1 and from the 1205841 SNA sequence
The SCN that indicates Oracle is above the range of SNA that you have in the ArchiveLog backups for sequence 1 to 15 (15 sequence ends at 1205840).
The message
channel ORA_DISK_1: restoring archives Journal
Archives journal thread = 1 sequence = 15
channel ORA_DISK_1: backup/u01/backup/DB_INC_ORCL_20160120_s117_p1 piece reading
channel ORA_DISK_1: piece handle = / u01/backup/DB_INC_ORCL_20160120_s117_p1 tag = ARCL_BKP_INC
indicates that he has restored the sequence up to 15
You can check the log file alert database instance for messages on the fact of recovery.
He is now asking sequence #1 it seems you did a RESETLOGS after sequence #15.
Note: If you have NOT issued a COMMIT after the line is INSERTED in the table 'Day', the recovery of the database will have no * transactions * to retrieve. An uncomitted transaction is cancelled.
Hemant K Collette
-
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 /";
(c) Once catalogued recovery logs archived, you can start the recovery media
change recover managed standby database disconnect log file using current;
or
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
-
A copy of recovery/db + archive logs
Hi champions.
There is a confusion in the recovery of a database. Version 10g.
I have a hot (using the copy command) of a database backup (mode of journal archive) I took to 22.00.00 on Sunday.
Now, my database is up and running Monday, Tuesday, Wednesday in archive log mode. Since the last backup .and (Sunday 10 pm) my database got crashed Wednesday 14.00 completely lost everything (CDR files) archive logs only is with me, I have the newspaper archive...
Can I recover my database using the backup from Sunday + newsletter archive until it crashed.
Kind regards
Shitesh ShuklaIf you have an old backup of the controlfile, you use restore database with backup cotrolfile to cancel. Backup Controlfile as of old, he would keep asking for the archivelogs to provide for backup if you need to cancel the recovery.
HTH
Aman... -
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';
-
Retention policy for archive logs.
Retention policy is set to "REDUNDANCY 2".
We do the complete disk backup without archive logs at 12:00.
After that, we make full backup with newspapers to archive tape at 18:00.
RMAN will consider newspapers to check-in after 12:00 as obsolete as it is backed up to tape?
Thank you.
REDUNDANCY applies only to the data files and control files. For archiving logs, there are POLICY of DELETE ARCHIVELOG. But "remove obsolete" won't use POLICY of DELETE ARCHIVELOG, so archiving logs should be removed separately if they meet this policy.
-
How to apply logs archiving missing on Eve db
Hello
I had to stop physical standby db 4 hours to move to another location.
After the reboot it seems there are 4 missing archive logs and I think that because of them other newspapers of archiving is not applied.
SYS@standbydb AS SYSDBA > select * from V$ ARCHIVE_GAP; -on the elementary level, there is no selected line.
THREAD # LOW_SEQUENCE # HIGH_SEQUENCE #.
---------- ------------- --------------
1 36226 36230
Standby: SELECT THREAD #, SEQUENCE #, APPLIED from V$ ARCHIVED_LOG if application = "NO";
1 36231 NO.
- - -
1 36247 NO.
36226 is the last with the LETTER: YES
I have as a result of errors in the GRID CONTROL DATA GUARD STATE option
ORA-16783: could not resolve the deficit for the database standby_db
ORA-16629: database shows a different level of protection the protection mode
Please help resolve this gap of archive...
Thank you very much
Best regards
Thank you very much for your contributions.
I solved the gap newspaper archive. restore sequence archivelog 36227, I have given that his backup was introduced. stopped and started new standby database and then gap resolved automatically.
Best regards
-
Secondary destination for archived logs
Version: 10.2, 11.1, 11.2
Occasionally, we get "archiver error" on our production because of our satiety LOG_ARCHIVE_DEST_1 DBs. How can I have a secondary for archiving logs location where my position "primary" (LOG_ARCHIVE_DEST_1) saturates?
I think that LOG_ARCHIVE_DEST_2 is reserved for archiving to Dataguard standby DB logs in which specify you the day before tns input using the parameter of the shipping SERVICE.
Can I specify LOG_ARCHIVE_DEST_3 as my secondary site in case LOG_ARCHIVE_DEST_1 saturates? -What is LOG_ARCHIVE_DEST_n meant for? Even though the documentation says that you can have up to 10 locations, I'm confused, if they are intended to store copies of archive logs multiplex? This is not what I'm looking for?>
Hi Tom,
Occasionally, we get "archiver error" on our production because of our satiety LOG_ARCHIVE_DEST_1 DBs. How
can I have a secondary for archiving logs location where my position "primary" (LOG_ARCHIVE_DEST_1) saturates?From [https://forums.oracle.com/forums/thread.jspa?threadID=1033460 url] here:
LOG_ARCHIVE_DEST_STATE_n = ALTERNATE
To specify the nth destination metnioned in the LOG_ARCHIVE_DEST_n as a destination alternative.Look at "replacement" [url http://docs.oracle.com/cd/E14072_01/server.112/e10595/archredo004.htm] here - if all else fails, read the docco ;)
Also check out here [url http://docs.oracle.com/cd/B10501_01/server.920/a96521/archredo.htm].
HTH,Paul...
-
RMAN backup for lack of archive log - Urgent
Dear all,
How to take backup in oracle rman for lack of logseq at logseq archiving log.
Please help me urgent.
Thank you
ManasThe SNA method before roll is easiest to get your sleep in harmony rather than completely rebuild.
The RCS on primary continues to rise and if the archives get generated on primary at a regular stage, would be late the night before by a huge margin.
If there is a gap of newspaper caused lack of archives and his backup is not available, then I'd rather go with the Roll Forward YVERT method.
-
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);
-
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
Maybe you are looking for
-
Y460p Fn + F6 button and volume button does not
Hi, currently only my mouse button disable and next to my slideNav buttons, shortcut keys do not work. Only my Fn + F6 button does not work, but my other keys work. I tried to update and reinstall the drivers for my mouse and the lenovo power managem
-
Pavilion G7-1070US: update Realtek 4313!
Someone has already tried Intel Centrino Advanced-N 6230 631956-001 in the Pavilion G7-1070, if so he worked and he 802.1 a/b/g/n
-
When I go to the "network and sharing" and try to disable file sharing, it automatically turns on the Windows Firewall. I want to be able and disable file sharing and disable the Windows Firewall (I use Norton 360 firewall). Any ideas? Thank you.
-
Hi allOur portfolio currently has 2 records of entry. 1 POINT 2. PRICE. For each element in the ELEMENT file, there may be multiple records of price in the PRICE file. It may be a situation where a particular item does not any price all (items expire
-
Buenas tardes. Tengo mas of 20 licenses a number desde el ano mid 2013 y no puedo access has ellas y tampoco puedo ponerme contact don't con nadie para what me can help.No to if of that estoy hablando the empresa in su dia pay 5000 euros o estoy perd