Installing recovery catalog!!

hello,
can anybody tell that how to install recovery
catalog on oracle8i?

Hi,
Here is the procedure for creating RMAN catalog:
Installing RMAN Catalog:
Install the recovery catalog schema in a different database (say RCAT) from the target database you will be backing up.
Assume the following for the examples below:
User SYS with password CHANGE_ON_INSTALL has SYSDBA privileges on the recovery catalog database RCAT.
There is a tablespace called CATTBS on the recovery catalog database RCAT that stores the recovery catalog.
There is a tablespace called TEMP in the recovery catalog database.
To set up the recovery catalog schema:
Start SQL*Plus and then connect with administrator privileges to the database containing the recovery catalog (RCAT). For example, enter:
SQL> CONNECT sys/change_on_install@rcat
Create a log file that you can use to check for errors. For example, enter:
SQL> SPOOL create_rman.log
Create a user and schema for the recovery catalog. For example, enter:
SQL> CREATE USER rman IDENTIFIED BY rman
2> TEMPORARY TABLESPACE temp
3> DEFAULT TABLESPACE cattbs
4> QUOTA UNLIMITED ON cattbs;
Grant the RECOVERY_CATALOG_OWNER role to the schema owner. This role provides the user with privileges to maintain and query the recovery catalog.
SQL> GRANT recovery_catalog_owner TO rman;
Grant other desired privileges to the RMAN user.
SQL> GRANT connect, resource TO rman;
Host out to the operating system to check the create_rman.log file for any errors before continuing. For example, a UNIX user can issue:
SQL> host
% vi create_rman.log
To create the recovery catalog:
Connect to the database that will contain the catalog as the catalog owner. For example, from the operating system command line enter:
% rman catalog rman/rman@rcat
You can also connect from the RMAN prompt:
% rman
RMAN> connect catalog rman/rman@rcat
Issue the create catalog command to create the catalog, specifying the CATTBS tablespace:
RMAN> create catalog tablespace cattbs;
Note that the creation of the catalog can take several minutes.
Host out to the operating system to check the create_rman.log file for any errors before continuing. For example, a UNIX user can issue:
RMAN> host;
% vi create_rman.log
Optionally, query the recovery catalog to see which tables were created:
SQL> SELECT table_name FROM user_tables;
Note: Database name, SYS password, tablespace names are for examples only. You can name change them.
You all set!!!! Good luck.
-Rama
null

Similar Messages

  • Error installing recovery catalog

    Hi,
    Inorder to implement RMAN in oracle 10g in windows environment I created a separate table space for rman and created a user as rman1;
    then I issued the following commands :
    GRANT connect, resource, recovery_catalog_owner TO rman1
    grant create session to rman1;
    grant create type to rman1;
    then i entered into rman from dos prompt,
    rman catalog=rman1/rman1@tc
    from rman prompt I issued the command,
    create catalog tablespace RMAN1;
    then the following error occurs,
    RMAN> create catalog tablespace RMAN1;
    ORACLE error from recovery catalog database: ORA-01031: insufficient privileges
    RMAN-00571: ====================
    RMAN-00569: ===== ERROR MESSAGE STACK FOLLOWS ===========
    RMAN-00571: ====================================
    RMAN-06433: error installing recovery catalog
    Due to this error I am unable to proceed further and let me know the solution.
    Thanks in advance.
    Regards,
    A.Mohammed Rafi.

    Hi,
    Thanks for the help and the problem is solved.
    Now I am facing another problem,
    RMAN-03009: failure of catalog command on default channel
    ORA-19657: cannot inspect current datafile D:\ORACLE\PRODUCT\10.1.0\DB_2\TC\EXAMPLE01.DBF
    Could you please help me in this regard.

  • How to install Recovery Catalog

    Hi:
    How to install the recovery catalog? I used the following commands from the menu and it didn't work:
    connect rman/rman
    @?/rdbms/admin/catrman
    There is no catrman.sql exists.
    Thank you very much.

    If you are using Oracle8i, make sure your compatibility is set to at least 8.1.0 and you are connected to the catalog database. Then type create catalog; at the RMAN command line.

  • Connecting rman and creating recovery catalog

    I'm using oracle8i with Window/Nt
    i have two database U10 and U20.
    Using recovery manager, target db is U10 and recovery catalog of U10 is saved in U20.
    i followed method in oracle8i manual(Rman Part)
    when i attempt to connect rman, following message bothers me..
    C:\WINDOWS>RMAN CATALOG RMAN/RMAN@U20
    Recovery Manager: Release 8.1.6.0.0 - Production
    RMAN-06008: connected to recovery catalog database
    RMAN-06428: recovery catalog is not installed
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-06004: ORACLE error from recovery catalog database: ORA-02112: PCC: SELECT.
    .INTO returns too many rows
    RMAN-06097: text of failing SQL statement: select user into :b1 from dual
    RMAN-06099: error occurred in source file: krmk.pc, line: 3842
    and when i attempt to create recovery catalog, i got a bunch of message
    RMAN> CREATE CATALOG TABLESPACE "RCVCAT"
    RMAN-06099: error occurred in source file: krmk.pc, line: 6549
    RMAN-06097: text of failing SQL statement: CREATE TABLE db
    db_key NUMBER NOT NULL, -- sequence generated primary key
    db_id NUMBER NOT NULL, -- kccfhdbi from controlfile
    -- updatable columns
    curr_dbinc_key NUMBER, -- current incarnation
    CONSTRAINT db_p PRIMARY KEY (db_key),
    CONSTRAINT db_u1 UNIQUE(db_id) -- ensure that db_id is unique
    tablespace "RCVCAT"
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-06433: error installing recovery catalog
    i'm so hectic... plz help me....

    Based on the following errors:
    RMAN-06004: ORACLE error from recovery catalog database: ORA-02112: PCC: SELECT..INTO returns too many rows
    RMAN-06097: text of failing SQL statement: select user into :b1 from dual
    It looks like the table dual has more than 1 row.
    select * from dual;
    What do you get?
    It should look like this:
    D
    X
    1 row selected.
    Your recovery catalog database may have a problem. You may need to start over and recreate the recovery catalog.
    null

  • How to install the Recovery Catalog

    Hi:
    How to install the recovery catalog? I used the following commands from the menu and it didn't work:
    connect rman/rman
    @?/rdbms/admin/catrman
    There is no catrman.sql exists.
    Thank you very much.

    If you are using Oracle8i, make sure your compatibility is set to at least 8.1.0 and you are connected to the catalog database. Then type create catalog; at the RMAN command line.

  • RMAN-06428 recovery catalog is not installed

    RDBMS Version: 8.1.6
    Operating System and Version: sun sparc 5.8
    Error : RMAN-06428 RMAN-06428 recovery catalog is not installed
    Product (i.e. SQL*Loader, Import, etc.): RMAN
    Product Version: 8.1.6
    Hi,
    I hv a database running in unix box 1 (say 'FAST')
    and Im trying to install a recovery catalog database in unix box
    2
    (Rcat)
    1) in unixbox2..I hv created a new database, and I hv created a
    tablespace rcvcat and user rman .granted catalog_recovery_owner
    to rman.
    also I hv created a catalogue using this command
    create catalogue tablespace rcvcat;
    (no error logs generated)
    2)now when I try to connect to the catalogue I am getting an
    error
    what I did is, I tried connecting to rman of target database
    (FAST database)
    % rman target /catalog rman/rman@rcat
    Recovery Manager: Release 8.1.6.0.0 - Production
    RMAN-06005: connected to target database: FAST (DBID=3819569154)
    RMAN-06008: connected to recovery catalog database
    RMAN-06428: recovery catalog is not installed
    also I tried like this,
    % rman target system/manager@fast catalog rman/rman@rcat
    Recovery Manager: Release 8.1.6.0.0 - Production
    RMAN-06005: connected to target database: FAST (DBID=3819569154)
    RMAN-06008: connected to recovery catalog database
    RMAN-06428: recovery catalog is not installed
    I dont understand why it says recovery catalog not installed ,
    when I hv created one in rcat database.
    Can anyone help me how to connect to catalog and register my
    database (I mean from which machine I need to run the commands)
    Thanks
    Venkat

    You do have a problem. It seems your "Shift" key is stuck.
    Anyway, please read: [ID 188682.1],
    Have a nice day.

  • Best tactic to migrate recovery catalog

    #Recovery Catalog
    Oracle9i 9.2.0.1.0
    Windows 2003 Server - 32 bit
    Our recovery catalog is an old one, we will upgrade this to 11g, but we will need to make a new server for him as well.
    Correct me if i am wrong but one way should be just to create a new server, install oracle and database, and re-connect all recovery catalog users to this one, and make new backups on them to get information about backup in the new catalog.
    However, should'nt it be possible to export the data from old recovery catalog , to new recovery catalog?
    Please guide me to the best tactic
    Regards,

    migrate catalog from 9i to 10g
    Read the link.
    Regards
    Asif Kabir

  • Config recovery catalog database

    dear all.
    i had read several documents about "create recovery catalog", but all of that start with statement
    CREATE TABLESPACE
    ...and continue with CREATE USER, etc.
    I want to create a NEW database for recovery catalog, this database what characteristics must to have ?? Anyone have a link or document where explain me how to create a database (only i need database creation) for recovery catalog.???
    thanks
    The version is ORacle 10gr2

    hi,
    the recovery catalog is just a normal database with a schema called rman or whatever you choose.
    it should ideally be on a separate server to your target database. The RMAN database as with any other database should have multiplexed control files and redo files.
    schema creation assumming windows O/S
    -- Create tablepsace to hold repository
    CREATE TABLESPACE "RMAN"
    DATAFILE 'C:\ORACLE\ORADATA\W2K1\RMAN01.DBF' SIZE 6208K REUSE
    AUTOEXTEND ON NEXT 64K MAXSIZE 32767M
    EXTENT MANAGEMENT LOCAL
    SEGMENT SPACE MANAGEMENT AUTO;
    -- Create rman schema owner
    CREATE USER rman IDENTIFIED BY rman
    TEMPORARY TABLESPACE temp
    DEFAULT TABLESPACE rman
    QUOTA UNLIMITED ON rman;
    GRANT connect, resource, recovery_catalog_owner TO rman;
    then create the recovery catalog
    C:>rman catalog=rman/rman@w2k1
    Recovery Manager: Release 9.2.0.1.0 - Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    connected to recovery catalog database
    recovery catalog is not installed
    RMAN> create catalog tablespace "RMAN";
    recovery catalog created
    RMAN> exit
    Recovery Manager complete.
    C:>
    then register your database
    C:>rman catalog=rman/rman@w2k1 target=sys/password@w2k2
    Recovery Manager: Release 9.2.0.1.0 - Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    connected to target database: W2K2 (DBID=1371963417)
    connected to recovery catalog database
    RMAN> register database;
    database registered in recovery catalog
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    let us know how you get on.
    rgds
    alan

  • Create a recovery catalog by using the Enterprise Manager Console

    Dear Sirs:
    I am using the Oracle9i database release 2. After installing the management server and running the Enterprise Manager Configuration Assistant, there was no recovery catalog and no CATTBS tablespace created. According to the Help and to your documentation entitled “Oracle Enterprise Manager Configuratrion Guide” this recovery catalog and CATTBS tablespace should be created automatically.
    Of course I am not running any target database on the same machine.
    How can I create a recovery catalog by using the Enterprise Manager Console, and not by using the rman command prompt?
    Please its urgent and I need an answer as soon as possible.
    Thank you in advance with best regards

    Dear Sir:
    Thank you very much for your reply, but unfortunately it didn’t help me. This article is repeating what is mentioned in the Help and the documents that I downloaded earlier. As I said earlier I know how to setup the recovery catalog by using the rman command prompt, but I couldn’t do it by using the Oracle Enterprise Manager Console. By using the wizards it is supposed to be created automatically but nothing of this happened.
    Please I need help urgently.

  • Recovery Catalog showing wrong Archive Destination

    Hi All,
    I am using Oracle 10g on Solaris 10.
    The problem I am facing is this, while taking backup using recover catalog..............
    Starting backup at 27-JUL-11
    current log archived
    released channel: ch00
    released channel: ch01
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 07/27/2011 11:16:47
    RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
    ORA-19625: error identifying file /u01/oracle/product/10.2.0/db_1/dbs/arch1_56_757089402.dbf
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    This is because of the following reason
    RMAN> list archivelog all;
    List of Archived Log Copies
    Key Thrd Seq S Low Time Name
    39401 1 1567 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1567_756523261.dbf
    39402 1 1568 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1568_756523261.dbf
    39403 1 1569 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1569_756523261.dbf
    39404 1 1570 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1570_756523261.dbf
    39405 1 1571 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1571_756523261.dbf
    39406 1 1572 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1572_756523261.dbf
    39407 1 1573 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1573_756523261.dbf
    39408 1 1574 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1574_756523261.dbf
    39409 1 1575 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1575_756523261.dbf
    39410 1 1576 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1576_756523261.dbf
    39411 1 1577 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1577_756523261.dbf
    39412 1 1578 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1578_756523261.dbf
    39413 1 1579 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1579_756523261.dbf
    39414 1 1580 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1580_756523261.dbf
    39415 1 1581 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1581_756523261.dbf
    39416 1 1582 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1582_756523261.dbf
    39417 1 1583 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1583_756523261.dbf
    39418 1 1584 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1584_756523261.dbf
    39419 1 1585 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1585_756523261.dbf
    39420 1 1586 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1586_756523261.dbf
    39421 1 1587 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1587_756523261.dbf
    39422 1 1588 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1588_756523261.dbf
    39423 1 1589 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1589_756523261.dbf
    39424 1 1590 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1590_756523261.dbf
    39425 1 1591 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1591_756523261.dbf
    39426 1 1592 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1592_756523261.dbf
    39427 1 1593 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1593_756523261.dbf
    39428 1 1594 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1594_756523261.dbf
    39429 1 1595 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1595_756523261.dbf
    39430 1 1596 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1596_756523261.dbf
    39431 1 1597 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1597_756523261.dbf
    39432 1 1598 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1598_756523261.dbf
    39433 1 1599 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1599_756523261.dbf
    39434 1 1600 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1600_756523261.dbf
    39435 1 1601 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1601_756523261.dbf
    39436 1 1602 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1602_756523261.dbf
    39437 1 1603 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1603_756523261.dbf
    39438 1 1604 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1604_756523261.dbf
    39439 1 1605 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1605_756523261.dbf
    39440 1 1606 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1606_756523261.dbf
    39441 1 1607 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1607_756523261.dbf
    39442 1 1608 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1608_756523261.dbf
    39443 1 1609 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1609_756523261.dbf
    39444 1 1610 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1610_756523261.dbf
    39445 1 1611 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1611_756523261.dbf
    39446 1 1612 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1612_756523261.dbf
    39447 1 1613 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1613_756523261.dbf
    39448 1 1614 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1614_756523261.dbf
    39449 1 1615 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1615_756523261.dbf
    39450 1 1616 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1616_756523261.dbf
    39451 1 1617 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1617_756523261.dbf
    39452 1 1618 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1618_756523261.dbf
    39453 1 1619 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1619_756523261.dbf
    39454 1 1620 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1620_756523261.dbf
    39455 1 1621 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1621_756523261.dbf
    39456 1 1622 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1622_756523261.dbf
    39457 1 1623 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1623_756523261.dbf
    39458 1 1624 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1624_756523261.dbf
    39459 1 1625 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1625_756523261.dbf
    39460 1 1626 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1626_756523261.dbf
    39461 1 1627 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1627_756523261.dbf
    39462 1 1628 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1628_756523261.dbf
    39463 1 1629 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1629_756523261.dbf
    39464 1 1630 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1630_756523261.dbf
    39465 1 1631 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1631_756523261.dbf
    39466 1 1632 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1632_756523261.dbf
    39467 1 1633 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1633_756523261.dbf
    39468 1 1634 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1634_756523261.dbf
    39469 1 1635 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1635_756523261.dbf
    39470 1 1636 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1636_756523261.dbf
    39471 1 1637 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1637_756523261.dbf
    39682 1 1638 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1638_756523261.dbf
    39689 1 1639 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1639_756523261.dbf
    40642 1 1640 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1640_756523261.dbf
    40643 1 1641 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1641_756523261.dbf
    40644 1 1642 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1642_756523261.dbf
    40645 1 1643 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1643_756523261.dbf
    40646 1 1644 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1644_756523261.dbf
    40647 1 1645 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1645_756523261.dbf
    40648 1 1646 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1646_756523261.dbf
    41310 1 1647 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1647_756523261.dbf
    41317 1 1648 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1648_756523261.dbf
    41373 1 1649 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1649_756523261.dbf
    41374 1 1650 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1650_756523261.dbf
    41375 1 1651 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1651_756523261.dbf
    41383 1 1652 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1652_756523261.dbf
    *38725 1 56 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_56_757089402.dbf*
    *38946 1 57 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_57_757089402.dbf*
    *39000 1 58 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_58_757089402.dbf*
    *39022 1 59 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_59_757089402.dbf*
    *39243 1 60 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_60_757089402.dbf*
    *39297 1 61 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_61_757089402.dbf*
    *39703 1 62 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_62_757089402.dbf*
    *39704 1 63 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_63_757089402.dbf*
    *39705 1 64 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_64_757089402.dbf*
    *39933 1 65 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_65_757089402.dbf*
    *39991 1 66 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_66_757089402.dbf*
    *40023 1 67 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_67_757089402.dbf*
    *40024 1 68 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_68_757089402.dbf*
    *40025 1 69 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_69_757089402.dbf*
    *40254 1 70 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_70_757089402.dbf*
    *40308 1 71 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_71_757089402.dbf*
    *40345 1 72 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_72_757089402.dbf*
    *40570 1 73 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_73_757089402.dbf*
    *41329 1 74 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_74_757089402.dbf*
    I dont know from where recovery catalog is getting the information in bold.
    I have crosschecked and deleted archives and resynced the catalog several times. Immediatly after doing that the backup works fine, but the other day its the same thing all over again.
    Can some one tell me from where the catalog is getting this wrong infomation about archivelogs???
    By the way here is some more info about my target Database:
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /oradb2/Archive/HCSPRD91
    Oldest online log sequence 1651
    Next log sequence to archive 1653
    Current log sequence 1653
    NAME TYPE VALUE
    archive_lag_target integer 0
    log_archive_config string
    log_archive_dest string
    log_archive_dest_1 string LOCATION=/oradb2/Archive/HCSPR
    D91
    log_archive_dest_10 string
    log_archive_dest_2 string
    log_archive_dest_3 string
    log_archive_dest_4 string
    log_archive_dest_5 string
    log_archive_dest_6 string
    NAME TYPE VALUE
    log_archive_dest_7 string
    log_archive_dest_8 string
    log_archive_dest_9 string
    log_archive_dest_state_1 string enable
    log_archive_dest_state_10 string enable
    log_archive_dest_state_2 string enable
    log_archive_dest_state_3 string enable
    log_archive_dest_state_4 string enable
    log_archive_dest_state_5 string enable
    log_archive_dest_state_6 string enable
    log_archive_dest_state_7 string enable
    NAME TYPE VALUE
    log_archive_dest_state_8 string enable
    log_archive_dest_state_9 string enable
    log_archive_duplex_dest string
    log_archive_format string %t_%s_%r.dbf
    log_archive_local_first boolean TRUE
    log_archive_max_processes integer 2
    log_archive_min_succeed_dest integer 1
    log_archive_start boolean FALSE
    log_archive_trace integer 0
    remote_archive_enable string true
    standby_archive_dest string ?/dbs/arch
    Regards .....

    Do you have any other DBs with the same DBID as the one you are backing up? Are they connect to the same RMAN catalog?
    Iordan Iotzov
    http://iiotzov.wordpress.com/

  • RMAN-06004:ORACLE error from recovery catalog ... ORA-00904: : invalid ...

    Good Morning All,
    One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
    ==================================================================================================
    Starting backup at 12/30/2008 22:03:47
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 12/30/2008 22:03:47
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
    2>
    3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
    4>
    5> # check if database can be restored
    6> # RESTORE DATABASE VALIDATE;
    7>
    8> # check if controlfile can be restored
    9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
    10>
    11> # check if archivelogs for the past two weeks can be restored
    12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
    13>
    14> # - Verify all backups on backup media are intact
    15> # CROSSCHECK BACKUP OF DATABASE;
    16>
    17> # - Display a list of files that need to be backed up based on the retention
    18> # policy. For this case study, files that don't have at least 1 backups
    19> # will be reported.
    20> REPORT NEED BACKUP;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 7 days
    Report of files whose recovery needs more than 7 days of archived logs
    File Days Name
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of report command at 12/30/2008 22:03:48
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> # - delete un-necessary backups. This command deletes backups based on the
    2> # retention policy.
    3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
    4> #########DELETE OBSOLETE;
    5>
    6> # - get complete list of existing backups
    7> LIST BACKUP;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of list command at 12/30/2008 22:03:49
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> #-end of file-
    2> **end-of-file**
    RMAN>
    Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AM

    This Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
    ====================================================================================================
    Recovery Manager: Release 9.2.0.6.0 - 64bit Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    RMAN>
    connected to recovery catalog database
    RMAN>
    connected to target database: CUSTPR (DBID=525071053)
    RMAN>
    RMAN> #########################################################################
    2> # LEVEL 0 BACKUP #
    3> #########################################################################
    4>
    5> # Configure backups to be written to disk.
    6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    old RMAN configuration parameters:
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    new RMAN configuration parameters:
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
    2> # RMAN retains all backups needed to recover the database to any point in time
    3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
    4> # backups that are no longer required by the retention policy. To exclude a
    5> # backup from consideration by the policy, you can use KEEP option with the
    6> # BACKUP command.
    7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
    2> # maintenance operations.
    3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    old RMAN configuration parameters:
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    new RMAN configuration parameters:
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to write disk backups to the /backup directory.
    2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
    3> # backup set number, and %p with the backup piece number.
    4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    old RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    new RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to back up the control file after each backup.
    2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
    2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
    2> # RMAN won't backup an archivelog or datafile if there already exists a backup
    3> # of that file. The FORCE option can be used to override optimization on a
    4> # specific BACKUP command.
    5> CONFIGURE BACKUP OPTIMIZATION ON;
    old RMAN configuration parameters:
    CONFIGURE BACKUP OPTIMIZATION ON;
    new RMAN configuration parameters:
    CONFIGURE BACKUP OPTIMIZATION ON;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Use the SHOW ALL command to see the current configuration settings.
    2> SHOW ALL ;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
    RMAN>
    RMAN> # The following commands are run each day to start the backup cycle.
    2> # The steps are:
    3> # - Take an incremental level 0 backup of the database. A level 0 backup is
    4> # a complete backup of the entire file which can be used as the basis
    5> # for a subsequent incremental backup.
    6> # - Backup all archivelogs that have not already been backed up.
    7> # - Delete on-disk archivelogs older than seven days.
    8>
    9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
    10> DATABASE maxsetsize 33G
    11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
    12> delete all input;
    Starting backup at 12/30/2008 22:01:40
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=11 devtype=DISK
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
    input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
    input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
    input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
    input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
    input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
    input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
    channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
    channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
    piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
    archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
    archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
    archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
    archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
    archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
    archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
    Finished backup at 12/30/2008 22:03:47
    Starting backup at 12/30/2008 22:03:47
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 12/30/2008 22:03:47
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
    2>
    3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
    4>
    5> # check if database can be restored
    6> # RESTORE DATABASE VALIDATE;
    7>
    8> # check if controlfile can be restored
    9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
    10>
    11> # check if archivelogs for the past two weeks can be restored
    12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
    13>
    14> # - Verify all backups on backup media are intact
    15> # CROSSCHECK BACKUP OF DATABASE;
    16>
    17> # - Display a list of files that need to be backed up based on the retention
    18> # policy. For this case study, files that don't have at least 1 backups
    19> # will be reported.
    20> REPORT NEED BACKUP;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 7 days
    Report of files whose recovery needs more than 7 days of archived logs
    File Days Name
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of report command at 12/30/2008 22:03:48
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> # - delete un-necessary backups. This command deletes backups based on the
    2> # retention policy.
    3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
    4> #########DELETE OBSOLETE;
    5>
    6> # - get complete list of existing backups
    7> LIST BACKUP;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of list command at 12/30/2008 22:03:49
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> #-end of file-
    2> **end-of-file**
    RMAN>
    Recovery Manager complete.

  • What's the recommended guideline on backing up a recovery catalog?

    while I understand "Benefits of Using the Recovery Catalog as the RMAN Repository" as stated in
    http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmquick.htm#442214
    as well as things to take note if using control file as the sole rman repository,
    as stated in "Monitoring the Overwriting of Control File Records" in http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmrepos.htm#446924
    I do not understand why in Backup and Recovery Advanced User's Guide
    http://download.oracle.com/docs/cd/B14117_01/server.101/b10734/rcmrepos.htm
    "Back Up the Recovery Catalog Often"
    Even if you have to restore the recovery catalog database using a control file autobackup, you can then use the full record of backups in your restored recovery catalog database to restore the target database without using a control file autobackup for the target database.
    =>probably implies that we can use another recovery catalog let's call it backupbackup to restore the recovery catalog
    "Choosing the Appropriate Method for Physical Backups"
    Follow these guidelines when developing an RMAN backup strategy for the recovery catalog database:
    * Run the recovery catalog database in ARCHIVELOG mode so that you can do point-in-time recovery if needed.
    * Set the retention policy to a REDUNDANCY value greater than 1.
    * Back up the database onto two separate media (for example, disk and tape).
    * Run BACKUP DATABASE PLUS ARCHIVELOG at regular intervals, to a media manager if available, or just to disk.
    * Do not use another recovery catalog as the repository for the backups.=> this contradicts the previous statement
    * Configure the control file autobackup feature to ON.
    so may I know what's the recommended guideline on backing up a recovery catalog? should we use another recovery catalog to keep the rman repositories of the the main primary catalog or just use a control file autobackup feature?
    thanks

    I understand the question and the confusion.
    Please note, however, that this forum is for discussing problems and errors with the documentation in general. Your question is related to a specific product and is, as far as I can tell, not a note about a documentation error or a correction.
    The appropriate place to discuss this is the Database (General) forum or - perhaps surprisingly - the RMAN forum. These can both be found by
    1) Clicking on the 'Forum Home' link at the top of this page;
    2) Scrolling down to the category 'Database' (a category is identified by a special row format that does not list the number of topics)
    3) Expanding the category by clicking on the 'More ...' link.
    4) Scrolling down to the "Database - General" or "Recovery Manager" forum and clicking on it's link.
    Note that forums have a search function that may be used to find answers if someone has already asked a similar question.

  • Problem while installing REcovery ..

    Hello , Please i need your Help As soon As possible and thanks Inadvance
    my Laptop type : Hp Envy dv7 Notebook pc
    there is REcovery partition on the laptop with the C partion .. i shrinked Anew partion from the C partion .. so C: become 100 gb and 30 gb for the Recovery and the rest 530 i guss i make new partion ..
    i i tried to install recovery to back the laptop for factory settings . but it get Error .. when i do the steps shown in support for how to make recovery there is missing choose .. when i search in programs for hp recovery manger and i choose to install the recovery lapy turned off then i press troubleshoot .. i didnt find REcovery manger .. i just see :
    refresh your pc ..
    reset your pc
    advanced options
    and when it try to make reset pc or any .. it say the system cann't fid the file specified (0x80070002)
    and when i choose another one . . it say the partion where the windows install is Locked .. Unlock it and Try again ..
    i deleted the partion i did and now the spaace is unlocated .. and i try again the same thing ,,
    when i tried to active the partition through run .. diskpart
    select patition 0
    list partition
    select partion 4 (the number appeared near C)
    when i select it and type Active
    it get Error say :  the Selected disk is not afixed MBR disk ,,
    the ACTIVE comman can only be used on fixed MBR disks..
    and reset bios for factory setting F10 then f 9
    i hope you help me to make my lappy back as i just get from Factory .. please Help me on this ..

    Changing the partitioning of the hdd usually breaks the Recovery function. That is why you should always burn your Recovery DVD set or create USB Flash Recovery before making any changes.
    If you did not make a Recovery set, you will need to contact HP Support to order Recovery Media. Worldwide contact info can be accessed here>>Contact HP
    ******Clicking the Thumbs-Up button is a way to say -Thanks!.******
    **Click Accept as Solution on a Reply that solves your issue to help others**

  • Oracle 10g express edition recovery catalog

    whether oracle 10g express edition spoort recovery catalog?

    Yes you can; the answer is in the manual.
    >
    In general, the rules of RMAN compatibility are as follows:
    <li>You can create 8.X or 9.X RMAN catalog schema in any Oracle database release 8.1.X (or higher) and Release 10g RMAN catalog schema in any Oracle database release 9.0.1 (or higher).</li>
    <li>The recovery catalog schema version must be greater than or equal to the RMAN client version.</li>
    <li>Ideally, the versions of the RMAN client and the target database should be the same (although there are other legal combinations, listed in Table B-1).</li>
    <li>While backing up a Release 10g database using the 9.X RMAN client, you cannot include a controlfile that was created using compatible=10.0.0 in a datafile backupset. The workaround is to turn controlfile autobackup ON.</li>
    >
    http://download.oracle.com/docs/cd/B12037_01/server.101/b10770/compat.htm
    http://download.oracle.com/docs/cd/B25329_01/doc/admin.102/b25107/backrest.htm#i1004902
    XE questions are best answered here {forum:id=251}
    Regards,
    Phiri
    Edited by: phiri on 02-Apr-2010 01:36

  • Oracle 10.2.0.4 RMAN Duplicate without a Recovery Catalog

    Production Backups are Tuesday - Sunday at 22:00:
    RUN {
    ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
    CROSSCHECK ARCHIVELOG ALL;
    CROSSCHECK BACKUP;
    DELETE NOPROMPT COPY OF ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE-2';
    DELETE NOPROMPT BACKUP;
    BACKUP DATABASE PLUS ARCHIVELOG;
    CROSSCHECK BACKUP;
    RELEASE CHANNEL c1;
    LIST BACKUPSET;
    EOF
    I have these files sent over to the development server on Wednesday, RMANbackup (log), backupset and the controlfile:
    rcp -rp /backup/$1/flash_recovery/$2/RMANbackup/* kacdb4:/backup/common/flash_recovery/$2/RMANbackup
    rcp -rp /backup/$1/flash_recovery/$2/backupset/* kacdb4:/backup/common/flash_recovery/$2/backupset
    rcp -rp /backup/$1/flash_recovery/$2/controlfile/* kacdb4:/backup/common/flash_recovery/$2/controlfile
    I run the RMAN Duplicate and the database gets created with no problems!
    The question is: If I wait unit Thursday, to run the duplicate script, I get the traditional RMAN errors: RMAN-03002, RMAN-03015, RMAN-06026, RMAN-06023:
    Starting restore at 20-SEP-12
    released channel: aux1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/20/2012 10:05:36
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 6 found to restore
    RMAN-06023: no backup or copy of datafile 5 found to restore
    RMAN-06023: no backup or copy of datafile 4 found to restore
    RMAN-06023: no backup or copy of datafile 3 found to restore
    RMAN-06023: no backup or copy of datafile 2 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restore
    Recovery Manager complete.
    Is this because of the 'SYSDATE-2' in the RMAN runlist? Does RMAN connect back to the target and it does not find the logs, because they've been deleted, it aborts the duplicate? I've shipped over the backupset and controlfile of the scn I'm using in the duplicate runlist all is there? If I'm trying to cleanup the archive area, would'nt 'delete expired archivelog all' in my runlist, be better than using the 'SYSDATE-2'?
    Or is it because of this database parameter:
    control_file_record_keep_time= 7, should I set this to say 14?
    Is it one of these RMAN configurations:
    Retention Policy to Redundancy 1, should I set this to say 7?
    Datafile Backup Copies for Device Type Disk to 1, to say 3, this takes up disk space which is precious
    Archivelog Backup Copies for Device Type Disk to 1, to say 3, this takes up disk space too
    Archive deletion policy to none change this to the other option?
    I've tested this a few times now, and always fails if the dupicate is not done the next day.
    If I have to create a development database on a Friday from Tuesday's copy FROM TAPE, I will get the error, because the files are no longer on disk.
    What can I do to ensure that I can create an RMAN duplicate any day of the week from Tuesday to Sunday?
    Look forward to your answer.
    Please let me know if I left any details out that you may need.
    Sincerely,
    Elizabeth Burns

    Hi Valentin,
    Here is the good duplicate log from Monday 9/24:
    oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs-> more clone_database_from_common_20120924.log
    SQL*Plus: Release 10.2.0.4.0 - Production on Mon Sep 24 18:07:32 2012
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    Connected.
    SQL> spool /u01/app/oracle/KAC_SCRIPTS/dupdb/logs/DBShutdown.log
    SQL> shutdown immediate
    ORA-01507: database not mounted
    ORACLE instance shut down.
    SQL> spool off
    SQL> exit;
    Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
    SQL*Plus: Release 10.2.0.4.0 - Production on Mon Sep 24 18:07:41 2012
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    Connected to an idle instance.
    File created.
    ORACLE instance started.
    Total System Global Area 134217728 bytes
    Fixed Size 2054448 bytes
    Variable Size 79693520 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 2138112 bytes
    Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
    Recovery Manager: Release 10.2.0.4.0 - Production on Mon Sep 24 18:07:43 2012
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    connected to target database: KEDSP (DBID=3370721566)
    connected to auxiliary database: DUPDB (not mounted)
    RMAN> RUN
    2> {
    3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
    4>
    5> set until scn 211054288;
    6> DUPLICATE TARGET DATABASE TO dupdb
    7> PFILE=/u01/app/oracle/product/10.2.0/db_1/dbs/initdupdb.ora
    8> DB_FILE_NAME_CONVERT=('/usr/local/OLlinks/kedsp/system/','/usr/local/OLlinks/dupdb/system/','/usr/local/OLlinks/kedsp/temp/','/us
    r/local/OLlinks/dupdb/temp/','/usr/local/OLlinks/kedsp/data01/','/usr/local/OLlinks/dupdb/data01/','/usr/local/OLlinks/kedsp/index01
    /','/usr/
    9> local/OLlinks/dupdb/index01/')
    10> LOGFILE
    11> GROUP 1 (
    12> '/usr/local/OLlinks/dupdb/redo01/redo0101.log',
    13> '/usr/local/OLlinks/dupdb/redo02/redo0102.log',
    14> '/usr/local/OLlinks/dupdb/redo03/redo0103.log'
    15> ) SIZE 50M,
    16> GROUP 2 (
    17> '/usr/local/OLlinks/dupdb/redo01/redo0201.log',
    18> '/usr/local/OLlinks/dupdb/redo02/redo0202.log',
    19> '/usr/local/OLlinks/dupdb/redo03/redo0203.log'
    20> ) SIZE 50M,
    21> GROUP 3 (
    22> '/usr/local/OLlinks/dupdb/redo01/redo0301.log',
    23> '/usr/local/OLlinks/dupdb/redo02/redo0302.log',
    24> '/usr/local/OLlinks/dupdb/redo03/redo0303.log'
    25> ) SIZE 50M,
    26> GROUP 4 (
    27> '/usr/local/OLlinks/dupdb/redo01/redo0401.log',
    28> '/usr/local/OLlinks/dupdb/redo02/redo0402.log',
    29> '/usr/local/OLlinks/dupdb/redo03/redo0403.log'
    30> ) SIZE 50M,
    31> GROUP 5 (
    32> '/usr/local/OLlinks/dupdb/redo01/redo0501.log',
    33> '/usr/local/OLlinks/dupdb/redo02/redo0502.log',
    34> '/usr/local/OLlinks/dupdb/redo03/redo0503.log'
    35> ) SIZE 50M,
    36> GROUP 6 (
    37> '/usr/local/OLlinks/dupdb/redo01/redo0601.log',
    38> '/usr/local/OLlinks/dupdb/redo02/redo0602.log',
    39> '/usr/local/OLlinks/dupdb/redo03/redo0603.log'
    40> ) SIZE 50M,
    41> GROUP 7 (
    42> '/usr/local/OLlinks/dupdb/redo01/redo0701.log',
    43> '/usr/local/OLlinks/dupdb/redo02/redo0702.log',
    44> '/usr/local/OLlinks/dupdb/redo03/redo0703.log'
    45> ) SIZE 50M,
    46> GROUP 8 (
    47> '/usr/local/OLlinks/dupdb/redo01/redo0801.log',
    48> '/usr/local/OLlinks/dupdb/redo02/redo0802.log',
    49> '/usr/local/OLlinks/dupdb/redo03/redo0803.log'
    50> ) SIZE 50M,
    51> GROUP 9 (
    52> '/usr/local/OLlinks/dupdb/redo01/redo0901.log',
    53> '/usr/local/OLlinks/dupdb/redo02/redo0902.log',
    54> '/usr/local/OLlinks/dupdb/redo03/redo0903.log'
    55> ) SIZE 50M,
    56> GROUP 10 (
    57> '/usr/local/OLlinks/dupdb/redo01/redo1001.log',
    58> '/usr/local/OLlinks/dupdb/redo02/redo1002.log',
    59> '/usr/local/OLlinks/dupdb/redo03/redo1003.log'
    60> ) SIZE 50M
    61> ;
    62> }
    63>
    using target database control file instead of recovery catalog
    allocated channel: aux1
    channel aux1: sid=242 devtype=DISK
    executing command: SET until clause
    Starting Duplicate Db at 24-SEP-12
    contents of Memory Script:
    set until scn 211054288;
    set newname for datafile 1 to
    "/usr/local/OLlinks/dupdb/system/system01.dbf";
    set newname for datafile 2 to
    "/usr/local/OLlinks/dupdb/system/undotbs01.dbf";
    set newname for datafile 3 to
    "/usr/local/OLlinks/dupdb/system/sysaux01.dbf";
    set newname for datafile 4 to
    "/usr/local/OLlinks/dupdb/system/users01.dbf";
    set newname for datafile 5 to
    "/usr/local/OLlinks/dupdb/data01/data1.dbf";
    set newname for datafile 6 to
    "/usr/local/OLlinks/dupdb/index01/index1.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
    Starting restore at 24-SEP-12
    channel aux1: starting datafile backupset restore
    channel aux1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /usr/local/OLlinks/dupdb/system/system01.dbf
    restoring datafile 00002 to /usr/local/OLlinks/dupdb/system/undotbs01.dbf
    restoring datafile 00003 to /usr/local/OLlinks/dupdb/system/sysaux01.dbf
    restoring datafile 00004 to /usr/local/OLlinks/dupdb/system/users01.dbf
    restoring datafile 00005 to /usr/local/OLlinks/dupdb/data01/data1.dbf
    restoring datafile 00006 to /usr/local/OLlinks/dupdb/index01/index1.dbf
    channel aux1: reading from backup piece /usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_nnndf_TAG20120924T1
    01837_860txxs8_.bkp
    channel aux1: restored backup piece 1
    piece handle=/usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_nnndf_TAG20120924T101837_860txxs8_.bkp tag=TAG
    20120924T101837
    channel aux1: restore complete, elapsed time: 00:00:47
    Finished restore at 24-SEP-12
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUPDB" RESETLOGS ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 584
    LOGFILE
    GROUP 1 ( '/usr/local/OLlinks/dupdb/redo01/redo0101.log', '/usr/local/OLlinks/dupdb/redo02/redo0102.log', '/usr/local/OLlinks/dup
    db/redo03/redo0103.log' ) SIZE 50 M ,
    GROUP 2 ( '/usr/local/OLlinks/dupdb/redo01/redo0201.log', '/usr/local/OLlinks/dupdb/redo02/redo0202.log', '/usr/local/OLlinks/dup
    db/redo03/redo0203.log' ) SIZE 50 M ,
    GROUP 3 ( '/usr/local/OLlinks/dupdb/redo01/redo0301.log', '/usr/local/OLlinks/dupdb/redo02/redo0302.log', '/usr/local/OLlinks/dup
    db/redo03/redo0303.log' ) SIZE 50 M ,
    GROUP 4 ( '/usr/local/OLlinks/dupdb/redo01/redo0401.log', '/usr/local/OLlinks/dupdb/redo02/redo0402.log', '/usr/local/OLlinks/dup
    db/redo03/redo0403.log' ) SIZE 50 M ,
    GROUP 5 ( '/usr/local/OLlinks/dupdb/redo01/redo0501.log', '/usr/local/OLlinks/dupdb/redo02/redo0502.log', '/usr/local/OLlinks/dup
    db/redo03/redo0503.log' ) SIZE 50 M ,
    GROUP 6 ( '/usr/local/OLlinks/dupdb/redo01/redo0601.log', '/usr/local/OLlinks/dupdb/redo02/redo0602.log', '/usr/local/OLlinks/dup
    db/redo03/redo0603.log' ) SIZE 50 M ,
    GROUP 7 ( '/usr/local/OLlinks/dupdb/redo01/redo0701.log', '/usr/local/OLlinks/dupdb/redo02/redo0702.log', '/usr/local/OLlinks/dup
    db/redo03/redo0703.log' ) SIZE 50 M ,
    GROUP 8 ( '/usr/local/OLlinks/dupdb/redo01/redo0801.log', '/usr/local/OLlinks/dupdb/redo02/redo0802.log', '/usr/local/OLlinks/dup
    db/redo03/redo0803.log' ) SIZE 50 M ,
    GROUP 9 ( '/usr/local/OLlinks/dupdb/redo01/redo0901.log', '/usr/local/OLlinks/dupdb/redo02/redo0902.log', '/usr/local/OLlinks/dup
    db/redo03/redo0903.log' ) SIZE 50 M ,
    GROUP 10 ( '/usr/local/OLlinks/dupdb/redo01/redo1001.log', '/usr/local/OLlinks/dupdb/redo02/redo1002.log', '/usr/local/OLlinks/dup
    db/redo03/redo1003.log' ) SIZE 50 M
    DATAFILE
    '/usr/local/OLlinks/dupdb/system/system01.dbf'
    CHARACTER SET WE8ISO8859P1
    contents of Memory Script:
    switch clone datafile all;
    executing Memory Script
    datafile 2 switched to datafile copy
    input datafile copy recid=1 stamp=794858918 filename=/usr/local/OLlinks/dupdb/system/undotbs01.dbf
    datafile 3 switched to datafile copy
    input datafile copy recid=2 stamp=794858918 filename=/usr/local/OLlinks/dupdb/system/sysaux01.dbf
    datafile 4 switched to datafile copy
    input datafile copy recid=3 stamp=794858918 filename=/usr/local/OLlinks/dupdb/system/users01.dbf
    datafile 5 switched to datafile copy
    input datafile copy recid=4 stamp=794858918 filename=/usr/local/OLlinks/dupdb/data01/data1.dbf
    datafile 6 switched to datafile copy
    input datafile copy recid=5 stamp=794858918 filename=/usr/local/OLlinks/dupdb/index01/index1.dbf
    contents of Memory Script:
    set until scn 211054288;
    recover
    clone database
    delete archivelog
    executing Memory Script
    executing command: SET until clause
    Starting recover at 24-SEP-12
    starting media recovery
    channel aux1: starting archive log restore to default destination
    channel aux1: restoring archive log
    archive log thread=1 sequence=1403
    channel aux1: reading from backup piece /usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_annnn_TAG20120924T1
    01923_860tzfd7_.bkp
    channel aux1: restored backup piece 1
    piece handle=/usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_annnn_TAG20120924T101923_860tzfd7_.bkp tag=TAG
    20120924T101923
    channel aux1: restore complete, elapsed time: 00:00:05
    archive log filename=/usr/local/OLlinks/dupdb/flash_recovery/DUPDB/archivelog/2012_09_24/o1_mf_1_1403_861phcc3_.arc thread=1 sequenc
    e=1403
    channel clone_default: deleting archive log(s)
    archive log filename=/usr/local/OLlinks/dupdb/flash_recovery/DUPDB/archivelog/2012_09_24/o1_mf_1_1403_861phcc3_.arc recid=1 stamp=79
    4858923
    media recovery complete, elapsed time: 00:00:02
    Finished recover at 24-SEP-12
    contents of Memory Script:
    shutdown clone;
    startup clone nomount pfile= '/u01/app/oracle/product/10.2.0/db_1/dbs/initdupdb.ora';
    executing Memory Script
    database dismounted
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area 134217728 bytes
    Fixed Size 2054448 bytes
    Variable Size 79693520 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 2138112 bytes
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUPDB" RESETLOGS ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 584
    LOGFILE
    GROUP 1 ( '/usr/local/OLlinks/dupdb/redo01/redo0101.log', '/usr/local/OLlinks/dupdb/redo02/redo0102.log', '/usr/local/OLlinks/dup
    db/redo03/redo0103.log' ) SIZE 50 M ,
    GROUP 2 ( '/usr/local/OLlinks/dupdb/redo01/redo0201.log', '/usr/local/OLlinks/dupdb/redo02/redo0202.log', '/usr/local/OLlinks/dup
    db/redo03/redo0203.log' ) SIZE 50 M ,
    GROUP 3 ( '/usr/local/OLlinks/dupdb/redo01/redo0301.log', '/usr/local/OLlinks/dupdb/redo02/redo0302.log', '/usr/local/OLlinks/dup
    db/redo03/redo0303.log' ) SIZE 50 M ,
    GROUP 4 ( '/usr/local/OLlinks/dupdb/redo01/redo0401.log', '/usr/local/OLlinks/dupdb/redo02/redo0402.log', '/usr/local/OLlinks/dup
    db/redo03/redo0403.log' ) SIZE 50 M ,
    GROUP 5 ( '/usr/local/OLlinks/dupdb/redo01/redo0501.log', '/usr/local/OLlinks/dupdb/redo02/redo0502.log', '/usr/local/OLlinks/dup
    db/redo03/redo0503.log' ) SIZE 50 M ,
    GROUP 6 ( '/usr/local/OLlinks/dupdb/redo01/redo0601.log', '/usr/local/OLlinks/dupdb/redo02/redo0602.log', '/usr/local/OLlinks/dup
    db/redo03/redo0603.log' ) SIZE 50 M ,
    GROUP 7 ( '/usr/local/OLlinks/dupdb/redo01/redo0701.log', '/usr/local/OLlinks/dupdb/redo02/redo0702.log', '/usr/local/OLlinks/dup
    db/redo03/redo0703.log' ) SIZE 50 M ,
    GROUP 8 ( '/usr/local/OLlinks/dupdb/redo01/redo0801.log', '/usr/local/OLlinks/dupdb/redo02/redo0802.log', '/usr/local/OLlinks/dup
    db/redo03/redo0803.log' ) SIZE 50 M ,
    GROUP 9 ( '/usr/local/OLlinks/dupdb/redo01/redo0901.log', '/usr/local/OLlinks/dupdb/redo02/redo0902.log', '/usr/local/OLlinks/dup
    db/redo03/redo0903.log' ) SIZE 50 M ,
    GROUP 10 ( '/usr/local/OLlinks/dupdb/redo01/redo1001.log', '/usr/local/OLlinks/dupdb/redo02/redo1002.log', '/usr/local/OLlinks/dup
    db/redo03/redo1003.log' ) SIZE 50 M
    DATAFILE
    '/usr/local/OLlinks/dupdb/system/system01.dbf'
    CHARACTER SET WE8ISO8859P1
    contents of Memory Script:
    set newname for tempfile 1 to
    "/usr/local/OLlinks/dupdb/temp/temp01.dbf";
    switch clone tempfile all;
    catalog clone datafilecopy "/usr/local/OLlinks/dupdb/system/undotbs01.dbf";
    catalog clone datafilecopy "/usr/local/OLlinks/dupdb/system/sysaux01.dbf";
    catalog clone datafilecopy "/usr/local/OLlinks/dupdb/system/users01.dbf";
    catalog clone datafilecopy "/usr/local/OLlinks/dupdb/data01/data1.dbf";
    catalog clone datafilecopy "/usr/local/OLlinks/dupdb/index01/index1.dbf";
    switch clone datafile all;
    executing Memory Script
    executing command: SET NEWNAME
    renamed temporary file 1 to /usr/local/OLlinks/dupdb/temp/temp01.dbf in control file
    cataloged datafile copy
    datafile copy filename=/usr/local/OLlinks/dupdb/system/undotbs01.dbf recid=1 stamp=794858932
    cataloged datafile copy
    datafile copy filename=/usr/local/OLlinks/dupdb/system/sysaux01.dbf recid=2 stamp=794858932
    cataloged datafile copy
    datafile copy filename=/usr/local/OLlinks/dupdb/system/users01.dbf recid=3 stamp=794858932
    cataloged datafile copy
    datafile copy filename=/usr/local/OLlinks/dupdb/data01/data1.dbf recid=4 stamp=794858932
    cataloged datafile copy
    datafile copy filename=/usr/local/OLlinks/dupdb/index01/index1.dbf recid=5 stamp=794858932
    datafile 2 switched to datafile copy
    input datafile copy recid=1 stamp=794858932 filename=/usr/local/OLlinks/dupdb/system/undotbs01.dbf
    datafile 3 switched to datafile copy
    input datafile copy recid=2 stamp=794858932 filename=/usr/local/OLlinks/dupdb/system/sysaux01.dbf
    datafile 4 switched to datafile copy
    input datafile copy recid=3 stamp=794858932 filename=/usr/local/OLlinks/dupdb/system/users01.dbf
    datafile 5 switched to datafile copy
    input datafile copy recid=4 stamp=794858932 filename=/usr/local/OLlinks/dupdb/data01/data1.dbf
    datafile 6 switched to datafile copy
    input datafile copy recid=5 stamp=794858932 filename=/usr/local/OLlinks/dupdb/index01/index1.dbf
    contents of Memory Script:
    Alter clone database open resetlogs;
    executing Memory Script
    database opened
    Finished Duplicate Db at 24-SEP-12
    Recovery Manager complete.
    SQL*Plus: Release 10.2.0.4.0 - Production on Mon Sep 24 18:09:39 2012
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    Connected.
    User altered.
    User altered.
    User altered.
    User altered.
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    ORACLE instance started.
    Total System Global Area 134217728 bytes
    Fixed Size 2054448 bytes
    Variable Size 79693520 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 2138112 bytes
    Database mounted.
    Database altered.
    Database altered.
    Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
    oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs->
    Here is the duplicate log from this morning:
    oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs-> more clone_database_from_common_20120926.log
    SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:31 2012
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    Connected.
    SQL> spool /u01/app/oracle/KAC_SCRIPTS/dupdb/logs/DBShutdown.log
    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> spool off
    SQL> exit;
    Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
    SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:42 2012
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    Connected to an idle instance.
    File created.
    ORACLE instance started.
    Total System Global Area 134217728 bytes
    Fixed Size 2054448 bytes
    Variable Size 79693520 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 2138112 bytes
    Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
    Recovery Manager: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:45 2012
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    connected to target database: KEDSP (DBID=3370721566)
    connected to auxiliary database: DUPDB (not mounted)
    RMAN> RUN
    2> {
    3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
    4>
    5> set until scn 211054288;
    6> DUPLICATE TARGET DATABASE TO dupdb
    7> PFILE=/u01/app/oracle/product/10.2.0/db_1/dbs/initdupdb.ora
    8> DB_FILE_NAME_CONVERT=('/usr/local/OLlinks/kedsp/system/','/usr/local/OLlinks/dupdb/system/','/usr/local/OLlinks/kedsp/temp/','/us
    r/local/OLlinks/dupdb/temp/','/usr/local/OLlinks/kedsp/data01/','/usr/local/OLlinks/dupdb/data01/','/usr/local/OLlinks/kedsp/index01
    /','/usr/
    9> local/OLlinks/dupdb/index01/')
    10> LOGFILE
    11> GROUP 1 (
    12> '/usr/local/OLlinks/dupdb/redo01/redo0101.log',
    13> '/usr/local/OLlinks/dupdb/redo02/redo0102.log',
    14> '/usr/local/OLlinks/dupdb/redo03/redo0103.log'
    15> ) SIZE 50M,
    16> GROUP 2 (
    17> '/usr/local/OLlinks/dupdb/redo01/redo0201.log',
    18> '/usr/local/OLlinks/dupdb/redo02/redo0202.log',
    19> '/usr/local/OLlinks/dupdb/redo03/redo0203.log'
    20> ) SIZE 50M,
    21> GROUP 3 (
    22> '/usr/local/OLlinks/dupdb/redo01/redo0301.log',
    23> '/usr/local/OLlinks/dupdb/redo02/redo0302.log',
    24> '/usr/local/OLlinks/dupdb/redo03/redo0303.log'
    25> ) SIZE 50M,
    26> GROUP 4 (
    27> '/usr/local/OLlinks/dupdb/redo01/redo0401.log',
    28> '/usr/local/OLlinks/dupdb/redo02/redo0402.log',
    29> '/usr/local/OLlinks/dupdb/redo03/redo0403.log'
    30> ) SIZE 50M,
    31> GROUP 5 (
    32> '/usr/local/OLlinks/dupdb/redo01/redo0501.log',
    33> '/usr/local/OLlinks/dupdb/redo02/redo0502.log',
    34> '/usr/local/OLlinks/dupdb/redo03/redo0503.log'
    35> ) SIZE 50M,
    36> GROUP 6 (
    37> '/usr/local/OLlinks/dupdb/redo01/redo0601.log',
    38> '/usr/local/OLlinks/dupdb/redo02/redo0602.log',
    39> '/usr/local/OLlinks/dupdb/redo03/redo0603.log'
    40> ) SIZE 50M,
    41> GROUP 7 (
    42> '/usr/local/OLlinks/dupdb/redo01/redo0701.log',
    43> '/usr/local/OLlinks/dupdb/redo02/redo0702.log',
    44> '/usr/local/OLlinks/dupdb/redo03/redo0703.log'
    45> ) SIZE 50M,
    46> GROUP 8 (
    47> '/usr/local/OLlinks/dupdb/redo01/redo0801.log',
    48> '/usr/local/OLlinks/dupdb/redo02/redo0802.log',
    49> '/usr/local/OLlinks/dupdb/redo03/redo0803.log'
    50> ) SIZE 50M,
    51> GROUP 9 (
    52> '/usr/local/OLlinks/dupdb/redo01/redo0901.log',
    53> '/usr/local/OLlinks/dupdb/redo02/redo0902.log',
    54> '/usr/local/OLlinks/dupdb/redo03/redo0903.log'
    55> ) SIZE 50M,
    56> GROUP 10 (
    57> '/usr/local/OLlinks/dupdb/redo01/redo1001.log',
    58> '/usr/local/OLlinks/dupdb/redo02/redo1002.log',
    59> '/usr/local/OLlinks/dupdb/redo03/redo1003.log'
    60> ) SIZE 50M
    61> ;
    62> }
    63>
    using target database control file instead of recovery catalog
    allocated channel: aux1
    channel aux1: sid=242 devtype=DISK
    executing command: SET until clause
    Starting Duplicate Db at 26-SEP-12
    contents of Memory Script:
    set until scn 211054288;
    set newname for datafile 1 to
    "/usr/local/OLlinks/dupdb/system/system01.dbf";
    set newname for datafile 2 to
    "/usr/local/OLlinks/dupdb/system/undotbs01.dbf";
    set newname for datafile 3 to
    "/usr/local/OLlinks/dupdb/system/sysaux01.dbf";
    set newname for datafile 4 to
    "/usr/local/OLlinks/dupdb/system/users01.dbf";
    set newname for datafile 5 to
    "/usr/local/OLlinks/dupdb/data01/data1.dbf";
    set newname for datafile 6 to
    "/usr/local/OLlinks/dupdb/index01/index1.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
    Starting restore at 26-SEP-12
    released channel: aux1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/26/2012 08:28:53
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 6 found to restore
    RMAN-06023: no backup or copy of datafile 5 found to restore
    RMAN-06023: no backup or copy of datafile 4 found to restore
    RMAN-06023: no backup or copy of datafile 3 found to restore
    RMAN-06023: no backup or copy of datafile 2 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restore
    Recovery Manager complete.
    SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:53 2012
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    Connected.
    alter user sys identified by "Sco_tch!1"
    ERROR at line 1:
    ORA-01109: database not open
    alter user system identified by "Sco_tch!1"
    ERROR at line 1:
    ORA-01109: database not open
    alter user dbsnmp identified by "Sco_tch!1"
    ERROR at line 1:
    ORA-01109: database not open
    alter user sysman identified by "Sco_tch!1"
    ERROR at line 1:
    ORA-01109: database not open
    ORA-01507: database not mounted
    ORACLE instance shut down.
    ORACLE instance started.
    Total System Global Area 134217728 bytes
    Fixed Size 2054448 bytes
    Variable Size 79693520 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 2138112 bytes
    ORA-00205: error in identifying control file, check alert log for more info
    alter database noarchivelog
    ERROR at line 1:
    ORA-01507: database not mounted
    alter database open
    ERROR at line 1:
    ORA-01507: database not mounted
    Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
    oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs->
    Please let me know if you need anything else.
    Sincerely,
    Elizabeth

Maybe you are looking for

  • Deleting photo's from iphone

    How can I delete photos on my phone from photo stream and/or camera roll without having to do it one by one from my iphone? I have hundreds of photo's that I have transferred onto my computer and I really need to free up some space on my phone. All t

  • [SOLVED] How to tunnel HTTP over SSH via SOCKS?

    This should be a simple issue to solve, but for some reason it's not working for me. `ssh vps` works just fine (I use authentication keys) I set up the tunnel with the command: ssh -C2TNv -D 8080 vps I then modify Firefox network settings: manual con

  • Logical standby problem on primary DB updates

    Hi all! I am quite new to standby databases, but I managed to sucessfully setup logical standby (11g on linux). However, I got some problem - when I try to insert some data into Primary DB using simple JDBC statements, I sometimes get exception: java

  • Java crash 64bit

    I seem to be having an issue with Java 64bit  with the 64bit version of windows 10. It will not allow Minecraft to load or it will not load the configure. It tells me "Java(TM) Platform SE binary has stopped working. A problem caused the program to s

  • File Adapter 3.0

    In my scenario File -> XI -> R3 The file is being read and converted to xml <?xml version="1.0" encoding="utf-8" ?> <ns:FileType1 xmlns:ns="http://test.com"> <ns:FileType1 xmlns:ns="http://test.com"> <FileType1>    <type>1</type>    <name>23</name>