remove the logs of archiving in log_archive_dest_2 with RMAN

Hello

Installation program:
Primary DB: oracle 10g
Standby DB: Oracle 10g
Physical active DataGuard paused.

We nun RMAN on the primary db every night, which also removes the archives connects log_archive_dest_1 located on the primary server. How to activate the same working RMAN delete logs archiving in log_archive_dest_2 located on the backup server.

-Shashi

Hey Shashi,

You can use similar job on your backup server for the removal of the old archivelogs in about 1 week. Also, please pay attention to the setting of the RMAN ARCHIVELOG DELETION POLICY on the primary database. Maybe it's to set as APPLIES ON STANDBY to prevent the removal of the archivelogs not yet applied to the primary.

Best regards
Alex

Tags: Database

Similar Questions

  • How to remove the log file archive

    HII,

    Currently, I am working on oracle 10 g 2 on windows server 2003.
    hard drive is almost full.



    When I run this command
    "REMOVE ALL EXPIRED ARCHIVE LOG THE ';

    It gives the message

    "indicates does not match any newspaper archive in the recovery catalog.



    How can I delete files from archive log?

    Concerning
    Vaibhav Dixit

    Yes you can.

    See you soon
    LIX.

  • RMAN not removed the old newspaper archive location disc ASM.

    Dear Oracle gurus

    Our platform
    OS: SUN SOLARIS10 64-bit
    DB: Oracle10g r2 10.2.0.4 64bits
    Architecture: 2 - no Oracle10g RAC with ASM configured for the data file and archivelog

    We have many available on my disk archiving log but when we perform the log backup archive using the following command

    RUN {}
    overlap archivelog all;
    backup as compressed backupset ' / location/%d_DB_%u_%s_%p.rman' all entered archivelog delete;
    }


    It has only removed the 1 month of archives newspapers only.

    that needs to removed the old archive logs using the rman. ?

    Concerning
    Hitesh Gondalia

    Published by: hitgon on November 17, 2011 21:42

    Try this one:

    CROSSCHECK ARCHIVELOG ALL;
RUN {
  BACKUP AS COMPRESSED BACKUPSET
     FORMAT '/location/%d_db_%u_%s_%p.rman'
     ARCHIVELOG ALL DELETE INPUT;
}
DELETE NOPROMPT EXPIRED ARCHIVELOG ALL:
DELETE NOPROMPT OBSOLETE:

    : p

  • delete the log file archive

    Hello
    I use oracle 10g on linux, I want to delete archive log file automatically, there is no way to do this.or can someone tell me scripts to do this.ur help on this is very appreciated

    Respect, s
    Umair Iqbal

    Hello

    Can you please let us know why you want to delete the log file archive?

    BTW, you can use RMAN to achieve by archiving log backup and delete the original file using the following command:

    Backup archivelog all delete input;

    Concerning

  • Archive the log files are not register with oracle 10g are

    Hello

    I have oracle 10.2.0 Linux redhat 4. my database is archivelog since that sequence mode no 30

    but when I backup all the files in the archives to help newspapers.

    rman> backup archivelog all delete input.

it backups up from sequence 67 

because.

SQL> select sequence# from v$archived_log;

 SEQUENCE#
----------
        67
        68
        69
        70
        71
        72
        73
        74
        75
        76
        77

 SEQUENCE#
----------
        78
        79
        80
        81
        82
        83
        84
        85
        86
        87
        88

 SEQUENCE#
----------
        89
        90
        91
        92
        93
        94
        95
        96
        97
        98
        99

 SEQUENCE#
----------
       100
       101
       102
       103
       104
       105
       106
       107
       108
       109
       110

 SEQUENCE#
----------
       111
       112
       113
       114
       115
       116
       117
       118
       119
       120
       121

 SEQUENCE#
----------
       122

56 rows selected.

while i left with

[oracle@Oracledatabas ArchiveDest]$ ls
1_30_694492901.dbf  1_40_694492901.dbf  1_50_694492901.dbf  1_60_694492901.dbf
1_31_694492901.dbf  1_41_694492901.dbf  1_51_694492901.dbf  1_61_694492901.dbf
1_32_694492901.dbf  1_42_694492901.dbf  1_52_694492901.dbf  1_62_694492901.dbf
1_33_694492901.dbf  1_43_694492901.dbf  1_53_694492901.dbf  1_63_694492901.dbf
1_34_694492901.dbf  1_44_694492901.dbf  1_54_694492901.dbf  1_64_694492901.dbf
1_35_694492901.dbf  1_45_694492901.dbf  1_55_694492901.dbf  1_65_694492901.dbf
1_36_694492901.dbf  1_46_694492901.dbf  1_56_694492901.dbf  1_66_694492901.dbf
1_37_694492901.dbf  1_47_694492901.dbf  1_57_694492901.dbf
1_38_694492901.dbf  1_48_694492901.dbf  1_58_694492901.dbf
1_39_694492901.dbf  1_49_694492901.dbf  1_59_694492901.dbf
[oracle@Oracledatabas ArchiveDest]$

i have backup of archive log as 

RMAN> list backup of archivelog all;


List of Backup Sets
===================

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
3       136.49M    DISK        00:00:08     27-AUG-09
        BP Key: 3   Status: AVAILABLE  Compressed: NO  Tag: TAG20090827T061019
        Piece Name: /home/oracle/product/10.2.0/flash_recovery_area/NEO/backupset/2009_08_27/o1_mf_annnn_TAG20090827T061019_59dpwfkb_.bkp

  List of Archived Logs in backup set 3
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    37      1530188    18-AUG-09 1549890    19-AUG-09
  1    38      1549890    19-AUG-09 1584124    19-AUG-09
  1    39      1584124    19-AUG-09 1628757    19-AUG-09

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
7       181.96M    DISK        00:00:12     27-AUG-09
        BP Key: 7   Status: AVAILABLE  Compressed: NO  Tag: TAG20090827T222915
        Piece Name: /home/oracle/product/10.2.0/flash_recovery_area/NEO/backupset/2009_08_27/o1_mf_annnn_TAG20090827T222915_59gj7x0o_.bkp

  List of Archived Logs in backup set 7
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    63      2413676    26-AUG-09 2435738    26-AUG-09
  1    64      2435738    26-AUG-09 2472234    27-AUG-09
  1    65      2472234    27-AUG-09 2515317    27-AUG-09
  1    66      2515317    27-AUG-09 2546805    27-AUG-09

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
9       15.94M     DISK        00:00:02     28-AUG-09
        BP Key: 9   Status: AVAILABLE  Compressed: NO  Tag: TAG20090828T001745
        Piece Name: /home/oracle/product/10.2.0/flash_recovery_area/NEO/backupset/2009_08_28/o1_mf_annnn_TAG20090828T001745_59gpmc0s_.bkp

  List of Archived Logs in backup set 9
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    30      1328116    17-AUG-09 1330698    17-AUG-09
  1    31      1330698    17-AUG-09 1343639    17-AUG-09

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
11      104.87M    DISK        00:00:07     28-AUG-09
        BP Key: 11   Status: AVAILABLE  Compressed: NO  Tag: TAG20090828T012913
        Piece Name: /home/oracle/product/10.2.0/flash_recovery_area/NEO/backupset/2009_08_28/o1_mf_annnn_TAG20090828T012913_59gtsbdk_.bkp

  List of Archived Logs in backup set 11
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    31      1330698    17-AUG-09 1343639    17-AUG-09
  1    32      1343639    17-AUG-09 1386340    17-AUG-09
  1    33      1386340    17-AUG-09 1418708    17-AUG-09

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
18      2.44G      DISK        00:03:18     17-SEP-09
        BP Key: 18   Status: AVAILABLE  Compressed: NO  Tag: TAG20090917T002120
        Piece Name: /home/oracle/product/10.2.0/flash_recovery_area/NEO/backupset/2009_09_17/o1_mf_annnn_TAG20090917T002120_5c3gb2m2_.bkp

  List of Archived Logs in backup set 18
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    67      2546805    27-AUG-09 2571963    28-AUG-09
  1    68      2571963    28-AUG-09 2610800    28-AUG-09
  1    69      2610800    28-AUG-09 2647832    28-AUG-09
  1    70      2647832    28-AUG-09 2668839    28-AUG-09
  1    71      2668839    28-AUG-09 2705408    29-AUG-09
  1    72      2705408    29-AUG-09 2749633    29-AUG-09
  1    73      2749633    29-AUG-09 2783675    30-AUG-09
  1    74      2783675    30-AUG-09 2826464    30-AUG-09
  1    75      2826464    30-AUG-09 2860499    30-AUG-09
  1    76      2860499    30-AUG-09 2903504    31-AUG-09
  1    77      2903504    31-AUG-09 2943108    31-AUG-09
  1    78      2943108    31-AUG-09 2977859    31-AUG-09
  1    79      2977859    31-AUG-09 2998785    01-SEP-09
  1    80      2998785    01-SEP-09 3042779    01-SEP-09
  1    81      3042779    01-SEP-09 3086898    01-SEP-09
  1    82      3086898    01-SEP-09 3103245    02-SEP-09
  1    83      3103245    02-SEP-09 3147628    02-SEP-09
  1    84      3147628    02-SEP-09 3192216    02-SEP-09
  1    85      3192216    02-SEP-09 3208480    02-SEP-09
  1    86      3208480    02-SEP-09 3248106    03-SEP-09
  1    87      3248106    03-SEP-09 3294064    03-SEP-09
  1    88      3294064    03-SEP-09 3323611    03-SEP-09
  1    89      3323611    03-SEP-09 3352060    04-SEP-09
  1    90      3352060    04-SEP-09 3399516    04-SEP-09
  1    91      3399516    04-SEP-09 3440740    04-SEP-09
  1    92      3440740    04-SEP-09 3457884    05-SEP-09
  1    93      3457884    05-SEP-09 3485157    05-SEP-09
  1    94      3485157    05-SEP-09 3523208    05-SEP-09
  1    95      3523208    05-SEP-09 3558325    05-SEP-09
  1    96      3558325    05-SEP-09 3600414    06-SEP-09
  1    97      3600414    06-SEP-09 3642729    06-SEP-09
  1    98      3642729    06-SEP-09 3678479    07-SEP-09
  1    99      3678479    07-SEP-09 3720642    07-SEP-09
  1    100     3720642    07-SEP-09 3748794    07-SEP-09
  1    101     3748794    07-SEP-09 3777963    08-SEP-09
  1    102     3777963    08-SEP-09 3823393    08-SEP-09
  1    103     3823393    08-SEP-09 3865230    08-SEP-09
  1    104     3865230    08-SEP-09 3880510    09-SEP-09
  1    105     3880510    09-SEP-09 3906888    09-SEP-09
  1    106     3906888    09-SEP-09 3961086    09-SEP-09
  1    107     3961086    09-SEP-09 3982103    10-SEP-09
  1    108     3982103    10-SEP-09 4034528    10-SEP-09
  1    109     4034528    10-SEP-09 4055556    11-SEP-09
  1    110     4055556    11-SEP-09 4115268    11-SEP-09
  1    111     4115268    11-SEP-09 4128557    12-SEP-09
  1    112     4128557    12-SEP-09 4165104    12-SEP-09
  1    113     4165104    12-SEP-09 4202850    12-SEP-09
  1    114     4202850    12-SEP-09 4258353    13-SEP-09
  1    115     4258353    13-SEP-09 4298900    14-SEP-09
  1    116     4298900    14-SEP-09 4341046    14-SEP-09
  1    117     4341046    14-SEP-09 4365180    15-SEP-09
  1    118     4365180    15-SEP-09 4424992    15-SEP-09
  1    119     4424992    15-SEP-09 4439538    15-SEP-09
  1    120     4439538    15-SEP-09 4489259    16-SEP-09
  1    121     4489259    16-SEP-09 4532807    16-SEP-09
  1    122     4532807    16-SEP-09 4548893    17-SEP-09



and when i try

RMAN> backup archivelog from sequence 30 until sequence 66;

Starting backup at 17-SEP-09
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 09/17/2009 04:01:25
RMAN-20242: specification does not match any archive log in the recovery catalog


when i try to restore database on testing server it ask me for



MAN> recover database until sequence 121;

Starting recover at 17-SEP-09
using channel ORA_DISK_1

starting media recovery

channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=37
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=38
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=39
channel ORA_DISK_1: reading from backup piece /home/oracle/o1_mf_annnn_TAG20090827T061019_59dpwfkb_.bkp
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/o1_mf_annnn_TAG20090827T061019_59dpwfkb_.bkp tag=TAG20090827T061019
channel ORA_DISK_1: restore complete, elapsed time: 00:00:17
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=63
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=64
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=65
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=66
channel ORA_DISK_1: reading from backup piece /home/oracle/o1_mf_annnn_TAG20090827T222915_59gj7x0o_.bkp
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/o1_mf_annnn_TAG20090827T222915_59gj7x0o_.bkp tag=TAG20090827T222915
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=31
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=32
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=33
channel ORA_DISK_1: reading from backup piece /home/oracle/o1_mf_annnn_TAG20090828T012913_59gtsbdk_.bkp
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/o1_mf_annnn_TAG20090828T012913_59gtsbdk_.bkp tag=TAG20090828T012913
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
archive log filename=/home/oracle/DataBaseBackups/ArchiveDest/1_31_694492901.dbf thread=1 sequence=31
archive log filename=/home/oracle/DataBaseBackups/ArchiveDest/1_32_694492901.dbf thread=1 sequence=32
archive log filename=/home/oracle/DataBaseBackups/ArchiveDest/1_33_694492901.dbf thread=1 sequence=33
archive log filename=/home/oracle/DataBaseBackups/ArchiveDest/1_34_694492901.dbf thread=1 sequence=34
archive log filename=/home/oracle/DataBaseBackups/ArchiveDest/1_34_694492901.dbf thread=1 sequence=35
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/17/2009 03:01:31
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/home/oracle/DataBaseBackups/ArchiveDest/1_34_694492901.dbf'
ORA-00310: archived log contains sequence 34; sequence 35 required
ORA-00334: archived log: '/home/oracle/DataBaseBackups/ArchiveDest/1_34_694492901.dbf'
    My question is why my 30 to 66 sequence archivelog file are not saved with the database in v$ archived_log and how to solve this problem.

    Thank you
    Umesh

    You may need to increase the CONTROL_FILE_RECORD_KEEP_TIME value.

    If the archivelogs are still on the disk, you can try to catalog them with:

    RMAN> catalog start with '/home/oracle/DataBaseBackups/ArchiveDest/;

    or if you don't need the file you can simply remove the o/s and run the following:

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

  • Size of the log file Archive

    Redlogfile size is 16 MB and generating the archivelog file size is approximately 10 Mb. what could be the reason?

    Oracle Version: 10.2.0.4

    OS: Windows

    Published by: Deccan charger 19 April 2010 23:31

    First of all:

    a redo log contains a lot of things necessary for instance etc. recovery an archived log is used only for the restorations - he didn't need all the stuff that is in a redo log, so when written CRA the archiving log that he does not write all knowledge, all that is required for restores

    Second:

    Archive logs is created with dimensions smaller, irregular, as the original redo logs. Why? [388627.1 ID]

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

    Last updated 2 June 2007 Type status MODERATE HOWTO

    In this Document
    Goal
    Solution
    References

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

    This document is available to you through process of rapid visibility (RaV) of the Oracle's Support and therefore was not subject to an independent technical review.

    Applies to:
    Oracle Server - Enterprise Edition - Version: 8.1.7.4 to 11.1
    Information in this document applies to any platform.

    Goal
    Archive logs is created with dimensions smaller, irregular, as the original redo logs.
    Commands like:
    ALTER SYSTEM SWITCH LOGFILE
    or
    ALTER SYSTEM ARCHIVE LOG...
    are not used to generate archives or change the log file. Thus, there is no parameter ARCHIVE_LAG_TARGET set.
    What else could cause this behaviour?
    Solution
    From:
    Bug: 5450861: NEWSPAPERS ARCHIVE IS GENERATED with one SIZE SMALLER THAN THE REDO LOG FILES
    the explanation of this situation has 2 main reasons:
    1 archiving logs do not have to be in the same size. This was decided very long ago, when blank padding archiving logs stopped for a very good reason - in order to save disk space.

    2. the log command does not exist when a redo log file is 100% full. There is an internal algorithm that determines when to switch journal. It also has a very good reason - do the command of newspaper at the last moment may incur performance problems (for various reasons, outside the scope of this note).
    So, after that newspaper ordering occurs the archivers are only copying the information from the redo log files. As recovery logs are not 100% full after the command to log and archive logs are empty not filled after the copy operation is complete, this results in unequal files smaller than the original of redo log files.
    This is very apparent for very low (less than 10 MB) log files; as a result, produced 2.5 MB archive logs of 5 MB recovery logs are very visible.
    Just note that currently, the default log files are 100 MB in size. If the archives log files would be between 98 and 100 MB person would notice.
    The main concern that one must have for newspapers of archives files is a possible corruption. This can be easily verified by attempting a resumption of testing. When it's ok, the size of the log archive uneven should be of no interest, as is expected.

  • How do I change the log mode archive in 12 c

    Hello

    [oracle@localhost Desktop] $ rman

    Recovery Manager: release 12.1.0.2.0 - Production on Mon May 4 00:38:33 2015

    Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved.

    RMAN > Connect target sys/oracle@cdb1

    connected to target database: CDB1 (DBID = 828012650)

    RMAN > backup database;

    From backup may 4, 15

    using the control file of the target instead of recovery catalog database

    allocated channel: ORA_DISK_1

    channel ORA_DISK_1: SID = 284 type device = DISK

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-03002: failure of the backup command at 04/05/2015 00:38:51

    RMAN-06149: cannot BACKUP of DATABASE in NOARCHIVELOG mode

    RMAN > exit

    Complete recovery manager.

    [oracle@localhost Desktop] $ sqlplus

    SQL * more: Production release 12.1.0.2.0 on Mon May 4 00:38:57 2015

    Copyright (c) 1982, 2014, Oracle.  All rights reserved.

    Enter the user name: sys as sysdba

    Enter the password:

    Connected to:

    Database Oracle 12 c Enterprise Edition Release 12.1.0.2.0 - 64 bit Production

    With the options of partitioning, OLAP, advanced analytics and Real Application Testing

    SQL > shutdown immediate;

    Connectable to closed database.

    SQL > startup nomount;

    SQL > startup;

    Connectable to open database.

    SQL >

    Please tell me how to change the mode of journal archive in db oracle 12.1.0.2.0

    Please tell me how to change the mode of journal archive in db oracle 12.1.0.2.0

    Please mark the thread ANSWERED and repost it in the forum shared.

    Multitenant

    Before you repost again the "Archiving for control" secion of the Oracle documentation

    http://docs.Oracle.com/database/121/Admin/archredo.htm#i1006208

    Archiving control

    This section describes how to set the mode of the database archiving and control the archiving process. The authors discuss the following topics:

    This article shows you step by step how to change the mode of journal archive.

  • Remove the Wordpress site and replace it with Muse site

    I currently have a Wordpress site, hosted by FatCow. I need to remove this site and download my new Muse site. I am a CC member so I would like to download by means of Business Catalyst to FatCow, if possible. Could someone please give a step by step on how to do it properly? I'm not very tech savvy and I'm afraid I'll screw something up.

    Thank you

    Neil

    Hi Neil

    Yes, you can do it. Steps would be

    -Remove the domain from wordpress site

    -Publish the Muse on Business Catalyst site

    http://helpx.Adobe.com/Muse/tutorials/launching-Muse-site-push-live-1.html

    http://helpx.Adobe.com/business-catalyst/partner/upgrade-temporary-site.html

    -Connection to the site admin section > Push direct admin site access ("Launch Site")

    https://www.YouTube.com/watch?v=gejclNKc51s

    -Go to Site Settings > Site areas > add the domain to your site (one that you removed from the wordpress site)

    http://helpx.Adobe.com/business-catalyst/using/change-site-domain.html

    -Connect to the console of administration of FatCow > go to DNS management > delete any existing record (server name / record etc.)

    -Add nameserver BC records

    http://helpx.Adobe.com/business-catalyst/using/change-site-domain.html

    That's all

    Thank you

    Sanjit

  • Remove the log during recovery, but everything is ok

    Hello

    I delete the log during recovery file, insert a value in a table and commit, it is committed and no error in the alert.log file
    I turn on logfile, it switches, once again no error

    What is the reason?

    Thank you

    John

    But when I commit, where do the Oracle stores data?

    First of all in the log buffer which is empty on commit to the CURRENT redo log in the redo log writer.

    As stated previously the writer newspaper most likely open the file before you delete - so he acquired a file descriptor and is still able to write to this file, even if you subsequently deleted. The journal writer retains the redo log permanently open at least until the file becomes inactive (I think even the file handles are never closed for performance reasons; but this should be verified).

  • Remove the log from external Table file?

    Hello

    I don't want the log file to create each time I use an external table.

    Is is possible?

    You can specify one or more of the following options:

    NOBADFILE NODISCARDFILE NOLOGFILE

    In the passage of ACCESS SETTINGS of your table definition.

    I hope this helps!

  • ORA-25408: can not read the appeal during a duplicate backup with rman catalog database safely

    Hello

    I did a database duplicate backup with rman catalog connection and got the ORA-25408: cannot read error call safely.

    The catalog database is running in a Data Guard environment.

    During the double process database failover occurred because of a server restart.

    The restore of the data files was successful:

    RMAN-08023: channel t1: restored the backup part 1

    RMAN-08180: channel t1: restoration complete, duration: 00:01:15

    RMAN-03091: finished the restoration at 27.08.2014 09:27:10

    During execution of script memory:

    RMAN-08161: content of the Script from memory:

    {

    switch from clone datafile;

    }

    RMAN-08162: execution of Script memory

    I got this error:

    RMAN-08162: execution of Script memory

    RMAN-08031: output channel: t1

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-03002: failure of Db in dual at 27/08/2014 09:27:10

    RMAN-05501: abandonment of duplicate target database

    RMAN-03015: an error has occurred in the script stored memory Script

    RMAN-06004: ORACLE recovery catalog database error: ORA-25408: cannot read safely call

    Dual boot time: 16:00

    Failover time: 18:00

    Error time: 09:00 the next day

    DB version: 11.2.0.4.0, not the RAC environment, single instances

    That's happened? My My db catalog rman session did not survive? Why the error happened at 09:00 (and not 17:00)? Why the session called the catalog rman during switching of the data files?

    Can someone explain it to me?

    Thank you!

    Hello

    The connection of the RMAN catalog remains inactive during the backup/restore process, once rman completes the task and try to activate the connection it gets error.

    What is expected as you said the rebooted server. If this happens because of the expiration time, we went with the parameter net expire_time to maintain the connection.

    Thank you

    Bigot

  • How to restore the tablespaces only 4 while cloning with RMAN?

    Hello
    How to restore the tablespaces only 4 not all areas of storage in one database to the new database of cloned all cloning with RMAN?

    I don't think it's possible to restore only 4 storage space for the database 'auxiliary '. Instead, you can use the "SKIP TABLESPACE" cloning while clause.

    You can exclude the tablespaces that you don't want the database duplicate with the SKIP TABLESPACE clause. You can exclude any tablespace except the SYSTEM tablespace or tablespaces containing rollback or undo segments.

    Refer to this http://docs.oracle.com/cd/B14117_01/server.101/b10770/rcmsynta28.htm

  • ORA-19870: you try to restore the database on a different host with rman...

    When I try to restore datafile 1 with this script

    RUN
    {
    SET up this THAT TIME = "to_date('2012-01-01:00:00:00','YYYY-MM-DD:HH24:MI:SS')";
    RESTORE THE FILE DATA 1;
    }


    ---------------------------
    ORA-19870: error reading backup total /mnt/hgfs/2012_01_01/o1_mf_nnndf_TAG20120101T050005_7hzm1qc4_.bkp
    ORA-19612: datafile 1 not restored because of missing or corrupted data
    switch to the previous backup

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

    RMAN > RESTORE DATAFILE 1 to this THAT TIME = "to_date('2012-01-01:00:00:00','YYYY-MM-DD:HH24:MI:SS')" Overview.

    From restoration to January 10, 12
    using channel ORA_DISK_1
    using the ORA_DISK_2 channel
    using the ORA_DISK_3 channel

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the restore command at the 13:11:19 10/01/2012
    RMAN-06026: some targets not found - abandonment of restoration
    RMAN-06023: no backup or copy of datafile 1 found to restore

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

    RMAN > LIST BACKUP OF THE DATA 1 Summary file;


    Backup list
    ===============
    S LV TY Device Type delay #Pieces compressed #Copies Tag key
    ------- -- -- - ----------- --------------- ------- ------- ---------- ---
    40969 A DISC 1 1 JANUARY 12 1 no TAG20120101T050005

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

    and when I write "backup list '; output is here where I can see datafile 1...


    Time of accomplishment BS key Type LV size device Type elapsed time
    ------- ---- -- ---------- ----------- ------------ ---------------
    40969 full 32,28 G DISC 02:07:15 1st January 12
    BP key: situation 28432: AVAILABLE Tablet: NO Tag: TAG20120101T050005
    Part name: /mnt/hgfs/2012_01_01/o1_mf_nnndf_TAG20120101T050005_7hzm1qc4_.bkp
    List of defined backup data files 40969
    Name of file LV Type cash SNA cash time
    ---- -- ---- ---------- --------- ----
    25035430765 full 1 1 January 12 /oradata1/ISPRODDB11/datafile/o1_mf_system_331jc17w_.dbf
    2 full 25035430765 /oradata1/ISPRODDB11/datafile/o1_mf_undotbs1_331jc19r_.dbf 1 January 12
    4 integer 25035430765 /oradata1/ISPRODDB11/datafile/o1_mf_users_331jc1b2_.dbf 1 January 12
    35 full 25035430765 /oradata1/ISPRODDB11/datafile/sap.dbf 1 January 12
    56 full 25035430765 /oradata2/ISPRODDB11/datafile/TBS_UYS05.dbf 1 January 12

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

    and the incarnation of the list;

    RMAN > LIST INCARNATION;


    List of Incarnations of the database
    DB key Inc key STATE ID DB name DB reset reset time SNA
    ------- ------- -------- ---------------- --- ---------- ----------
    1 1 ISPRODDB 4210711725 PARENT 1 19 DECEMBER 06
    2 2 ISPRODDB 4210711725 RUNNING 564488 26 APRIL 07


    I m able to restore all data files but datafile 1 (system) and 3 (sysaux)... I don't know what to do...

    828193 wrote:
    When I put until 2012-01-01 12:00

    From back to January 10, 12
    using channel ORA_DISK_1
    using the ORA_DISK_2 channel
    using the ORA_DISK_3 channel
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the command recover at the 15:28:53 10/01/2012
    RMAN-06094: datafile 1 must be restored.

    so, if I want to restore a datafile to 2012-01-01 00:00 I need previous backupset? right?

    Fix.
    Has done restoration work when you set the until to 2012-01-01 12:00?

    Brgds
    Johan

  • Removal of log file archive on the backup database

    Hi all

    This command delete CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY archive log file automatically on the basis of data pending?

    Thank you

    Hello

    There are two areas... (1) primary 2 pending)

    I thought that you have set this parameter on primary... So like I said if set you in primary this custom delete archive logs in the standby mode.

    But if you choose standby, Yes it will be erased.

    More evidence - based Archivelogs maintenance ensures [464668.1 ID]

    I hope this helps...

  • Say I have use a bookmark to access a web page. Subsequently I have manually delete the reference on historical Panel - also removes the current bookmark. Never happened with vn!

    Sequence of operations leading to the problem:

    !) Existing bookmark to go to the requested web page.
    (2) later, the I delete manually the reference panel historical at this bookmark - command 'delete '.
    Search 3) via the bookmark panel list some time later, I noticed that the bookmark I would have used previously was deleted. I did not went to the Bookmarks panel and deleted explicitly point. The deletion is certainly due to him removing point of reference in the history panel.

    This behavior started recently - and I think with FF for Android exit 31 or 32. Certainly is not happened with versions before clearing the historic bar on historic Panel were introduced. I am now on version 32.0.3

    Question being entered on desktop machine so 'guessed' version info irrelevant, so I've manually entered version info, etc. below...

    Thank you, Rob.

    HI dislexic_wobmat,

    It seems that this problem is fixed in the next version of Firefox beta.

Maybe you are looking for