Missing ARCHIVELOG

All the

u could answer question 2?
1. in rman an archivelog is deleted unknowly.afer i gave command overlap archivelog all. can I restore if a transaction happened in the missing archivelog?
2 what is of root.sh?

Concerning
Bamba

If your archive log is missing you restore your database in a certain point in time. Deleting an archiving log will not affect your database running. You can only restore your database before the missing log archiving.

If possible take a cold backup of your database.

Concerning
Asif Kabir

Tags: Database

Similar Questions

RMAN backup with a missing archivelog.
Hello

I backed up my database yesterday after that you guys helped me to solve some problems I've had on this subject. I have used RMAN with the following command in an execution block:

* run {*}
allocate channel t1 type disk;
backup current controlfile;
backup database;
delete any backup archivelog entry;
output channel c1;
*}*

At the end of the operation, RMAN indicates that archivelog is missing, and he couldn't find it. Therefore, recover the operation may be compromised. Now am confused because I don't know if the command executed successfully or not and how to fix the missing archivelog.

Here are all of the output of the operation with the error message:

channel Affectu: t1
channel t1: sid = 131 typedev = DRIVE

Dumarrage of backup in 16/04/09
channel t1: backup of all files in Donnues all Dumarrage

channel t1: insertion of the Donnues in all of backup file
insertion of the current score in all of backup file
channel t1: Dumarrage of Ulument 1 in 16/04/09
channel t1: Ulument 1 Terminu in 16/04/09
pointeur=+ASMTEST/Meta4/backupset/2009_04_16/ncnnf0_tag20090416t211049_0.334.684
* Utiquette 364257 = TAG20090416T211049 comment = NONE *.
channel t1: all backup Terminu, time Ucoulu: 00:00:14
End of backup in 16/04/09

Dumarrage of backup in 16/04/09
channel t1: backup of all files in Donnues all Dumarrage

channel t1: insertion of the Donnues in all of backup file
file Donnues en Entrue fno = nom=+ASMTEST/meta4/m4prod.dbf 00008
Donnues en Entrue fno name 00010 = file is H:\ORADATA\M4REC. DBF
Donnues en Entrue fno = 00009 name file is E:\DATAFILEMETA4\M4PROD02. DBF
Donnues en Entrue fno = 00001 nom=+ASMTEST/meta4/system01.dbf file
file Donnues en Entrue fno = nom=+ASMTEST/meta4/sysaux01.dbf 00003
Donnues en Entrue fno = name 00006 file is C:\TEST. DBF
Donnues en Entrue fno nom=+ASMTEST/meta4/meta4.dbf 00007 = file
Donnues en Entrue fno = 00005 nom=+ASMTEST/meta4/example01.dbf file
Donnues en Entrue fno = 00002 nom=+ASMTEST/meta4/undotbs01.dbf file
file Donnues en Entrue fno = nom=+ASMTEST/meta4/users01.dbf 00004
channel t1: Dumarrage of Ulument 1 in 16/04/09
channel t1: Ulument 1 Terminu in 16/04/09
pointeur=+ASMTEST/Meta4/backupset/2009_04_16/nnndf0_tag20090416t211107_0.333.684
* Utiquette 364271 = TAG20090416T211107 comment = NONE *.
channel t1: all backup Terminu, time Ucoulu: 00:51:10
channel t1: backup of all files in Donnues all Dumarrage

channel t1: insertion of the Donnues in all of backup file
insertion of the current score in all of backup file
inclusion of the current SPFILE in all of backup
channel t1: Dumarrage of Ulument 1 in 16/04/09
channel t1: Ulument 1 Terminu in 16/04/09
pointeur=+ASMTEST/Meta4/backupset/2009_04_16/ncsnf0_tag20090416t211107_0.345.684
* Utiquette 367351 = TAG20090416T211107 comment = NONE *.
channel t1: all backup Terminu, time Ucoulu: 00:00:26
End of backup in 16/04/09

Dumarrage of backup in 16/04/09
Journal Archivu underway
channel Liburu: t1
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: Uchec of the command backup O 16/04/2009 22:04:03
RMAN-06059: journal archiving waited not found; the loss of the log arch
ivago compromises the Possibilitu of Rucupuration
ORA-19625: error identification of the H:\ARCHIVEMETA4\ARC00001_0 file
* 682674928.001*
ORA-27041: opening the file impossible
04002 - OSD: cannot open the file
S/O-error: (OS2) the Spucifiu file is not found.

Here is my l and please correct me if am wrong:

The first 3 statements in the block run executed successfully, but
the last of them is not. Is this true?

Whatever the understanding, should I have a backup? What can I do to get a consistent backup?

Thanks in advance.
Adomi,

It is sad to see that you are still RMAN in 8i mode where you are on 10g.

The script is bs, sorry

Run {}
allocate channel t1 type disk; -not required
backup current controlfile; -not necessary, as this is already done backup of database
backup database;
delete any backup archivelog entry;
output channel c1; -not required.
}

If you have autobackup controlfile, you might just

backup database archivelog

and be done with it.

Like you didn't made a RMAN backup from the start, should have read your archivelog backup statement

ARCHIVELOG backup all Skip inaccessible delete entry.

Once successful Oracle shouldn't the archivelog has more need, and you should make a second backup without the skip inaccessible clause.

------
Sybrand Bakker
Senior Oracle DBA

Manuel Standby Database not in harmony with the missing archivelogs
Hello

Operating system: Solaris
DB: Oracle 11.2.0.1 EA
Do not use RAC or ASM

I have a Production database which is in archivelog mode and standby server DR.
The two servers (Prod, standby) have the same structure and exact db name/version.

We manually scp archive logs and recover them to a database of manual standby via the SQL Scripts "cron". (I.e. the value of automatic recovery on; restore database Eve ;))
Recently, we got out of sync with our log files and were not applying on the eve. As part of the maintenance of the Prod, these log files have been removed and are no longer available.
I tried several ways to 'rebuild' our database awaiting. I tried to prod Shutdown, backup all files db and scp sleep them, recreate standby controlfile and startup mount and recover the.
Whenever I try to apply a new journal archive via recover Eve, here are the errors:

ORA-00279: change 211077622 September at 27/01/2012 12:18:42 necessary to screw 1
ORA-00289: suggestion: /oradump/arch/PROD/PROD_arch_1_69486_736618850.arc
ORA-00280: change 211077622 thread 1 is in sequence #69486

ORA-00308: cannot open archived log ' / oradump/arch/PROD/PROD_arch_1_69486_736618850.arc'
ORA-27037: unable to get file status
SVR4 error: 2: no such file or directory
Additional information: 3

ORA-10879: error reported in parallel recovery slave
ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error
ORA-01152: 1 no file has been restored from a sufficiently old backup
ORA-01110: data file 1: ' / oradevices/PROD/oraPRODsystem1.dbf'

When I check v$ log_history, new newspapers have not been implemented.
I also tried the method 'Restore from incremental backup via YVERT' with the same results.

Is there a way to re - create own forward and ensure that the chain of the newspaper which is now defective gets fixed or reset?
Finally, I would get DataGuard here, but this isn't the case at the moment.
Thanks for your suggestions.

-Dav
If you use the backup to cold to create the database pending, check whether you have followed these steps.

1. Remove
all the data files and the database pending controlfiles.

2. create a new controlfile eve of production to standby by using the following command
"change the database create controlfile as 'Location'"; "."

3. move the controlfile back to the location of the server database of such relief as specified in the initialization parameter file.

4. replace its appropriate place that was taken through cold backup all data files.

5 startup nomount

6 change the mounting base pending;

7 restore database pending.
CPS archives newspapers sequence which is posed by the database of the production.

You can try these steps.

Recovery with ArchiveLogs

Hello
I need a little help in the recovery. This is my test case:
-Database running on the virtual machine (linux) in archivelog
-backup all night snapshot of the virtual machine
-archivelogs are duplicated on the local disk and remote disk (via sshfs and log_archive_dest_2)
At lunch, I recover the snapshot together every night to simulate a disaster. Here are my steps to bring the database for the last time as possible with only archivelogs - I know that some data is lost now.
1. Copy the archivelogs missing the sshfs to the local host (virtual machine)
2. start the database in Mount - mode
3. connect rman
4. CATALOG START WITH /path/ - to get the missing archivelogs (sequence 11-20)
5. RECOVER THE DATABASE UP TO THE SEQUENCE 21;
Ausgabe von 5. :
starting media recovery
Journal archived for thread 1 with sequence 11 is already on the disc in the file /ora/archiv/KITA_1_11_875808530.dbf
Journal archived for thread 1 with sequence 12 is already on the disc in the file /ora/archiv/KITA_1_12_875808530.dbf
Journal archived for thread 1 with sequence 13 is already on the disc in the file /ora/archiv/KITA_1_13_875808530.dbf
Journal archived for thread 1 with sequence 14 is already on the disc in the file /ora/archiv/KITA_1_14_875808530.dbf
Journal archived for thread 1 with sequence 15 is already on the disc in the file /ora/archiv/KITA_1_15_875808530.dbf
Journal archived for thread 1 with 16 sequence is already on the disc in the file /ora/archiv/KITA_1_16_875808530.dbf
Journal archived for thread 1 with sequence 17 is already on the disc in the file /ora/archiv/KITA_1_17_875808530.dbf
Journal archived for thread 1 with sequence 18 is already on the disc in the file /ora/archiv/KITA_1_18_875808530.dbf
Journal archived for thread 1 with sequence 19 is already on the disc in the file /ora/archiv/KITA_1_19_875808530.dbf
Journal archived for thread 1 with sequence 20 is already on the disc in the file /ora/archiv/KITA_1_20_875808530.dbf
Archive log file name=/ora/archiv/KITA_1_11_875808530.dbf thread = 1 sequence = 11
Archive log file name=/ora/archiv/KITA_1_12_875808530.dbf thread = 1 sequence = 12
Archive log file name=/ora/archiv/KITA_1_13_875808530.dbf thread = 1 = 13 sequence
Archive log file name=/ora/archiv/KITA_1_14_875808530.dbf thread = 1 sequence = 14
Archive log file name=/ora/archiv/KITA_1_15_875808530.dbf thread = 1 sequence = 15
Archive log file name=/ora/archiv/KITA_1_16_875808530.dbf thread = 1 sequence = 16
Archive log file name=/ora/archiv/KITA_1_17_875808530.dbf thread = 1 sequence = 17
Archive log file name=/ora/archiv/KITA_1_18_875808530.dbf thread = 1 sequence = 18
Archive log file name=/ora/archiv/KITA_1_19_875808530.dbf thread = 1 sequence = 19
Archive log file name=/ora/archiv/KITA_1_20_875808530.dbf thread = 1 sequence = 20
Oracle error:
ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error
ORA-01194: file 1 needs a recovery more match
ORA-01110: data file 1: ' / ora/data/KITA/system01.dbf'
media recovery complete, duration: 00:00:36
Finished recover at April 1, 15
I don't know why this is happening. Later, I did restore database; alter database open; and everything works, wait for the fact, that the archivelog with sequence number 11 is replaced (it would be OK if I don't get it back). I checked the LIST of NEWSPAPERS of ARCHIVES:
list of archive logs;
Database log mode Archive Mode
Active AutoArchive
Archives/mnt/sshfs/archiv/KITA of destination
More old sequence of journal online 9
Log sequence archive 11
Current log sequence 11
What is the problem with my package? How can I avoid the database replaces the archivelogs?
Thanks for help.

Have a read of http://docs.oracle.com/cd/E11882_01/backup.112/e10642/osadvsce.htm#

Likely to want to do recover database using backup controlfile

Enter the number of process... missing newspaper archive!

Hello

Oracle Streams capture process is alternating between the State INITIALIZING and DICTIONARY of INITIALIZATION and not proceed after this State in order to capture the updates made on the table.

We accidentally missing archivelogs and no log backup archive.

Now I'm going to recreate the process of capture again.

How can I start the new SNA, the capture process?

And what is the way of dough to delete files from archive central server log, because
YVERT used by the capture process?

Thank you
Faziarain

Published by: [email protected] on August 12, 2009 12:27 AM

Use dbms_Streams_Adm to add a capture, also do a dbms_capture_adm.build. You will see in v$ archived_log to the dictionary_begin of the column "Yes", which means that the first_change # this archivelog is first SNA appropriate to start the capture.

"rman" is the way favorite in 10 g + to delete the archive that he is aware of the constraints of flow. If you cannot use rman to purge the archives, you must verify that the min required YVERT in your system by script and react accordingly.

Since the 10g, I recommend using rman, but nevertheless, here's the script I did 9i in former time were rman ate the records by streams with appetite.

#!/usr/bin/ksh
# program : watch_arc.sh
# purpose : check your archive directory and if actual percentage is > MAX_PERC
#           then undertake the action coded by -a param
# Author : Bernard Polarski
# Date   :  01-08-2000
#           12-09-2005      : added option -s MAX_SIZE
#           20-11-2005      : added option -f to check if an archive is applied on data guard site before deleting it
#           20-12-2005      : added option -z to check if an archive is still needed by logminer in a streams operation

# set -xv

#--------------------------- default values if not defined --------------
# put here default values if you don't want to code then at run time
MAX_PERC=85
ARC_DIR=
ACTION=
LOG=/tmp/watch_arch.log
EXT_ARC=
PART=2
#------------------------- Function section -----------------------------
get_perc_occup()
{

  cd $ARC_DIR
  if [ $MAX_SIZE -gt 0 ];then
       # size is given in mb, we calculate all in K
       TOTAL_DISK=`expr $MAX_SIZE \* 1024`
       USED=`du -ks . | tail -1| awk '{print $1}'`    # in Kb!
  else
    USED=`df -k . | tail -1| awk '{print $3}'`    # in Kb!
    if [ `uname -a | awk '{print $1}'` = HP-UX ] ;then
           TOTAL_DISK=`df -b . | cut -f2 -d: | awk '{print $1}'`
    elif [ `uname -s` = AIX ] ;then
           TOTAL_DISK=`df -k . | tail -1| awk '{print $2}'`
    elif [ `uname -s` = ReliantUNIX-N ] ;then
           TOTAL_DISK=`df -k . | tail -1| awk '{print $2}'`
    else
             # works on Sun
             TOTAL_DISK=`df -b . | sed  '/avail/d' | awk '{print $2}'`
    fi
  fi
  USED100=`expr $USED \* 100`
  USG_PERC=`expr $USED100 / $TOTAL_DISK`
  echo $USG_PERC
}
#------------------------ Main process ------------------------------------------
usage()
{
    cat < -e  -l -d -m  -r 
                                    -t  -c  -v 
                                    -s  -i  -g -f

              Note :

                       -c compress file after move using either compress or gzip (if available)
                          if -c is given without -m then file will be compressed in ARCHIVE DIR
                       -d Delete selected files
                       -e Extention of files to be processed
                       -f Check if log has been applied, required -i  and -g if v8
                       -g Version 8 (use svrmgrl instead of sqlplus /
                       -i Oracle SID
                       -l List file that will be processing using -d or -m
                       -h help
                       -m move file to TARGET_DIR
                       -p Max percentage above wich action is triggered.
                          Actions are of type -l, -d  or -m
                       -t ARCHIVE_DIR
                       -s Perform action if size of target dir is bigger than MAX_SIZE (meg)
                       -v report action performed in LOGFILE
                       -r Part of files that will be affected by action :
                           2=half, 3=a third, 4=a quater .... [ default=2 ]
                       -z Check if log is still needed by logminer (used in streams),
                                it requires -i  and also -g for Oracle 8i

              This program list, delete or move half of all file whose extention is given [ or default 'arc']
              It check the size of the archive directory and if the percentage occupancy is above the given limit
              then it performs the action on the half older files.

        How to use this prg :

                run this file from the crontab, say, each hour.
     example

     1) Delete archive that is sharing common arch disk, when you are at 85% of 2500 mega perform delete half of the files
     whose extention is 'arc' using default affected file (default is -r 2)

     0,30 * * * * /usr/local/bin/watch_arc.sh -e arc -t /arc/POLDEV -s 2500 -p 85 -d -v /var/tmp/watch_arc.POLDEV.log

     2) Delete archive that is sharing common disk with oother DB in /archive, act when 90% of 140G, affect by deleting
     a quater of all files (-r 4) whose extention is 'dbf' but connect before as sysdba in POLDEV db (-i) if they are
     applied (-f is a dataguard option)

     watch_arc.sh -e dbf -t /archive/standby/CITSPRD -s 140000 -p 90 -d -f -i POLDEV -r 4 -v /tmp/watch_arc.POLDEV.log

     3) Delete archive of DB POLDEV when it reaches 75% affect 1/3 third of files, but connect in DB to check if
     logminer do not need this archive (-z). this is usefull in 9iR2 when using Rman as rman do not support delete input
     in connection to Logminer.

     watch_arc.sh -e arc -t /archive/standby/CITSPRD  -p 75 -d -z -i POLDEV -r 3 -v /tmp/watch_arc.POLDEV.log

EOF
}
#------------------------- Function section -----------------------------
if [ "x-$1" = "x-" ];then
      usage
      exit
fi

MAX_SIZE=-1  # disable this feature if it is not specificaly selected
while getopts  c:e:p:m:r:s:i:t:v:dhlfgz ARG
  do
    case $ARG in
       e ) EXT_ARC=$OPTARG ;;
       f ) CHECK_APPLIED=YES ;;
       g ) VERSION8=TRUE;;
       i ) ORACLE_SID=$OPTARG;;
       h ) usage
           exit ;;
       c ) COMPRESS_PRG=$OPTARG ;;
       p ) MAX_PERC=$OPTARG ;;
       d ) ACTION=delete ;;
       l ) ACTION=list ;;
       m ) ACTION=move
           TARGET_DIR=$OPTARG
           if [ ! -d $TARGET_DIR ] ;then
               echo "Dir $TARGET_DIR does not exits"
               exit
           fi;;
       r)  PART=$OPTARG ;;
       s)  MAX_SIZE=$OPTARG ;;
       t)  ARC_DIR=$OPTARG ;;
       v)  VERBOSE=TRUE
           LOG=$OPTARG
           if [ ! -f $LOG ];then
               > $LOG
           fi ;;
       z)  LOGMINER=TRUE;;
    esac
done

if [ "x-$ARC_DIR" = "x-" ];then
     echo "NO ARC_DIR : aborting"
     exit
fi
if [ "x-$EXT_ARC" = "x-" ];then
     echo "NO EXT_ARC : aborting"
     exit
fi
if [ "x-$ACTION" = "x-" ];then
     echo "NO ACTION : aborting"
     exit
fi

if [ ! "x-$COMPRESS_PRG" = "x-" ];then
   if [ ! "x-$ACTION" =  "x-move" ];then
         ACTION=compress
   fi
fi

if [ "$CHECK_APPLIED" = "YES" ];then
   if [ -n "$ORACLE_SID" ];then
         export PATH=$PATH:/usr/local/bin
         export ORAENV_ASK=NO
         export ORACLE_SID=$ORACLE_SID
         . /usr/local/bin/oraenv
   fi
   if [ "$VERSION8" = "TRUE" ];then
      ret=`svrmgrl <> $LOG
                                 fi ;;
                      'delete' ) rm $ARC_DIR/$ARC
                                 if [ "x-$VERBOSE" = "x-TRUE" ];then
                                       echo " `date +%d-%m-%Y' '%H:%M` : $ARC deleted" >> $LOG
                                 fi ;;
                      'list'   )   ls -l $ARC_DIR/$ARC ;;
                      'move'   ) mv  $ARC_DIR/$ARC $TARGET_DIR
                                 if [ ! "x-$COMPRESS_PRG" = "x-" ];then
                                       $COMPRESS_PRG $TARGET_DIR/$ARC
                                       if [ "x-$VERBOSE" = "x-TRUE" ];then
                                             echo " `date +%d-%m-%Y' '%H:%M` : $ARC moved to $TARGET_DIR and compressed" >> $LOG
                                       fi
                                 else
                                       if [ "x-$VERBOSE" = "x-TRUE" ];then
                                             echo " `date +%d-%m-%Y' '%H:%M` : $ARC moved to $TARGET_DIR" >> $LOG
                                       fi
                                 fi ;;
                  esac

          done
      else
          echo "Warning : The filesystem is not full due to archive logs !"
          exit
      fi
elif [ "x-$VERBOSE" = "x-TRUE" ];then
     echo "Nothing to do at `date +%d-%m-%Y' '%H:%M`" >> $LOG
fi

Pull on the RMAN backup archive logs?

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

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

1 manually transfer the backup to forward files

2 replace the archivelog destination configured on the eve

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

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

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

Kind regards
Oscar

DG is reliable?

Hi all
11.2.0.1
We have DG physical standby created for our site recovery. Whereas the implementation and follow-up of this standby db, sometimes I meet gaps for archivelogs error not created the day before. For some unknown reason it lacks (especially arch 1 newspaper) but newspapers succeeding as 5 or more are pending or not applied. To solve the problem, I then copy the missing archivelog from primary to standby and resume the auto recovery.

My question is, what happens if during this period of issue of gap, one strike all wiping our main server disaster? So this means I have a lot of lost transactions?

Your opinions and comments are very much appreciated.

Thank you
pK

f55237a7-2c38-4DB3-a7a3-1d77256f0730 wrote:

Trunc, Mahir, Anar, thanks

TRUE or FALSE.

If you have configured properly which meets the requirement of network, YOU WILL NEVER ENCOUNTER GAPS?

This means that your archivelog transportation will be always perfect?

Someone at - it you don't yet meet gaps?

Thank you

It's a very difficult question, we cannot say what we expect in the future

But if your DataGuard works well and monitor you, checking every thing, they don't have space,

then we can say that you can protect your data with DataGuard technology.

Concerning

Mahir

What to do after starting db_recovery_file_dest is full

We have an installer of data with the primary and secondary physical custody both on 11g 2. A few days before Flash_recover_area is full and replication stopped. Now, I cleaned the disc and made room for log shipping. I saw the new files, redo log shipped to the standby host.
The last post I've seen in alert_log Eve's daughter

Archived Log entry 6191 added for thread 3 sequence 2735 rlc 710164789 ID 0x33498a35 dest 2:
RFS[14958]: Opened log for thread 3 sequence 2737 dbid 860456245 branch 710164789
Archived Log entry 6192 added for thread 3 sequence 2736 rlc 710164789 ID 0x33498a35 dest 2:
Archived Log entry 6193 added for thread 3 sequence 2737 rlc 710164789 ID 0x33498a35 dest 2:
Mon Aug 16 14:11:30 2010
RFS[14960]: Assigned to RFS process 29122
RFS[14960]: Identified database type as 'physical standby': Client is Foreground pid 22317

Check v$ archived_log

select thread#,applied, max(sequence#) max_sequence#,count(*) from v$archived_log 
 group by thread#, applied order by 1;

THREAD#                     APPLIED                     MAX_SEQUENCE#               COUNT(*)                    
1                           NO                          3731                        831                         
1                           YES                         2912                        1544                        
2                           NO                          2642                        786                         
2                           YES                         1868                        1069                        
3                           NO                          2739                        810                         
3                           YES                         1941                        1157

I didn't know the current session in standby. is the replication in the treatment? If so, why, all sessions are inactive.
What should I do to restart the replication if it is not already started.

Dear user13148231,

Oracle cannot feel the archivelogs you copied across. You must register all first to inform Oracle that the missing archivelog sequences are there in the archivelog directory.

ALTER DATABASE REGISTER LOGFILE '/PATH/ARC_LOG_FILE_NAME';

After registering, you must restart the MRP (managed recovery) process and see that the MRP will apply this archivelogs one by one. He traces the v $ archived_log corrected display.

Hope that helps.

Ogan

RMAN identifies corrupted block
Hello

If Rman identify block corrupted when running a backup of archive logfiles, this failover to an existing copy intact... wht means tht...
If there is no copy available then RMAN backup fails. You can replace this using skip inaccessible option with the backup command.

RMAN > BACKUP DATABASE MORE ARCHIVELOG SKIP INACCESSIBLE; OR
RMAN > BACKUP ARCHIVELOG ALL JUMP INACCESSIBLE;

BUT compromising sthe database as current missed archivelog file recovery is not the backup. The SKIP INACCESSIBLE option requires just the RMAN to continue the backup if it lacks an archivelog. This completes the backup of all the other data files, files archivelog, controlfiles. Don't miss the backup in this case.

RMan is missing some files when deleting obsolete archivelogs
Hi all

in one of our databases 9iR2, I noticed a rather strange behavior of the RMan delete obsolete archivelogs. The RMan script has the "OBSOLETE RECOVERY WINDOW DELETE 7 DAYS DEVICE TYPE DISK"-command. If RMan deletes the archivelogs regularly. But unfortunately, in every race, it leaves 3 files cancelled. The log file is (only relevant lines):

Remove the following obsolete backups and copies:
Making key time filename/handle type
---- ----
Archive 24779 08 - SEVEN journal.-10 /oralogs/oraArchive/VG41MED/VG41MED_12402.ora
Archive Log 24780 08-SEVEN.-10 /oralogs/oraArchive/VG41MED/VG41MED_12403.ora
...
Archive 24785 08 - SEVEN journal.-10 /oralogs/oraArchive/VG41MED/VG41MED_12408.ora

on the next race (the next day) the log file says:

Remove the following obsolete backups and copies:
Making key time filename/handle type
---- ----
Archive Log 24799 09-SEPT.-10 /oralogs/oraArchive/VG41MED/VG41MED_12412.ora
Archive 24800 09 - SEVEN journal.-10 /oralogs/oraArchive/VG41MED/VG41MED_12413.ora
...
Archive Log 24805 09-SEPT.-10 /oralogs/oraArchive/VG41MED/VG41MED_12418.ora

As you can see, RMan lack VG41MED12409.ora log file, VG41MED12410.ora, and VG41MED_12411.ora that are available before and after the backup procedure. We treat archivelogs on operating system level. A "overlap archivelog all ' - command does not list these 3 files, if the database thinks that they are removed - which is not really true. This odd pattern is repeated every day, so my archivelog directory is growing everyday with the 3 files not deleted.

This behavior appears still more strange, because the RMan backup script even run on 3 other databases with same structure does not show this "error". I checked the configuration of 4 databases and not detected no difference.

Maybe it's a corrupt controlfile (we do not catalog-db). Someone has any idea how to solve this problem?

Thank you
Friedhelm

Edited by: user8964905 the 20.09.2010 00:18
Hello
(1) I think the command of OVERLAP is the only way to know what archivelogs are always specific to the database (expired or available) kn.
(2) thank you for your explanations. You're right - the order REPORT OBSOLETE list backups, but my problem are the obsolete archivelogs of backups. If my humble opinion REPORT OBSOLETE wouldn't help.

In fact no and no :).

(1) a simple
```
list archivelog all;
```
lists the known archivelog (expired or available) files.
```
crosscheck archivelog all;
```
will check if the information on their availability is still topical, but it will not help you in this case (they exist!)

2.
```
report obsolete recovery...;
```
http://download.Oracle.com/docs/CD/B10501_01/server.920/a96566/rcmconc3.htm#463220
Order REPORT displays OBSOLETE backups and copies of data files, control files, and archived redo logs that can be deleted because they are no longer needed.
...
OK, but if you read a little more of the documentation:
...
In addition to backups of file obsolete data, RMAN reports obsolete archived newspapers and archived backups of logs. When backups of files of data from one point in time are obsolete, then archived logs that can apply to these data files are also is no longer necessary and become obsolete according to the specified retention policy.

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

I have increased the CONTROLFILE_RECORD_KEEP_TIME now and watch the results next night. Perhaps the reason for this behavior is the fact that this database is very small compared to other databases, which do not show the effect.
I'll post the result of this strategy, here the next few days.
Wait & see

Best regards
Phil

Waiting for redo log file missing when restore main database using RMAN backup that was taken on the database physical standby

Here's my question after tons of research and test without have the right solutions.
Target:
(1) I have a 12.1.0.2 database unique main enterprise 'testdb' as database instance running on the server "node1".
(2) I created physical standby database "stbydb" on the server "node2".
(3) DataGuard running on the mode of MaxAvailability (SYNC) with roll forward in real time 12 default c apply.
(4) primary database has 3 groups of one-man redo. (/oraredo/testdb/redo01.log redo02.log redo03.log)
(5) I've created 4 standby redo logfiles (/oraredo/testdb/stby01.log stby02.log stby03.log stby04.log)
(6) I do RMAN backup (database and archivelog) on the site of relief only.
(7) I want to use this backup for full restore of the database on the primary database.
He is a DR test to simulate the scenario that has lost every primary & Eve total servers.
Here is how to save, on the database pending:
(1) performance 'alter database recover managed standby database Cancel' to ensure that compatible data files
(2) RMAN > backup database;
(3) RMAN > backup archivelog all;
I got elements of backup and copied to primary db Server something like:
/Home/Oracle/backupset/o1_mf_nnndf_TAG20151002T133329_c0xq099p_.BKP (data files)
/Home/Oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.BKP (spfile & controlfile)
/Home/Oracle/backupset/o1_mf_annnn_TAG20151002T133357_c0xq15xf_.BKP (archivelogs)
So here's how to restore, on the main site:
I clean all the files (data files, controlfiles oder all gone).
(1) restore spfile from pfile
RMAN > startup nomount
RMAN > restore spfile from pfile ' / home/oracle/pfile.txt' to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';
(2) modify pfile to convert to db primary content. pFile shows below
*.audit_file_dest='/opt/Oracle/DB/admin/testdb/adump '
* .audit_trail = "db".
* full = '12.1.0.2.0'
*.control_files='/oradata/testdb/control01.ctl','/orafra/testdb/control02.ctl'
* .db_block_size = 8192
* .db_domain = "
*.db_file_name_convert='/testdb/','/testdb /'
* .db_name = "testdb".
* .db_recovery_file_dest ='/ orafra'
* .db_recovery_file_dest_size = 10737418240
* .db_unique_name = "testdb".
*.diagnostic_dest='/opt/Oracle/DB '
* .fal_server = "stbydb".
* .log_archive_config = 'dg_config = (testdb, stbydb)'
* .log_archive_dest_2 = "service = stbydb SYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = stbydb'"
* .log_archive_dest_state_2 = 'ENABLE '.
*.log_file_name_convert='/testdb/','/testdb /'
* .memory_target = 1800 m
* .open_cursors = 300
* runoff = 300
* .remote_login_passwordfile = "EXCLUSIVE."
* .standby_file_management = "AUTO".
* .undo_tablespace = "UNDOTBS1.
(3) restart db with updated file pfile
SQLPLUS > create spfile from pfile='/home/oracle/pfile.txt'
SQLPLUS > the judgment
SQLPLUS > startup nomount
(4) restore controlfile
RMAN > restore primary controlfile to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';
RMAN > change the editing of the database
(5) all elements of backup catalog
RMAN > catalog starts by ' / home/oracle/backupset / '.
(6) restore and recover the database
RMAN > restore database;
RMAN > recover database until the SNA XXXXXX; (this YVERT is the maximum in archivelog backups that extends beyond the scn of the backup of the data file)
(7) open resetlogs
RMAN > alter database open resetlogs;
Everything seems perfect, except one of the file log roll forward pending is not generated
SQL > select * from v$ standby_log;
ERROR:
ORA-00308: cannot open archived log ' / oraredo/testdb/stby01.log'
ORA-27037: unable to get file status
Linux-x86_64 error: 2: no such file or directory
Additional information: 3
no selected line
I intended to use the same backup to restore primary basic & helps record traffic and the downtime between them in the world of real output.
So I have exactly the same steps (except STANDBY restore CONTROLFILE and not recover after database restore) to restore the database pending.
And I got the same missing log file.
The problem is:
(1) complete alert.log filled with this error, not the concern here
(2) now repeat it in real time apply won't work since the Party shall LGWR shows always "WAITING_FOR_LOG."
(3) I can't delete and re-create this log file
Then I tried several and found:
The missing standby logfile was still 'ACTIVE' at present RMAN backup was made.
For example, on db standby, under Group #4 (stby01.log) would be lost after the restoration.
SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;
GROUP # SEQUENCE # USED STATUS
---------- ---------- ---------- ----------
4 19 ACTIVE 133632
5 0 0 UNASSIGNED
6 0 0 not ASSIGNED
7 0 0 UNASSIGNED
So until I take the backup, I tried on the primary database:
SQL > alter system set log_archive_dest_state_2 = delay;
This was the Group of standby_log side Eve #4 was released:
SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;
GROUP # SEQUENCE # USED STATUS
---------- ---------- ---------- ----------
4 0 0 UNASSIGNED
5 0 0 UNASSIGNED
6 0 0 not ASSIGNED
7 0 0 UNASSIGNED
Then, the backup has been restored correctly without missing standby logfile.
However, to change this primary database means break DataGuard protection when you perform the backup. It's not accept on the production environment.
Finally, my real questions come:
(1) what I do may not do on parameter change?
(2) I know I can re-create the control file to redo before delete and then recreate after. Is there any simple/fast to avoid the standby logfile lost or recreate the lost one?
I understand that there are a number of ways to circumvent this. Something to keep a copy of the log file waiting restoration progress and copy up one missing, etc, etc...
And yes I always have done no real-time applies "to the aid of archived logfile" but is also not accept mode of protection of production.
I just want proof that the design (which is displayed in a few oracle doc Doc ID 602299.1 is one of those) that backs up data backup works effectively and can be used to restore the two site. And it may be without spending more time to resume backups or put the load on the primary database to create the database before.
Your idea is very much appreciated.
Thank you!

Hello

1--> when I take via RMAN backup, RMAN does not redo log (ORL or SRL) file, so we cannot expect ORLs or SRL would be restored.

2nd--> when we opened the ORL database should be deleted and created

3rd--> Expecting, SRL should not be an issue.we should be able to do away with the fall.

DR sys@cdb01 SQL > select THREAD #, SEQUENCE #, GROUP #, STATUS from v$ standby_log;

THREAD # SEQUENCE # GROUP # STATUS

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

1 233 4 ACTIVE

1 238 5 ACTIVE

DR sys@cdb01 SQL > select * from v$ logfile;

GROUP # STATUS TYPE MEMBER IS_ CON_ID

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

3 /u03/cdb01/cdb01/redo03.log no. 0 online

/U03/cdb01/cdb01/redo02.log no. 0 2 online

1 /u03/cdb01/cdb01/redo01.log no. 0 online

4 /u03/cdb01/cdb01/stdredo01.log WATCH No. 0

/U03/cdb01/cdb01/stdredo02.log EVE 5 No. 0

DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

method: cannot access the /u03/cdb01/cdb01/stdredo01.log: no such file or directory

DR sys@cdb01 SQL >! ls - ltr /u03/cdb01/cdb01/stdredo02.log

-rw - r-. 1 oracle oinstall 52429312 17 Oct 15:32 /u03/cdb01/cdb01/stdredo02.log

DR sys@cdb01 SQL > alter database force claire logfile 4;

change the database group claire logfile 4

*

ERROR on line 1:

ORA-01156: recovery or current flashback may need access to files

DR sys@cdb01 SQL > alter database recover managed standby database cancel;

Database altered.

DR sys@cdb01 SQL > change the database group claire logfile 4;

Database altered.

DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

-rw - r-. 1 oracle oinstall 52429312 17 Oct 15:33 /u03/cdb01/cdb01/stdredo01.log

DR sys@cdb01 SQL >

If you do, you can recreate the controlfile without waiting for redo log entry...

If you still think it's something is not acceptable, you must have SR with support to analyze why he does not abandon SRL when controlfile_type is "underway".

Thank you

Recover a database using the archivelogs

We have restored a backup of cold base using avamar from one server to another. All data, controlfiles, pfiles files are in place right after restoration. It is a 9i database. All I have to do now is to recover the database to a point in time which is 3 days after the last cold backup. I have all necessary archivelogs that transferred to destination Ark. Here are the steps that I think we need to do to recover the database using the archivelogs until the point in time with RMAN:
RUN {}
BOOTABLE MEDIA;
RECOVER THE DATABASE;
ALTER DATABASE OPEN;
}
Please let me know if I'm missing something here.

your third step is able, as sybrand_b said that your DB is already in a consistent state.

The backup controlfile clause must notify oracle that SNA to controlfile is not common and needs recovery to bring back to the most recent State, is recommended to use the backup controlfile clause if you are recovering from an old controlfile or recreated controlfile.

Mark post below to roll forward from a cold backup.

Hemant Oracle DBA blog: RollForward from backup to cold

Duplicate target database failed with the newspaper missing in the CCR

Hi all
I'm duplicating a database of node 2 CARS to the test environment.
I took archivelog and pending full database backup in the database. dB Dimensions 950 g.
I restored it to test the environment but get error during recovery
operating system: aix 7.1
version of DB: oracle 10g
I ran the following command to launch two copies
RMAN > run
2 > {}
3 > allocate auxiliary channel ch1 type disk;
4 > allocate auxiliary channel ch2 type disk;
5 > allocate auxiliary channel ch3 type disk;
6 > allocate auxiliary channel ch4 type disk;
7 > target database duplicate testing up to THAT TIME "2013-12 - 25:10:47:00';"
{8 >}
and get below error
content of Script memory:
{
until ' 2013-12 - 25:10:47:00 ";
recover
clone database
delete archivelog
;
}
execution of Script memory
executing command: SET until clause
From pick up to 2013-12 - 27:18:12:49
starting media recovery
Oracle error:
ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error
ORA-01194: file 1 needs a recovery more match
ORA-01110: data file 1: '+ DATA/test/datafile/system.390.835293413 '.
output channel: ch1
output channel: ch2
output channel: ch3
output channel: ch4
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of Db in dual at 27/12/2013 18:14:10
RMAN-03015: an error has occurred in the script stored memory Script
RMAN-06053: unable to perform the recovery of the media because of the missing journal
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291696 lowscn 74780879027
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153927 lowscn 74780427224
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291691 lowscn 74763859437
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291690 lowscn 74763843501
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291689 lowscn 74762972560
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153920 lowscn 74761443419
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291688 lowscn 74758111689
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153919 lowscn 74758103358
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291687 lowscn 74758088445
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153918 lowscn 74758078214
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291686 lowscn 74758067675
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153917 lowscn 74758049415
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291685 lowscn 74758046873
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291684 lowscn 74758026214
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153916 lowscn 74757674479
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291683 lowscn 74757658342
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153915 lowscn 74757643881
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291682 lowscn 74757641006
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291681 lowscn 74757621180
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153914 lowscn 74757618464
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291680 lowscn 74757599470
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153913 lowscn 74757584128
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291679 lowscn 74757584121
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291678 lowscn 74757567231
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291677 lowscn 74757550865
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153912 lowscn 74757547289
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291676 lowscn 74757533624
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153911 lowscn 74757513739
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291675 lowscn 74757513659
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291674 lowscn 74757498265
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291673 lowscn 74757483667
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153910 lowscn 74757469005
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291672 lowscn 74757468526
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291671 lowscn 74757453293
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291670 lowscn 74757440237
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153909 lowscn 74757426220
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291669 lowscn 74757422172
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291668 lowscn 74757407202
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153908 lowscn 74757389651
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291667 lowscn 74757386560
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291666 lowscn 74757369955
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153907 lowscn 74757352175
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291665 lowscn 74757351898
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291664 lowscn 74757335274
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291663 lowscn 74757319172
RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153906 lowscn 74757314019
RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291662 lowscn 74756304245
MAN-06102: no restaurant chain
RMAN >
RMAN >
well let me know what command should I use to do the archivelog backup if it is not present in our existing backup, restore and recover up to what sequence and thread

Can you restore your backup to tape archivelogs and apply them manually to the restoration of the database?

list backup of archivelog from the logseq in the error message to check if they are available. And what type of device. You may find that they are available on the device of type TAPE (SBT) but you specified the device DISC type in the command duplicate.

As long as you have the archivelogs need supported somewhere, you can restore it and apply then having the OPEN RESETLOGS command completed successfully

"The Archivelog file size" and the question of 'db_recovery_file_dest_size.

Hello
According to the literature, DB_RECOVERY_FILE_DEST specifies the default location for the flash recovery area. The flash recovery area contains copies of files of control current multiplexes and remake online of newspapers, but also archived redo logs
And DB_RECOVERY_FILE_DEST_SIZE specifies (in bytes) of the strict limit on the total space to be used by the target database recovery files created in the flash recovery area.
Here's the info from my database (10 gr 2, RHEL 64-bit database is in archivelog mode):
Log_archive_dest_1 = ' LOCATION = + recovery /'
db_recovery_file_dest = '+ RECOVERY. "
db_recovery_file_dest_size = 550 GB
-Size of archivelog files:
Select
SUM(BLOCKS * BLOCK_SIZE)/1024/1024/1024 SIZE_GB
Of
V$ ARCHIVED_LOG
-> 672,39 GB
If I have question used flash recovery area space, it is to be:
SELECT name
, ceil (space_limit / 1024 / 1024) SIZE_M
, ceil (space_used / 1024 / 1024) USED_M
, decode (nvl (space_used, 0),)
0, 0
ceil ((space_used / space_limit) * 100)) PCT_USED
V $ recovery_file_dest
ORDER BY name
NAME SIZE_M USED_M PCT_USED
+ 563200 8 1 RECOVERY
I'm confused where are the archivelogs saved if not + recovery?
Total current total size of ARCHIVELOG files if "672.39" but especially the request saying that only 8% of the db_recovery_file_dest was used. So obviously they are either not in + RECOVERY or they are not accounted for.
I chedk on ASM using asmcmd:
ASMCMD > cd ARCHIVELOG
ASMCMD > ls
2013_09_05 /.
2013_09_06 /.
2013_09_09 /.
2013_09_10 /.
2013_09_11 /.
2013_09_12 /.
ASMCMD >
Whereas the query on the view V$ ARCHIVED_LOG shows me the file names for the month of August as well.
I don't know that I am misunderstanding/missing something. I'm lost :-(
Please advise!
Thanks in advance!

You wrong understand archiving at the area of fast recovery works. You have done the fast recovery area to a certain destination and also set up check-in to the same physical location: but Oracle doesn't know that they are in the same place. You must explicitly set:

ALTER system set log_archive_dest_1 is 'location = USE_DB_RECOVERY_FILE_DEST';.

and then Oracle will understand and follow the space in the paper archive used against the db_recovery_file_dest_size.

--

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

Missing ARCHIVELOG

Similar Questions

Maybe you are looking for