In Regarding to Rman

Hi,
There is client requirement to confiquire rman on all development environments.
The prodcution and preproduction environment Rman confiquired by third party vendor and the team who are supporting production and preproduction are reluctant to share the setup document.
I have being supporting only the development environments.I am new to rman setup.
Now the requirement from third party,To perform cloning from prodcution to test environment, rman should be confiquired on all development environments. Can you please shed some light on how to enable/confiquire this on development environment.
With Regards,
Srini

Please refer to RMAN documentation for your database version.
Database Documentation
http://www.oracle.com/technetwork/indexes/documentation/index.html#database
For RMAN Cloning, please see old threads which discuss the same topic -- http://forums.oracle.com/forums/search.jspa?threadID=&q=RMAN+AND+Cloning&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Thanks,
Hussein

Similar Messages

  • RMAN Script & RMAN Configuration

    Dear All,
    This is the first time i am using RMAN. i just wanted to execute the following RMAN script for a testing purpose, for this what are the RMAN configuration i must have to do before executing this script below:
    RMAN> run {
    shutdown immediate;
    startup mount;
    backup database;
    alter database open;
    }This is my current setup of RMAN
    RMAN> show all;
    RMAN configuration parameters for database with db_unique_name DP are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'E:\RMAN\';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'E:\APP\10004\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFDP.ORA'; # defaultKindly advice me and give me a very clear study for this above parameters
    Regards
    HAMEED
    Once i execute that script i got this following error :
    +RMAN> run {+
    +2> shutdown immediate;+
    +3> startup mount;+
    +4> backup database;+
    +5> alter database open;+
    +6> };+
    database closed
    database dismounted
    Oracle instance shut down
    connected to target database (not started)
    Oracle instance started
    database mounted
    Total System Global Area     770019328 bytes
    Fixed Size                     1374780 bytes
    Variable Size                301991364 bytes
    Database Buffers             461373440 bytes
    Redo Buffers                   5279744 bytes
    Starting backup at 18-MAY-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=134 device type=DISK
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00006 name=E:\APP\10004\ORADATA\DP\HAMEED01.DBF
    input datafile file number=00007 name=E:\APP\10004\ORADATA\DP\ABDUL01.DBF
    input datafile file number=00008 name=E:\APP\10004\ORADATA\DP\TEST01.DBF
    input datafile file number=00001 name=E:\APP\10004\ORADATA\DP\SYSTEM01.DBF
    input datafile file number=00002 name=E:\APP\10004\ORADATA\DP\SYSAUX01.DBF
    input datafile file number=00005 name=E:\APP\10004\ORADATA\DP\EXAMPLE01.DBF
    input datafile file number=00003 name=E:\APP\10004\ORADATA\DP\UNDOTBS01.DBF
    input datafile file number=00004 name=E:\APP\10004\ORADATA\DP\USERS01.DBF
    channel ORA_DISK_1: starting piece 1 at 18-MAY-11
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/18/2011 17:22:30
    ORA-19504: failed to create file "E:\RMAN\"
    ORA-27038: created file already exists
    OSD-04010: <create> option specified, file already exists
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    Edited by: Hameed on May 18, 2011 4:59 AM

    Dear Chinar, can you please varify this below ,, is it correct,, after given your setup i ran this script,,,
    Kindly advice me
    Regards
    HAMEED
    RMAN> run
    2> {
    3> backup current controlfile;
    4> }
    Starting backup at 18-MAY-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=143 device type=DISK
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    channel ORA_DISK_1: starting piece 1 at 18-MAY-11
    channel ORA_DISK_1: finished piece 1 at 18-MAY-11
    piece handle=E:\RMAN\FULL_06MCLH66_1_1.BK tag=TAG20110518T180910 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    Finished backup at 18-MAY-11
    Starting Control File Autobackup at 18-MAY-11
    piece handle=E:\RMAN\CFC-796596855-20110518-00 comment=NONE
    Finished Control File Autobackup at 18-MAY-11Edited by: Hameed on May 18, 2011 5:55 AM

  • How to read RMAN data into an ORACLE Table?

    Hallo,
    With regards to RMAN, how should we store the data into a database table, from the commands which can run only on RMAN prompt without using Recovery Catalog?
    For Example:
    RMAN> Report need backup days 3;
    RMAN DATA:
    RMAN-03022: compiling command: report
    Report of files whose recovery needs more than 3 days of archived logs
    File Days Name
    1 1203 D:\ORACLE\ORADATA\TEST\SYSTEM01.DBF
    2 1203 D:\ORACLE\ORADATA\TEST\RBS01.DBF
    3 1203 D:\ORACLE\ORADATA\TEST\USERS01.DBF
    Should it done via UTL_FILE?
    If so, could someone give simple example/code how to do that, in order to write this RMAN data into an Oracle Database table?
    I also set the utl_file_dir parameter to a particular directory in my database.
    Thanks
    W.Benvort

    Actually, I am not using Recovery Catalog, so the views like RC_database, Rc_tablespaces etc , which are specific to recovery catalog are not available.
    r.- this make sense at 100% because those views belong to the recovery catalog.
    So, I wanted that these information, which we can get via using the commands like above, transfer into an Oracle table
    r.- If you want to access the views of the Recovery Catalog to store part of that information in tables you have to have the database registered in a Recovery Catalog.
    Should we keep the Recovery Catalog in Control file? Instead of using separate Schema.
    r.- I recommend you to create a catalog for your database because the space the controlfile to store information regarding RMAN is reused and you can lose important information about your backups.
    Can we run Catrman.sql script as a sys in order to keep the recovery catalog in sys schema?
    r.- As you know, this is not recommended at all.
    Conclusion : Create a Recovery Catalog and you will be able to perform all that you want regardind what you mentioned above.
    I have a thread for this:
    RMAN ( CATALOG CREATION ) STEP BY STEP by Joel Pérez
    Joel Pérez
    http://otn.oracle.com/experts

  • Problem with time based rman recovery

    Hi and happy boxing day:
    I am following by the letter the instructions in Sybex FundamentalsII book p.348 regarding an rman time based recovery. Here is the syntax:
    RMAN> run {
    2> allocate channel ch1 type disk;
    3> set until time 'DEC 26 2007 10:30:00';
    4> restore database;
    5> recover database;
    6> sql 'alter database open resetlogs';
    7> }
    and here is the error:
    allocated channel: ch1
    channel ch1: sid=11 devtype=DISK
    executing command: SET until clause
    released channel: ch1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of set command at 12/26/2007 11:06:45
    ORA-01858: a non-numeric character was found where a numeric was expected
    Is this a format issue? Any tips please!
    Thanks,
    DA

    You can only register a database once if you are using a recovery catalog, so whoever or whatever told you to re-register is simply getting their terminology in a knot!
    There **is** a sort-of "re-register" command which does sometimes need to be issued after a resetlogs: it's called a RESET command. See http://tinyurl.com/29t5lr for details. A "reset" is, effectively, a "re-register".
    One of the details you will see is that you only need to do a manual reset if it was **you** that issued a resetlogs, outside of RMAN. If you get RMAN to do the resetlogs, however, then there's no need to also issue the reset command, because RMAN already knows about it (and has already updated its own metadata accordingly).
    The other thing you'll notice from the documentation is that if you aren't using a recovery catalog then the concept of issuing a reset is entirely redundant. That's because you can't recover to a prior incarnation of the database without a catalog: it's one of the main reasons for wanting to run in catalog mode in the first place. No catalog = no ability to step through incarnations = no need to inform RMAN that you're in a new incarnation.

  • Rman Bkup

    Hi..
    I have a 2 node RAC DB , so how to take RMAN backup. Is it same as for 1 node Db.Writing backup archivelog all.. will it backup the archivelog from both the instance.
    Regards,
    Anand

    Anand,
    RMAN works in the same fashion whether you are in single instance or in RAC.In RAC, the nodes contain memory footprint differently , physical db is one only for which RMAN has to work.So there wont be any much difference with the RMAN and its backup methods. Please read the following for the RMAN backup over non clustered and clustered systems,
    http://download-east.oracle.com/docs/cd/B19306_01/rac.102/b14197/rmanops.htm#i474611
    HTH
    Aman....

  • Run RMAN using UTL_FILE

    Hi
    With regards to RMAN, Should we run the RMAN program via UTL_FILE .
    If so, please inform how to do that.
    Regards
    Kumar

    I think you are confused regarding what UTL_FILE does.
    UTL_FILE
    With the UTL_FILE package, your PL/SQL programs can read and write operating system text files. UTL_FILE provides a restricted version of operating system stream file I/O.
    UTL_FILE I/O capabilities are similar to standard operating system stream file I/O (OPEN, GET, PUT, CLOSE) capabilities, but with some limitations. For example, you call the FOPEN function to return a file handle, which you use in subsequent calls to GET_LINE or PUT to perform stream I/O to a file. When file I/O is done, you call FCLOSE to complete any output and free resources associated with the file.
    http://download-west.oracle.com/docs/cd/B10501_01/appdev.920/a96612/u_file.htm#ARPLS069
    Clarify better what you want to do please.
    Joel Pérez
    http://otn.oracle.com/experts

  • Cannot access RMAN

    all,
    I have cloned a database.
    The original database is under RMAN control and I can access the target as follows
    rman target username/password@db
    On the cloned database however when I try the same connection string I get the following errors
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04005: error from target database:
    ORA-01031: insufficient privileges
    Everything else about the database works, the application connects fine and has been running for the past 2 weeks.
    can anyone help
    regards
    Alan

    With rman target username/password you are connect via O/S authentication and with rman target username/password@db you are utilizing the password file. It appears that you added the user to the password file on the primary database, but never added him to the password file on the clone.

  • Implementation of Goldengate with RMAN

    hi,
    I just want to integrate the RMAN with Goldengate. just want to purge the trailfiles on source through RMAN.
    Any document or link You reffer.
    Regards,
    AMSII

    So, RMAN, being used for backup and recovery, is now supposed to be used to manage files in an entirely separate application? I don't think so.

  • RMAN Priviligies and Role to Create backups

    Hi everyone,
    I have some questions regarding RMAN backup options in my mind and want your help in their clarification.
    1) We want to taken backup of Database with RMAN and for that we want to create a new Database user to take the backup rather than sys user. For this what prives this users need other than connect, quota etc. What we want to do is that we want to ensure that this RMAN user can only take backups and nothing else. I've read in the documentation that in order to take backup through RMAN ; the RMAN users must have sysdba role. Is this necessary? Don't you think this can compromise the db security?
    Kindly note that currently we are using control file as RMAN repository so no need the discussion of Recovery catalog in our case.
    Regards,
    Kamran

    All RMAN database connections require SYSDBA privilege. So if you are using any other user other than SYS then you should grant it SYSDBA privilege.
    http://docs.oracle.com/cd/B19306_01/backup.102/b14192/setup003.htm#i1005954

  • RMAN-06085

    Hello!
    I try to restore database:
    set newname for datafile '/....dbf' to '/....dbf';
    set newname for datafile '/....dbf' to '/....dbf';
    restore database;
    switch datafile all;
    release channel ch00;
    }During restore of db I get next message:
    *11.2.0.3*
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 08-NOV-12
    released channel: ch00
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 11/08/2012 19:00:47
    RMAN-06085: must use SET NEWNAME command to restore datafile 1Thanks and regards,
    Pavel

    Hello;
    RMAN-06085 - A RESTORE command for the specified datafile could not find a destination name for the specified datafile.
    Example
    SET NEWNAME FOR DATAFILE 1 TO '/u01/app/oracle/oradata/RECLONE/system01.dbf';
    So it will create the datafile in the correct path.With a little dynamic SQL this is easy :
    set heading off
    set feedback off
    set pagesize 400
    select ' newname  for datafile ' || file#|| ' to ' || name from v$datafile;Make sure your file structure is setup too.
    Best Regards
    mseberg
    Edited by: mseberg on Nov 8, 2012 7:17 AM

  • Purpose of Retention Policy Recovery Window and Redundancy

    Hi,
    Good Evening,
    I have some queries regarding the RMAN Retention Policy Recovery Window and Redundancy.
    1. Any condition is there to set the Retention Policy Recovery Window and Redundancy and control_file_record_keep_time?What is the relationship between these 3 parameters?
    2. Explain the scenario if i set the control_file_record_keep_time=4 Redundancy=3 and Recovery Window=7?
    3. If i set the Redundancy=3 and Recovery Window=7 means my backup place only have 3 copies of backup based on the redundancy then what is the purpose of Recovery Window=7 please give some example.
    4. If i change the values for Recovery Window=3 and Redundancy=7 what will happened, how many days backup will be available in my FRA location?Explain with one scenario?
    Thanks in advance.
    Vijay.

    Hi,
    Take a look of the above doc contents:
    Configuring the Backup Retention Policy
    As explained in "Backup Retention Policies", the backup retention policy specifies which backups must be retained to meet your data recovery requirements. This policy can be based on a recovery window or redundancy. Use the CONFIGURE RETENTION POLICY command to specify the retention policy.
    so  you have option to choose either  recovery windows or redundancy based you can set the configuration like
    read in the Doc What it said for both:
    Recovery Window-Based Retention Policy ==>RMAN does not consider any full or level 0 incremental backup as obsolete if it falls within the recovery window.  Additionally, RMAN retains all archived logs and level 1 incremental backups that are needed to recover to a random point within the window.
    Redundancy-Based Retention Policy==>The REDUNDANCY parameter of the CONFIGURE RETENTION POLICY command specifies how many full or level 0 backups of each datafile and control file that RMAN should keep. If the number of full or level 0 backups for a specific datafile or control file exceeds the REDUNDANCY setting, then RMAN considers the extra backups as obsolete. The default retention policy is REDUNDANCY 1.
    RMAN> show RETENTION POLICY;
    using target database control file instead of recovery catalog
    RMAN configuration parameters for database with db_unique_name DDTEST are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    new RMAN configuration parameters are successfully stored
    RMAN> show RETENTION POLICY;
    RMAN configuration parameters for database with db_unique_name DDTEST are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters are successfully stored
    RMAN> show RETENTION POLICY;
    RMAN configuration parameters for database with db_unique_name DDTEST are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    CONTROL_FILE_RECORD_KEEP_TIME:This parameter applies only to records in the control file that are circularly reusable (such as archive log records and various backup records) ref Doc:CONTROL_FILE_RECORD_KEEP_TIME
    1. Any condition is there to set the Retention Policy Recovery Window and Redundancy and control_file_record_keep_time?What is the relationship between these 3 parameters?
    2. Explain the scenario if i set the control_file_record_keep_time=4 Redundancy=3 and Recovery Window=7?
    3. If i set the Redundancy=3 and Recovery Window=7 means my backup place only have 3 copies of backup based on the redundancy then what is the purpose of Recovery Window=7 please give some example.
    4. If i change the values for Recovery Window=3 and Redundancy=7 what will happened, how many days backup will be available in my FRA location?Explain with one scenario?
    so i believe you can get the Answer from Your Question from Above details.
    HTH

  • Doubt in export/import

    Hi All,
    I have oracle 9i database.
    i have a requirement from one of my user. He wants to restore 2 tables as of 31 dec 2010.
    initially i thought of using flashback_scn but seems like i cant use this in 9i
    can anyone please help how to find the last SCN for 31 dec 2010?
    Regards,
    Chris

    With Rman, duplicate database until scn and then imp/exp the tables.
    With imp/exp. Find the correct file and do a imp with it.
    If you do not have backups and the flashback is off then you can not do ithow to find out if flashback is turned on? show parameter flash ? i did this but couldnt find any parameter..i even tried db_recevoery_file_dest but still couldnt find.

  • Error handling when removing expired stuff

    8.1.7.1.0 on Sun...
    Trying to delete expired backups when, in fact, there aren't any expired backups does not return an error. And it shouldn't. This is correct.
    Trying to delete expired backup sets older than a specific date when there aren't any returns an error message. Why?
    Regards,
    per
    RMAN> delete expired backup of archivelog all ;
    RMAN-03022: compiling command: delete expired
    RMAN-03023: executing command: delete expired
    RMAN-03023: executing command: partial resync
    RMAN> delete expired backup of archivelog until time 'sysdate -14' ;
    RMAN-03022: compiling command: delete expired
    RMAN-03026: error recovery releasing channel resources
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: delete expired
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archivelog in the
    recovery catalog

    Thanks for responding.
    I suppose I could instruct an operator to disregard certain
    error messages. What4s more troublesome is that RMAN returns
    error status and that's really not the kind of help you want
    when trying to create shell scripts... :(
    I4d be interested to learn how others deal with this.
    rgds, per

  • Cannot restore some archivelog files?

    Dear all,
    It is very strange when I restore archivelog, it comes up lots of errors.
    I am not sure is it I shutdown database using abort command, so that I cannot restore some of the archive logs during recovery? If Yes, what can I do?
    Best Regards,
    Amy
    RMAN> restore archivelog all;
    Starting restore at 25-JUL-08
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 07/25/2008 19:47:58
    RMAN-06026: some targets not found - aborting restore
    RMAN-06025: no backup of log thread 1 seq 2762 scn 1968789551 found to restore
    RMAN-06025: no backup of log thread 1 seq 2761 scn 1968764174 found to restore
    RMAN-06025: no backup of log thread 1 seq 2760 scn 1968739033 found to restore
    RMAN-06025: no backup of log thread 1 seq 2759 scn 1968713720 found to restore
    RMAN-06025: no backup of log thread 1 seq 2758 scn 1968688635 found to restore
    RMAN-06025: no backup of log thread 1 seq 2757 scn 1968663371 found to restore
    RMAN-06025: no backup of log thread 1 seq 2756 scn 1968638155 found to restore
    RMAN-06025: no backup of log thread 1 seq 2755 scn 1968612857 found to restore
    RMAN-06025: no backup of log thread 1 seq 2754 scn 1968587680 found to restore
    RMAN-06025: no backup of log thread 1 seq 2753 scn 1968562338 found to restore
    RMAN-06025: no backup of log thread 1 seq 2752 scn 1968537004 found to restore
    RMAN-06025: no backup of log thread 1 seq 2751 scn 1968511599 found to restore
    RMAN-06025: no backup of log thread 1 seq 2750 scn 1968486469 found to restore
    RMAN-06025: no backup of log thread 1 seq 2749 scn 1968461266 found to restore
    RMAN-06025: no backup of log thread 1 seq 2748 scn 1968436092 found to restore
    RMAN-06025: no backup of log thread 1 seq 2747 scn 1968411162 found to restore
    RMAN-06025: no backup of log thread 1 seq 2746 scn 1968385930 found to restore
    RMAN-06025: no backup of log thread 1 seq 2745 scn 1968360528 found to restore
    RMAN-06025: no backup of log thread 1 seq 2744 scn 1968335221 found to restore
    RMAN-06025: no backup of log thread 1 seq 2743 scn 1968310054 found to restore
    RMAN-06025: no backup of log thread 1 seq 2742 scn 1968284858 found to restore
    RMAN-06025: no backup of log thread 1 seq 2741 scn 1968259554 found to restore
    RMAN-06025: no backup of log thread 1 seq 2740 scn 1968234484 found to restore
    RMAN-06025: no backup of log thread 1 seq 2739 scn 1968209320 found to restore
    RMAN-06025: no backup of log thread 1 seq 2738 scn 1968184044 found to restore
    RMAN-06025: no backup of log thread 1 seq 2737 scn 1968158741 found to restore
    RMAN-06025: no backup of log thread 1 seq 2736 scn 1968133666 found to restore
    RMAN-06025: no backup of log thread 1 seq 2735 scn 1968108336 found to restore
    RMAN-06025: no backup of log thread 1 seq 2734 scn 1968083209 found to restore
    RMAN-06025: no backup of log thread 1 seq 2732 scn 1968034276 found to restore
    RMAN-06025: no backup of log thread 1 seq 2731 scn 1968009957 found to restore
    RMAN-06025: no backup of log thread 1 seq 2730 scn 1967985969 found to restore
    RMAN-06025: no backup of log thread 1 seq 2729 scn 1967964167 found to restore
    RMAN-06025: no backup of log thread 1 seq 2728 scn 1967939600 found to restore
    RMAN-06025: no backup of log thread 1 seq 2727 scn 1967916916 found to restore
    RMAN-06025: no backup of log thread 1 seq 2726 scn 1967891727 found to restore
    RMAN-06025: no backup of log thread 1 seq 2725 scn 1967866502 found to restore
    RMAN-06025: no backup of log thread 1 seq 2724 scn 1967854121 found to restore
    RMAN-06025: no backup of log thread 1 seq 2723 scn 1967828623 found to restore
    RMAN-06025: no backup of log thread 1 seq 2722 scn 1967803608 found to restore
    RMAN-06025: no backup of log thread 1 seq 2721 scn 1967778602 found to restore
    RMAN-06025: no backup of log thread 1 seq 2720 scn 1967753508 found to restore
    RMAN-06025: no backup of log thread 1 seq 2719 scn 1967728518 found to restore
    RMAN-06025: no backup of log thread 1 seq 2718 scn 1967703771 found to restore
    RMAN-06025: no backup of log thread 1 seq 2717 scn 1967678560 found to restore
    RMAN-06025: no backup of log thread 1 seq 2716 scn 1967653108 found to restore
    RMAN-06025: no backup of log thread 1 seq 2715 scn 1967628050 found to restore
    RMAN-06025: no backup of log thread 1 seq 2714 scn 1967602962 found to restore
    RMAN-06025: no backup of log thread 1 seq 2713 scn 1967578073 found to restore
    RMAN-06025: no backup of log thread 1 seq 2712 scn 1967552804 found to restore
    RMAN-06025: no backup of log thread 1 seq 2711 scn 1967527631 found to restore
    RMAN-06025: no backup of log thread 1 seq 2710 scn 1967502597 found to restore
    RMAN-06025: no backup of log thread 1 seq 2709 scn 1967477554 found to restore
    RMAN-06025: no backup of log thread 1 seq 2708 scn 1967452498 found to restore
    RMAN-06025: no backup of log thread 1 seq 2707 scn 1967427443 found to restore
    RMAN-06025: no backup of log thread 1 seq 2706 scn 1967402206 found to restore
    RMAN-06025: no backup of log thread 1 seq 2705 scn 1967376951 found to restore
    RMAN-06025: no backup of log thread 1 seq 2704 scn 1967351794 found to restore
    RMAN-06025: no backup of log thread 1 seq 2703 scn 1967326458 found to restore
    MAN-0

    I am crystal clear from the very begining ,you are misleading this thread to increase yours post and nothing else.
    OP is restoring only archive logs and for that it need all archive logs including the archive for the current redo log file. So for that we need "alter system archive log current;".
    Yours this illusion is abrupt and without any proof.As you think that before backing up "alter system archivelog current" will be helpful in restoring all the OP's below archived log.Its a fun...
    RMAN-06025: no backup of log thread 1 seq 2762 scn 1968789551 found to restore
    RMAN-06025: no backup of log thread 1 seq 2761 scn 1968764174 found to restore
    RMAN-06025: no backup of log thread 1 seq 2760 scn 1968739033 found to restore
    RMAN-06025: no backup of log thread 1 seq 2759 scn 1968713720 found to restore
    RMAN-06025: no backup of log thread 1 seq 2758 scn 1968688635 found to restore
    RMAN-06025: no backup of log thread 1 seq 2757 scn 1968663371 found to restore
    RMAN-06025: no backup of log thread 1 seq 2756 scn 1968638155 found to restore
    RMAN-06025: no backup of log thread 1 seq 2755 scn 1968612857 found to restore
    RMAN-06025: no backup of log thread 1 seq 2754 scn 1968587680 found to restore
    RMAN-06025: no backup of log thread 1 seq 2753 scn 1968562338 found to restore
    RMAN-06025: no backup of log thread 1 seq 2752 scn 1968537004 found to restore
    RMAN-06025: no backup of log thread 1 seq 2751 scn 1968511599 found to restore
    RMAN-06025: no backup of log thread 1 seq 2750 scn 1968486469 found to restore
    RMAN-06025: no backup of log thread 1 seq 2749 scn 1968461266 found to restore
    RMAN-06025: no backup of log thread 1 seq 2748 scn 1968436092 found to restore
    RMAN-06025: no backup of log thread 1 seq 2747 scn 1968411162 found to restore
    RMAN-06025: no backup of log thread 1 seq 2746 scn 1968385930 found to restore
    RMAN-06025: no backup of log thread 1 seq 2745 scn 1968360528 found to restore
    RMAN-06025: no backup of log thread 1 seq 2744 scn 1968335221 found to restore
    RMAN-06025: no backup of log thread 1 seq 2743 scn 1968310054 found to restore
    RMAN-06025: no backup of log thread 1 seq 2742 scn 1968284858 found to restore
    RMAN-06025: no backup of log thread 1 seq 2741 scn 1968259554 found to restore
    RMAN-06025: no backup of log thread 1 seq 2740 scn 1968234484 found to restore
    RMAN-06025: no backup of log thread 1 seq 2739 scn 1968209320 found to restore
    RMAN-06025: no backup of log thread 1 seq 2738 scn 1968184044 found to restore
    RMAN-06025: no backup of log thread 1 seq 2737 scn 1968158741 found to restore
    RMAN-06025: no backup of log thread 1 seq 2736 scn 1968133666 found to restore
    RMAN-06025: no backup of log thread 1 seq 2735 scn 1968108336 found to restore
    RMAN-06025: no backup of log thread 1 seq 2734 scn 1968083209 found to restore
    RMAN-06025: no backup of log thread 1 seq 2732 scn 1968034276 found to restore
    RMAN-06025: no backup of log thread 1 seq 2731 scn 1968009957 found to restore
    RMAN-06025: no backup of log thread 1 seq 2730 scn 1967985969 found to restore
    RMAN-06025: no backup of log thread 1 seq 2729 scn 1967964167 found to restore
    RMAN-06025: no backup of log thread 1 seq 2728 scn 1967939600 found to restore
    RMAN-06025: no backup of log thread 1 seq 2727 scn 1967916916 found to restore
    RMAN-06025: no backup of log thread 1 seq 2726 scn 1967891727 found to restore
    RMAN-06025: no backup of log thread 1 seq 2725 scn 1967866502 found to restore
    RMAN-06025: no backup of log thread 1 seq 2724 scn 1967854121 found to restore
    RMAN-06025: no backup of log thread 1 seq 2723 scn 1967828623 found to restore
    RMAN-06025: no backup of log thread 1 seq 2722 scn 1967803608 found to restore
    RMAN-06025: no backup of log thread 1 seq 2721 scn 1967778602 found to restore
    RMAN-06025: no backup of log thread 1 seq 2720 scn 1967753508 found to restore
    RMAN-06025: no backup of log thread 1 seq 2719 scn 1967728518 found to restore
    RMAN-06025: no backup of log thread 1 seq 2718 scn 1967703771 found to restore
    RMAN-06025: no backup of log thread 1 seq 2717 scn 1967678560 found to restore
    RMAN-06025: no backup of log thread 1 seq 2716 scn 1967653108 found to restore
    RMAN-06025: no backup of log thread 1 seq 2715 scn 1967628050 found to restore
    RMAN-06025: no backup of log thread 1 seq 2714 scn 1967602962 found to restore
    RMAN-06025: no backup of log thread 1 seq 2713 scn 1967578073 found to restore
    RMAN-06025: no backup of log thread 1 seq 2712 scn 1967552804 found to restore
    RMAN-06025: no backup of log thread 1 seq 2711 scn 1967527631 found to restore
    RMAN-06025: no backup of log thread 1 seq 2710 scn 1967502597 found to restore
    RMAN-06025: no backup of log thread 1 seq 2709 scn 1967477554 found to restore
    RMAN-06025: no backup of log thread 1 seq 2708 scn 1967452498 found to restore
    RMAN-06025: no backup of log thread 1 seq 2707 scn 1967427443 found to restore
    RMAN-06025: no backup of log thread 1 seq 2706 scn 1967402206 found to restore
    RMAN-06025: no backup of log thread 1 seq 2705 scn 1967376951 found to restore
    RMAN-06025: no backup of log thread 1 seq 2704 scn 1967351794 found to restore
    RMAN-06025: no backup of log thread 1 seq 2703 scn 1967326458 found to restore
    MAN-0 Khurram

  • Configuring a physical standby database in 9i

    Hi all,
       SO: Solaris 10 SPARC x64
       DB: 9.2.0.6 x64
       I have a task of creating a physical standby database in a solaris 10 - Oracle 9.2.0.6 env. I am used to do this configuration on the 11.2 version of Oracle, and because of that i have some doubts regarding the possible different configurations necessary to do in a 9i Database.
       1) The main doubt that i have is regarding the RMAN use. I Would like to know if it is possible to restore a normal backup of my primary database into the standby database, and after that, apply the necessary archived logs to sync the standby with the primary? The controlfile that i would use would be the one created by the  "BACKUP CURRENT CONTROLFILE FOR STANDBY" RMAN command. The RMAN script woulb be like the one below:
    run {
    allocate channel ch01 device type disk;
    allocate channel ch02 device type disk;
    allocate channel ch03 device type disk;
    allocate channel ch04 device type disk;
    restore controlfile from 'standby_controlfile.ctl';
    sql 'alter database mount';
    restore database;
    recover database;
       2) The directory structure will be the same, so i think it is not necessary to use the SET NEWNAME and the DB_FILE_NAME_CONVERT/LOG_FILE_NAME_CONVERT, is that correct?
       3) Do you have any other considerations regarting the differences between a 9i and a 11g Physical Standby Configuration?
    Thanks for your attention and pacience.

    Hello;
    On question 1 - See this:
    http://docs.oracle.com/cd/B10500_01/server.920/a96566/rcmstand.htm
    On question 2 - Assuming RMAN work then DB_FILE_NAME_CONVERT/LOG_FILE_NAME_CONVERT would NOT have to be set for the same directory structure.
    On question 3 - double check this:
    http://docs.oracle.com/cd/B10500_01/server.920/a96653.pdf
    Best Regards
    mseberg

Maybe you are looking for