Lost archive log?

Similar Questions

• Backup the database with archiving logs lost

  How can I get a backup of the database when all archive logs have been lost?

  So, it looks that you use RMAN to back up, since all the archivelog went. You can do

  RMAN> crosscheck archivelog all;
  
  RMAN> delete archivelog all;
  

  then make a backup.

• 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
  

• Oracle database archive logs

  Hi all

  I searched the Oracle and Internet Documents. It is really hard to get information on the management of the archive Log, so I thought to post it here:

  Now, our Database 9i (EBS 11.5.x) was in no archive mode, so I allowed him to archive mode.

  Edit the pfile $ORACLE_HOME/admin/SID/pfile who will be /oracle/proddb/9.2.0/dbs/initPROD.ora

  ############################

  # Archive Log Destinations-benr(10/15/04)

  ############################

  Log_archive_dest_1 = ' location = / Uncordon / archive.

  log_archive_start = TRUE

  
  

  then connect to the database

  
  

  
  

  
  

  
  

  SQL > shutdown normal;

  SQL > startup mount exclusive;

  SQL > alter system set log_archive_start = TRUE scope = spfile;
  SQL > alter system set log_archive_dest_1='LOCATION= /oracle/archivelog ' scope=both;
SQL > alter archivelog database;
  SQL > CHANGE the START of the SYSTEM ARCHIVE LOG;
  SQL > alter database open;
  SQL > alter system archive log all;
  SQL > change the start of the archive log system;
  SQL > archive log start;

  
  

  The next day, I checked the location of archive and sparked an archive of 1 GB even if there is no activity on the database.

  root@test4:/oracle/archivelog>ls
  1_844.dbf   1_862.dbf   1_880.dbf   1_898.dbf   1_916.dbf   1_934.dbf
  1_845.dbf   1_863.dbf   1_881.dbf   1_899.dbf   1_917.dbf   1_935.dbf
  1_846.dbf   1_864.dbf   1_882.dbf   1_900.dbf   1_918.dbf   1_936.dbf
  1_847.dbf   1_865.dbf   1_883.dbf   1_901.dbf   1_919.dbf   1_937.dbf
  1_848.dbf   1_866.dbf   1_884.dbf   1_902.dbf   1_920.dbf   1_938.dbf
  1_849.dbf   1_867.dbf   1_885.dbf   1_903.dbf   1_921.dbf   1_939.dbf
  1_850.dbf   1_868.dbf   1_886.dbf   1_904.dbf   1_922.dbf   1_940.dbf
  1_851.dbf   1_869.dbf   1_887.dbf   1_905.dbf   1_923.dbf   1_941.dbf
  1_852.dbf   1_870.dbf   1_888.dbf   1_906.dbf   1_924.dbf   1_942.dbf
  1_853.dbf   1_871.dbf   1_889.dbf   1_907.dbf   1_925.dbf   1_943.dbf
  1_854.dbf   1_872.dbf   1_890.dbf   1_908.dbf   1_926.dbf   1_944.dbf
  1_855.dbf   1_873.dbf   1_891.dbf   1_909.dbf   1_927.dbf   1_945.dbf
  1_856.dbf   1_874.dbf   1_892.dbf   1_910.dbf   1_928.dbf   1_946.dbf
  1_857.dbf   1_875.dbf   1_893.dbf   1_911.dbf   1_929.dbf   1_947.dbf
  1_858.dbf   1_876.dbf   1_894.dbf   1_912.dbf   1_930.dbf   lost+found
  1_859.dbf   1_877.dbf   1_895.dbf   1_913.dbf   1_931.dbf   test.txt
  1_860.dbf   1_878.dbf   1_896.dbf   1_914.dbf   1_932.dbf
  1_861.dbf   1_879.dbf   1_897.dbf   1_915.dbf   1_933.dbf
  

  Question

  1. How can I delete old logs archiving without using RMAN?

  2. How should I know which Archives connects to keep and delete?

  3. is there a way to know why the database generates so many newspapers to check-in?

  Hello

  Yes, you must keep this archive. You can schedule the job to compress files to archive (record use of space) and move it to another place as a backup.

  You can schedule both COLD backup once a week, in this case it is scabies archive for a week.

  HTH

• RMAN-06059: expected archived log not found

  DB version: 11.1.0.7
  Operating system: Solaris 10
  
  Our cron job RMAN has met the following error.
  -First save attempt (complete bkp more archive log) done by connecting to the catalog

  Starting backup at 14-MAR-12
  current log archived
  released channel: ch00
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of backup plus archivelog command at 03/14/2012 08:09:58
  RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
  ORA-19625: error identifying file +PQWSP_ARCH01/pqwsp_arch/pqwsp_26530_1_764525298.arc
  ORA-17503: ksfdopn:2 Failed to open file +PQWSP_ARCH01/pqwsp_arch/pqwsp_26530_1_764525298.arc
  ORA-15173: entry 'pqwsp_26530_1_764525298.arc' does not exist in directory 'pqwsp_arch'

  Because I didn't share RMAN catalog schema password, I used the control as a catalog file and run the CROSSCHECK command.
  
  -Use the control as a catalog file

  $ rman target /
  
  Recovery Manager: Release 11.1.0.7.0 - Production on Wed Mar 14 09:45:59 2012
  
  Copyright (c) 1982, 2007, Oracle.  All rights reserved.
  
  connected to target database: PQWSP (DBID=1638594930)
  
  RMAN> crosscheck archivelog all;
  
  using target database control file instead of recovery catalog
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID=429 instance=pqwsp1 device type=DISK
  validation succeeded for archived log
  archived log file name=+PQWSP_ARCH01/pqwsp_arch/pqwsp_26563_1_764525298.arc RECID=19019 STAMP=777888587
  validation succeeded for archived log
  archived log file name=+PQWSP_ARCH01/pqwsp_arch/pqwsp_26564_1_764525298.arc RECID=19022 STAMP=777890270
  validation succeeded for archived log
  .
  .
  .
  .
  .
  
  Crosschecked 14 objects

  Cannot find objects expired in the output above. I had * "validation succeeded" * message to arch all newspapers.
  
  So I ran a

  BACKUP ARCHIVELOG ALL DELETE ALL INPUT;

  and this backup was successful.
  
  No idea why the first attempt failed when there were not all logs archived expired? If I run the command of OVERLAP by connecting to the catalog, I could find out of date newspapers?

  No idea why the first attempt failed when there were not all logs archived expired?
  this case is not releated archivelog expired, however it seems the requested archivelog 26530 isn't available on destinationas, that it can be removed manually or another taking backup operation the backup and deleted if the execution of the whole.

  crosscheck updated detail that its not available for backup... Check the output of you overlap cmd to 26530 archivelog.

  Thank you
  Tylay Singh

• 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 Shukla

  If 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...

• DB Back at a specific time with archiving logs (up to cancel or time?)

  I'll try to be as clear as possible with my goals and limits of the system, I'm working with:
  
  1. we have a test instance of our Oracle database I want to be able to update with data from the instance of production at any time, without having to close the production database or tablespaces in backup mode to warm.
  
  2. the two systems are HP Itanium boxes with different numbers of processors and RAM. These differences have been taken into account in the file init.ora for instances of the DB.
  
  3. test and production instances use a SAN to maintain the following file systems: ora_redo1, ora_redo2, ora_archlog, oradata10g. The test instance uses snapshots SAN (HP EVA SAN series) the production file systems into the data when necessary. The problem is that the single window to do it is when the production system is down for maintenance every night, which is about a 20 minute period. I want to escape this limitation.
  
  I do use the aforementioned SAN HP to take snapshots of filesystems on the production system. I'm doing this, while the production DB is running. I then import these snapshots in the test system, run a fsck to the integrity of system files, and then start the Oracle instance as follows:
  
  Startup mount
  
  Then I run the following query, I found online to determine the current redo log:
  Select Member from v$ logfile lf, v$ log l where l.status = 'CURRENT' and lf.group #= l.group #;
  
  Then I try to run a recovery as follows:
  recover database using backup controlfile until cancel;
  
  When you are prompted, enter the path to the first of the current redo logs and press ENTER. After waiting, sometimes it is said that the recovery is completed, other times it stops saying there was an error and that several files are required to standardize the DB.
  
  I took the road above because to do a recovery until the time (which is what I really want to do) kept invited me for the next archiving log in the sequence that did not exist when I took the picture of SAN. This is my back up to the order of time:
  
  recover database until time ' yyyy-mm - dd:hh:mm:ss using backup controlfile;
  
  What I want to do is to take the SAN snapshot and then retrieve the database about a minute before the snapshot by using the archive logs. I don't want to use RMAN, since it seems like overkill for this purpose. A simple recovery to a specific point in time seems to be all that is needed and I archive logs which, I suppose, SHOULD help me get there. Even if I lose the value of the last hour of trading, I could live with that. But my tests affect the recovery time even 12 hours sooner more resulted in a command prompt to the next, no archivelog.
  
  I note also that I even tried to copy the next log archiving on once there is and the recovery would then invite me to the next archive log! I recognize now that I know really much about Oracle or DBs, but it's my duty to try and make it possible to "Refresh" the DB test with the latest data with no impact on production DB.
  
  The reason why I want to use the hot backup mode, it is that I don't know the other DB schema that there probably 58 or more storage spaces. The goal is to use SAN snapshots for their speed instead of having to take RMAN files and copy them to the test instance. I don't know that I'm not the only person who has already tried that. But most of what I found online made reference on RMAN, hot backup mode, or downtime. The first two take advantage of SAN snapshots for a quick exchange of all Oracle file systems, and I can't afford downtime other than this window during the night. Is there a reason that did not retrieve it in time even if I archive logs?
  
  One last point. Recover until cancel actually worked a few times, but it seems to be sporadic. Probably has something to do with what was going on on the production DB when I created the SAN snapshots. In fact, I thought I had a solution with recover until cancel last week until he failed three times in a row.

  As I've mentioned before, I highly recommend setting the database in BACKUP mode.

  You can see a collection of papers to the
  http://www.Oracle.com/technology/deploy/availability/htdocs/oscp_papers.html
  Unfortunately, Oracle stopped the Oracle storage compliance program and now he leaves vendors to certify their memory and their file system. The documents on the site of the OSCP are now "old."

  Each storage provider has also published articles. I worked with snapshot / SnapClone / SnapView / technologies ShadowImage EMC CLARiiON, Hitachi Lightning, IBM ESS, etc. of NetApp. Only the EMC engineer did not recommend the BACKUP mode. However, when you test the EMC under high concurrency, we found corrupt index when we used the image of the snapshot. I returned to the EMC site and downloaded a specified document that we had to use the BACKUP mode and SUSPEND / SUMMARY - and why said. The main lines were "However, the operation of fracturing the clones or from sessions of snapshot with multiple devices is not atomic. Particular periods may exist as well and all of the Oracle files being backed up can seem to have lost the required I/O order sequencing. ». So it really depends on the technology. The engineer later confirmed that it was a requirement on the particular type of storage we were using, but not on the DMX class (or something like that - I don't remember all the details of a previous task a few years ago).

  (White papers of all other providers also included BACKUP mode).

  Contact the vendor for their own white papers.

  Hemant K Collette
  http://hemantoracledba.blogspot.com

• 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

• 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_p1


  And
  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_INC

  My 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:22
RMAN-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

• DataGuard slowed db: generating the archive logs?

  Hello

  I have a 11.2.0.4 db using Data Guard to play with. I just set up and could do a failover and vice versa.

  However I have noticed there are great number of generated archive logs, one every minute. As it is an empty database, I wonder why?

  No recovery is generated by sessions:

  Select v$ session.sid, username, value/1024/1024 redo_size_MB
  v $ sesstat, v$ statname of v$ session
  where v$ sesstat. STATISTICS of # = v$ statname. STATISTICS FROM #.
  and v$ v = session.sid $sesstat.sid
  and name = "redo size."
  and > 0
  and username is not null
  2 3 4 5 6 7 8 value order;

  no selected line

  Logs are generated on the disc:

  -rw - r - 1 oracle oinstall K 77, 30 Nov 12:06 o1_mf_1_1119_c5rcg7b1_.arc

  -rw - r - 1 oracle oinstall 35K 30 Nov 12:07 o1_mf_1_1120_c5rcj3gh_.arc

  -rw - r - 1 oracle oinstall 103K 30 Nov 12:08 o1_mf_1_1121_c5rckzo0_.arc

  -rw - r - 1 oracle oinstall 36K 30 Nov 12:09 o1_mf_1_1122_c5rcmvo2_.arc

  -rw - r - 1 oracle oinstall 35K 30 Nov 12:10 o1_mf_1_1123_c5rcoqry_.arc

  -rw - r - 1 oracle oinstall 35K 30 Nov 12:11 o1_mf_1_1124_c5rcqmxm_.arc

  -rw - r - 1 oracle oinstall 35K 30 Nov 12:12 o1_mf_1_1125_c5rcsj2j_.arc

  -rw - r - 1 oracle oinstall 35K 30 Nov 12:13 o1_mf_1_1126_c5rcvd3t_.arc

  Someone has an idea of what to check?

  Concerning

  3

  Something abnormal. If this a test box, are you allowed to bounce the DB?

  If so, give it a shot and try.

  -Jonathan Rolland

• 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

• Multiplex Archived Logs

  With the help of 11.2.0.4.0

  I am trying to mux the newspapers archived (duplicate); However, do not know if I'm doing things.

  I followed this http://docs.oracle.com/cd/B28359_01/server.111/b28310/archredo004.htm and made the following

  LOG_ARCHIVE_DEST_1 = 'LOCATION=Z:\FlashRecoveryArea\archlogs\'

  LOG_ARCHIVE_DEST_2 = 'LOCATION=\\backupserver\archlogs_location'

  I thought I was doing the right thing with handwritten copies in both places when I run

  "alter newspaper archive of the current system. However, to take a closer look, looks like maybe it's different.

  Z:\FlashRecoveryArea\archlogs has the logs archived LOG_1_68_xxxx. ARC and LOG_1_71_xxxx. ARC

  \\backupserver\archlogs_location archived LOG_1_69_xxxx newspapers. ARC, LOG_1_70_xxxx. ARC and LOG_1_71_xxxx. ARC

  I misunderstood the document? This is not duplication of archived newspapers?

  Thank you

  I think your problem is the backup archivelog and remove that happens at the same time as the journal was cheating (i.e. newspaper is too slow).

  Just do this - see crossouts and "BOLD" text 'everything '...

  RUN

  {

  SQL "alter session set nls_date_format = 'MON-DD-YYYY HH24:MI:SS' ';"

  overlap archivelog all;

  cross-checking of backup;

  SQL 'alter system archive log current';

  SQL 'alter system archive log current';

  backup

  (database FORMAT '\backupserver\full\FULLBKUP_%d.DBID%I.%T.%s.%p.rman')

  more all archivelog delete all input FORMAT '\\backupserver\full\ARCHLOGBKUP_%d.%e.DBID%I.%T.%s.%p.rman' TAG = "FULLBKUP_PLUS_ARCHLOG";

  window recovery obsolete report of 5 days;

  delete noprompt obsolete recovery window of 5 days;

  SPFile FORMAT '\\backupserver\full\SPFILE_BKUP_%d.DBID%I.%T.%s.%p.rman' label backup = "BKUP_SPFILE";

  SQL 'alter controlfile backup database path as "\\backupserver\full\ctlfilePROD.txt" RE-USE";

  SQL "' create pfile =" \\backupserver\full\pfile_PROD.ora "of spfile"; "

  SQL 'alter system archive log current';

  SQL 'alter system archive log current';

  backup FORMAT '\\backupserver\full\ARCHLOGBKUP_%d.%e.DBID%I.%T.%s.%p.rman' archivelog delete all all the entries TAG = "BKUP_ARCHLOG";

  backup current controlfile FORMAT '\\backupserver\full\CTLFILE_BKUP_%d.DBID%I.%T.%s.%p.rman' TAG = "BKUP_CTLFILE";

  }

• Recovery media - cannot find the archived log

  Oracle 10g Release 2

  Database works in mode noarchive - isn't my choice, so I'm stuck with it.

  SQL> select startup_time,status,database_status from v$instance;
  
  STARTUP_T STATUS       DATABASE_STATUS
  --------- ------------ -----------------
  20-AUG-15 MOUNTED      ACTIVE
  
  SQL> alter database open;
  alter database open
  *
  ERROR at line 1:
  ORA-01113: file 2 needs media recovery
  ORA-01110: data file 2: '/ads/database06/oracle/oradata/ODB1/UNDOTBS03.dbf'
  
  SQL> recover datafile '/ads/database06/oracle/oradata/ODB1/UNDOTBS03.dbf';
  ORA-00279: change 24699944499 generated at 08/08/2015 01:07:04 needed for thread 1
  ORA-00289: suggestion :
  /oracle/product/10.2.0/flash_recovery_area/ODB1/archivelog/2015_08_21/o1_mf_1_698472_%u_.arc
  ORA-00280: change 24699944499 for thread 1 is in sequence #698472
  
  Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
  
  ORA-00308: cannot open archived log
  '/oracle/product/10.2.0/flash_recovery_area/ODB1/archivelog/2015_08_21/o1_mf_1_698472_%u_.arc'
  ORA-27037: unable to obtain file status
  SVR4 Error: 2: No such file or directory
  Additional information: 3
  
  $ cd /oracle/product/10.2.0/flash_recovery_area/ODB1/archivelog/2015_08_21
  
  $ ls o1_mf_1_698472_%u_.arc
  o1_mf_1_698472_%u_.arc: No such file or directory
  
  The entire directory is empty.
  

  There is no data for August 21, 2015, the database is offline for a few days.

  The database has been cloned by the system administrator, so nobody was on this database. New server.

  orclrunner wrote:

  That was my thought as well. They have made a copy ' hot' all the files. I think they should have stop the database before copying files.

  a ' hot' copy can succeed but each tablespace must have been in online BACKUP before doing the copy of OS files.

  With DB mode noarchive, a copy hot may or may not succeed according to the DML activity & duration of the COPY

  It's better to STOP NOW before copy of OS

• 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