How do duplex CARS DB archiving logs?

Similar Questions

• How to control too many archived log generation

  Hello
  
  This is one of the interview questions,
  
  I answered it. Just as what the answer to this.
  
  How can we control the excessive generation of archived log?
  
  Thank you

  Hello;

  Archive is to ensure the recovery of the database, which can be done with NOLOGGING who does not put it at risk? (Data copy from one table to the other, for example).

  Excessive diagnosis Redo generation - limited with Nologging [ID 199298.1]

  Best regards

  mseberg

• Current archive log has been deleted, how to recover using the previous archive log?

  Hello
  
  My current log sequence #819 and it has been deleted and no other choice to get it back and I have previous newspapers archived with sequences #814 à 818.
  
  When I start my database is to show that the use ' MUST USE RESETLOGS or NORESETLOGS option of database open, then I used the command
  
  SQL > ALTER DATABASE OPEN RESETLOGS;
  ALTER DATABASE OPEN RESETLOGS
  *
  ERROR on line 1:
  ORA-01113: file 1 needs media recovery
  ORA-01110: data file 1: ' E:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01. DBF'
  
  SQL > alter database recover;
  ALTER database recover
  *
  ERROR on line 1:
  ORA-00283: cool cancelled due to errors
  ORA-01610: recovery using BACKUP CONTROLFILE option must be
  SQL > alter database recovery using backup controlfile;
  change the database recovery using backup controlfile
  *
  ERROR on line 1:
  ORA-00279: change 8433746 September at 15/01/2013 19:51:59 needed to screw 1
  ORA-00289: suggestion:
  E:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_01_16\O1_MF_1_819_
  
  % U_. ARC
  ORA-00280: change 8433746 thread 1 is in sequence #819
  
  now, I don't have the log archiving with 819 sequence, I recover from 818. Please tell me how to do?

  Hello

  1. select * from v$log and see which log file is current. Query v$logfile to check physical file location belonging to current log group.
  2. Take bacup of your curent control file using copy/paste of your OS
  3. Issue following command in mount state
  recover database until cancel using backup controlfile
  4. When it finishes applying available archived logs, still it will ask for the location of archived logs which have not been applied, here provide path of current redo log file you got in first step. Here your recovery will finish after applying current redo log
  5.alter database open resetlogs.
  

  Salman

• Archiving logs fill quickly... How to find the culprit?

  Hi, all.
  
  Oracle Dabase 10.2.0.5.0 on RHEL 5
  
  I am followed by a PROD database where the archive logs fill up fast. Archive logs are generated every minute or so... Can you tell me how I can find the culprit and solve the problem... Thank you!

  Use LOGMNR.

  http://psoug.org/reference/dbms_logmnr.html

  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14215/LogMiner.htm#SUTIL019

  Go to these links.

  In addition, check the size of your redo log files. Its can be sized less now.

  # Redo size recommendation

  What should be the size of redlog in OLTP environment such as banks? (10g)

  Concerning
  Asif Kabir

• Rconfig fails with "DEST ARCHIVE LOG does not exist on all nodes of the cl.

  Dear Sir
  
  I am to convert a single instance database RAC
  Next Note:
  Using Oracle 10 g Release 2 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12
  DOC - ID: 388577.1
  
  
  the trial seems fine until I got this error.
  This directory is only one instance and the binary FCAC did not have a configuration database, and then how do I receive this error
  < Microsoft.PowerShell.Commands.GetChildItemCommand >
  U01/Oracle/Gold/DB/apps_st/Data DEST ARCHIVE LOG does not exist on all nodes of the cluster
  
  Please give us a solution.
  Thanks in advance.
  
  
  Here is the ConvertToRAC.xml
  
  [dgold@ebs64 u01] $ ConvertToRAC.xml more
  <? XML version = "1.0" encoding = "UTF-8"? >
  < n: RConfig xmlns:n = "http://www.oracle.com/rconfig".
  xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance".
  xsi: schemaLocation = "http://www.oracle.com/rconfig" >
  < n: ConvertToRAC >
  <!-check is a precheck to ensure that all prerequisites are met, before the con
  version is attempted. The allowed values are: YES | NO. | ONLY->
  < n: Convert check 'ONLY' = >
  <!-specify current database OracleHome no cars to-> SourceDBHome
  < n: SourceDBHome > /u01/oracle/GOLD/db/tech_st/10.2.0 < / n: SourceDBHome
  >
  <!-OracleHome specify where should be configured in the rac database. It may be in Africa
  me as a SourceDBHome->
  < n: TargetDBHome > / u01/ora/GOLD/db < / n: TargetDBHome >
  <!-SID specify no rac database and credentials. User with the sysdba role is req
  receipt to achieve a conversion->
  < n: SourceDBInfo SID 'OR' = >
  < n: Credentials >
  sys < n: User > < / n: User >
  Oracle of < n: Password > < / n: Password >
  SYSDBA < n: Role > < / n: Role >
  < / Credentials: n >
  < / n: SourceDBInfo >
  <!-ASMInfo element is required only if the active non-rac database uses ASM St
  Storm->
  < n: ASMInfo SID = '+ ASM1' >
  < n: Credentials >
  sys < n: User > < / n: User >
  ASM < n: Password > < / n: Password >
  SYSDBA < n: Role > < / n: Role >
  < / Credentials: n >
  < / n: ASMInfo >
  <!-specify the list of nodes that should have instances of cars running. LocalNode
  should be the first node in the nodelist. ->
  < n: NodeList >
  < name n: Node = "ebs64" / >
  < name n: Node = "ebs641" / >
  < / n: NodeList >
  <!-specifies the prefix for the rac instances. It may be same as instance name for no
  database n - cars or different. The instance number will be attached to this prefix
  . ->
  < n: InstancePrefix > RAC < / n: InstancePrefix >
  <!-specify the port for the listener is configured for the rac database. If ports ="",
  alistener existing on the local host will be used for the rac database. The listener will be
  be extended to all the nodes in the nodelist->
  < n: Listener port = "" / >
  <!-specify the type of storage to serve as rac database. The allowed values are
  CFS | ASM. The non-rac database must have the same type of storage. ->
  < n: SharedStorage type = "ASM" >
  <!-location of database field specify is configured for the rac database. If this fie
  LD is left blank, current storage will be used for the rac database. For CFS, this f
  ield will be the directory path. ->
  < n: TargetDatabaseArea > + DATA < / n: TargetDatabaseArea >
  <!-specify the Flash recovery area is set up for the rac database. If this field
  is left empty, current data base retrieval area no cars will be set to
  RAC database. If current database uses no recovery area, FCAC resulting
  database will not be a recovery zone. ->
  < n: TargetFlashRecoveryArea > + DATA < / n: TargetFlashRecoveryArea >
  < / n: SharedStorage >
  < / n: Convert >
  < / n: ConvertToRAC >
  < / n: RConfig >

  Hello

  Do you mean that it is no longer a problem?

  Kind regards
  Hussein

• 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

• Recovery window retention policy removes the archive logs before backup?

  Hi all

  Oracle 11G on Windows 2008 R2

  This afternoon, I've changed my retention policy RMAN "RETENTION POLICY 3 REDUNDANCY"on RECOVERY WINDOW OF 3 DAYS RETENTION POLICY

  However, I checked tonight and after that my daily backup, all the archive before backup logs had been removed! So that means I don't think I can restore to any point in time, before my daily backup. All newspapers .arc were there after the backup. Then I tried another test and began the daily backup again. During the backup process, archive logs were deleted again! Now, I don't have any archives of newspapers...

  Is this good behavior OF RETENTION POLICY RECOVERY WINDOW? I thought that she would keep all the files needed for to restore me to any point in time for the previous 3 days. When I used a REDUNDANCY, with my daily backups, he kept 3 days of backups + archiving logs so that I could restore point-in-time at any point. How can I use WINDOW RECOVERY so that I can actually restore to any point in time for the 3 days?

  I wanted to change WINDOW of recovery, since I read that using the REDUNDANCY, it keeps only X copy a backup (so if I ran the backup 3 times a day, I would have only these 3).

  Thanks in advance.

  After a database RESTORE, Oracle tries to RECOVER a DATABASE.  He tries to 'find' the archivelogs for this phase in the location expected archivelog.  If they are NOT present in the location expected archivelog, it attempts to restore backups before applying them.

  Since your BACKUP... DELETE ENTRY deletes the archivelogs after that that they are saved, Oracle will have to use backups to recover the archivelogs.

  Hemant K Collette

• No clarity about the location of archive logs in Oracle database 11g

  I have this request which I am not able to solve. There is a location of the log archiving mentioned as /oraarch/app/oracle/oradata/snlprod/archive_logs/in the parameter log_archive_dest_1. But the archive logs appear in another location/orabackup/rman/snlprod/archive_logs. I wonder how the archive logs show at this location, / orabackup/rman/snlprod/archive_logs.

  
  

  I assume that there is only one way in what place can be given which is seen availability-> restore settings-> Media Recovery.

  
  

  Hopefully, my question is clear.

  
  

  Please get back with the answer to my query.

  
  

  Concerning

  Check the location of the archive log backup in the script. What is /orabackup/rman/snlprod/archive_logs.

• 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

• 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

• ORA-19504: failed to create the file, ORA-00270: creation of the archiving log error

  Hello
  
  Oracle 11 g 2 on windows 7, I of primary and standby on the same system (learning).
  
  When I check on status of primary and secondary use under request it gives applied log is 'NO '.
  
  SQL > select sequence #, used from v$ archived_log;
  
  SEQUENCE # APPLIED
  ---------- ---------
  516 NO.
  517 NO.
  NO. 523
  NO. 524
  525 NO.
  531 NO.
  NO. 532
  533 NO.
  NO. 541
  544 NO.
  
  When I checked error on DB primary .he give me more erro.
  SQL > SELECT 'ID', 'DB_status' STATUS DEST_ID, EXCURSION place "Archive_dest', 'ERROR' OF V$ ARCHIVE_DEST WHERE DEST_ID < = 5;
  ---------- ---------
  Error Archive_dest
  ------------------------------------------------------------------------------------------------------------------------------------------------------
  1 D:\app\kamdarvg\flash_recovery_area\test\ARCHIVELOG ORA-19504: cannot create the file «»
  
  2 STAND ORA-00270: creation of the archiving log error
  
  I checked the space on the system... is there enough free space on the disk.
  
  On primary DB (destination of the journal archive)
  
  SQL > list of archive logs
  Database log mode Archive Mode
  Active AutoArchive
  Destination of archive D:\app\kamdarvg\flash_recovery_area\test\ARCHIVELOG
  More old sequence of journal online 564
  Log sequence archive 566
  Current log sequence 566
  
  On standby DB (list of newspapers of record)
  
  SQL > list of archive logs
  Database log mode Archive Mode
  Active AutoArchive
  Destination of archive D:\app\kamdarvg\flash_recovery_area\test\ARCHIVELOG
  More old sequence of journal online 564
  Log sequence archive 566
  Current log sequence 566
  
  Please guide it's because of the destination of the journal archive even shared by the standby and primary?
  
  If yes how do I change the destination of the newspaper archive on standby DB?
  
  Thank you.
  
  Edited by: 977220 April 18, 2013 20:49

  change initialization parameter

• 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 with no backup of the archive logs

  I suffer from enormous size archive of the newspaper. In my previous post, I asked for help. I almost 480 GB archive log every day in our database of 11 2 under redhat linux 5.8 GR. Now, if you please help me in another case.
  
  If I take backup of archive logs and run delete archivelog everything until ' sysdate-1' with each backup database of day how it affects. " In my opinion there should be no problem in that I have the last incremental backup and recovery 1 days archive log in archivelog destination. If I do not archive log backups to how it will be different. Help, please.

  >

  Hello

  Sir, I know how to remove. But in my opinion delete up to sysdate-1 and taking no backup of the Archives of newspapers will
  no effect. Is in my opinion is right or wrong, that is the question.

  What I read in your original post, is that you take a daily incremental backup - Yes? I'm assuming that you also take
  a full backup on a regular basis (Sunday?).

  I was working on the assumption that the foregoing is available? I worked on a project where installation has been similar. We
  tested regularly backups - I hope that you do the same thing?

  What we used to do was FTP (script Unix - cron job - if you Google you will find Python or Perl to do the same thing - that is)
  what I wanted to, but was cancelled - very 1980, anyway) the archived redo logs on to a specific computer that holds only these files.
  After FTP "d - they have been removed from the server, freeing up space.

  Now, you say you have TB 0.5 per day - while more than a week, you will need a machine with ~ 3 TB of disk - if you can get a kind
  the scenario as this place and running, then you will have both your incremental backup and your archived redo logs for the last
  24 hours and the full backup with recovery archived records dating back to this full backup. You can also always archive on tape if
  suits. So, you will have redundant coverage - 'belt and braces' as the Americans say.

  But, to answer your question directly, "take no backup of archive logs have no effect" - that is true - it
  will not affect the operation of the database server, but if I were you, I would hang on to enough archived redo log to return to the
  last backup. That's just my humble OPINION.

  HTH,

  Paul...

  Published by: Paulie July 21, 2012 19:28

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