Log archiving

Similar Questions

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

  Hi Oracle Community,

  I have a few databases (11.2.0.4 POWER 2 block and 12.1.0.2) with Data Guard. Back up this database with RMAN to ribbons, only on the primaries.

  During the backup, sometimes I got RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

  By reason of this global warning to backup status is "COMPLETED WITH WARNINGS". Is it possible to remove this warning, or perhaps change RMAN configuration to avoid the appearance of this warning?

  Concerning

  J

  Where is the problem on these warnings? If you do not want to see such warnings, why not simply to perform the removal of the archivelogs in a separate step? For example:

  RMAN> backup database plus archivelog;
  RMAN> delete noprompt archivelog all completed before 'sysdate-1';
  

• Delete logs archive > 1 day

  Hi all

  9i

  RHEL5

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

  But I don't find it anymore

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

  Thank you all,

  JC

  Hello;

  You old thread:

  Remove the archivelogs and old backups

  Best regards

  mseberg

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

  
  Hi, I saw a couple of orders in regard to the purge archive records in a Data Guard configuration.

  Set UP the STRATEGY of SUPPRESSION of ARCHIVE to SHIPPED to All RELIEF;

  Set UP the STRATEGY of ARCHIVELOG DELETION to APPLIED on All RELIEF;

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

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

  I also saw

  CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED;

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

  I saw the following advice in the manual of Concepts of data protection & Admin

  Configure the DB_UNIQUE_NAME in RMAN for each database (primary and Standby) so RMAN can connect remotely to him

  Q4. Why would I want my primary ro connect to the RMAN Repository (I use the local control file) of the standby? (is this for me to say define RMAN configuration settings in the Standby) manual

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

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

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

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

  Any idea greatly appreciated,

  Jim

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

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

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

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

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

  Its a configuration, it will not erase by itself.

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

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

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

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

  Great example:

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

  All Oracle is worth a peek here:

  http://emrebaransel.blogspot.com/

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

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

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

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

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

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

  Also if it remains idle for awhile you want.

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

  Always use a database of catalog RMAN with Data Guard.

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

  Same answer as 5, use a catalog database.

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

  Same answer as 5, use a catalog database.

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

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

  Best regards

  mseberg

  Summary

  Always use a database with RMAN catalog.

  Always use CRF with RMAN.

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

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

  Post edited by: mseberg

• Reg apply log archiving after the transfer of data files

  Hi all
  
  That I reinstalled the main server of the D-Drive E-reader data files using the command line.

  C:\>Move <source_path> <destination_path>

  The redo logs for the move operation will apply on the eve of the database?
  In addition, what happens if the data files are moved manually in the primary database (i.e. without using the command prompt)?
  
  
  Thank you
  Madhu

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

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

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

  And also close this thread

  Reg apply log archiving after the transfer of data files

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

• Size of the huge log archive

  I have 5 redo log files. Each is 4 GB. There are huge transactions (1800-2000 per second). So we have every hour 5-6 journal of the switches. So all the hours of archives journal 20 to 24 GB and daily increase in size, the size 480 GB.
  
  I had planned to take an incremental backup of level 1 and level 0 per week daily with the option delete log archiving 'sysdate-1 '.
  
  But we have little storage if, it is impossible to the sphere 480 GB per day and take backup of these 480 GB for 7 days (480 * 7) GB = 4 TB. How can I correct this situation? Help, please.

  1 disk is cheap
  2 the onus on those who "Advanced" application
  3 you can use Log Miner to check what is happening.

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

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

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

• Logs archiving for the RAC ASM basics

  Hello
  
  I have a question about logs archiving on the ASM database located on a RAC. I created a database orcl who has orcl1 instance on node1 and orcl2 on Node2. For the backup of this database, I enabled for the database to archivelog.
  
  After a few transactions and backups, I noticed that there are two sets of archiving logs created on each node in the folder $ORACLE_HOME/dbs. In node 1, it starts with arch1_ * and node2 is arch2_ *.
  
  IWhy is it creates logs archiving on local disks, in which she should ideally create disks asm which is shared between the nodes. My backup application fails with journal archive not found error, because it searches newspaper archives in the other node.
  
  All entries on this will be useful.
  
  Amith

  Hello

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

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

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

  ARCHIVELOG must focus on a shared domain.

  You need the parameter config below:

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

  Or location of default config:

  SQL> show parameter log_archive_dest
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  log_archive_dest                     string
  

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

  To resolve this problem see this example:

  SQL> show parameter recover
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  db_recovery_file_dest                string
  db_recovery_file_dest_size           big integer 1
  
  SQL> archive log list;
  Database log mode              Archive Mode
  Automatic archival             Enabled
  Archive destination            /u01/app/oracle/product/10.2.0/db_1/dbs/
  Oldest online log sequence     2
  Next log sequence to archive   3
  Current log sequence           3
  SQL>
  
  SQL> alter system set db_recovery_file_dest_size=20G scope=both sid='*';
  
  System altered.
  
  SQL> alter system set db_recovery_file_dest='+FRA' scope=both sid='*';
  
  System altered.
  
  SQL> archive log list;
  Database log mode              Archive Mode
  Automatic archival             Enabled
  Archive destination            USE_DB_RECOVERY_FILE_DEST
  Oldest online log sequence     5
  Next log sequence to archive   6
  Current log sequence           6
  SQL>
  

  With RMAN

  RMAN> CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT 'sys/oracle@db10g1';
  
  new RMAN configuration parameters:
  CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT '*';
  new RMAN configuration parameters are successfully stored
  starting full resync of recovery catalog
  full resync complete
  
  RMAN>  CONFIGURE CHANNEL 2  DEVICE TYPE DISK CONNECT  'sys/oracle@db10g2';
  
  new RMAN configuration parameters:
  CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT '*';
  new RMAN configuration parameters are successfully stored
  starting full resync of recovery catalog
  full resync complete
  
  RMAN> list archivelog all;
  
  using target database control file instead of recovery catalog
  
  List of Archived Log Copies
  Key     Thrd Seq     S Low Time  Name
  ------- ---- ------- - --------- ----
  1       1    3       A 28-FEB-11 /u01/app/oracle/product/10.2.0/db_1/dbs/arch1_3_744216789.dbf
  2       2    2       A 27-FEB-11 /u01/app/oracle/product/10.2.0/db_1/dbs/arch2_2_744216789.dbf
  
  RMAN> crosscheck archivelog all;
  
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid=127 instance=db10g1 devtype=DISK
  allocated channel: ORA_DISK_2
  channel ORA_DISK_2: sid=135 instance=db10g2 devtype=DISK
  validation succeeded for archived log
  archive log filename=/u01/app/oracle/product/10.2.0/db_1/dbs/arch1_3_744216789.dbf recid=1 stamp=744292116
  Crosschecked 1 objects
  
  validation succeeded for archived log
  archive log filename=/u01/app/oracle/product/10.2.0/db_1/dbs/arch2_2_744216789.dbf recid=2 stamp=743939327
  Crosschecked 1 objects
  
  RMAN> backup archivelog all delete input;
  
  Starting backup at 28-FEB-11
  current log archived
  using channel ORA_DISK_1
  using channel ORA_DISK_2
  channel ORA_DISK_1: starting archive log backupset
  channel ORA_DISK_1: specifying archive log(s) in backup set
  input archive log thread=1 sequence=3 recid=1 stamp=744292116
  channel ORA_DISK_1: starting piece 1 at 28-FEB-11
  channel ORA_DISK_2: starting archive log backupset
  channel ORA_DISK_2: specifying archive log(s) in backup set
  input archive log thread=2 sequence=2 recid=2 stamp=743939327
  channel ORA_DISK_2: starting piece 1 at 24-FEB-11
  channel ORA_DISK_1: finished piece 1 at 28-FEB-11
  piece handle=+FRA/db10g/backupset/2011_02_28/annnf0_tag20110228t120354_0.265.744293037 tag=TAG20110228T120354 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
  channel ORA_DISK_1: deleting archive log(s)
  archive log filename=/u01/app/oracle/product/10.2.0/db_1/dbs/arch1_3_744216789.dbf recid=1 stamp=744292116
  channel ORA_DISK_2: finished piece 1 at 24-FEB-11
  piece handle=+FRA/db10g/backupset/2011_02_24/annnf0_tag20110228t120354_0.266.743940249 tag=TAG20110228T120354 comment=NONE
  channel ORA_DISK_2: backup set complete, elapsed time: 00:00:03
  channel ORA_DISK_2: deleting archive log(s)
  archive log filename=/u01/app/oracle/product/10.2.0/db_1/dbs/arch2_2_744216789.dbf recid=2 stamp=743939327
  channel ORA_DISK_1: starting archive log backupset
  channel ORA_DISK_1: specifying archive log(s) in backup set
  input archive log thread=1 sequence=4 recid=4 stamp=744293023
  input archive log thread=2 sequence=3 recid=3 stamp=743940232
  channel ORA_DISK_1: starting piece 1 at 28-FEB-11
  channel ORA_DISK_1: finished piece 1 at 28-FEB-11
  piece handle=+FRA/db10g/backupset/2011_02_28/annnf0_tag20110228t120354_0.267.744293039 tag=TAG20110228T120354 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
  channel ORA_DISK_1: deleting archive log(s)
  archive log filename=+FRA/db10g/archivelog/2011_02_28/thread_1_seq_4.264.744293023 recid=4 stamp=744293023
  archive log filename=+FRA/db10g/archivelog/2011_02_24/thread_2_seq_3.263.743940231 recid=3 stamp=743940232
  Finished backup at 28-FEB-11
  
  Starting Control File and SPFILE Autobackup at 28-FEB-11
  piece handle=+FRA/db10g/autobackup/2011_02_28/s_744293039.263.744293039 comment=NONE
  Finished Control File and SPFILE Autobackup at 28-FEB-11
  
  SQL> alter system archive log current;
  
  System altered.
  
  RMAN> list archivelog all;
  
  using target database control file instead of recovery catalog
  
  List of Archived Log Copies
  Key     Thrd Seq     S Low Time  Name
  ------- ---- ------- - --------- ----
  5       1    5       A 28-FEB-11 +FRA/db10g/archivelog/2011_02_28/thread_1_seq_5.264.744293089
  6       2    4       A 24-FEB-11 +FRA/db10g/archivelog/2011_02_24/thread_2_seq_4.268.743940307
  
  RMAN> CONFIGURE CHANNEL 1 DEVICE TYPE DISK CLEAR;
  
  old RMAN configuration parameters:
  CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT '*';
  old RMAN configuration parameters are successfully deleted
  
  RMAN> CONFIGURE CHANNEL 2 DEVICE TYPE DISK CLEAR;
  
  old RMAN configuration parameters:
  CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT '*';
  old RMAN configuration parameters are successfully deleted
  
  RMAN> exit
  
  Recovery Manager complete.
  

  Kind regards
  Levi Pereira

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

• Size log Archive

  Hi all

  EBS R12.1.3

  RHEL 5.3

  I enabled logging realize for our R12.1.3 EBS

  So I check how much newspapers and size it generates for the day.

  [root@erp ~] # cd/u01/ARCH

  [root@erp ARCH] # ls - lrt

  Total 4045056

  -rw - r - 1 oracle dba 21882368 18 Oct 21:33 1_682_849306543.dbf

  -rw - r - 1 oracle dba 999739904 19 October 00:03 1_683_849306543.dbf

  -rw - r - 1 oracle dba 999739904 Oct 19 01:24 1_684_849306543.dbf

  -rw - r - 1 oracle dba 999739904 Oct 19 17:02 1_685_849306543.dbf

  -rw - r - 1 oracle dba 116670464 20 Oct 09:52 1_686_849306543.dbf

  -rw - r - 1 oracle dba 1000268800 20 Oct 10:49 1_687_849306543.dbf

  1 GB of size of each archive log is good for the performance of the EBS?

  Thank you very much

  JC

  Total size of the archive logs generated depends on the activity on the database. As rule of thumb if there is around 15-20 log off the / hour (that is to say 15-20 archive logs generated per hour) is acceptable. Your generation archive current seems ok.

  concerning

  Pravin

• Logs archiving not required for recovery

  Hello

  I have a basic test of 200 GB with backup running every night. He made a full backup with a cleaning of the archiving log

  The backup has not happened for the past 2 weeks and the archivelog filled the disk free space available.

  Now, if I take a backup completes, or a backup of level 0 in the database right now, can I go ahead and remove the logs of archiving that were created before backups?

  Unfortunately, archive logs are too big to make a backup of it to the backup location

  According to my understanding of the current backup should have all changes recorded in the archivelogs created before she and I should be able to remove the archive logs

  Thank you

  Hello;

  I remove all but the last two days and then do an overlap archivelog all;

  And then do the backup.

  And then ask the boss to drive more!

  Best regards

  mseberg

• Log archive backup son separately

  Hello community,

  I have a 11.1.0.7 RAC database on a cluster with two nodes AIX HACMP and use shared raw logical volumes for the data files and of the local filesystems, not simultaneous for the archiving of newspapers.  RMAN is currently back up the data from the secondary node files and archive logs are saved using backups of files only.  I would add archiving logs, for the RMAN backup, but the destination of the main newspaper "/ arch01" is mounted over NFS on the secondary node using the mount point ' / archo01_NFS '.  The sys admin says that he cannot change the mount point to match what is on the primary node because it will affect HACMP failover.  I looked in the documentation of RMAN for a setting in which I might be able to specify thread 2 archivelogs only during the main backup and before you run a log backup archive separate thread 1 on the primary node, but there seems to be such a parameter.  Someone encountered this and found a way to remedy this?

  Thanks in advance.

  It will open the canal to the second node that connects to the instance on another node through NET services. The process server for the channel will be in your second instance.

  You can distribute the workload across nodes without making all the I/o node. It also helps when each node stores the logs to archive locally rather than on a shared drive

  Perform backup and restore in Real Application Clusters environments

  RMAN and Oracle Net in Real Application Clusters

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

  11.2.0.4 DB Oracle Linux 6.5

  We have a database whose archive generation is as follows.

  Average of generation of archive log: 400 GB/day

  Max log generation: 900 GB/day

  Archive log diskgroup size: 4 TB

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

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

  Sunday-> level 0 backup

  Monday-> level 1 backup

  Tuesday-> level 1 backup

  Wednesday-> level 0 backup

  Thursday-> level 1 backup

  Friday-> level 1 backup

  Saturday-> level 1 backup

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

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

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

  delete noprompt archivelog until 'SYSDATE -2";

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

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

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

  
  

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

  DELETE OBSOLETE is not the same thing as REMOVE EXPIRES.

  -EDIT

  Never mind.  I found it.

  DELETE

  OBSOLETE

  Removes backups of data files and copies stored in the repository RMAN which are obsolete, in other words, is no longer required (see example 2-66). RMAN also deletes the log of the obsolete filesand archived redo log backups. RMAN determines what backups and copies of data files are no longer needed, which in turn determines what records (and backups of logs) are no longer needed. RMAN considers that the creation of a data file as a backup to decide which connects to keep.

  Post edited by: EdStevens

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

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

• New log archiving

  Hi all

  11.2.0.1

  AIX 6.1

  Our database crashes again due to the full archive log.

  I remove all in the fast_recovery_area, so the size will be free

  and cancel the stop the database, but still the same error:

  SQL > startup

  ORACLE instance started.

  Total System Global Area 6196547584 bytes

  Bytes of size 2232952 fixed

  3657436552 variable size bytes

  2516582400 of database buffers bytes

  Redo buffers 20295680 bytes

  Mounted database.

  ORA-03113: end of file on communication channel

  Process ID: 7078052

  Session ID: 125 serial number: 5

  Please helppp.

  Thank you

  zxy

  Hello

  How much free space you have yesterday:

  / u02/oracle/fast_recovery_area/BATCHQAT /.

  / U02 is full?

  Try:

  bootable media;

  ALTER database noarchivelog

  change the database open.

  Kind regards.

• The fast recovery area cannot be used for log archiving?

  I use the version 11.0.2.3 for testing.  I read a line like below from the book of the OCP.

  If none of the LOG_ARCHIVE_DEST_n settings have been defined, then the transition

  the database in archivelog mode will define LOG_ARCHIVE_DEST_10 internally to the

  Flash zone recovery, if it has been configured.

  In my database, fast recovery already defined as below.

  SQL > show parameter db_recovery

  VALUE OF TYPE NAME

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

  db_recovery_file_dest string + FASTRECOVERY

  whole large db_recovery_file_dest_size 4248M

  So I thought that if I turn the database in log mode archive, the log_archive_dest_10 will be defined as the same value as db_recovery_dest.

  SQL > alter archivelog database;

  Database altered.

  SQL > alter database open;

  Database altered.

  SQL > show the log_archive_dest parameter

  VALUE OF TYPE NAME

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

  Log_archive_dest chain

  Log_archive_dest_1 chain

  LOG_ARCHIVE_DEST_10 string

  See archive of the database becomes, the log_archive_dest_10 always be empty.

  So is there something wrong with my understanding?

  It is quote an Oracle Press all-in-one exam guide of the I had a part in writing. Your problem is you are using 11.2.x,, but the book was written with 11.1.x. glance the relevant parameters in the docs for both versions, and you will see that the situation has changed.

  Uni Oracle validates the examinations against both versions, so avoid any question where the difference would matter, but in any case, with your attention to detail, I'm sure that tat will have no problem with the exams.

  --

  John Watson

  Oracle Certified Master s/n

• 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

• Removal of the log archiving using RMAN Target in Oracle 10 g

  Hi all
  Recently, I noticed that archive logs have been 102 GBs out of the car and I need to free up space. When I tried to connect using the RMAN catalog

  connect catalog user@db

  I got error message like

  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been used

  But I could get through the use

  connect target user@db

  My query is that I can use
  

  RMAN> delete noprompt expired archivelog all;

  as shown in [how to remove the log file archive | https://forums.oracle.com/forums/thread.jspa?threadID=2321257 & start = 0 & tstart = 0]
  Or I'll take another approach to remove obsolete archive logs?
  
  Kind regards
  * 009 *.

  Hello;

  Recently, I noticed that archive logs have been 102 GBs out of the car and I need to free up space. When I tried to connect using the RMAN catalog

  connect catalog user@db
  

  I got error message like

  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been used
  

  But I could get through the use

  connect target user@db
  

  Are you trying to connect through Grid control? If you connect via a script, then please post its content.
  Make sure that you are not connected to the database target using "nocatalog.

  rman target sys/@ catalog /@
  

  My query is that I can use

  RMAN> delete noprompt expired archivelog all;
  

  as shown in [how to remove the log file archive | https://forums.Oracle.com/forums/thread.jspa?threadID=2321257&Start=0&tstart=0]
  Or I'll take another approach to remove obsolete archive logs?

  Kind regards
  * 009 *.

  These archives are saved? The command above does not update the RMAN Repository if in case, the archives have been manually delete at the OS level.
  I recommend you save these records and then remove them.

  RMAN>backup archivelog all not backedup 1 times delete input;
  

  If these archives are already saved and were not deleted from the disk, then you can use the below command

  RMAN>delete force noprompt archivelog all completed before 'SYSDATE-n';
  

  where "n" is the number of days of delay on the current date. Be sure to check if these archives have been saved before deleting.

  Kind regards
  Shivananda