RMAN DUPLICATION

Hello
in 10g R2, if OVERLAP is issued, can it be seen (caterpillars) somewhere?

How can I check if a command of OVERLAP is given?
Thank you.

Read

http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14192/maint002.htm

Tags: Database

Similar Questions

  • DataGuard enviornment, rman duplication showed validation failed

    I have backup rman to backup site installation.
    DB version is GR 11, 2,
    version of the OS is redhat linux

    I did the rman duplication, here are some results:

    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/system.324.792993247 RECID = 621 STAMP = 793373396
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/system.314.788073527 RECID = 483 STAMP = 792994113
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/system.323.786903909 RECID = 343 STAMP = 788102778
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/system.333.785989831 RECID = 206 STAMP = 786907706
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/system.347.785963645 RECID = 69 = 785990015 STAMP
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/sysaux.355.792993227 RECID = 622 STAMP = 793373396
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/sysaux.293.788073519 RECID = 484 STAMP = 792994113
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/sysaux.322.786903909 RECID = 344 STAMP = 788102779
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/sysaux.332.785989833 RECID = 207 STAMP = 786907706
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/sysaux.346.785963645 RECID = 70 = 785990015 STAMP
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/undotbs1.351.792993227 RECID = 623 STAMP = 793373396
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/undotbs1.361.788073413 RECID = 485 STAMP = 792994114
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/undotbs1.319.786903909 RECID = 345 STAMP = 788102779
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/undotbs1.258.785989851 RECID = 208 = 786907706 STAMP
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/undotbs1.345.785963645 RECID = STAMP 71 = 785990015
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arindex.341.785186191 RECID = 624 STAMP = 793373396
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arindex.319.713996145 RECID = 346 STAMP = 788102779
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/undotbs2.291.792993257 RECID = 625 STAMP = 793373396
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/undotbs2.315.788073545 RECID = 487 STAMP = 792994114
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/undotbs2.316.786903931 RECID = 347 STAMP = 788102779
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/undotbs2.348.785989855 RECID = 210 STAMP = 786907706
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/undotbs2.339.785963789 RECID = 73 = 785990015 STAMP
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arindex.429.785173115 RECID = 626 STAMP = 793373396
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arindex.274.713990673 RECID = 348 STAMP = 788102779
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/ggs_data.290.792993255 RECID = 627 STAMP = 793373397
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/ggs_data.294.788073529 RECID = 489 STAMP = 792994114
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/ggs_data.329.786903917 RECID = 349 STAMP = 788102779
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/ggs_data.257.785989847 RECID = 212 STAMP = 786907706
    validation failed for the copy of the data file
    DataFile copy file name=+DAT/prd/datafile/ggs_data.305.785981949 RECID = 75 = 785990015 STAMP
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arindex.407.785164105 RECID = 628 STAMP = 793373397
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arindex.273.713990667 RECID = 350 STAMP = 788102779
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arsystem.313.785209331 RECID = 629 STAMP = 793373397
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arsystem.360.770344487 RECID = 351 STAMP = 788102779
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arsystem.408.785164107 RECID = 630 STAMP = 793373397
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arsystem.359.770344385 RECID = 352 STAMP = 788102779
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arsystem.347.785193013 RECID = STAMP 631 = 793373397
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arsystem.358.770343541 RECID = 353 STAMP = 788102779
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arsystem.327.785199047 RECID = 632 STAMP = 793373397
    validation failed for the copy of the data file
    Copy file name=/oracle_backup/stage/arsystem.357.770343495 RECID DataFile = 354 STAMP = 788102779
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arsystem.309.785213677 RECID = 633 STAMP = 793373397
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arsystem.286.713990693 RECID = 355 STAMP = 788102780
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arsystem.317.785207493 RECID = 634 STAMP = 793373397
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arsystem.288.713990693 RECID = 356 STAMP = 788102780
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arsystem.316.785204659 RECID = 635 STAMP = 793373398
    validation failed for the copy of the data file

    How can I remove these entries from invalid rman? I can't overlap with success their.

    Thank you

    DataFile copy file name=/oracle_backup/stage/arsystem.288.713990693 RECID = 356 STAMP = 788102780
    validation failed for the copy of the data file
    DataFile copy file name=/oracle_backup/stage/arsystem.316.785204659 RECID = 635 STAMP = 793373398
    validation failed for the copy of the data file

    Have you tried below command?

    RMAN > CHANGE DATAFILECOPY '+ DAT/prd/datafile/undotbs2.339.785963789' UNCATALOG;

  • RMAN duplication and expiration of the directives on the environment of data warehouse

    Operating systems: Windows Server 2008
    DB: Oracle 11 g 2

    Are there guidelines how often one should do a RMAN duplication and assign an expiration on archivelogs for data warehouse environments?
    It me appears once a day would be enough for overlapping in a data warehouse environment which is updated nightly. Expiration, I don't expect less than 1 week.
    See you soon!

    I agree with damorgan

    See the links for the best practices below.

    http://www.Oracle.com/technetwork/database/features/availability/311394-132335.PDF
    https://blogs.Oracle.com/Datawarehousing/entry/data_warehouse_in_archivelog_m

    Hope this helps,

    Concerning
    http://www.oracleracepxert.com
    Understand the power of the Oracle RMAN
    http://www.oracleracexpert.com/2011/10/understand-power-of-Oracle-RMAN.html
    Duplication of data base RAC with RMAN
    http://www.oracleracexpert.com/2009/12/duplicate-RAC-database-using-RMAN.html

  • Active RMAN duplication problem

    Experts,

    I am trying to set up a standby database single-server to a primary database RAC, using configurations of data Gaurad. In this process, I finished all the configurations, and I was about to run the RMAN script to duplicate primary DB on Standby DB.

    When I turn off the RMAN script, he throws under the errors:

    ince the backup to December 5, 11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID = instance 901 = iam1 = DISK device type
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Db in dual at 05/12/2011 15:31:42
    RMAN-05501: abandonment of duplicate target database
    RMAN-03015: an error has occurred in the script stored memory Script
    RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 05/12/2011 15:31:42
    ORA-17629: unable to connect to the remote database server
    ORA-17627: ORA-01031: insufficient privileges
    ORA-17629: unable to connect to the remote database server

    Additional information:



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

    -Password is correctly copied the main database and the RAC rescue.
    -Capable to connect to DB primary waiting for database via sqlplus tool.
    -Telnet is conversely works very well.
    -All the pings work correctly.

    Please let me know if you have any suggestions. Happy to provide further information if necessary.

    Thank you

    Make sure that you should not use the password file that is located under /dbs. There is a folder called "database", where a password file must have been already generated at installation time. Simply copy the file to the same location on the standby node. I hope it should work now.

  • Is log_file_name_convert in block running rman duplication.

    Log_file_name_convert is allowed in the execution of rman block?

    If Yes, what is the correct syntax for pair of mutiple coversion

    I have 3 newspaper group on target (source). Each has 2 members.

    target-> in the
    Group1
    U01/oradata/prod/redo01.log-> /ora1/oradata/test/redo01.log
    /U02/oradata/prod/redo01b.log-> /ora2/oradata/test/redo0b.log

    group2
    /U01/oradata/prod/redo02.log-> /ora1/oradata/test/redo02.log
    /U02/oradata/prod/redo02b.log-/oRA2/oradata/test/redo02b.log

    Group 3

    /U01/oradata/prod/redo03.log-> /ora1/oradata/test/redo03.log
    /U02/oradata/prod/redo03b.log-> /ora2/oradata/test/redo03b.log


    Run {}
    ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
    ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
    CHANNEL AUXILIARY ALLOCATE aux3 DEVICE TYPE DISK;
    until ' to_date (24 June 11 10:22 ',' DD-MON-YY HH24:MI:SS') ";
    DUPLICATE TARGETS of DATABASE 'test '.
    PFILE=/opt/Oracle/product/10.2/Db_1/DBS/inittest.ora
    DB_FILE_NAME_CONVERT = ' / u01/oradata/prod / "," / ora1/oradata/test / '.
    log_file_name_convert = ' / u01/oradata/prod / "," / ora1/oradata/test / "," / u02/oradata/prod / "," / ora2/oradata/test / '.

    output channel aux_01;
    output channel aux_02;
    }

    Rename data files in the DATABASE DUPLICATE RMAN

    There are several methods of specification of new names to use for your database duplicate data files. Listed in order of precedence, they are:

    Use the RMAN SET NEWNAME command for DATA file within a RUN block that surrounds the SET NEWNAME commands both DUPLICATE the order.

    Use the RMAN command CONFIGURE AUXNAME to specify the new name of the existing data files. Run the CONFIGURE AUXNAME command before the command DUPLICATE.

    Specify the parameter DB_FILE_NAME_CONVERT on ordering DUPLICATE to specify a rule to convert filenames to data not renamed with the VALUE of NEWNAME or CONFIGURE AUXNAME files.

    Note:
    DUPLICATE the DB_FILE_NAME_CONVERT the command clause cannot be used to control the generation of new names for the files to duplicate instance that are Oracle-managed files (OMF) to the target instance. For more information about this restriction, see Oracle database backup and recovery Reference.

    Set the DB_FILE_NAME_CONVERT initialization parameter.

    Note:
    The DB_FILE_NAME_CONVERT initialization parameter cannot be used to control the generation of new names for the files to duplicate instance that are Oracle-managed files (OMF) to the target instance. It is subject to the same semantics and limitations as DUPLICATE DB_FILE_NAME_CONVERT parameter to the command. He see reference recovery and backup of Oracle database for more details.

    Set DB_CREATE_FILE_DEST initialization parameter to create Oracle managed files data files at the specified location.

    If you do not use the previous options, then the duplicate database reuses the locations of original data file of the target database.

    See the link:-http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmdupdb.htm#i1008481

    See also:-http://www.akadia.com/services/ora_duplicate_database_rman.html

  • RMAN Duplication failed on another host

    Hi, I use oracle 10.2.0.4 on solaris 5.10 to duplicate the database of 1 host 2 host. I had tried that before and it was successful, except that the first time I had tried with a smaller database.

    Here's the code I ran host 1 and the error message below. Any help would be greatly appreciated:
    RMAN> run{
2> allocate auxiliary channel aux1 device type disk;
3> allocate auxiliary channel aux2 device type disk;
4> allocate auxiliary channel aux3 device type disk;
allocate auxiliary channel aux4 device type disk;
5> allocate auxiliary channel aux5 device type disk;
6> 7> allocate auxiliary channel aux6 device type disk;
duplicate target database to UNOLTSVT;8> }

allocated channel: aux1
channel aux1: sid=1995 devtype=DISK

allocated channel: aux2
channel aux2: sid=999 devtype=DISK

allocated channel: aux3
channel aux3: sid=1994 devtype=DISK

allocated channel: aux4
channel aux4: sid=998 devtype=DISK

allocated channel: aux5
channel aux5: sid=2997 devtype=DISK

allocated channel: aux6
channel aux6: sid=3992 devtype=DISK

Starting Duplicate Db at 07-FEB-11

contents of Memory Script:
{
   set until scn  1413162899;
   set newname for datafile  1 to
 "/databases/da001/UNOLTSVT/system01.dbf";
   set newname for datafile  2 to
 "/databases/da001/UNOLTSVT/undotbs01.dbf";
   set newname for datafile  3 to
 "/databases/da001/UNOLTSVT/sysaux01.dbf";
   set newname for datafile  4 to
 "/databases/da001/UNOLTSVT/users01.dbf";
   set newname for datafile  5 to
 "/databases/da001/UNOLTSVT/tools01.dbf";
   set newname for datafile  6 to
 "/databases/da001/UNOLTSVT/siebel_data01.dbf";
   set newname for datafile  7 to
 "/index/ix001/UNOLTSVT/siebel_index01.dbf";
   set newname for datafile  8 to
 "/databases/da001/UNOLTSVT/sbl_data_md01.dbf";
   set newname for datafile  9 to
 "/databases/da001/UNOLTSVT/sbl_data_lg01.dbf";
   set newname for datafile  10 to
 "/databases/da001/UNOLTSVT/sbl_data_xl01.dbf";
   set newname for datafile  11 to
 "/databases/da001/UNOLTSVT/sbl_data_xl02.dbf";
   set newname for datafile  12 to
 "/databases/da001/UNOLTSVT/sbl_data_xl03.dbf";
   set newname for datafile  13 to
 "/index/ix001/UNOLTSVT/sbl_idx_md01.dbf";
   set newname for datafile  14 to
 "/index/ix001/UNOLTSVT/sbl_idx_lg01.dbf";
   set newname for datafile  15 to
 "/index/ix001/UNOLTSVT/sbl_idx_xl01.dbf";
   set newname for datafile  16 to
 "/databases/da001/UNOLTSVT/genuser01.dbf";
   set newname for datafile  17 to
 "/index/ix001/UNOLTSVT/siebel_index02.dbf";
   set newname for datafile  18 to
 "/index/ix001/UNOLTSVT/sbl_idx_md02.dbf";
   set newname for datafile  19 to
 "/index/ix001/UNOLTSVT/sbl_idx_xl02.dbf";
   set newname for datafile  20 to
 "/index/ix001/UNOLTSVT/sbl_idx_lg02.dbf";
   set newname for datafile  21 to
 "/databases/da001/UNOLTSVT/siebel_data02.dbf";
   set newname for datafile  22 to
 "/databases/da001/UNOLTSVT/sbl_data_lg02.dbf";
   set newname for datafile  23 to
 "/databases/da001/UNOLTSVT/sbl_data_xl04.dbf";
   set newname for datafile  24 to
 "/index/ix001/UNOLTSVT/sbl_idx_lg03.dbf";
   set newname for datafile  25 to
 "/index/ix001/UNOLTSVT/sbl_idx_xl03.dbf";
   set newname for datafile  26 to
 "/index/ix001/UNOLTSVT/sbl_idx_xl04.dbf";
   set newname for datafile  27 to
 "/index/ix001/UNOLTSVT/sbl_idx_xl05.dbf";
   set newname for datafile  28 to
 "/index/ix001/UNOLTSVT/sbl_idx_xl06.dbf";
   set newname for datafile  29 to
 "/index/ix001/UNOLTSVT/sbl_idx_lg04.dbf";
   set newname for datafile  30 to
 "/index/ix001/UNOLTSVT/sbl_idx_md03.dbf";
   set newname for datafile  31 to
 "/index/ix001/UNOLTSVT/siebel_index03.dbf";
   restore
   check readonly
   clone database
   ;
}
executing Memory Script

executing command: SET until clause

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

Starting restore at 07-FEB-11

channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00018 to /index/ix001/UNOLTSVT/sbl_idx_md02.dbf
restoring datafile 00027 to /index/ix001/UNOLTSVT/sbl_idx_xl05.dbf
channel aux1: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52mr_.bkp
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00023 to /databases/da001/UNOLTSVT/sbl_data_xl04.dbf
restoring datafile 00024 to /index/ix001/UNOLTSVT/sbl_idx_lg03.dbf
restoring datafile 00025 to /index/ix001/UNOLTSVT/sbl_idx_xl03.dbf
restoring datafile 00026 to /index/ix001/UNOLTSVT/sbl_idx_xl04.dbf
restoring datafile 00030 to /index/ix001/UNOLTSVT/sbl_idx_md03.dbf
restoring datafile 00031 to /index/ix001/UNOLTSVT/siebel_index03.dbf
channel aux2: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52n3_.bkp
channel aux3: starting datafile backupset restore
channel aux3: specifying datafile(s) to restore from backup set
restoring datafile 00008 to /databases/da001/UNOLTSVT/sbl_data_md01.dbf
restoring datafile 00013 to /index/ix001/UNOLTSVT/sbl_idx_md01.dbf
restoring datafile 00015 to /index/ix001/UNOLTSVT/sbl_idx_xl01.dbf
restoring datafile 00019 to /index/ix001/UNOLTSVT/sbl_idx_xl02.dbf
channel aux3: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52qf_.bkp
channel aux4: starting datafile backupset restore
channel aux4: specifying datafile(s) to restore from backup set
restoring datafile 00028 to /index/ix001/UNOLTSVT/sbl_idx_xl06.dbf
restoring datafile 00029 to /index/ix001/UNOLTSVT/sbl_idx_lg04.dbf
channel aux4: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyk4tct_.bkp
channel aux5: starting datafile backupset restore
channel aux5: specifying datafile(s) to restore from backup set
restoring datafile 00009 to /databases/da001/UNOLTSVT/sbl_data_lg01.dbf
channel aux5: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyknmt9_.bkp
channel aux6: starting datafile backupset restore
channel aux6: specifying datafile(s) to restore from backup set
restoring datafile 00002 to /databases/da001/UNOLTSVT/undotbs01.dbf
restoring datafile 00003 to /databases/da001/UNOLTSVT/sysaux01.dbf
restoring datafile 00005 to /databases/da001/UNOLTSVT/tools01.dbf
restoring datafile 00011 to /databases/da001/UNOLTSVT/sbl_data_xl02.dbf
restoring datafile 00016 to /databases/da001/UNOLTSVT/genuser01.dbf
restoring datafile 00020 to /index/ix001/UNOLTSVT/sbl_idx_lg02.dbf
channel aux6: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52mx_.bkp
channel aux5: restored backup piece 1
piece handle=/archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyknmt9_.bkp tag=MON_114501
channel aux5: restore complete, elapsed time: 00:15:16
channel aux5: starting datafile backupset restore
channel aux5: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /databases/da001/UNOLTSVT/system01.dbf
restoring datafile 00004 to /databases/da001/UNOLTSVT/users01.dbf
restoring datafile 00006 to /databases/da001/UNOLTSVT/siebel_data01.dbf
restoring datafile 00010 to /databases/da001/UNOLTSVT/sbl_data_xl01.dbf
restoring datafile 00014 to /index/ix001/UNOLTSVT/sbl_idx_lg01.dbf
restoring datafile 00022 to /databases/da001/UNOLTSVT/sbl_data_lg02.dbf
channel aux5: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52b2_.bkp
channel aux1: restored backup piece 1
piece handle=/archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52mr_.bkp tag=MON_114501
channel aux1: restore complete, elapsed time: 00:19:42
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00007 to /index/ix001/UNOLTSVT/siebel_index01.dbf
restoring datafile 00012 to /databases/da001/UNOLTSVT/sbl_data_xl03.dbf
restoring datafile 00017 to /index/ix001/UNOLTSVT/siebel_index02.dbf
restoring datafile 00021 to /databases/da001/UNOLTSVT/siebel_data02.dbf
channel aux1: reading from backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52b7_.bkp
channel aux4: restored backup piece 1
piece handle=/archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyk4tct_.bkp tag=MON_114501
channel aux4: restore complete, elapsed time: 00:19:45
channel aux2: restored backup piece 1
piece handle=/archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52n3_.bkp tag=MON_114501
channel aux2: restore complete, elapsed time: 00:28:01
channel aux3: restored backup piece 1
piece handle=/archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52qf_.bkp tag=MON_114501
channel aux3: restore complete, elapsed time: 00:42:37
channel aux6: restored backup piece 1
piece handle=/archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52mx_.bkp tag=MON_114501
channel aux6: restore complete, elapsed time: 00:47:42
channel aux5: restored backup piece 1
piece handle=/archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52b2_.bkp tag=MON_114501
channel aux5: restore complete, elapsed time: 00:56:02
ORA-19870: error reading backup piece /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07/o1_mf_nnndf_MON_114501_6nyj52b7_.bkp
ORA-19502: write error on file "/index/ix001/UNOLTSVT/siebel_index01.dbf", blockno 2365601 (blocksize=8192)
ORA-27063: number of bytes read/written is incorrect
SVR4 Error: 28: No space left on device
Additional information: -1
Additional information: 131072
Outer dbms_backup_restore.restoreCancel() failed
failover to previous backup

channel aux1: reading from backup piece /scratch/bu002/UNTPUAT2/backupset/2011_02_05/UNTPUAT2_34_1_1
*ORA-19870: error reading backup piece /scratch/bu002/UNTPUAT2/backupset/2011_02_05/UNTPUAT2_34_1_1*
*ORA-19505: failed to identify file "/scratch/bu002/UNTPUAT2/backupset/2011_02_05/UNTPUAT2_34_1_1"*
*ORA-27037: unable to obtain file status*
*SVR4 Error: 2: No such file or directory*
Additional information: 3
failover to previous backup

released channel: aux1
released channel: aux2
released channel: aux3
released channel: aux4
released channel: aux5
released channel: aux6
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 02/07/2011 16:58:11
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06100: no channel to restore a backup or copy of datafile 17
RMAN-06100: no channel to restore a backup or copy of datafile 12
RMAN-06100: no channel to restore a backup or copy of datafile 7

RMAN>

    fuzzydba wrote:
    Hi Alex,

    The file it is trying to restore is approximately 22 GB and the drive carrier has about 34 GB of free space, as shown below:

    [oracle@siedbauq01] /archive/ar003/UNTPUAT2/UNTPUAT2/backupset/2011_02_07 [UNOLTSVT]>df -h /index/*
Filesystem             size   used  avail capacity  Mounted on
/dev/md/dsk/d36        197G   161G    34G    83%    /index/ix001

    Please notify.

    As says this problem with the free space above the oracle. Thus, to increase the free space and try again. See above the first error, this indicates that it is error of space.

  • RMAN recovery failed with the incarnation of target of error 03002,11003 and recovery 19906 changed during recovery

    Hi all

    I was cloning a Prod DB (Oracle 10.2.0.5) from tape backup. So the cloning is going on it failed with the below error in RMAN:

    archive log thread = 2 sequence 23044 = filename=+DG_zeus_FRA_01/zeus/archivelog/2014_05_23/thread_2_seq_23044.3558.848348137

    output channel: ch01

    output channel: ch02

    output channel: ch03

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

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

    RMAN-03002: failure of Db in dual at 23/05/2014 20:15:48

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

    ORA-00283: cool cancelled due to errors

    RMAN-11003: failure in parsing / execution of the SQL statement: alter database recover logfile ' +DG_zeus_FRA_01/zeus/archivelog/2014_05_23/thread_2_seq_23044.3558.84

    8348137'

    ORA-00283: cool cancelled due to errors

    ORA-19906: embodiment of changed during recovery recovery targets

    Any possible solution to the resume and cloning complete successfully?

    Kind regards

    Ritu

    incarnation of the list;

    It listed 2 incarnation. I have reset the previous incarnation

    RESET DATABASE TO INCARNATION 2;

    and recovered again and it solved my problem.

    After that added temp files as usual after failing RMAN duplication;

    After this nest of DB and open reset logs.

  • RMAN duplicate for standby the active database and the missing data files

    We have a car of 2 node ASM 11 GR 2 and 11.1 of database and a standby with ASM also. Our database is relatively low (300 GB)

    and in one recent event the day before was such a departure from the primary that we decided to "repopulate" the data using duplicate RMAN.

    I deleted the data files of the previous day and followed the Oracle documentation to duplicate a database. In the waiting

    I created a static listener and a pfile containing only the essential information (db_unique_name). I started the day before with nomount using the 'empty' pfile.

    I run RMAN, connected to the target and ancillary catalogues and run this command:

    run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate channel prmy5 type disk;
allocate auxiliary channel stby1 type disk;
duplicate target database for standby from active database nofilenamecheck;
}

    RMAN duplication completed without errors, so I started the rescue database and got

    an error saying that datafile XXX is missing. I checked XXX datafile at the primary level

    and it is in a DISCONNECTED state. In the standby database the same data file is in the online state.

    So I think the problem is that during the duplication, RMAN (as documentation States) does not work

    Copy the files of data in offline mode, but the standby control file seem to think that these data files

    are online and should be present.

    Can someone please help me solve this problem? From my understanding, I could just copy the missing persons

    data files (there are many however) and in the standby go offline, but I don't think it's

    the right solution, edit this file for control of the standby? I would add another option

    in the RMAN script?

    Take the data file in offline mode on the site of the previous day.

    I don't think that two COPIES try to manage separately offline files.

    Hemant K Collette

  • Purge the rman backup

    Hello, since the alert.log file find this error:

    Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc3_25352.trc file:
    ORA-19809: limit exceeded for file recovery
    ORA-19804: cannot retrieve 12582912 bytes limit 59055800320 disk space
    ARC3: 19809 creation error archive log file ' DATA01'+.
    Sea 25 09:51:58 Jan 2012
    Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc0_25306.trc file:
    ORA-19815: WARNING: 59055800320 bytes db_recovery_file_dest_size is 100.00% used and has 0 bytes remaining available.
    ************************************************************************
    You have choice to free up space in the recovery area:
    + 1. Consider changing the RMAN RETENTION POLICY. If you are using Data Guard +.
    then consider changing POLICY of DELETE ARCHIVELOG RMAN.
    + 2. Back up files on a tertiary device such as a tape using RMAN.
    SAFEGUARDING RECOVERY AREA command.
    + 3. Add disk space and increase the db_recovery_file_dest_size setting to +.
    reflect the new space.
    + 4. Delete unnecessary files by using the RMAN DELETE command. If operation +.
    the system control has been used to remove the files, and then use the RMAN DUPLICATION and
    Commands DELETE has EXPIRED.
    ************************************************************************
    Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc0_25306.trc file:
    ORA-19809: limit exceeded for file recovery
    ORA-19804: cannot retrieve 12582912 bytes limit 59055800320 disk space
    ARC0: error creating 19809 archive log file ' DATA01'+.

    So I'm trying to purge the rman backup, but I have an error message:


    rman target = oratest@oraprdlnx1:~$ /+.
    Recovery Manager: release 11.2.0.1.0 - Production on sea Jan 25 09:47:30 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: TEST (DBID = 2044700519)

    + RMAN > show all; +.

    using the control file of the target instead of recovery catalog database
    RMAN settings for database with db_unique_name TEST are:
    CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
    CONFIGURE BACKUP OPTIMIZATION # by default
    SET UP DEFAULT DISK DEVICE TYPE; # by default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/oratest/product/11.2.0/dbhome_1/dbs/snapcf_TEST1.f'; # by default

    + RMAN > allocate channel for maintenance of type; disc +.

    allocated channel: ORA_MAINT_DISK_1
    channel ORA_MAINT_DISK_1: SID = 237 instance = type of TEST1 = DISK

    + RMAN > crosscheck backup; +.

    "" element of verified backup: turned out to be "AVAILABLE"
    backup handle piece = RECID = 68 = 758320264 STAMP DATA01/test/autobackup/2011_08_04/s_758320263.794.758320265 +.
    Cut objects 1

    RMAN > delete obsolete; ** +

    RMAN retention policy apply to the order
    RMAN retention policy is set to 1 redundancy
    Remove the following obsolete backups and copies:
    Making key time filename/handle type
    -------------------- ------ ------------------ --------------------
    Backup Set 25 July 4, 11
    Backup total 25 4 July 11 1omgk64v_1_1
    Backup Set 26 July 4, 11
    Backup total 26 July 4, 11 1pmgk650_1_1
    Backup Set 24 July 4, 11
    Total backup, 24 4 July 11 1qmgk650_1_1
    Backup Set 21 July 4, 11
    Backup total 21 4 July 11 1rmgk650_1_1
    Backup Set 28 July 4, 11
    28 1vmgk69v_1_1 July 4, 11 total backup
    Save game 29 July 4, 11
    Backup total 29 July 4, 11 20mgk6a0_1_1
    Backup Set 30 July 4, 11
    Backup total 30 4 July 11 21mgk6a0_1_1
    Save game 31 July 4, 11
    Backup total 31 July 4, 11 22mgk6a0_1_1
    Backup Set 34 4 July 11
    Backup total 34 4 July 11 c-2044700519-20110704-07
    Backup Set 35 July 4, 11
    Total backup, 35 26mgk8ib_1_1 4 July 11
    Backup Set 36 4 July 11
    Backup total 36 4 July 11 c-2044700519-20110704-08
    Backup Set 41 4 July 11
    Backup total 41 4 July 11 28mgk94i_1_1
    Backup Set 42 4 July 11
    Backup total 42 4 July 11 29mgk94j_1_1
    Backup Set 37 July 4, 11
    Backup total 37 4 July 11 2amgk94j_1_1
    Backup Set 40 July 4, 11
    Backup total 40 July 4, 11 2bmgk94j_1_1
    Backup Set 38 July 4, 11
    Backup total 38 4 July 11 2cmgk95c_1_1
    Backup Set 39 July 4, 11
    Backup total 39 4 July 11 2dmgk95k_1_1
    Backup Set 43 July 4, 11
    Backup total 43 July 4, 11 c-2044700519-20110704-09
    Backup Set 46 4 July 11
    Backup total 46 4 July 11 2fmgk99f_1_1
    Backup Set 47 July 4, 11
    Backup total 47 4 July 11 2gmgk99g_1_1
    Backup Set 44 4 July 11
    Backup total 44 4 July 11 2hmgk99g_1_1
    Backup Set 48 4 July 11
    Backup total 48 4 July 11 2imgk99g_1_1
    Backup Set 45 4 July 11
    Backup total 45 4 July 11 2jmgk9a9_1_1
    Backup Set 50 4 July 11
    Backup total 50 4 July 11 2kmgk9aq_1_1
    Backup Set 49 July 4, 11
    Backup total 49 4 July 11 2lmgk9aq_1_1
    Backup Set 51 4 July 11
    51 4 July total backup has 11 c-2044700519-20110704-0
    Backup Set 56 4 July 11
    Total backup 56 2rmgk9qb_1_1 July 4, 11
    Backup Set 55 July 4, 11
    Backup total 55 4 July 11 2smgk9qb_1_1
    Backup Set 58 4 July 11
    Backup total 58 4 July 11 b c-2044700519-20110704-0
    Backup Set 60 4 July 11
    Total backup 60 2umgk9tb_1_1 July 4, 11
    Backup Set 61 4 July 11
    Backup total 61 4 July 11 2vmgk9tc_1_1
    Backs up the entire 62 4 July 11
    Backup total 62 4 July 11 30mgk9tc_1_1
    Backup Set 66 4 July 11
    Backup total 66 4 July 11 34mgk9ua_1_1
    Backs up the entire 65 4 July 11
    Backup total 65 4 July 11 35mgk9ua_1_1
    Backup Set 67 4 July 11
    Total backup, July 4, 11 c-2044700519-20110704-0 67C
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the delete command to the 25/01/2012 09:48:42
    RMAN-06091: any string allocated for maintenance (of a suitable type)

    How can I purge the db dest file recovery?

    Thank you!!!

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the delete command to the 25/01/2012 09:48:42
    RMAN-06091: any string allocated for maintenance (of a suitable type)

    There is a metalink note that talks about this error.

    Met RMAN-03002 and RMAN-06091 when deleting obsolete backups [567555.1 ID]
    RMAN could not remove obsolete in right Backupsets change Sbt_tape to disk and again Server [ID 1287755.1]

    HTH

    Kind regards
    Nagendra Chillale

    Published by: NC on January 25, 2012 17:00

  • RMAN Duplicate Database from backups without a target without a catalog.

    I apologize if this has been posted before, although I couldn't find in the forums.
    We are currently on 11 GR 1 matter of database and currently implementing RMAN backup and restore.
    We have databases of test periodically refresh us sources of production for our clients on a regular basis (exp / imp currently). As with general practice, these test reside on a different server.
    I have been through a lot of documentation on RMAN and I have several questions regarding the creation of a database of duplicate backup copies (backup of level 0 currently) without a target database and catalogue (No. Duplication Active)

    We have Oralce files managed, implemented.

    (1) RMAN requires a database for replication?
    The reason I ask this question, it is only
    http://download.Oracle.com/docs/CD/B28359_01/backup.111/b28270.PDF Chapter 23, 23-13/23-14. Alll indicate that need a target.

    (2) if there is No target, then setting SPFILE used the backup SpFILE?

    (3) what are recommended approaches.

    (4) what is the command for the simple reproduction of backup without purpose and without catalog

    Thank you

    'Target-free' RMAN duplication is a feature of 11 GR 2:

    http://download.Oracle.com/docs/CD/E11882_01/server.112/e17128/Chapter1.htm#FEATURENO06994

  • RMAN, auxiliary db and blocked listener?

    Hey;

    I am to the point of trying the rman duplication in my study of backup/restore and I ran into a bit of a problem with oracle net.

    Oracle 10g, 10.2.0.1.0, under oracle redhat linux.

    I know rman requires a dedicated server, so I'm in netmgr and tried to create a.

    The listener.ora file has not changed and shows:

    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = CIP)(KEY = EXTPROC1))
    )
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = ocidb1.olearycomputers.com) (PORT = 1521))
    )
    )

    The tnsnames.ora file now has a section for oci3 (auxiliary, hope to be cloned db) as follows:

    OCI3 =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = ocidb1.olearycomputers.com) (PORT = 1521))
    )
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = oci3)
    )
    )


    And who exactly resembles the entrance to oci1 with the exception of the service_name.

    I reload, restart the listener, then "startup nomount" oci3.

    RMAN target / catalog rcat/${mypwd}@oci2

    shows a good connection to the source and the catalog, then:

    RMAN > Connect auxiliary sys/${mypwd}@oci3

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-04006: auxiliary database error: ORA-12528: TNS:listener: all appropriate instances are blocking new connections

    Headset shows the connection as blocked oci3:

    $ lsnrctl status
    [[snip]]
    Service 'oci3' has 1 instance (s).
    Instance 'oci3', LOCKED status, has 1 operation for this service...
    Service 'oci3_XPT' has 1 instance (s).
    Instance 'oci3', LOCKED status, has 1 operation for this service...
    The command completed successfully

    Can someone indicate on what I am to spoil? Net Oracle was my next field of study; However, what little I know, and, more importantly, from what I read, it looks like it's supposed to work

    Thanks for all the tips/advice/suggestions.


    Doug

    Dear dkoleary,

    BLOCKED instance means that the auxiliary instance in the phase nomount. If you mount the database or open it, you can connect via the entry of ID of the Oracle (sqlplus @ oracle_sid).

    You can use the following command on the auxiliary instance, where the primary is defined in the tnsnames.ora.

    # RMAN TARGET SYS/PASSWORD@PRIMARY AUXILIARY /

    Hope that helps.

    Ogan

  • Restoration of Rel2 (64-bit) 10 G to 10g (32-bit) Rel2 via RMAN

    Hello

    I use 10.2.0.4 on HP - UX 11iV2 (64-bit Itanium server) operating system.

    We want to create the instance of Test on RHEL 5, so please let me know if it is possible using backup RMAN.

    Source database:
    Operating system: HP - UX 11iV2 (64-bit Itanium server)
    Database: 10.2.0.4 (64-bit)

    Target database:
    OS: RHEL 5 (32-bit)
    Database: Database 10 G R2 (32 bit)


    Thanks in advance
    Amith

    In the source system and the target using different OS, you can do so by using RMAN duplication. You can use the option of the transportable tablespace for this migration.

    Please click on this link.

    http://www.dbasupport.com/Oracle/Ora10g/transportable_tablespace01.shtml

    Concerning
    Asif Kabir

  • "PING [ARC2]: Heartbeat cannot connect to standby mode"

    Dear Experts,

    I have n/w connectivity between two servers.  IP is the ping requests.

    But primary alert log datbase shows PING [ARC2]: Heartbeat cannot connect to standby mode '

    This standby alert log database already mounted.

    SYS > select nom_dest, status, type, database_mode, recovery_mode, error, destination, synchronization_status from v$ archive_dest_status where type = 'PHYSICAL ';

    STATUS TYPE ERROR DESTINATION SYNCHRONIZATION_STATUS RECOVERY_MODE DATABASE_MODE NOM_DEST

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

    LOG_ARCHIVE_DEST_2 ERROR PHYSICS FORCE RESCUE IDLE ORA-16058: standby database instance is not mounted stby_crmsdb CHECK the CONFIGURATION

    Heartbeat PING [ARC2]: Unable to connect to the day before "stby_crmsdb". The error is 16058.

    Sam Oct 31 12:20:12 2015

    Errors in the /u01/app/oracle/diag/rdbms/crms/crms/trace/crms_arc2_32417.trc file:

    ORA-16058: standby database instance is not mounted

    Heartbeat PING [ARC2]: Unable to connect to the day before "stby_crmsdb". The error is 16058.

    Sam Oct 31 12:26:16 2015

    Errors in the /u01/app/oracle/diag/rdbms/crms/crms/trace/crms_arc2_32417.trc file:

    ORA-16058: standby database instance is not mounted

    Heartbeat PING [ARC2]: Unable to connect to the day before "stby_crmsdb". The error is 16058.

    Sam Oct 31 12:32:18 2015

    Errors in the /u01/app/oracle/diag/rdbms/crms/crms/trace/crms_arc2_32417.trc file:

    ORA-16058: standby database instance is not mounted

    Heartbeat PING [ARC2]: Unable to connect to the day before "stby_crmsdb". The error is 16058.

    Sam Oct 31 12:37:20 2015

    Errors in the /u01/app/oracle/diag/rdbms/crms/crms/trace/crms_arc2_32417.trc file:

    ORA-16058: standby database instance is not mounted

    Heartbeat PING [ARC2]: Unable to connect to the day before "stby_crmsdb". The error is 16058.

    Sam Oct 31 12:38:31 2015

    > > On standby server I delivered after a command.  Cloning process is running

    $ rman target sys/passwd@CRMSDB auxiliary sys/passwd@STBY_CRMSDB

    ...

    ....

    > > alert_log ensures msgs

    Sam Oct 31 12:07:17 2015

    Connections of RFS were rejected

    change the basis of mountain rescue

    Defined in the converted due to the incompatibility of db_unique_name control file

    Change di2dbun of MRC to stbycrms

    ARK: START OF THE ARCH PROCESS

    Sam Oct 31 12:07:21 2015

    Arc0 started with pid = 22, OS id = 7103

    Arc0: Started archiving

    ARCH: FROM PROCESS ARCH COMPLETE

    ARC0: FROM PROCESS ARCH

    Sam Oct 31 12:07:22 2015

    Mount of redo thread 1, with mount id 1596596917

    Physical Standby Database mounted.

    Lost write protect mode the "typical" value

    ..

    Sam Oct 31 12:07:22 2015

    Arc1 started with pid = 23, OS id = 7105

    Completed: alter database mount standby

    Sam Oct 31 12:07:22 2015

    ARC2 started with pid = 24, OS id = 7107

    Arc1: Started archiving

    ARC2: Started archiving

    Arc1: become the "no FAL' ARCH

    Sam Oct 31 12:07:22 2015

    ARC3 started with pid = 25, OS id = 7109

    ARC2: Become the heartbeat ARCH

    ARC3: Started archiving

    ARC0: FROM PROCESS ARCH COMPLETE

    Sam Oct 31 12:07:24 2015

    Using the default for the STANDBY_ARCHIVE_DEST as USE_DB_RECOVERY_FILE_DEST parameter value

    > On primary and Stanby (output is even only)

    SYS > select thread #, max(sequence#) from v$ archived_log group thread #;

    THREAD # MAX(SEQUENCE#)

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

    1 14452

    Your standby database health seems good and is in phase with the primary. Mistakes "hearbeat failed", you've seen, maybe during the RMAN duplication, Eve could have been returned a couple of times, who would have said these errors in the primary alert log file.

    -Jonathan Rolland

  • ORA-19815: WARNING: 42949672960 bytes db_recovery_file_dest_size is 100.00% used and has 0 bytes remaining available.

    Hello

    When I try to start my database, I get this error:

    SQL > startup;

    ORACLE instance started.

    Total System Global Area 8551575552 bytes

    Bytes of size 2245480 fixed

    2365590680 variable size bytes

    6157238272 of database buffers bytes

    Redo buffers 26501120 bytes

    Mounted database.

    ORA-03113: end of file on communication channel

    Process ID: 9789

    Session ID: 321 serial number: 3

    I checked the alert log file and concluded that,

    Errors in the /u01/app/oracle/diag/rdbms/dev/dev/trace/dev_arc1_11834.trc file:

    ORA-19815: WARNING: 42949672960 bytes db_recovery_file_dest_size is 100.00% used and has 0 bytes remaining available.

    ************************************************************************

    You have choice to free up space in the recovery area:

    1 consider changing STRATEGY OF RETENTION of RMAN. If you are using Data Guard

    then consider changing POLICY of DELETE ARCHIVELOG RMAN.

    2 back up files on a tertiary device such as a tape with RMAN

    SAFEGUARDING RECOVERY AREA command.

    3. Add space drive and increase the db_recovery_file_dest_size setting to

    reflect the new space.

    4 remove the unnecessary files using the RMAN DELETE command. If a service

    the system control has been used to remove the files, and then use the RMAN DUPLICATION and

    Commands DELETE has EXPIRED.

    ************************************************************************

    Arc1: 19809 error creating archive log file at "+ RECO.

    ARCH: Stopped archiving, error occurred. Will continue to retry

    ORACLE Instance dev - archive error

    ORA-16038: log sequence 1 # 46 can be archived

    ORA-19809: limit exceeded for file recovery

    ORA-00312: 1 1 online journal thread: "+ REDO/dev/onlinelog/group_1.284.879765261".

    To do this,

    I can't connect to database, so I deleted the archivelogs manually from + RECO/DEV/ARCHIVELOG/and tried to start the database once again, still the same error.

    The problem here is that I can't open the database, so I am unable to increase db_recovery_file_dest_size or connecting to RMAN and remove the archivelogs.

    Any suggestions on how to fix this?

    Thank you

    bootable media;

    Than the command again a problem.

    ALTER system set db_recovery_file_dest_size = 50G scope = both;

    ALTER database open;

    Best regards

    mseberg

  • Database does not start... ALTER database open; change the database open * ERROR at line 1: ORA-03113: end of file on the channel of communication process ID: 10400 Session ID: 418 serial number: 3 -.

    HI during startup of the database of the following errors is. Please help solve the problem.

    SQL > alter database open;

    change the database open * ERROR at line 1: ORA-03113: end of file on the channel of communication process ID: 10400 Session ID: 418 serial number: 3 -.

    ============================================================

    Please see the alerts log entries

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

    Commissioning:

    Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production

    With the options of partitioning, OLAP, Data Mining and Real Application Testing.

    Using parameters in spfile D:\APP\ADMINISTRATOR\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEATTNDPRD server-side. ORA

    Parameters of the system with default values:

    process = 400

    sessions = 624

    memory_target = 4G

    control_files = 'D:\ORACLE\ORADATA\ATTNDPRD\CONTROLFILE\O1_MF_8LRQYB0M_. CTL.

    control_files = 'C:\ORACLE\ORADATA\ATTNDPRD\CONTROLFILE\O1_MF_8LRQYB13_. CTL.

    DB_BLOCK_SIZE = 8192

    compatible = "11.2.0.0.0."

    log_archive_format = "ARC%S_%R.%T."

    db_create_file_dest = 'D:\oracle\oradata. '

    db_create_online_log_dest_1 = "D:\oracle\oradata".

    db_create_online_log_dest_2 = "C:\oracle\oradata".

    db_recovery_file_dest = 'C:\oracle\oradata\flash_area. '

    db_recovery_file_dest_size = 8G

    undo_tablespace = 'UNDOTBS1.

    Remote_login_passwordfile = "EXCLUSIVE."

    db_domain = «»

    dispatchers = "(PROTOCOL=TCP) (SERVICE = ATTNDPRDXDB)" "

    audit_file_dest = "D:\APP\ADMINISTRATOR\ADMIN\ATTNDPRD\ADUMP".

    AUDIT_TRAIL = 'DB '.

    db_name = "ATTNDPRD".

    open_cursors = 300

    diagnostic_dest = "D:\APP\ADMINISTRATOR".

    Sun 24 May 13:43:09 2015

    PMON started with pid = 2, OS id = 5792

    Sun 24 May 13:43:09 2015

    VKTM started with pid = 3, OS id = 6500 high priority

    VKTM clocked at (10) precision of milliseconds with DBRM quantum (100) ms

    Sun 24 May 13:43:09 2015

    GEN0 started with pid = 4, OS id = 13072

    Sun 24 May 13:43:09 2015

    DIAG started with pid = 5, OS id = 1424

    Sun 24 May 13:43:09 2015

    DBRM started with pid = 6, OS id = 8240

    Sun 24 May 13:43:09 2015

    PSP0 started with pid = 7, OS id = 2980

    Sun 24 May 13:43:09 2015

    DIA0 started with pid = 8, OS id = 12956

    Sun 24 May 13:43:09 2015

    MA started with pid = 9, OS id = 13356

    Sun 24 May 13:43:09 2015

    DBW0 started with pid = 10, OS id = 14248

    Sun 24 May 13:43:09 2015

    DBW1 started with pid = 11, OS id = 17900

    Sun 24 May 13:43:09 2015

    LGWR started with pid = 12, OS id = 5564

    Sun 24 May 13:43:09 2015

    CKPT started with pid = 13, OS id = 16736

    Sun 24 May 13:43:09 2015

    SMON started with pid = 14, OS id = 14068

    Sun 24 May 13:43:09 2015

    RECCE has started with pid = 15, OS id = 16288

    Sun 24 May 13:43:09 2015

    MMON started with pid = 16, OS id = 10884

    commissioning 1 dispatcher (s) for '(ADDRESS =(PARTIAL=YES) (PROTOCOL = TCP))' network address...

    commissioning or shared server 1...

    Environment ORACLE_BASE = D:\app\Administrator

    Sun 24 May 13:43:09 2015

    ALTER DATABASE MOUNT

    Sun 24 May 13:43:09 2015

    MMNL started with pid = 17, OS id = 16128

    Mount of redo thread 1, with mount id 3325657453

    Database mounted in exclusive Mode

    Disabled lost write protect

    Completed: ALTER DATABASE MOUNT

    Sun 24 May 13:43:23 2015

    change the database open

    Sun 24 May 13:43:23 2015

    LGWR: FROM PROCESS ARCH

    Sun 24 May 13:43:23 2015

    Arc0 started with pid = 21, OS id = 10084

    Arc0: Started archiving

    LGWR: FROM PROCESS ARCH COMPLETE

    ARC0: FROM PROCESS ARCH

    Sun 24 May 13:43:24 2015

    Arc1 started with pid = 22, OS id = 18400

    Sun 24 May 13:43:24 2015

    ARC2 started with pid = 23, OS id = 17280

    Arc1: Started archiving

    ARC2: Started archiving

    Arc1: become the "no FAL' ARCH

    Arc1: become the "no SRL" ARCH

    ARC2: Become the heartbeat ARCH

    Errors in the d:\app\administrator\diag\rdbms\attndprd\attndprd\trace\attndprd_ora_10400.trc file:

    ORA-19815: WARNING: db_recovery_file_dest_size 8589934592 bytes is 100.00% used and has 0 bytes remaining available.

    ************************************************************************

    You have choice to free up space in the recovery area:

    1 consider changing STRATEGY OF RETENTION of RMAN. If you are using Data Guard

    then consider changing POLICY of DELETE ARCHIVELOG RMAN.

    2 back up files on a tertiary device such as a tape with RMAN

    SAFEGUARDING RECOVERY AREA command.

    3. Add space drive and increase the db_recovery_file_dest_size setting to

    reflect the new space.

    4 remove the unnecessary files using the RMAN DELETE command. If a service

    the system control has been used to remove the files, and then use the RMAN DUPLICATION and

    Commands DELETE has EXPIRED.

    ************************************************************************

    Errors in the d:\app\administrator\diag\rdbms\attndprd\attndprd\trace\attndprd_ora_10400.trc file:

    ORA-19809: limit exceeded for file recovery

    ORA-19804: cannot recover disk 44571136 bytes limit 8589934592 space

    ARCH: 19809 error creating archive log file to ' C:\ORACLE\ORADATA\FLASH_AREA\ATTNDPRD\ARCHIVELOG\2015_05_24\O1_MF_1_10343_%U_. ARC'

    Errors in the d:\app\administrator\diag\rdbms\attndprd\attndprd\trace\attndprd_ora_10400.trc file:

    ORA-16038: log 2 # 10343 sequence can be archived

    ORA-19809: limit exceeded for file recovery

    ORA-00312: wire 2 1 online journal: ' D:\ORACLE\ORADATA\ATTNDPRD\ONLINELOG\O1_MF_2_8LRQYD8B_. JOURNAL"

    ORA-00312: wire 2 1 online journal: ' C:\ORACLE\ORADATA\ATTNDPRD\ONLINELOG\O1_MF_2_8LRQYDF6_. JOURNAL"

    USER (ospid: 10400): put an end to litigation because of the error 16038

    Sun 24 May 13:43:24 2015

    ARC3 started with pid = 24, OS id = 2188

    Errors in the d:\app\administrator\diag\rdbms\attndprd\attndprd\trace\attndprd_arc2_17280.trc file:

    ORA-19815: WARNING: db_recovery_file_dest_size 8589934592 bytes is 100.00% used and has 0 bytes remaining available.

    ************************************************************************

    You have choice to free up space in the recovery area:

    1 consider changing STRATEGY OF RETENTION of RMAN. If you are using Data Guard

    then consider changing POLICY of DELETE ARCHIVELOG RMAN.

    2 back up files on a tertiary device such as a tape with RMAN

    SAFEGUARDING RECOVERY AREA command.

    3. Add space drive and increase the db_recovery_file_dest_size setting to

    reflect the new space.

    4 remove the unnecessary files using the RMAN DELETE command. If a service

    the system control has been used to remove the files, and then use the RMAN DUPLICATION and

    Commands DELETE has EXPIRED.

    ************************************************************************

    Instance of stopped by USER, pid = 10400

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

    Regarding

    Ngoyi

    Hello

    Now it works very well... with following

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

    using sqlplus

    • Startup mount
    • ALTER database noarchivelog;
    • ALTER database open;

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

    Concerning

    Ngoyi

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

Maybe you are looking for