Application of an rman duplicate database archiving log

Similar Questions

• RMAN-06059: expected archived log not found

  DB version: 11.1.0.7
  Operating system: Solaris 10
  
  Our cron job RMAN has met the following error.
  -First save attempt (complete bkp more archive log) done by connecting to the catalog

  Starting backup at 14-MAR-12
  current log archived
  released channel: ch00
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of backup plus archivelog command at 03/14/2012 08:09:58
  RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
  ORA-19625: error identifying file +PQWSP_ARCH01/pqwsp_arch/pqwsp_26530_1_764525298.arc
  ORA-17503: ksfdopn:2 Failed to open file +PQWSP_ARCH01/pqwsp_arch/pqwsp_26530_1_764525298.arc
  ORA-15173: entry 'pqwsp_26530_1_764525298.arc' does not exist in directory 'pqwsp_arch'

  Because I didn't share RMAN catalog schema password, I used the control as a catalog file and run the CROSSCHECK command.
  
  -Use the control as a catalog file

  $ rman target /
  
  Recovery Manager: Release 11.1.0.7.0 - Production on Wed Mar 14 09:45:59 2012
  
  Copyright (c) 1982, 2007, Oracle.  All rights reserved.
  
  connected to target database: PQWSP (DBID=1638594930)
  
  RMAN> crosscheck archivelog all;
  
  using target database control file instead of recovery catalog
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID=429 instance=pqwsp1 device type=DISK
  validation succeeded for archived log
  archived log file name=+PQWSP_ARCH01/pqwsp_arch/pqwsp_26563_1_764525298.arc RECID=19019 STAMP=777888587
  validation succeeded for archived log
  archived log file name=+PQWSP_ARCH01/pqwsp_arch/pqwsp_26564_1_764525298.arc RECID=19022 STAMP=777890270
  validation succeeded for archived log
  .
  .
  .
  .
  .
  
  Crosschecked 14 objects

  Cannot find objects expired in the output above. I had * "validation succeeded" * message to arch all newspapers.
  
  So I ran a

  BACKUP ARCHIVELOG ALL DELETE ALL INPUT;

  and this backup was successful.
  
  No idea why the first attempt failed when there were not all logs archived expired? If I run the command of OVERLAP by connecting to the catalog, I could find out of date newspapers?

  No idea why the first attempt failed when there were not all logs archived expired?
  this case is not releated archivelog expired, however it seems the requested archivelog 26530 isn't available on destinationas, that it can be removed manually or another taking backup operation the backup and deleted if the execution of the whole.

  crosscheck updated detail that its not available for backup... Check the output of you overlap cmd to 26530 archivelog.

  Thank you
  Tylay Singh

• RMAN duplicate database RAC w/ASM to stand alone without ASM fails

  Trying to duplicate database in order to upgrade to 11.2 and migrate from Windows to Solaris with minimal downtime, using GoldenGate. The source database is 11.1.0.7 on Windows 2003 x 64 a 2 RAC node. The auxiliary database is 11.1.0.7 on a single Windows 2003 x 64 server. The steps to reach where the error has occurred are:
  
  1 created auxiliary instance on remote node. creating oradim and the listener.
  
  2 copied password for the remote node target file and put it in the directory %ORACLE_HOME%\database and % ORACLE_HOME%\dbs.
  
  3 created PFILE in %ORACLE_HOME%\database and copied to %ORACLE_HOME%\dbs just in case.
  
  db_name = "UTILAX".
  instance_name = UTILAX
  diagnostic_dest = a: \oracle\admin\utilax'
  db_file_name_convert =('+Data/util','D:\oracle\oradata\utilax')
  log_file_name_convert =('+Data/util','D:\oracle\log\utilax')
  SGA_TARGET = 5g
  control_files=D:\oracle\oradata\utilax\control01.dbf
  compatible = '11.1.0'
  
  4 Startup nomount performed.
  
  5. backup Ran full on the head node to the D drive and outside the DSO.
  
  rman target % = / catalog=rman/password@RMAN
  
  RMAN > run {}
  allocate channel d1 type disk;
  database backup in format "D:\backups\df_t%t_s%s_p%p".
  SQL 'alter system archive log current';
  backup format 'D:\backups\al_t%t_s%s_p%p' archivelog all;
  output channel d1;
  }
  
  6 copied only the manual backup (22 GB) to the remote host files in the same directory on the D drive. D:\backups same folder on both servers.
  
  7. connected with rman, target, catalog and auxiliary databases. A run the rman command to duplicate the database on the target instance.
  
  DUPLICATE THE TARGET DATABASE TO 'UTILAX' IN THE CURRENT DATABASE.
  
  Errors received
  RMAN-03009: failure of the backup on the channel ORA_DISK_1 command
  ORA-17628: error Oracle 19505 returned by remote Oracle Server
  
  8. looked in the auxiliary database alerts log. Errors found:
  ORA-19505: impossible to identify the file 'D:\ORACLE\ORADATA\UTILAX\DATAFILE\SYSTEM.327.716381457 '.
  ORA-27040: create file error, cannot create the file
  04002 - OSD: could not open the file
  S/O-error: (OS 3) the system cannot find the path specified
  
  9 creates all directories to the path and try again. Same mistakes.
  
  
  Must miss one or two steps but document metalink 382269.1 followed as closely as possible. Sorry for the lack of screenshots but databases are private networks. Someone who did that regularly offer any help?
  
  Thank you

  Since you have already made the backup and copied to the auxiliary server, why use again 'data base active'

  DUPLICATE THE TARGET DATABASE TO 'UTILAX' IN THE CURRENT DATABASE.

  Just try to DUPLICATE the DATABASE to 'UTILAX' TARGET nofilenamecheck;

  This would work out.

  or if you want to continue to make use of the active database functionality, then

  DUPLICATE TARGETS DATABASE to the 'UTILAX' of the active database nofilenamecheck.

  Published by: srp on December 28, 2011 12:24 AM

• Oracle database archive logs

  Hi all

  I searched the Oracle and Internet Documents. It is really hard to get information on the management of the archive Log, so I thought to post it here:

  Now, our Database 9i (EBS 11.5.x) was in no archive mode, so I allowed him to archive mode.

  Edit the pfile $ORACLE_HOME/admin/SID/pfile who will be /oracle/proddb/9.2.0/dbs/initPROD.ora

  ############################

  # Archive Log Destinations-benr(10/15/04)

  ############################

  Log_archive_dest_1 = ' location = / Uncordon / archive.

  log_archive_start = TRUE

  
  

  then connect to the database

  
  

  
  

  
  

  
  

  SQL > shutdown normal;

  SQL > startup mount exclusive;

  SQL > alter system set log_archive_start = TRUE scope = spfile;
  SQL > alter system set log_archive_dest_1='LOCATION= /oracle/archivelog ' scope=both;
SQL > alter archivelog database;
  SQL > CHANGE the START of the SYSTEM ARCHIVE LOG;
  SQL > alter database open;
  SQL > alter system archive log all;
  SQL > change the start of the archive log system;
  SQL > archive log start;

  
  

  The next day, I checked the location of archive and sparked an archive of 1 GB even if there is no activity on the database.

  root@test4:/oracle/archivelog>ls
  1_844.dbf   1_862.dbf   1_880.dbf   1_898.dbf   1_916.dbf   1_934.dbf
  1_845.dbf   1_863.dbf   1_881.dbf   1_899.dbf   1_917.dbf   1_935.dbf
  1_846.dbf   1_864.dbf   1_882.dbf   1_900.dbf   1_918.dbf   1_936.dbf
  1_847.dbf   1_865.dbf   1_883.dbf   1_901.dbf   1_919.dbf   1_937.dbf
  1_848.dbf   1_866.dbf   1_884.dbf   1_902.dbf   1_920.dbf   1_938.dbf
  1_849.dbf   1_867.dbf   1_885.dbf   1_903.dbf   1_921.dbf   1_939.dbf
  1_850.dbf   1_868.dbf   1_886.dbf   1_904.dbf   1_922.dbf   1_940.dbf
  1_851.dbf   1_869.dbf   1_887.dbf   1_905.dbf   1_923.dbf   1_941.dbf
  1_852.dbf   1_870.dbf   1_888.dbf   1_906.dbf   1_924.dbf   1_942.dbf
  1_853.dbf   1_871.dbf   1_889.dbf   1_907.dbf   1_925.dbf   1_943.dbf
  1_854.dbf   1_872.dbf   1_890.dbf   1_908.dbf   1_926.dbf   1_944.dbf
  1_855.dbf   1_873.dbf   1_891.dbf   1_909.dbf   1_927.dbf   1_945.dbf
  1_856.dbf   1_874.dbf   1_892.dbf   1_910.dbf   1_928.dbf   1_946.dbf
  1_857.dbf   1_875.dbf   1_893.dbf   1_911.dbf   1_929.dbf   1_947.dbf
  1_858.dbf   1_876.dbf   1_894.dbf   1_912.dbf   1_930.dbf   lost+found
  1_859.dbf   1_877.dbf   1_895.dbf   1_913.dbf   1_931.dbf   test.txt
  1_860.dbf   1_878.dbf   1_896.dbf   1_914.dbf   1_932.dbf
  1_861.dbf   1_879.dbf   1_897.dbf   1_915.dbf   1_933.dbf
  

  Question

  1. How can I delete old logs archiving without using RMAN?

  2. How should I know which Archives connects to keep and delete?

  3. is there a way to know why the database generates so many newspapers to check-in?

  Hello

  Yes, you must keep this archive. You can schedule the job to compress files to archive (record use of space) and move it to another place as a backup.

  You can schedule both COLD backup once a week, in this case it is scabies archive for a week.

  HTH

• RMAN DUPLICATE DATABASE RESULT IN A RE - ORG

  Database Version 10.2.0.4
  
  When I perform a duplicate database RMAN is the new database completely reorganized? The new database can be any fragmentation or water marks high if the source database has done?
  
  Thank you

  The answer to your question is no duplicate RMAN does not cause a re - org, RMAN is a block of files of database level backup, RMAN duplicate is a double level of a data block. Therefore, duplicate RMAN is fundamentally a restoration of the source database, because it is in another location and an instance of the database and the database name change.

• 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 duplicate database

  Hi experts. I duplicate my database to another server. My question is what should I copy file full backup on my server to another or not?

  Hello

  Follow the same pattern

  http://docs.Oracle.com/CD/B19306_01/server.102/b14237/initparams112.htm#REFRN10098

  LOG_FILE_NAME_CONVERT = 'string1' , 'string2' , 'string3' , 'string4' , ...

  Where:

  • string1is the model of the primary database file name
  • string2is the model of the database backup file name
  • string3is the model of the primary database file name
  • string4is the model of the database backup file name

  -Thank you

  Pavan Kumar N

• RMAN Duplicate Database Error error ORA-00201

  Hello

  I tried to create the restore scenario backup in vmware. I have 2 similar server in Oracle Linux 6.2 (64-bit) where 11.2.0.4 has been installed. In my source server I orcl database and in the destination, there is no database. I took RMAN backup of database in the Source. Then I tried to Clone of Destination on Backup-based database without connection to the target and the catalog. Backup Destination and issued the command as follows:

  1 has created a pfile.ora with db_name = "orcl" only

  2. in the sqlplus command line: Startup nomount pfile = 'pfile.ora'

  Then

  started with RMAN, auxiliary

  Auxiliary RMAN.

  RMAN > duplicated to the backup location "orcl" database "/ home/Oracle/tmp";

  After some progress appears error ORA-00201 control file not compatible with 11.2.0.0.0 . Attempted to solve all day but failed. In trying so I even uninstalled and reinstalled several times oracle.

  Help, please

  Hasan Al Mamun

  Hello

  The problem is resolved. I added a line in the pfile.ora, i.e. * full = '11.2.0.4.0' then it's OK, Clone of database was complete.
  

  
  

• RMAN Duplicate Database of ASM to the no ASM files to the remote computer system

  Hello
  
  I have 11.2.0.3.0 of oracle in Windows 2008 server R2 64 bit version. I installed the ASMDB with ASM database... Now, I have another a machine, I want to clone my
  database in this machine with no ASM filesystem ... Can someone tell me step by step document to do?
  
  Can I keep the name of the database as ASMDB in another Machine?
  
  
  Thank you and best regards,
  Vikash Chauradia

  What about password file? also, should I create in the auxiliary database?

  Yes

  and also a doubt when you create pfile should I mention the location of the control file in that?

  Yes

• Archiving log backup RMAN

  Hi guys,.
  
  Can advise you on the syntax for the rman backup of archive logs generated in the last 2 days?
  
  Wouldn't be 1 or 2?
  
  Thank you!
  
  1 BACKUP ARCHIVELOG UNTIL ' SYSDATE-2';
  
  2 BACKUP ARCHIVELOG FROM TIME ' SYSDATE-2';

  Run the commands and see what is RMAN - it will show you what files it runs a backup of!

  OR

  Search the documentation
  http://docs.Oracle.com/CD/E11882_01/backup.112/e10643/TOC.htm

  Hemant K Collette

• RMAN-04014: failed to start: ORA-00600 during the duplicate database

  Hello
  
  Oracle version: 11.2.0.2
  
  OS: linux rhel 5
  
  I do duplicate database of active database
  

  rman target sys/*******@pindb AUXILIARY sys/*****@test
  
  Recovery Manager: Release 11.2.0.2.0 - Production on Mon Nov 26 19:56:41 2012
  
  Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
  
  connected to target database: pindb (DBID=4116200880)
  connected to auxiliary database: TEST (not mounted)
  
  RMAN> run {
  allocate channel C1 type disk;
  allocate auxiliary channel DUP type disk;
  DUPLICATE TARGET DATABASE  TO 'TEST' FROM ACTIVE DATABASE  DB_FILE_NAME_CONVERT '/oradata/pindb','/oradata/test';
  }2> 3> 4> 5>
  
  using target database control file instead of recovery catalog
  allocated channel: C1
  channel C1: SID=699 device type=DISK
  
  allocated channel: DUP
  channel DUP: SID=5 device type=DISK
  
  Starting Duplicate Db at 26-NOV-12
  
  contents of Memory Script:
  {
     sql clone "create spfile from memory";
  }
  executing Memory Script
  
  sql statement: create spfile from memory
  
  contents of Memory Script:
  {
     shutdown clone immediate;
     startup clone nomount;
  }
  executing Memory Script
  
  Oracle instance shut down
  
  connected to auxiliary database (not started)
  released channel: C1
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of Duplicate Db command at 11/26/2012 19:57:07
  RMAN-06403: could not obtain a fully authorized session
  RMAN-04006: error from auxiliary database: ORA-01034: ORACLE not available
  ORA-27101: shared memory realm does not exist
  Linux-x86_64 Error: 2: No such file or directory
  RMAN-03015: error occurred in stored script Memory Script
  RMAN-04014: startup failed: ORA-00600: internal error code, arguments: [kck_rls_check must use (11,0,0,0,0) or lower], [kdt.c], [9576], [11.2.0.2.0], [], [], [], [], [], [], [], []
  RMAN-04017: startup error description: ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

  Please can someone offer
  
  Thank you

  Hello;

  In my view, that it is a bug that has to do with the compatibility of the compression.

  I think that work around is:

  alter system  set "_compression_compatibility"="11.2.0";
  

  Let me confirm with a document number of MOS

  Subsequently Cannot find the doc of MOS - this has some details:

  http://www.acehints.com/2011/11/fix-RMAN-duplicate-database-failed-ora.html

  http://bryangrenn.blogspot.com/2011/12/ora-600-kckrlscheck-must-use-110000-or.html

  Best regards

  mseberg

  Published by: mseberg on November 26, 2012 16:07

• RMAN duplicate: ORA-00283, ORA-0060internal error code, arguments: [kcvhvdf

  This is related to this thread: Re: duplicated to database: ends with error: rman-06136 ora-01110
  
  I supported the newspaper of archive and continues:
  
  RMAN > overview of the database to recover
  2 >.
  
  To go back to November 16, 12
  using channel ORA_DISK_1
  using channel ORA_DISK_1
  
  Archive logs generated after that YVERT 0 not found in the repository
  Start of recovery Media SNA is 0
  Recovery must be beyond SNA 91215577536 to clear the hazy data file
  Finished recover at 16 November 12
  
  RMAN > run {}
  2 > set up what SNA 91215577536.
  3 > restore database;
  4 > sql ' alter database open resetlogs;
  {5 >};
  
  executing command: SET until clause
  
  To go back to November 16, 12
  using channel ORA_DISK_1
  
  starting media recovery
  media recovery failed
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the command recover at 11/16/2012 19:45:40
  ORA-00283: cool cancelled due to errors
  RMAN-11003: failure in parsing / execution of the SQL statement: alter database reco worm if necessary
  forward this 91215577536 change using backup controlfile
  ORA-00283: cool cancelled due to errors
  [ORA-00600: internal error code, arguments: [kcvhvdf_1], [], [], [], [], [], [], [], [], [], []]
  
  In the alerts log, the ora-00600 even raised.
  
  How to get around this problem?
  
  Thank you

  Hello;

  I agree with you. And while I have nothing to correct your error, this document is worth seeing:

  http://gavinsoorma.com/2012/04/RMAN-duplicate-database-RAC-to-RAC/

  If nothing else its useful to add to any collection of notes, you can have.

  Best regards

  mseberg

• list of archive logs show only 1 location instead of 2

  Friends...
  OS: OEL 5.5 64-bit
  DB: 11g R2 (11.2.0.3) 64-bit
  I put 2 destination to archive. Log_archive_dest_1 = / u01/archive1 and log_archive_dest_2 under/u01/archive2.
  When I do this...

  SQL> archive log list
  Database log mode              Archive Mode
  Automatic archival             Enabled
  Archive destination            /u01/archive2/
  Oldest online log sequence     8
  Next log sequence to archive   10
  Current log sequence           10

  at the same time, when I do this...

  SQL> select dest_name,status,destination from v$archive_dest;
  
  DEST_NAME                                          STATUS                                             DESTINATION
  -------------------------------------------------- -------------------------------------------------- --------------------------------------------------
  LOG_ARCHIVE_DEST_1                                 VALID                                              /u01/archive1/
  LOG_ARCHIVE_DEST_2                                 VALID                                              /u01/archive2/

  Why list archives logs showing that one location whereas the query indicates both the location. and why list of newspapers of record showing instead of archive1 archive2?
  
  Thank you

  The LIST of NEWSPAPERS of ARCHIVES control gives a quick overview of the State of archive, it clearly should not be used to report on destinations.

  The ARCHIVE_DEST view $ V gives a clear view into where on the disk are these destinations and when you use the LOG_ARCHIVE_DEST_n parameter, is closely related to what has been entered in the file init.ora parameters

  Maybe this might help you http://www.databasejournal.com/features/oracle/article.php/3867646/Oracle-Database-Archive-Logging---Where-are-my-archive-logs.htm

• Why do we use RMAN DUPLICATE to cloning DB on a different server?

  DB version: 11.2.0.2, 10.2.0.5
  
  I want to create a clone of my Production DB in a test server. In the past, I have taken the backup hot of this DB production and restored and retrieved it in another server using simple RMAN commands.
  After restoring the control file, editing of the DB and catalogue items from backup on the test server, I run

  run {
  restore database ;
  recover database until time <time> ;
  alter database open resetlogs ;
  }

  In OTN, I ran into long discussions such as running
  RMAN duplicate database
  
  where they are trying to restore and recover using DOUBLE command, as shown below.

  run
   {
  duplicate target database to RBS
  nofilenamecheck
  pfile=/tmp/aux.ora;
   }
   

  They can't just use plain RMAN restore and retrieve orders I've done? What advantage have RMAN DUPLICATE on orders of Plains?

  RMAN DUPLICATE is designed to give the database clone a new name of the database and the new database identifier:

  >
  If you copy a database with the operating system instead of the command utilities DUPLICATE, then the DBID of the database copied remains identical to the original database. To register for the database of the copy in the same catalog of recovery with the original, you must change the DBID with utility DBNEWID (see the Oracle database utilities). On the other hand, the command DUPLICATE assigns the duplicate DBID different database so that it can be saved in the same catalog of recovery than the source database.

• Another issue duplicate RMAN - RAC database to single instance

  Hello
  
  I have a problem with RMAN duplicate procedure and hoped that someone can help you.
  
  I would like to create a duplicate of our data base RAC production on a separate and autonomous, database on another site server. This duplicate will be used to execute queries to another business unit that I don't want to have access to our database of intensive production.
  
  My procedure goes like this:
  
  1. create a (not ASM) disk based backup data files and recovery logs archived:
  
  'run {} '.
  allocate channel d1 type disk;
  backup format ' / u02/stage/df_t%t_s%s_p%p' database more entered archivelog delete;
  output channel d1;
  }"
  
  2 tar and scp those files to the same location on the standalone database server.
  
  3. in the meantime, work that's happened on the basis of data production and other archived redo logs have been generated. I don't really care about these papers for the purposes of the duplicate however, I just want to replicate to the point of the last backup. I have to do this, run the following SQL to determine the sequence number should I be duplicating up to:
  
  "Select max(sequence#) thread # v $ archived_log, whereas the deleted = 'YES' group by thread #;"
  
  4 duplicate the production to the stand-alone database database (SQL Net work orders).
  
  'run {} '.
  until the sequence (the value returned by the SQL statement above);
  duplicate target database xxx;
  }"
  
  However, my problem because I don't know how to handle the fact that he has two sons. I understand that each thread relates to one of the CARS, I don't know which one to specify the copy. We have a service of data that the client application connects through, and that the service runs on any of the bodies. I should just care about newspapers in the instance where the service is running?
  
  AM I even approach that this is the right way?
  
  I look forward to any help that people may be able to offer.
  
  Kind regards
  
  Phil

  1 9746 569095777 28 OCTOBER 09 569150229 28 OCTOBER 09
  1 9747 569150229 28 OCTOBER 09 569187892 28 OCTOBER 09
  1 9748 569187892 28 OCTOBER 09 569231956 28 OCTOBER 09
  1 9749 569231956 28 OCTOBER 09 569259816 28 OCTOBER 09
  2 7931 569095774 28 OCTOBER 09 569187902 28 OCTOBER 09
  2 7932 569187902 28 OCTOBER 09 569259814 28 OCTOBER 09

  You must use the VALUE until and specify the sequence with the next lowest change, or RMAN will search for the next log in this thread.

  for example, if you specify until the thread in the sequence 9750 1; RMAN will search journal 7933 on thread2 to catch the 1 wire SNA 569259816.
  Specify the set as a thread in 7933 2 sequence; and two copies must go ok!

  Published by: MrShh on October 29, 2009 14:35