Missing archivelog in standby db

In Standby database, if some archive logs are missing (could not be transferred), then how do you recover?
pls advice

Hi
If archivelog is exists at primary site and due to network failure not transfered at standby site then copy it from primary site and paste at standby site then
alter database register logfile '<location of archivelog>';
If some archivelog is not transfered at standby site and it is also deleted from primary site and you also don't have backup of it then you need to recreate standby again.
Tinku

Similar Messages

  • Pb of doubled archivelog at standby

    Hi all,
    I've got doubled archivelog at standby and this stops the normal applying process :
    SQL> select thread#,first_time, applied, registrar from v$archived_log where sequence#=3868;
    THREAD# FIRST_TIME APP REGISTR
    2 10/07/25 20:20:10 YES RFS
    *1 10/07/26 19:49:51 NO RFS*
    1 10/07/26 19:49:51 YES RFS
    How to delete the line marked 'NO' beacause the number 3868 has already be applied ?
    TIA
    Yang

    TIA.
    Standby database :
    SQL> show parameter log_archive_dest
    NAME TYPE VALUE
    log_archive_dest string
    log_archive_dest_1 string LOCATION=XXXXXXXX VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=XXXXXX
    log_archive_dest_10 string
    log_archive_dest_2 string SERVICE=XXXXXX VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=XXXXXX
    log_archive_dest_3 string
    log_archive_dest_4 string
    log_archive_dest_5 string
    log_archive_dest_6 string
    log_archive_dest_7 string
    log_archive_dest_8 string
    log_archive_dest_9 string
    log_archive_dest_state_1 string enable
    log_archive_dest_state_10 string enable
    log_archive_dest_state_2 string enable
    log_archive_dest_state_3 string enable
    log_archive_dest_state_4 string enable
    log_archive_dest_state_5 string enable
    log_archive_dest_state_6 string enable
    log_archive_dest_state_7 string enable
    log_archive_dest_state_8 string enable
    log_archive_dest_state_9 string enable

  • Missing archivelog

    All
    could u answer 2 question?
    1. In rman one archivelog is deleted unknowly.afer that i given command crosscheck archivelog all. can i restore if some transcation happened in the missing archivelog ?
    2.what is purpose of root.sh ?
    Regards
    baheer

    [email protected] wrote:
    All
    could u answer 2 question?
    1. In rman one archivelog is deleted unknowly.afer that i given command crosscheck archivelog all. can i restore if some transcation happened in the missing archivelog ?If you have deleted any archived redo log file and you haven't backup of it, then you can recover until that deleted archived redo log file. But you can contact to ORacle Support to help you to bypass the missed archived redo log file and apply archived redo log files generated after it. Do it only with the help of Oracle Support
    2.what is purpose of root.sh ?Refer to the following link:
    http://dbaforums.org/oracle/index.php?showtopic=17429
    >
    Regards
    baheer

  • Rman backup with a missing archivelog.

    hello,
    I backed my database up yesterday after you guys helped me fix few problems I had on it. I used RMAN with the following command in a run block:
    *run {*
    allocate channel t1 type disk;
    backup current controlfile ;
    backup database;
    backup archivelog all delete input;
    release channel c1;
    At the end of the operation, RMAN indicates that and archivelog is missing and it couldn't find it. As a result, recover operation can be compromised. Now am confused because I do not know whether the command executed successfully or not and how to fix the missing archivelog.
    Below is the entire output of the operation along with error message:
    canal affectÚ : t1
    canal t1 : sid=131 typedev=DISK
    DÚmarrage de backup dans 16/04/09
    canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
    canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
    insertion du fichier de contr¶le en cours dans l'ensemble de sauvegarde
    canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
    canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
    pointeur=+ASMTEST/meta4/backupset/2009_04_16/ncnnf0_tag20090416t211049_0.334.684
    *364257 Útiquette=TAG20090416T211049 commentaire=NONE*
    canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:00:14
    Fin de backup dans 16/04/09
    DÚmarrage de backup dans 16/04/09
    canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
    canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
    fichier de donnÚes en entrÚe fno=00008 nom=+ASMTEST/meta4/m4prod.dbf
    fichier de donnÚes en entrÚe fno=00010 nom=H:\ORADATA\M4REC.DBF
    fichier de donnÚes en entrÚe fno=00009 nom=E:\DATAFILEMETA4\M4PROD02.DBF
    fichier de donnÚes en entrÚe fno=00001 nom=+ASMTEST/meta4/system01.dbf
    fichier de donnÚes en entrÚe fno=00003 nom=+ASMTEST/meta4/sysaux01.dbf
    fichier de donnÚes en entrÚe fno=00006 nom=C:\TEST.DBF
    fichier de donnÚes en entrÚe fno=00007 nom=+ASMTEST/meta4/meta4.dbf
    fichier de donnÚes en entrÚe fno=00005 nom=+ASMTEST/meta4/example01.dbf
    fichier de donnÚes en entrÚe fno=00002 nom=+ASMTEST/meta4/undotbs01.dbf
    fichier de donnÚes en entrÚe fno=00004 nom=+ASMTEST/meta4/users01.dbf
    canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
    canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
    pointeur=+ASMTEST/meta4/backupset/2009_04_16/nnndf0_tag20090416t211107_0.333.684
    *364271 Útiquette=TAG20090416T211107 commentaire=NONE*
    canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:51:10
    canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
    canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
    insertion du fichier de contr¶le en cours dans l'ensemble de sauvegarde
    inclusion du SPFILE en cours dans l'ensemble de sauvegarde
    canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
    canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
    pointeur=+ASMTEST/meta4/backupset/2009_04_16/ncsnf0_tag20090416t211107_0.345.684
    *367351 Útiquette=TAG20090416T211107 commentaire=NONE*
    canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:00:26
    Fin de backup dans 16/04/09
    DÚmarrage de backup dans 16/04/09
    journal en cours archivÚ
    canal libÚrÚ : t1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: Úchec de la commande backup Ó 04/16/2009 22:04:03
    RMAN-06059: journal d'archivage attendu introuvable ; la perte du journal d'arch
    ivage compromet la possibilitÚ de rÚcupÚration
    ORA-19625: erreur lors de l'identification du fichier H:\ARCHIVEMETA4\ARC00001_0
    *682674928.001*
    ORA-27041: ouverture du fichier impossible
    OSD-04002: ouverture impossible du fichier
    O/S-Error: (OS 2) Le fichier spÚcifiÚ est introuvable.
    Here's my nderstanding and please correct me if am wrong:
    The first 3 instructions of the run block executed successfully, but
    the last one didn't. Is that so?
    Whatever the understanding, do I have a backup? WHat can I do to have a consistent backup?
    Thanks in advance.

    Adomi,
    It is sad to see you are still running RMAN in 8i fashion where you are on 10g.
    The script is bs, sorry
    run {
    allocate channel t1 type disk; -- not required
    backup current controlfile ; -- not required, as this is already done by backup database
    backup database;
    backup archivelog all delete input;
    release channel c1; -- not required.
    If you have controlfile autobackup on, you could just
    backup database plus archivelog
    and be done with it.
    As you didn't make a RMAN backup from the start, your backup archivelog statement should have read
    backup archivelog all skip inaccessible delete input;
    Once that succeeds Oracle shouldn't need the archivelog anymore, and you should make a second backup without the skip inaccessible clause.
    Sybrand Bakker
    Senior Oracle DBA

  • Manual Standby Database not in sync with missing archivelogs

    Hello,
    OS: Solaris
    DB: Oracle 11.2.0.1 EE
    Not Using ASM or RAC
    I have a Production database that is in archivelog mode and a Standby DR server.
    Both servers (Prod, Standby) have exact same structure and db name/version.
    We manually scp archive logs and recover them to a manual standby database via SQL Scripts "cron". (I.E. set autorecovery on; recover standby database;)
    We recently got out of sync with our log files and have not been applying them to the standby. As part of Prod Maintenance, these log files were deleted and are not available anymore.
    I've tried several ways to "rebuild" our standby database. I have tried to Shutdown prod, backup all the db files and scp them to standby, re-create standby controlfile and startup mount and recover standby.
    Every time I try to apply a new archive log via recover standby, these are the errors:
    ORA-00279: change 211077622 generated at 1/27/2012 12:18:42 needed for thread 1
    ORA-00289: suggestion : /oradump/arch/PROD/PROD_arch_1_69486_736618850.arc
    ORA-00280: change 211077622 for 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 obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-10879: error signaled in parallel recovery slave
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/oradevices/PROD/oraPRODsystem1.dbf'
    When I check v$log_history, the new logs have not been applied.
    I've also tried the "Restore from incremental backup via SCN" method with same results.
    Is there a way to re-create the standby clean and ensure that the log chain that is currently broken gets fixed or reset?
    I would eventually like to get DataGuard in here, but that's not the case at the moment.
    Thanks for your suggestions.
    -Dav

    if you are using the cold backup to create the standby database, Check that have you followed the following steps or not.
    1. remove
    all the datafiles and controlfiles from the standby database.
    2. Create a new standby controlfile of the production for standby using the following cmd
    'alter database create standby controlfile as 'Location';'
    3. move the new controlfile to standby database server location as specified in initialization parameter file.
    4. Restore all the datafiles to its appropriate loaction which was taken through cold backup.
    5. startup nomount
    6. alter database mount standby database;
    7. recover standby database.
    scp the archive log sequence that is asked by the database, from production.
    You can try this steps.

  • Recover database with missing archivelog...

    Oracle10gR2 RHEL 4
    Hi,
    I am having a problem. I'm trying to recover my database to an previous point in time but the archive logs that I need were accidentally removed. Is there anyway I can restore it to a previous point in time? None of the SCN's are working no matter how far I go back (note: I can created the database lastweek so it can't go further than that).
    Thanks
    RMAN> recover database until time "to_date('2008-04-08:17:47:00','YYYY-MM-DD:HH24:MI:SS')";
    Starting recover at 14-APR-08
    using channel ORA_DISK_1
    starting media recovery
    archive log thread 2 sequence 4 is already on disk as file +FLASH1/vmracdev/archivelog/2008_04_08/thread_2_seq_4.290.651538751
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 04/14/2008 16:11:11
    RMAN-06053: unable to perform media recovery because of missing log
    RMAN-06025: no backup of log thread 1 seq 9 lowscn 153309685 found to restore
    RMAN> recover database until SCN 153330712;
    Starting recover at 14-APR-08
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 04/14/2008 16:12:40
    RMAN-06556: datafile 1 must be restored from backup older than scn 153330712
    RMAN> recover database until SCN 153266607;
    Starting recover at 14-APR-08
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 04/14/2008 16:15:01
    RMAN-06556: datafile 1 must be restored from backup older than scn 153266607

    Ok, I am trying that but I get the following error:
    RMAN> recover database until SCN 153219977;
    Starting recover at 17-APR-08
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 04/17/2008 13:33:00
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    And this is the latest SCN I have.
    Thanks

  • Recovery process applies old archivelogs on standby database

    Right now my standby database is in sync with my primary database and is waiting for the archived log sequeuence# 8378 to arrive.
    But when I stop the recovery process (alter database recover managed standby database cancel;) and re-start it (alter database recover managed standby database disconnect), it starts all over again and starts applying archive logs starting from the sequence# 5739 (looks like its scanning thru the logs). To catchup with primary it takes 2+ hours as it need to skim thru all the logs starting from 5739 to 8377.
    Please let me know if you need any further information to fix this.
    Thank you
    Sunny boy
    Details:
    Database version: 11.2.0.3
    OS : RHEL 5
    On Standby Database
    SQL> SELECT THREAD#, MAX(SEQUENCE#) AS "LAST_APPLIED_LOG"
    FROM V$LOG_HISTORY
    GROUP BY THREAD#; 2 3
    THREAD# LAST_APPLIED_LOG
    1 8377
    Alert log
    alter database recover managed standby database disconnect
    Attempt to start background Managed Standby Recovery process (MNODWDR)
    Tue May 08 16:13:09 2012
    MRP0 started with pid=28, OS id=26150
    MRP0: Background Managed Standby Recovery process started (MNODWDR)
    started logmerger process
    Tue May 08 16:13:15 2012
    Managed Standby Recovery not using Real Time Apply
    Parallel Media Recovery started with 8 slaves
    Waiting for all non-current ORLs to be archived...
    All non-current ORLs have been archived.
    Completed: alter database recover managed standby database disconnect
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/arch/mnodw_1_5739_765032423.arc
    Tue May 08 16:13:48 2012
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5740.1466.781015749
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5741.1468.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5742.1474.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5743.1473.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5744.1477.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5745.1478.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5746.1472.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5747.1475.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5748.1469.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5749.1470.781017203
    Tue May 08 16:13:57 2012
    Edited by: Sunny boy on May 8, 2012 5:29 PM

    Hello;
    V$LOG_HISTORY is the information from the control file. I would use a different query to check :
    From the Primary :
    SET PAGESIZE 140
    COL DB_NAME FORMAT A10
    COL HOSTNAME FORMAT A14
    COL LOG_ARCHIVED FORMAT 999999
    COL LOG_APPLIED FORMAT 999999
    COL LOG_GAP FORMAT 9999
    COL APPLIED_TIME FORMAT A14
    SELECT
       DB_NAME, HOSTNAME, LOG_ARCHIVED, LOG_APPLIED, APPLIED_TIME, LOG_ARCHIVED-LOG_APPLIED LOG_GAP
    FROM
    ( SELECT
       NAME DB_NAME
    FROM
       V$DATABASE
    SELECT
       UPPER(SUBSTR(HOST_NAME,1,(DECODE(INSTR(HOST_NAME,'.'),0,LENGTH(HOST_NAME), (INSTR(HOST_NAME,'.')-1))))) HOSTNAME
    FROM
       V$INSTANCE
    SELECT
       MAX(SEQUENCE#) LOG_ARCHIVED
    FROM
       V$ARCHIVED_LOG
    WHERE
       DEST_ID=1
    AND
       ARCHIVED='YES'
    SELECT
       MAX(SEQUENCE#) LOG_APPLIED
    FROM
       V$ARCHIVED_LOG
    WHERE
       DEST_ID=2
    AND
       APPLIED='YES'
    SELECT
       TO_CHAR(MAX(COMPLETION_TIME),'DD-MON/HH24:MI') APPLIED_TIME
    FROM
       V$ARCHIVED_LOG
    WHERE
       DEST_ID=2
    AND
       APPLIED='YES'
    );Change DEST_ID as needed for your system. I would also bump the parameter LOG_ARCHIVE_MAX_PROCESSES assuming its set to default to a higher value up to 30.
    Maybe instead of stopping the recovery process you should DEFER on the Primary
    alter system set log_archive_dest_state_2=defer;Change the _n from 2 to what your system requires. I use this and have watch DG catch up 200 archives in about 15 minutes.
    You have Standby Redo setup and are using the same size as your redo right?
    Have never seen the Standby try to apply twice.
    ORA-600 [3020] "Stuck Recovery" [ID 30866.1] ( But I do not see your issue )
    Metalink Note 241438.1 Script to Collect Data Guard Physical Standby Diagnostic Information
    Metalink Note 241374.1 Script to Collect Data Guard Primary Site Diagnostic Information
    Best Regards
    mseberg
    Edited by: mseberg on May 8, 2012 5:16 PM

  • Problem on archivelog for standby database

    Hi,
    I have an RAC architecture on linux in standard edition.
    I build a standby database on an other server in standard edition.
    I have build my standby database and open in read only but when i do some modifications in my rac i can't apply my archive logs because in
    RAC i have the thread notion and the apply give me an error:
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /db/RSAPRODS/FRA/RSAPROD/archivelog/2011_03_30/thread_1_seq_166.354.747075275
    ORA-00325: archived log for thread 2, wrong thread # 1 in header
    ORA-00334: archived log:
    I don't know how to do to generate an archive log for my standby.
    Thanks

    $ oerr ora 325
    00325, 00000, "archived log for thread %s, wrong thread # %s in header"
    // *Cause:  The archived log is corrupted or for another thread. Can not
    //          use the log for applying redo.
    // *Action: Find correct archived log.Make sure you have transfered archived redo logs in binary mode if using ftp and that they are not corrupted : you can try to use cksum or md5sum on source archived redo log and on target archived redo log.

  • How to automatically delete archivelogs on standby using RMAN?

    Hello team. I just setup a physical standby on windows environment. The primary database is been backed up via RMAN and everything works fine except that the archivelogs moved to standby site are not been deleted.
    I couldn't find some rman option to add to the scripts to take care of this issue.
    Environment:
    Windows 2003 server 32bits
    Oracle Database 9.2.0.8
    Thanks in advance!

    If you were using 10g or later you could use a deletion policy as per Oracle support note ID 728053.1.
    In 9i you need to schedule an RMAN job or shell script to delete these archives, e.g.:
    RMAN> delete archvielog all completed before 'sysdate-1';
    I have not tried it, but you can schedule also a PL/SQL script to take care of this, e.g.:
    http://www.dbasupport.com/forums/archive/index.php/t-18680.html
    http://gnjatovic.blogspot.com/2011/03/delete-applied-arhivelogs-on-standby.html

  • Recovery with missing archivelog

    I've got a client whose 10gR2 database has been running with the SYSAUX tablespace marked for "recovery" for 9 months. To properly bring SYSAUX online, they need an archivelog from 9 months ago and it no longer exists.
    They think they are in good shape, since they are in archivelog mode and are taking nightly RMAN backups.
    I contend that they are walking on very thin ice: while they can restore from last night's backup, media recovery is impossible and they risk losing up to 24 hours of data.
    Am I correct? Or is there some way to perform an RMAN "recover" operation that by-passes the SYSAUX tablespace, leaving it offline, but brings all the other datafiles up to date?
    I have performed a test using a sample database and my theory is confirmed. But I would like a reality check in case I am missing something.
    Thanks.

    SYSAUX offline and inaccessible for 9 months, really? As you probably already know, there are a ton of objects that exist in this tablespace and therefore, you are probably not able to use some database features.
    As far as recovery, you could use SKIP TABLESPACE to avoid recovery of this tablespace.

  • I missed to add Standby Logfile groups? What now?

    Hi there
    I have created a Standby database in a test environment using RMAN   (followed the procedure given here -> URL:  Creating a Standby Database with Recovery Manager).
    When I tried to start the recovery on Standby, I got the following error:
    [code]
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT
    ERROR at line 1:
    ORA-38500: USING CURRENT LOGFILE option not available without stand
    SQL> select NAME, OPEN_MODE, GUARD_STATUS, DATABASE_ROLE from v$database;
    NAME      OPEN_MODE  GUARD_S DATABASE_ROLE
    PRIM      MOUNTED    NONE    PHYSICAL STANDBY
    SQL>
    [/code]
    I missed the step to add standby logfile groups. Do I need to recreate the Standby database now? I mean, add standby logfile groups to Primary, then take full RMAN backup and recreate the standby database (following the procedure described in the URL above)?
    I am using Oracle 10gR2 on OEL 5.8.
    Please advise!
    Best regards

    OK thank you both - I have added the standby logfile groups both on Primary and Standby (mounted) database and I was able to successfully issue the following command:
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;
    I hope this was the right thing to do under the circumstances, right?
    And now there seems to be a gap:
    PRIM_SQL> SELECT MAX(SEQUENCE#) FROM V$ARCHIVED_LOG;
    MAX(SEQUENCE#)
                11
    STDBY_SQL> SELECT MAX(SEQUENCE#) FROM V$LOG_HISTORY;
    MAX(SEQUENCE#)
                 9
    I issued "alter system switch logfile" few times on the Primary but logs don't seem to be shipping? How to check this and fix?
    EDIT: OK I checked the Primary alert log file and see following messages:
    Error 1031 received logging on to the standby
    Tue Jun 25 15:22:43 2013
    Errors in file /u01/app/oracle/admin/prim/bdump/prim_arc0_6880.trc:
    ORA-01031: insufficient privileges
    PING[ARC0]: Heartbeat failed to connect to standby 'stan'. Error is 1031.
    Tue Jun 25 15:27:43 2013
    Error 1031 received logging on to the standby
    Tue Jun 25 15:27:43 2013
    Errors in file /u01/app/oracle/admin/prim/bdump/prim_arc0_6880.trc:
    ORA-01031: insufficient privileges
    PING[ARC0]: Heartbeat failed to connect to standby 'stan'. Error is 1031.
    Tue Jun 25 15:32:43 2013
    I do have password file both on Primary and Standby servers. What is this "ORA-01031: insufficient privileges" referring to?
    EDIT#2:
    I copied the password file from Primary DB server to Standby server (with same name "orapwprim" - previously I used "orapwstan" name for standby password file) and the "login issue" is resolved. But now I see following error in the alert log file on Primary:
    PING[ARC0]: Heartbeat failed to connect to standby 'stan'. Error is 1031.
    Tue Jun 25 15:48:08 2013
    ARCH: Possible network disconnect with primary database
    Any clues here?
    EDIT#3:
    Sorry I was a bit impatient I guess.The logs a re being shipped and applied now.
    Thank you both!
    Best regards
    Message was edited by: user130038 (added alert log file info)
    Message was edited by: user130038 (Added EDIT#2)
    Message was edited by: user130038 (added EDIT#3)

  • Restore archivelog on standby failed

    When I tried to restore an archivelog on the physical standby, it failed with the following error:
    ORA-19870: error reading backup piece 3ekc9vsh_1_1
    ORA-19507: failed to retrieve sequential file, handle="3ekc9vsh_1_1", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
    Backup file <3ekc9vsh_1_1> not found in NetBackup catalog
    failover to previous backup
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 04/13/2009 10:12:00
    RMAN-06026: some targets not found - aborting restore
    RMAN-06025: no backup of log thread 1 seq 2941 lowscn 7414699310630 found to restore
    However, I checked on the primary, it shows the archivelog was backed up:
    SEQUENCE# THREAD# ARC COMPLETIO
    2941 1 YES 12-APR-09
    Why is that and what can I do?
    Thanks in acvance!

    Check out this doc....it will show you how to recover your standby using an incremental RMAN backup with SCN based reference. Willl be faster than rebuilding your standby:
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmdupdb.htm#sthref955

  • Ye olde "delete archivelogs in standby" question

    11.2.0.2.0
    According to note
    Configure RMAN to purge archivelogs after applied on standby [ID 728053.1]
    oracle should remove archive logs if we have deletion policy set to "delete applied on standby" which I have set on primary and standby. Monitoring the alert log we see
    "Deleted Oracle managed file /path/to/an/archive/log"
    so we think cool, its removing them automatically. Question is, when does it delete them? Right now my standby is in sync, yet my alert log is only sporadically showing my logs being deleted which were applied hours ago which I can visibly verify.

    Hemant K Chitale wrote:
    Oracle automatically deletes archivelogs only when it needs to clear space in the FRA (db_recovery_file_dest).
    Hemant K ChitaleI had thought this so tested.
    SQL> SELECT
      2  substr(name, 1, 30) name,
      3  space_limit/(1073741824) AS Quota_GB,
      4  space_used/(1073741824) AS Used_GB,
      5  space_reclaimable/(1073741824) AS Reclaimable_GB,
      6  number_of_files AS files
      7  FROM
      8  v$recovery_file_dest ;
    NAME                             QUOTA_GB    USED_GB RECLAIMABLE_GB      FILES
    /u00/oracle/flash_recovery_are        310 19.7361012     18.1420259         46
    -- bring the db_recovery_dest_size to 20gb to so we know we're over 90%.  according to that first note I posted, the FRA deems anything over 85% as space pressure
    SQL>  alter system set db_recovery_file_dest_size=20g scope=both;
    System altered.
    SQL> SELECT
      2   substr(name, 1, 30) name,
      3   space_limit/(1073741824) AS Quota_GB,
      4   space_used/(1073741824) AS Used_GB,
      5   space_reclaimable/(1073741824) AS Reclaimable_GB,
      6   number_of_files AS files
      7   FROM
      8   v$recovery_file_dest ;
    NAME                             QUOTA_GB    USED_GB RECLAIMABLE_GB      FILES
    /u00/oracle/flash_recovery_are         20 19.7437358     18.1420259         47
    SQL> So i waited a good ten minutes but still no extra logs cleared out.
    So I switched the logs a couple of times in production as well to see would that help and we did get some deleted then to bring the space used down to 17.5.gb which is just below the 85% mark.
    SQL> SELECT
      2   substr(name, 1, 30) name,
      3   space_limit/(1073741824) AS Quota_GB,
      4   space_used/(1073741824) AS Used_GB,
      5   space_reclaimable/(1073741824) AS Reclaimable_GB,
      6   number_of_files AS files
      7   FROM
      8   v$recovery_file_dest ;
    NAME                             QUOTA_GB    USED_GB RECLAIMABLE_GB      FILES
    /u00/oracle/flash_recovery_are         20 17.5075302     15.6462598         47
    SQL> quick experiment, dropped to 15gb which is below the 17gb currently used. And yes immediately, I can see the files being deleted.
    so what I take from this is that if there is any space available in the 15% free then Oracle waits to be woken up by the receipt of a log from primary, sees that theres less than 15% free and deletes logs to below that limit. however, if the space free is less than the space used then oracle wakes up itself and deletes the logs. Cool.
    Thanks hemant.
    Edited to fix coding

  • Rman backup excluding missing archivelogs

    Please help me in the following scenario :
    I have 2 months old archivelog in my disk..am taking full rman database backup daily at night..but not the archivelog. once I moved some of my archivelog files to another mount point as the archivelog destination is almost filled.
    when i try to take the backup of archivelogs,I got the message
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 11/24/2008 23:16:23
    RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
    ORA-19625: error identifying file /archv/PROD/PROD1_234_662754021.arc
    ORA-17503: ksfdopn:4 Failed to open file /archv/PROD/PROD1_234_662754021.arc
    ORA-17500: ODM err:File does not exist
    which is expected, since I moved the file /archv/PROD/PROD1_234_662754021.arc to another location inorder to have that as a temp.solution ..
    now , I have all my archivelogs starting from nov-3 till date in the log_archive_dest_1
    RMAN> run
    ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
    ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
    BACKUP FORMAT 'arch_u%u_s%s_p%p_t%t'
    Archivelog
    FROM TIME "TO_DATE('11-03-2008:23:46:15', 'MM-DD-YYYY:HH24:MI:SS')"
    UNTIL TIME "TO_DATE('11-24-2008:23:46:15', 'MM-DD-YYYY:HH24:MI:SS')"
    DELETE INPUT;
    release channel ch00;
    release channel ch01;
    now, is there anyway i can include the old archivelogs in the rman by restoring from the temporay location and taking backup. I know that I have a full database backup, but I need to have my old archivelogs also included in that ? or () does backup arhcivelog all will give any error message now ?(ORA-17500: ODM err:File does not exist)
    Any way ?
    Kai

    You need to unregister the old archivelog path and register the new archivelog path for the backup to be successful without changing the backup command.
    Assuming you're using 9i or 10g (although 'SBT_TAPE' hints 8i), you can either
    1. use the 'change' and 'catalog' command to unregister the archivelogs from the old place and re-register the archivelogs in the new place:
    change archivelog 'oldpath\archivelogname' unregister';
    catalog archivelog 'newpath\archivelogname';
    or
    change archivelog 'oldpath\archivelogname' unregister';
    catalog start with 'newpath';
    2. Not include the archivelog clause in the backup (not recommended)
    I generally backup archivelogs at least 2-3 times before deleting them and make sure they are on seperate tapes (if possible). Deleting on input has one point of failure.
    References: http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/toc.htm

  • Archivelog in standby database

    Hai
    i have some confusion regarding the archiving process in the primary database and the standby database.so log_archive_dest_2 ='service=stby' param copies the archive logfiles to the standby from the primary database.
    at the same time will the changes in the redolog files in the primary database will be applied to the standby lofiles of the target database.
    is it a correct method to copy the redolog files from the primary database to the standby database or its better to create the standby lofiles for the target database in the primary database and then copy it to the target database.wat method should be implemented?
    if group numbers for primary database are assigned as group 1.group 2 and group 3 then how should i name the newly created standby redolog groups.can i name it as group 4.group 5 and group 6.can i follow this method?
    Regards
    orauser123

    i have some confusion regarding the archiving process in the primary database and the standby database.so log_archive_dest_2 ='service=stby' param copies the archive logfiles to the standby from the primary database.
    at the same time will the changes in the redolog files in the primary database will be applied to the standby lofiles of the target database.
    is it a correct method to copy the redolog files from the primary database to the standby database or its better to create the standby lofiles for the target database in the primary database and then copy it to the target database.wat method should be implemented?You can opt for any one of the two process. I would personally suggest you to do it by setting parameter log_archive_dest_2 ='service=stby' in this case log shipping will happen automatically. You need not worry about that.
    if group numbers for primary database are assigned as group 1.group 2 and group 3 then how should i name the newly created standby redolog groups.can i name it as group 4.group 5 and group 6.can i follow this method?You can transfer a normal archive log generated at primary site, so far and register them with the standby database. After this you can apply and then delete them.
    Rgds.

Maybe you are looking for

  • Slow Response by Safari (not slow network)

    I've been having problems with Safari's speed for a while and I've treid the usual things (reset, clean out icons folder, trash prefs) but nothing seems to work. I'm using an MBP 1.83Ghz with 2GB RAM. As I'm typing this in the web form on the Apple s

  • SQL Developer and 3rd Party Drivers: JavaDB

    Go the latest 3rd party drivers for MySQL and <ugh>MS Access</ugh> but what I am looking for is a third party driver for Apache_derby JAVADB. Anyone? Manually adding the derby.jar in the thirdparty drivers under Preferences appears to do nothing in t

  • How can I select multiple people when filtering media using Photoshop Premier Elements Organizer 11?

    I noticed that in using Photoshop Premier Elements Organizer V10, I was able to select more than a single person when filtering media. For example, I may want to find all of my photos that have me with my cousin, John as well as my friend Norm in the

  • Why are iMac calender enties not showing on iPhone?

    I have made calendar entries in the month of May just recently that are not showing on my iPhone. This has not happened in the past. What has changed to make this happen?  I must add that the iMac entry is showing on my iPad mini.

  • Up/down project compatibility in AE 9.0X

    I have a project created and saved using AE 9.02.  When I tried to open it in 9.01, AE wouldn't play ball. Is there a way to save a project in 9.02 to make it openable in 9.01? My situation: I am a student in a school, so I have almost no control ove