Auxiliary channel allocation in TSPITR with RMAN-managed instance

Hi,
I'm trying do perform TSPITR with RMAN-managed auxiliary instance. All backups are stored on tape. I need to send MML environment values while allocating auxiliary channel to connect to correct NetWorker server and send other NetWorker parameters.
Unfortunately I have issues with sending these params - I can't send them from recover RUN block, as auxiliary instance does not exists at the time when I'm starting to execute script. (example from test env using disk channels)
RMAN> RUN
2> {
3> ALLOCATE CHANNEL c1 DEVICE TYPE disk;
4> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE disk;
5> SET NEWNAME FOR DATAFILE 1 TO '/u01/backup/tspitr/10gdb2/system01.f';
6> SET NEWNAME FOR DATAFILE 2 TO '/u01/backup/tspitr/10gdb2/undo01.f';
7> SET NEWNAME FOR DATAFILE 7 TO '/u01/backup/tspitr/10gdb2/hr_bak01.f';
8> SET AUXILIARY INSTANCE PARAMETER FILE TO '/home/oracle/params_auxinit.ora';
9> RECOVER TABLESPACE hr_test UNTIL TIME "SYSDATE - 1/4"
10> AUXILIARY DESTINATION '/u01/backup/tspitr/10gdb2';
11> RELEASE CHANNEL c1;
12> RELEASE CHANNEL aux1;
13> }
allocated channel: c1
channel c1: sid=141 devtype=DISK
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at 04/07/2010 17:21:53
RMAN-06174: not connected to auxiliary databaseI know I can do it using configure, but is there any way to set this on session level?
10.2.0.4, RHEL
Thanks,
Lukasz

What can be done here, is to CONFIGURE AUXILIARY CHANNEL to set appropriate params for auxiliary instance (without allocating channels manually).
I just wanted to know, if I can do it just for this one session (without permanent modification). What I can do, is:
CONFIGURE AUXILIARY CHANNEL DEVICE TYPE sbt_tape PARMS 'mml settings';
CONFIGURE CHANNEL DEVICE TYPE sbt_tape PARMS 'mml settings';
CONFIGURE DEFAULT DEVICE TYPE TO sbt_tape;
RUN
(new names, auxiliary parameter file)
RECOVER TABLESPACE ...
CONFIGURE AUXILIARY CHANNEL DEVICE TYPE sbt_tape CLEAR;
CONFIGURE CHANNEL DEVICE TYPE sbt_tape CLEAR;
CONFIGURE DEFAULT DEVICE TYPE CLEAR;I just wanted more 'elegant' solution.
Update:
Due to bug no. 4768353 there is no possibility to use automatic channel allocation in auxiliary instance. Problem resolved by using own customized auxiliary instance started before recovery process. Channels have been allocated manually using ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt... on already running aux.
Thanks,
Lukasz
Edited by: Łukasz Mastalerz on Apr 19, 2010 6:47 PM

Similar Messages

  • RMAN-05001 auxiliary .... conflicts with a file used by the target database

    I can´t recreate my physical standby.
    It worked in the past.
    Now I reinstalled the 3 standbyclients.
    Copied the spfile from the primary - modified the entries and did a rman backup.
    But when issuing the duplicate database command - it comes up with the error above
    SPFILE standyby db:
    *.db_file_name_convert='+DATA/prim/','+DATA/stdy/','+RECOVERY/prim','+RECOVERY/stdy'
    *.log_file_name_convert='+DATA/prim/','+DATA/stdy/','+RECOVERY/prim','+RECOVERY/stdy'
    Starting restore at 15-APR-10
    using channel ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: starting datafile backupset restore
    channel ORA_AUX_DISK_1: restoring control file
    channel ORA_AUX_DISK_1: reading from backup piece /oracle/stage/33lb65n2_1_1
    channel ORA_AUX_DISK_1: restored backup piece 1
    piece handle=/oracle/stage/33lb65n2_1_1 tag=TAG20100415T102434
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:11
    output filename=+REDO1/stdy/controlfile/current.262.716293055
    output filename=+REDO2/stdy/controlfile/backup.262.716293055
    Finished restore at 15-APR-10
    sql statement: alter database mount standby database
    released channel: ORA_AUX_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 04/15/2010 10:31:46
    RMAN-05501: aborting duplication of target database
    RMAN-05001: auxiliary filename DATA/prim/datafile/system.262.715097535 conflicts with a file used by the target database+
    RMAN-05001: auxiliary filename DATA/prim/datafile/sysaux.263.715097499 conflicts with a file used by the target database+
    RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs3.269.710521021 conflicts with a file used by the target database+
    RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs2.270.710521021 conflicts with a file used by the target database+
    RMAN-05001: auxiliary filename DATA/prim/datafile/example.272.710521021 conflicts with a file used by the target database+
    RMAN-05001: auxiliary filename DATA/prim/datafile/users.268.710521021 conflicts with a file used by the target database+
    RMAN-05001: auxiliary filename DATA/prim/datafile/sysaux.273.710521021 conflicts with a file used by the target database+
    RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs1.271.710521021 conflicts with a file used by the target database+
    RMAN-05001: auxiliary filename DATA/prim/datafile/system.264.710521021 conflicts with a file used by the target database+

    Hi ,
    I feel you are using ASM but still check the below details:
    Cause
    Production and Auxiliary have same directory structure and are running on two different machines. RMAN must be told not check that the target datafiles are sharing the same names as the duplicated files being created. Otherwise, the following errors will be returned:
    RMAN-05001: auxiliary filename /qmaxnt/u04/qmaxntorafiles/table/QMAXAD08_03.dbf
    conflicts with a file used by the target database
    RMAN-05001: auxiliary filename /qmaxnt/u04/qmaxntorafiles/table/QMAXAD08_02.dbf
    Solution
    To implement the solution, please use nofilenamecheck in syntax as follows:
    1. Connect to Target, auxiliary, and rman catalog and
    2. use script as
    run{
    set until time "to_date('2005/09/17 14:00:00','yyyy/mm/dd HH24:MI:SS')";
    allocate auxiliary channel aux1 type 'sbt_tape';
    allocate auxiliary channel aux2 type 'sbt_tape';
    duplicate target database for standby dorecover nofilenamecheck;
    Make sure to use auxiliary type of channel so RMAN restore take place at auxiliary database.
    Thanks,
    Rafi.
    http://rafioracledba.blogspot.com/

  • RMAN-06181 thrown when only 1 SBT channel allocated

    Hello,
    I'm using Oracle 8.1.7.0 Standard Edition on Windows Server 2000 SP4. I am aware that we cannot allocate multiple channels with our version of Oracle as the RMAN-06181 error states. However I am only allocating a single channel when this error occurs. Here's the error when I simply test the allocation of the channel:
    RMAN> run {
    2> allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=C:\Program Files
    \Tivoli\TSM\AgentOBA\tdpo.opt)';
    3> }
    RMAN-03022: compiling command: allocate
    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: allocate
    RMAN-06181: multiple channels require Oracle8 Enterprise Edition
    RMAN>
    Does anyone have any ideas?
    Thank you,
    rbrieck

    rbrieck wrote:
    Hello,
    I'm using Oracle 8.1.7.0 Standard Edition on Windows Server 2000 SP4. I am aware that we cannot allocate multiple channels with our version of Oracle as the RMAN-06181 error states. However I am only allocating a single channel when this error occurs. Here's the error when I simply test the allocation of the channel:
    RMAN> run {
    2> allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=C:\Program Files
    \Tivoli\TSM\AgentOBA\tdpo.opt)';
    3> }
    RMAN-03022: compiling command: allocate
    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: allocate
    RMAN-06181: multiple channels require Oracle8 Enterprise Edition
    RMAN>
    Does anyone have any ideas?
    Thank you,
    rbrieck
    rman> show all;Post results of above

  • R12 clone with RMAN auxiliary db.

    Hi all,
    We require daily clone for our setup due to testing and other reason. Can we replace only database via RMAN Clone?
    R12 clone with RMAN Auxiliary DB. Find below steps, if I am wrong correct me.
    1.     run autoconfig on apps tier.
    2.     perl <AD_TOP>/bin/admkappsutil.pl and Synchronize appsutil on db tier.
    3.     Run autoconfig on dbtier or adconfig.sh <contextfile>) (which is correct? i am using autoconfig not with contextfile)
    4.     adpreclone.pl dbTier
    5.     adpreclone.pl appsTier
    6.     copy source to target including db and apps tiers.
    7.     perl adcfgclone.pl dbTechStack .
    8.     create duplicate db (auxiliary db) from rman backup.
    9.     sqlplus "/ as sysdba" @adupdlib.sql so
    10.     perl adcfgclone.pl dbconfig <CONTEXT_NAME.xml> (This gives error, I am skipping this step. I have tried with perl adcfgclone.pl database but then also its give error. )
    11.     exec FND_CONC_CLONE.SETUP_CLEAN;
    12.     perl adcfgclone.pl dbTier (if we run perl adcfgclone.pl dbTechStack ,Is this step require?)
    13.     perl adcfgclone.pl appsTier
    please correct my steps.
    thanks in advance,
    sandeep

    Hi,
    3.     Run autoconfig on dbtier or adconfig.sh <contextfile>) (which is correct? i am using autoconfig not with contextfile)Run $ORACLE_HOME/appsutil/bin/adconfig.sh contextfile=$CONTEXT_FILE appspass=apps -- See (Note: 603104.1 - Troubleshooting RapidClone issues with Oracle Applications R12) for details.
    10.     perl adcfgclone.pl dbconfig <CONTEXT_NAME.xml> (This gives error, I am skipping this step. I have tried with perl adcfgclone.pl database but then also its give error. )What is the error?
    12.     perl adcfgclone.pl dbTier (if we run perl adcfgclone.pl dbTechStack ,Is this step require?)After running "perl adcfgclone.pl dbTechStack", you need to run "perl adcfgclone.pl dbconfig <Database target context file> -- See (Note: 406982.1 - Cloning Oracle Applications Release 12 with Rapid Clone) and (Note: 799735.1 - Rapid Clone Documentation Resources, Release 11i and 12) for details.
    Regards,
    Hussein

  • RMAN -AUXILIARY CHANNEL

    Hi,
    Please help me to understand the following commands, which I have found in an RMAN script.
    allocate auxiliary channel 'dev_0' type 'sbt_tape' parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=JK_P3e,OB2BARHOSTNAME=server1)';
    CONFIGURE AUXILIARY CHANNEL 1 DEVICE TYPE 'SBT_TAPE' PARMS env=(nb_ora_serv=mgtserv, nb_ora_client=cervantes)";
    regards,
    Mathew.

    Some RMAN operations, such as DUPLICATE, involve two databases (in addition to the catalog DB).
    The second database is called auxiliary. To connect to that database one has to issue something like
    connect auxiliary sys/...;To open channel to auxiliary DB (as opposed to the target DB), an auxiliary channel is needed
    allocate auxiliary channel aux0 …;Iordan Iotzov
    http://iiotzov.wordpress.com/

  • Channel allocation in rman at the time of backup

    what happens when one channel of five channels allocated for taking backup got corrupt at the time of backup process is still going on?
    does the backup will continue if so is that backup is consistent or inconsistent?

    > I am using the brbackup to do the backup and i configured the init<SID>.sap file and i started the brbackup tool from the command prompt . I am getting the problem at password the password containing Basis@2008.
    You opened that thread in SQL Server but your database seems to be Oracle...
    as which user do you start brbackup?
    Markus

  • Oracle 3113 creating a standby with rman

    Hello,
    environment is 11gR2 on Linux.
    Tested on CentOS 5.5 as OS and local LAN as interconnect and the duplicate command terminates successfully in some minutes.
    Same script but using oel 5.5 and a wan (3Mbit/s) and I keep getting 3113 errors after about 2h or 3h.
    I suspect some timeout on wan (that is over vpn) but I would also like to trace something at my side.
    I run a shell script with nohup and send it to background and this is the log, from which you can see the rman script:
    Recovery Manager: Release 11.2.0.1.0 - Production on Tue Sep 7 14:50:11 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    RMAN>
    connected to target database: TESDB1 (DBID=11492743)
    RMAN>
    connected to auxiliary database: DUMMY (not mounted)
    RMAN>
    RMAN> run{
    2> allocate channel prmy1 type disk;
    3> allocate auxiliary channel stby1 type disk;
    4> duplicate target database for standby from active database
    5> spfile
    6> parameter_value_convert 'TESDB1','TESDB1DR'
    7> set db_file_name_convert='/TESDB1/','/TESDB1DR/'
    8> set log_file_name_convert='/TESDB1/','/TESDB1DR/'
    9> set 'db_unique_name'='TESDB1DR'
    10> set control_files='/app/oradata/TESDB1DR/control01.ctl','/app/oradata/flash_recovery_area/TESDB1DR/control02.ctl'
    11> set db_recovery_file_dest='/app/oradata/flash_recovery_area'
    12> set DB_RECOVERY_FILE_DEST_SIZE='4977M'
    13> nofilenamecheck;
    14> }
    using target database control file instead of recovery catalog
    allocated channel: prmy1
    channel prmy1: SID=12 device type=DISK
    allocated channel: stby1
    channel stby1: SID=135 device type=DISK
    Starting Duplicate Db at 07-SEP-10
    executing Memory Script
    executing command: SET NEWNAME
    renamed tempfile 1 to /app/oradata/TESDB1DR/temp01.dbf in control file
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting backup at 07-SEP-10
    channel prmy1: starting datafile copy
    input datafile file number=00003 name=/app/oradata/TESDB1/undotbs01.dbf
    .. after about three hours (and 3.2Gb transferred) it continues with:
    RMAN-03009: failure of backup command on prmy1 channel at 09/07/2010 17:53:49
    RMAN-06136: ORACLE error from auxiliary database: ORA-03113: end-of-file on communication channel
    Process ID: 3187
    Session ID: 192 Serial number: 3
    continuing other job steps, job failed will not be re-run
    .. after 15 minutes:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/07/2010 18:09:35
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on clone_default channel at 09/07/2010 18:09:34
    RMAN-10038: database session for channel clone_default terminated unexpectedly
    RMAN> **end-of-file**
    RMAN>
    Recovery Manager complete.
    the undo tbs is 3.2 Gb so I'm not sure if the 3113 happens at the end of copy... but the tablespace doesn't succeed
    and the other jobs don't start even if it says "continuing other job steps"..
    rman started at 14:50 and in listener at dr site I have:
    Tue Sep 07 14:50:55 2010
    07-SEP-2010 14:50:55 * service_update * TESDB1DR * 0
    07-SEP-2010 14:50:55 * (CONNECT_DATA=(SERVICE_NAME=TESDB1DR)(CID=(PROGRAM=oracle)(HOST=lb-orajde.boiron.ntm)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.49.1.93)(PORT=35240)) * establish * TESDB1DR * 0
    Tue Sep 07 15:00:58 2010
    07-SEP-2010 15:00:58 * service_update * TESDB1DR * 0
    Tue Sep 07 16:35:04 2010
    07-SEP-2010 16:35:04 * service_update * TESDB1DR * 0
    Tue Sep 07 17:02:04 2010
    07-SEP-2010 17:02:04 * service_update * TESDB1DR * 0
    07-SEP-2010 17:02:10 * service_update * TESDB1DR * 0
    Tue Sep 07 17:53:17 2010
    07-SEP-2010 17:53:17 * service_update * TESDB1DR * 0
    Tue Sep 07 18:09:00 2010
    07-SEP-2010 18:09:00 * (CONNECT_DATA=(SERVICE_NAME=TESDB1DR)(CID=(PROGRAM=rman)(HOST=lb-orajde.boiron.ntm)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.49.1.93)(PORT=32610)) * establish * TESDB1DR * 0
    In alert.log at dr site I have at 17:02 (about 50 minutes before error):
    Tue Sep 07 15:05:01 2010
    db_recovery_file_dest_size of 4977 MB is 0.00% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Tue Sep 07 17:02:03 2010
    Fatal NI connect error 12170.
    VERSION INFORMATION:
    TNS for Linux: Version 11.2.0.1.0 - Production
    Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
    TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
    Time: 07-SEP-2010 17:02:03
    Tracing not turned on.
    Tns error struct:
    ns main err code: 12535
    TNS-12535: TNS:operation timed out
    ns secondary err code: 12560
    nt main err code: 505
    TNS-00505: Operation timed out
    nt secondary err code: 110
    nt OS err code: 0
    Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.49.1.93)(PORT=35226))
    some times (always at 17:02) and nothing more
    In alert.log at primary site:
    Tue Sep 07 14:50:36 2010
    Clearing standby activation ID 11529351 (0xafec87)
    The primary database controlfile was created using the
    'MAXLOGFILES 16' clause.
    There is space for up to 13 standby redo logfiles
    Use the following SQL commands on the standby database to create
    standby redo logfiles that match the primary database:
    ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800;
    Tue Sep 07 16:00:40 2010
    Thread 1 advanced to log sequence 759 (LGWR switch)
    Current log# 3 seq# 759 mem# 0: /app/oradata/TESDB1/redo03.log
    Tue Sep 07 16:00:41 2010
    Archived Log entry 528 added for thread 1 sequence 758 ID 0xafec87 dest 1:
    In sqlnet.log of primary site:
    Tue Sep 07 17:53:49 2010
    Fatal NI connect error 12170.
    VERSION INFORMATION:
    TNS for Linux: Version 11.2.0.1.0 - Production
    TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
    Time: 07-SEP-2010 17:53:49
    Tracing not turned on.
    Tns error struct:
    ns main err code: 12535
    TNS-12535: TNS:operation timed out
    ns secondary err code: 12560
    nt main err code: 505
    TNS-00505: Operation timed out
    nt secondary err code: 110
    nt OS err code: 0
    Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.12.41)(PORT=1521))
    and the same at 18:09
    No other errors.
    Any hints?
    BTW: what is the minimum size of undo tbs? Can I have compression enabled also during duplication if transport service is configured with COMPRESSION=ENABLED, or does it count only when copying redo files?
    Thanks in advance,
    Gianluca

    Thanks for your reply.
    I will try your suggestion as it could come useful some time.
    So with this alternate method at the end I would have standby aligned as of backup time, correct?
    And after running something like this on standby:
    SQL> alter database recover managed standby database disconnect from session;
    It will begin to receive, archive and apply redo logs, correct?
    Some answers regarding the original question. It was confirmed that there was a 2hours cut-off time at firewall level.
    The first datafile that the rman session began to copy was 3.2Gb in size, taking more than 2 hours completing.
    Monitoring with netstat on source and target I saw this at source during the duplicate process:
    tcp 0 0 10.49.1.93:46626 192.168.12.41:1521 ESTABLISHED
    tcp 0 0 10.49.1.93:46627 192.168.12.41:1521 ESTABLISHED
    tcp 0 0 10.49.1.93:46629 192.168.12.41:1521 ESTABLISHED
    tcp 0 369240 10.49.1.93:50371 192.168.12.41:1521 ESTABLISHED
    and the session bound to port 50371 was the only one pushing data (send queue not empty).
    The other 3 ones I presume are for control of rman session. I get 3 sessions even if I open only one channel on primary side.
    After the first datafile completes copy, a new session (with port 14871) is established substituting the other one.
    The three initial ones instead remain for all the duplicate process.
    tcp 0 487872 10.49.1.93:14871 192.168.12.41:1521 ESTABLISHED
    tcp 0 0 10.49.1.93:46626 192.168.12.41:1521 ESTABLISHED
    tcp 0 0 10.49.1.93:46627 192.168.12.41:1521 ESTABLISHED
    tcp 0 0 10.49.1.93:46629 192.168.12.41:1521 ESTABLISHED
    So after the copy of the first file, the session come back to one or more of the initial 3 ones, and they probably make a push-ack, got a 3113 as the firewall has silently cut them after 2 hours.... and the datafile, even if completed, is not marked as completed. A new run would copy again it...
    Now the time has been put to 8hours, with 24hours being the maximum value set (no disable possible as far as the network guy said...).
    And the duplicate completed correctly.
    Would I have to fear any problems with this cut-off due to "normal" dataguard operations or not, in your opinion?
    Thanks
    Gianluca

  • Tablespace Point in Time Recovery fails with RMAN-06026:

    I have cataloged with RMAN the datafiles from Snapshot backup. Still it fails with the following error.
    RMAN> RECOVER TABLESPACE TSPC UNTIL TIME "to_date('03-apr-2013 02:18:00','dd-mon-yyyy hh24:mi:ss')" AUXILIARY DESTINATION '/tmp/auxpran';
    Starting recover at 03-APR-13
    using channel ORA_DISK_1
    RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time
    List of tablespaces expected to have UNDO segments
    Tablespace SYSTEM
    Tablespace UNDOTBS1
    Creating automatic instance, with SID='Ebgt'
    initialization parameters used for automatic instance:
    db_name=ORCL
    db_unique_name=Ebgt_tspitr_ORCL
    compatible=11.2.0.0.0
    db_block_size=8192
    db_files=200
    sga_target=280M
    processes=50
    db_create_file_dest=/tmp/auxpran
    log_archive_dest_1='location=/tmp/auxpran'
    #No auxiliary parameter file used
    starting up automatic instance ORCL
    Oracle instance started
    Total System Global Area 292933632 bytes
    Fixed Size 1336092 bytes
    Variable Size 100666596 bytes
    Database Buffers 184549376 bytes
    Redo Buffers 6381568 bytes
    Automatic instance created
    Running TRANSPORT_SET_CHECK on recovery set tablespaces
    TRANSPORT_SET_CHECK completed successfully
    contents of Memory Script:
    # set requested point in time
    set until time "to_date('03-apr-2013 02:18:00','dd-mon-yyyy hh24:mi:ss')";
    # restore the controlfile
    restore clone controlfile;
    # mount the controlfile
    sql clone 'alter database mount clone database';
    # archive current online log
    sql 'alter system archive log current';
    # avoid unnecessary autobackups for structural changes during TSPITR
    sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
    executing Memory Script
    executing command: SET until clause
    Starting restore at 03-APR-13
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=19 device type=DISK
    channel ORA_AUX_DISK_1: restoring control file
    channel ORA_AUX_DISK_1: copied control file copy
    input file name=/tmp/auxpran/controlbc.ctl
    output file name=/tmp/auxpran/ORCL/controlfile/o1_mf_8opkv8v4_.ctl
    Finished restore at 03-APR-13
    sql statement: alter database mount clone database
    sql statement: alter system archive log current
    sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
    contents of Memory Script:
    # set requested point in time
    set until time "to_date('03-apr-2013 02:18:00','dd-mon-yyyy hh24:mi:ss')";
    # set destinations for recovery set and auxiliary set datafiles
    set newname for clone datafile 1 to new;
    set newname for clone datafile 3 to new;
    set newname for clone datafile 2 to new;
    set newname for clone tempfile 1 to new;
    set newname for datafile 5 to
    "+DG_DATA/orcl/datafile/tspc.268.811733685";
    # switch all tempfiles
    switch clone tempfile all;
    # restore the tablespaces in the recovery set and the auxiliary set
    restore clone datafile 1, 3, 2, 5;
    switch clone datafile all;
    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
    renamed tempfile 1 to /tmp/auxpran/ORCL/datafile/o1_mf_temp_%u_.tmp in control file
    Starting restore at 03-APR-13
    using channel ORA_AUX_DISK_1
    One or more auxiliary set datafiles could not be removed
    Removing automatic instance
    shutting down automatic instance
    database dismounted
    Oracle instance shut down
    Automatic instance removed
    auxiliary instance file /tmp/auxpran/ORCL/controlfile/o1_mf_8opkv8v4_.ctl deleted
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 04/03/2013 02:32:55
    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 2 found to restore
    RMAN-06023: no backup or copy of datafile 3 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restore
    Could anyone please reply ASAP?
    Regards,
    Pranam

    I had created a snapshot of the database(datafiles and archivelogs) and cataloged them.
    CATALOG START WITH "+TBL_DG_DATA/ORCL/DATAFILE/" NOPROMPT;
    catalog start with "+DG_ARCH/ORCL/ARCHIVELOG/" NOPROMPT;
    The time i gave was after the snapshot was created.
    When it failed the first time I created another controlfile using
    sql "alter database backup controlfile to ''/tmp/auxpran/controlbc.ctl''";
    And ran the recover command after the time after i generated this controlfile. Changed nothing else. TSPITR completed successfully. But it had failed first time. Cannot figure how it ran the second time but failed the first time.
    Removing automatic instance
    Automatic instance removed
    auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_temp_8opndd87_.tmp deleted
    auxiliary instance file /tmp/auxpran/ORCL/onlinelog/o1_mf_3_8opnd1o6_.log deleted
    auxiliary instance file /tmp/auxpran/ORCL/onlinelog/o1_mf_2_8opncy32_.log deleted
    auxiliary instance file /tmp/auxpran/ORCL/onlinelog/o1_mf_1_8opncv7d_.log deleted
    auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_sysaux_8opn516p_.dbf deleted
    auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_undotbs1_8opn4j14_.dbf deleted
    auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_system_8opmyvly_.dbf deleted
    auxiliary instance file /tmp/auxpran/ORCL/controlfile/o1_mf_8opmy14q_.ctl deleted
    Finished recover at 03-APR-13

  • Problem with rman backups

    We upgraded, the rman catalog due to the following error:
    PL/SQL package RMAN.DBMS_RCVCAT version 11.02.00.01 in RCVCAT database is not current PL/SQL package RMAN.DBMS_RCVMAN version 11.02.00.01 in RCVCAT database is not current
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of sql command at 01/17/2011 21:00:36
    ORA-03114: not connected to ORACLEWe registered our database on the catalog again
    problem we have now is that our backup fails with the following errors:
    RMAN> connect target *
    2> connect catalog *
    3>
    4> run {
    5>      crosscheck archivelog all;
    6>     }
    7>
    connected to target database: MAC (DBID=710471977)
    connected to recovery catalog database
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of crosscheck command at 01/20/2011 06:00:29
    ORA-03114: not connected to ORACLEany suggestions, as to how we can fix these errors

    Must this be done fron the local machine where my backup scripts reside..
    or must it be done on the catalog server?????
    I ran the crosscheck command from the local machine without connecting to the catalog
    here are the eroors I received:
    oracle $ rman
    Recovery Manager: Release 11.2.0.2.0 - Production on Thu Jan 20 11:42:42 2011
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    RMAN> connect target /
    connected to target database: MAC (DBID=710471977)
    RMAN> run{
    2> crosscheck backup COMPLETED AFTER 'sysdate-1';
    3> }
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of crosscheck command at 01/20/2011 11:43:48
    RMAN-12010: automatic channel allocation initialization failed
    ORA-03114: not connected to ORACLE
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    ORA-03114: not connected to ORACLE
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of crosscheck command at 01/20/2011 11:43:48
    RMAN-12010: automatic channel allocation initialization failed
    ORA-03114: not connected to ORACLE

  • Duplicate database command fails with RMAN-06023

    Hello,
    I am trying to test out the duplicate database command in RMAN and am running into some issues.
    I did a backup of my test database, copied the backup files to a second server, and now I'm trying to run the duplicate command and I get RMAN-06023 errors for all of my datafiles.
    I did crosschecks on my backupsets and they showed as available. They are in the same location on the new server, with the same permissions. There are no recent archived logs, as this is a very quiet environment.
    My commands and output (edited slightly) were as follows:
    RMAN> run {
    2> allocate channel d1 device type disk;
    3> allocate channel d2 device type disk;
    4> backup database;
    5> }
    allocated channel: d1
    channel d1: sid=32 devtype=DISK
    allocated channel: d2
    channel d2: sid=36 devtype=DISK
    Starting backup at 03-JUL-07
    channel d1: starting full datafile backupset
    channel d1: specifying datafile(s) in backupset
    channel d2: starting full datafile backupset
    channel d2: specifying datafile(s) in backupset
    input datafile fno=00012 name=/database/oradata/source/matrix_ts01.dbf
    input datafile fno=00004 name=/database/oraindex/source/ind_ts01.dbf
    input datafile fno=00006 name=/database/oradata/source/users_ts01.dbf
    input datafile fno=00003 name=/database/oradata/source/drsys01.dbf
    input datafile fno=00007 name=/database/oradata/source/ORACLEORADATATST2CWMLITE01.DBF
    input datafile fno=00009 name=/database/oradata/source/ORACLEORADATATST2ODM01.DBF
    input datafile fno=00005 name=/database/oradata/source/tools_ts01.dbf
    channel d2: starting piece 1 at 03-JUL-07
    including current SPFILE in backupset
    including current controlfile in backupset
    input datafile fno=00011 name=/database/oradata/source/ORACLEORADATADATA.DBF
    input datafile fno=00001 name=/database/oradata/source/system_ts01.dbf
    input datafile fno=00002 name=/database/oradata/source/undo_ts01.dbf
    input datafile fno=00008 name=/database/oradata/source/ORACLEORADATATST2EXAMPLE01.DBF
    input datafile fno=00010 name=/database/oradata/source/ORACLEORADATATST2XDB01.DBF
    channel d1: starting piece 1 at 03-JUL-07
    channel d2: finished piece 1 at 03-JUL-07
    piece handle=/database/oracle/product/9.2.0/dbs/0ciltjgn_1_1 comment=NONE
    channel d2: backup set complete, elapsed time: 00:08:17
    channel d1: finished piece 1 at 03-JUL-07
    piece handle=/database/oracle/product/9.2.0/dbs/0biltjgn_1_1 comment=NONE
    channel d1: backup set complete, elapsed time: 00:09:22
    Finished backup at 03-JUL-07
    released channel: d1
    released channel: d2
    ** at this point I copied the files listed above to same directory on destination server **
    RMAN> connect auxiliary sys/[email protected]
    connected to auxiliary database: destination (not mounted)
    RMAN> run {
    2> allocate auxiliary channel aux1 device type disk;
    3> allocate auxiliary channel aux2 device type disk;
    4> duplicate target database to destination nofilenamecheck;
    5> }
    llocated channel: aux1
    channel aux1: sid=10 devtype=DISK
    allocated channel: aux2
    channel aux2: sid=13 devtype=DISK
    Starting Duplicate Db at 03-JUL-07
    printing stored script: Memory Script
    set until scn 4873550;
    set newname for datafile 1 to
    "/database/oradata/destination/system_ts01.dbf";
    set newname for datafile 2 to
    "/database/oradata/destination/undo_ts01.dbf";
    set newname for datafile 3 to
    "/database/oradata/destination/drsys01.dbf";
    set newname for datafile 4 to
    "/database/oraindex/destination/ind_ts01.dbf";
    set newname for datafile 5 to
    "/database/oradata/destination/tools_ts01.dbf";
    set newname for datafile 6 to
    "/database/oradata/destination/users_ts01.dbf";
    set newname for datafile 7 to
    "/database/oradata/destination/ORACLEORADATATST2CWMLITE01.DBF";
    set newname for datafile 8 to
    "/database/oradata/destination/ORACLEORADATATST2EXAMPLE01.DBF";
    set newname for datafile 9 to
    "/database/oradata/destination/ORACLEORADATATST2ODM01.DBF";
    set newname for datafile 10 to
    "/database/oradata/destination/ORACLEORADATATST2XDB01.DBF";
    set newname for datafile 11 to
    "/database/oradata/destination/ORACLEORADATADATA.DBF";
    set newname for datafile 12 to
    "/database/oradata/destination/matrix_ts01.dbf";
    restore
    check readonly
    clone database
    executing script: Memory Script
    executing command: SET until clause
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 03-JUL-07
    released channel: aux1
    released channel: aux2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 07/03/2007 14:35:13
    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 12 found to restore
    RMAN-06023: no backup or copy of datafile 11 found to restore
    RMAN-06023: no backup or copy of datafile 10 found to restore
    RMAN-06023: no backup or copy of datafile 9 found to restore
    RMAN-06023: no backup or copy of datafile 8 found to restore
    RMAN-06023: no backup or copy of datafile 7 found to 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
    Thanks for any help,

    Hi,
    Where is you RMAN catalog? I think you forgot to connect to it.
    To duplicate a database check that folowing applies:
    1-the auxiliary instance is mounted
    2-the listener for the auxiliary db is up
    3-the backup pieces that RMAN is going to restore ARE AVAILABLE on the
    secondary/auxilary server with SAME NAME the have on the primary server (you can use NFS to avoid the copy of the pieces from primary to auxuliary box)
    Remember to be conected to both: target and auxiliary db.
    I have extracted the folowing lines from an RMAN script I used to create an standby database with the DUPLICATE command (the RMAN catalog was in the primary db controlfile, and the command was run on the primary server:
    $ rman target / nocatalog auxiliary sys/pwd@standbycard log=crCARD.log
    RMAN> duplicate target database for standby nofilenamecheck dorecover;
    I hope this helps
    Gustavo Restuccia

  • Problem creating physical Standby database with RMAN

    Hi All
    I am trying to learn oracle dataguard and as part of the process learning creating standby database.
    Platform : Sun-Fire-V250 Sparc, Solaris 10
    Database Version - Oracle 11R2
    I am creating standby database on same server, so directory structure is different.
    Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
    1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
    2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
    On Primary Database:
    *.FAL_CLIENT='orcl11020' #Primary database unique name
    *.FAL_SERVER='stdby_11' #Standby database unique name
    db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
    log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
    standby_file_management=auto
    *.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
    *.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
    *.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
    *.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
    *.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
    *.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
    *.LOG_ARCHIVE_MAX_PROCESSES=30
    Copied same pfile for standby database and modified following-
    *.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
    *.db_name='orcl1102'
    *.db_unique_name='stdby_11'
    *.FAL_CLIENT='stdby_11'
    *.FAL_SERVER='orcl11020'
    db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
    log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
    standby_file_management=auto
    *.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
    *.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
    db_unique_name=orcl11020'
    3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
    3. Created password file with same credential as primary database.
    4.Up-to-date RMAN backup of primary database available.
    5.Create standby controlfile with rman
    While primary database s open (I tried with primary database in mount mode as well)-
    $>rman catalog rman/paswd@rman target /
    RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
    6. Open a new terminal and startup standby database in nomount mode using parameter file created -
    $>ORACLE_SID=stdby_11
    $>export ORACLE_SID
    $>sqlplus / as sysdba
    SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
    SQL>quit
    $> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
    RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
    RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
    Error 1017 received logging on to the standby
    Check that the primary and standby are using a password file
    and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
    and that the SYS password is same in the password files.
    returning error ORA-16191
    FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
    Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
    ORA-16191: Primary log shipping client not logged on standby
    Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
    ORA-16191: Primary log shipping client not logged on standby
    So on both primary and standby I confirmed
    SQL> show parameter remote_login_passwordfile
    NAME TYPE VALUE
    remote_login_passwordfile string EXCLUSIVE
    To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
    Password files are called - orapworcl11020 and orapwstdby_11
    Can someone guide me where thisngs are going wrong here please.

    Not sure if I understood it clearly.
    SELECT * FROM V$ARCHIVE_GAP;
    returns no rows so there is no gap.
    But could you please explain me the result of the previous query. To catch up again, on standby when I check
    SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
    SEQUENCE# APPLIED
    75 NO
    74 NO
    76 NO
    77 NO
    I understand that though archive files have been copied across but they are not applied yet.
    On primary when I give your query -
    SELECT name as STANDBY,SEQUENCE#,applied, completion_time
    2 FROM v$archived_log
    3 where dest_id=2
    4 and sequence# BETWEEN 74 and 80;
    I get -
    STANDBY SEQUENCE# APPLIED COMPLETIO
    stdby_11 74 YES 28-JUN-11
    stdby_11 75 YES 28-JUN-11
    stdby_11 76 YES 29-JUN-11
    stdby_11 77 YES 29-JUN-11
    stdby_11 78 YES 29-JUN-11
    stdby_11 79 YES 29-JUN-11
    stdby_11 80 YES 29-JUN-11
    stdby_11 75 NO 07-JUL-11
    stdby_11 74 NO 07-JUL-11
    stdby_11 76 NO 07-JUL-11
    stdby_11 77 NO 07-JUL-11
    stdby_11 78 NO 07-JUL-11
    I have intentionally given
    sequence# BETWEEN 74 and 80
    because I know in the current incarnaion of the database, max sequence is 78.
    So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
    Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
    Then my final question is, when will these archives be applied to standby database?
    I am sorry to ask too many questions but I am just trying to understand how it all works.
    Thanks for your help again

  • How to start with RMAN as I am beginner?

    Dear all,
    How to start with RMAN as I am beginner? Any simple document or guide line for me.
    Thanks,
    Amy

    How to start with RMAN as I am beginner? Any simple
    document or guide line for me.go to yours oracle home directory /orahome/bin there is RMAN exe tool run it it will show you prompt RMAN
    Recovery Manager: Release 10.1.0.2.0 - Production
    Copyright (c) 1995, 2004, Oracle.  All rights reserved.
    RMAN> connect target sys/sys
    connected to target database: ORCL (DBID=1171886541)
    RMAN> backup database
    2> ;
    Starting backup at 21-JAN-08
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\SYSTEM01.DBF
    input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\SYSAUX01.DBF
    input datafile fno=00005 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\EXAMPLE01.DBF
    input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\UNDOTBS01.DBF
    input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\USERS01.DBF
    channel ORA_DISK_1: starting piece 1 at 21-JAN-08
    channel ORA_DISK_1: finished piece 1 at 21-JAN-08
    piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2008_01_21\O1_MF_NNNDF_TAG20080121T135924_3S8QQF74_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    including current controlfile in backupset
    including current SPFILE in backupset
    channel ORA_DISK_1: starting piece 1 at 21-JAN-08
    channel ORA_DISK_1: finished piece 1 at 21-JAN-08
    piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2008_01_21\O1_MF_NCSNF_TAG20080121T135924_3S8QSSN4_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 21-JAN-08
    http://www.orafaq.com/faq/rmanKhurram

  • How to get the size of the backed up datafile in a backup set with rman?

    Oracle 10gR2 and catalog is in place.
    Since RMAN only backups the used blocks(does not take backup from NEVER USED blocks), what can be the explanation of some extra space during backups?
    And also how to trace this space allocation by datafile with v$% - rc_% views or any rman command?
    Thank you, best regards.
    Tonguç

    Before 10G R2 rman does not backup never used blocks but it backs up blocks which have been previously used. So, dropping or truncating a table does not make the backup size smaller since the blocks of that segment are not "never used" anymore.
    Starting with 10G R2 a new feature named "unused block compression" comes into play. With this feature rman does not backup unused blocks (even if they have been used before). But it has some restrictions like: you need to backup to disk unless you are using Oracle Secure Backup, the datafile needs to be locally managed, etc...
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#RCMRF98765

  • Create standby DB with RMAN backup in Oracle 9.2.0.6

    I am tring to create a standby DB in different host with different directory using RMAN. The commandv with which I tried to create the standby database is the follow:
    (in the primary server side)
    RUN
    ALLOCATE AUXILIARY CHANNEL DUP1 TYPE DISK;
    DUPLICATE TARGET DATABASE FOR STANDBY
    NOFILENAMECHECK
    DORECOVER;
    but RMAN give me this error:
    Starting restore at 18-FEB-08
    channel DUP1: starting datafile backupset restore
    channel DUP1: restoring controlfile
    output filename=/opferi/oradata/oradata01/data01/cntrl01.dbf
    released channel: DUP1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 02/18/2008 17:57:20
    RMAN-03015: error occurred in stored script Memory Script
    ORA-19505: failed to identify file "/opferi/oracle/product/9.2.0/dbs/l4j9127p_1_1"
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    The standby database is in a different host with the same directory structure. I started (with nomount option) with the same init file that the primary database.
    I read solution like the backupset must be copied manually to the standby host, but for me is not a solution.
    The RMAN backup script is the follow (like
    RUN {
    CROSSCHECK BACKUPSET;
    DELETE NOPROMPT OBSOLETE;
    DELETE NOPROMPT EXPIRED BACKUPSET;
    crosscheck archivelog all;
    ALLOCATE CHANNEL ch00 TYPE disk;
    BACKUP
    $BACKUP_TYPE
    FORMAT '/rman/opferi2/df_sipd_%d_%u_%s_%p'
    DATABASE INCLUDE CURRENT CONTROLFILE FOR STANDBY;
    sql 'alter system archive log current';
    backup format '/rman/opferi2/archive_log_%d_t%t_s%s_p%p' (archivelog all);
    RELEASE CHANNEL ch00;
    when $BACKUP_TYPE=0
    Can anyone help my with this problem?? Thaks
    Cristian.
    PS. Sorry my bad english because I am from Latin America

    Requirements are:
    1 the backup should be accessible to both target and auxiliary database in the same location.
    2 On Unix this can be arranged through NFS, provided you set the read and write buffer to 32k.
    Obviously the backup can not be located in $ORACLE_HOME/dbs, as you can not mount a NFS directory over $ORACLE_HOME/dbs without loosing functionality.
    Hth
    Sybrand Bakker
    Senior Oracle DBA

  • Trying to restore a database with RMAN in new server

    Hello,
    Database: Oracle 10gR2
    O/S: Windows Server 2003
    My RMAN backuppieces are stored in a network drive:
    \\old_location\FULL
    and
    \\old_location\INC
    I'm trying to restore a whole database with RMAN in another server from my FULL backup.
    For that, I copy all backuppieces files
    from: \\old_location\FULL
    to new server: D:\new_location\
    Also I created the relevant folder hierarchy under <ORACLE_BASE> directory, as follows:
    a. Create BDUMP, CDUMP, and UDUMP directories under '<ORACLE_ BASE>\admin' directory
    b. Create <DATABASE_NAME> directory under '<ORACLE_BASE>\oradata' directory
    c. pfile.ora and controlfile (CTL_MTDPROD_2308_20120401_1.CTL) are backup from original database and they are in D:\new_location\
    d. I copied pfile.ora and controlfile to folder: C:\oracle\product\10.2.0\db_1\database\
    I started creating an instance in new server from scratch:
    C:\>oradim -new -sid MTDPROD -intpwd mtdprod
    C:\> SET ORACLE_SID=MTDPROD
    C:\> rman
    RMAN> connect target sys
    RMAN> SET DBID=21692876873
    RMAN> STARTUP force nomount PFILE=C:\oracle\product\10.2.0\db_1\database\init_mtdprod.ora
    RMAN> restore controlfile from 'C:\oracle\product\10.2.0\db_1\database\CTL_MTDPROD_2308_20120401_1.CTL';
    RMAN> alter database mount;
    #Since I want to read my backuppieces from D:\new_location and not from \\old_location\FULL then I catalog and restore like:
    RMAN> catalog start with 'D:\new_location\';
    RMAN> restore database;
    Starting recover at 25/04/12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=541 devtype=DISK
    channel ORA_DISK_1: starting incremental datafile backupset restore
    channel ORA_DISK_1: specifying datafile copies to recover
    recovering datafile copy fno=00003 name=D:\BD_MTDPROD\CONTROLFILES\SYSAUX01.DBF
    recovering datafile copy fno=00004 name=D:\BD_MTDPROD\CONTROLFILES\USERS01.DBF
    recovering datafile copy fno=00007 name=D:\BD_MTDPROD\DATAFILES_DATA\MSE.ORA
    recovering datafile copy fno=00010 name=D:\BD_MTDPROD\DATAFILES_DATA\EXPEDIENTES2.ORA
    channel ORA_DISK_1: reading from backup piece \\old_location\FULL\FULL_MTDPROD_20120401_2304_1.BAK
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: failover to piece handle=D:\new_location\FULL\FULL_MTDPROD_20120401_2304_1.BAK tag=TAG20120401T190004
    .....(continues)
    Questions:
    1. RMAN still reads from old_location. The only way to avoid that would be deleting all files from \\old_location\FULL ?
    2. The message "failover to piece handle=D:\new_location\...." indicates that that file is not usefull? I just copy them from old_location to new_location... how can they get useless?
    I suspect there is something in controlfile that redirects to \\old_location\FULL\ and doesn't let to read from D:\new_location\
    Please, advice.

    user521219 wrote:
    Questions:
    1. RMAN still reads from old_location. The only way to avoid that would be deleting all files from \\old_location\FULL ?
    2. The message "failover to piece handle=D:\new_location\...." indicates that that file is not usefull? I just copy them from old_location to new_location... how can they get useless?
    I suspect there is something in controlfile that redirects to \\old_location\FULL\ and doesn't let to read from D:\new_location\Is this a cold backup? Did you change the location of control file in your PFILE or is it still pointing to old location?
    You may want to check the output of RESTORE DATABASE PREVIEW command, which will just report which backup files it uses without actually restoring thhe DB.

Maybe you are looking for

  • Why i can't open adf.ly window?

    i don't understand with my mozilla, every time i open this site "adf.ly" it didn't work. there is always a words like this appear in my mozilla window 'Firefox can't establish a connection to the server at adf.ly', so what happen with my mozilla? i a

  • Identifying the BW report behind a long-running DIA wp

    Hello - if you see a long running work process in sm66/50...then i can correlate it to the oracle session w/ st04...and then i can see the actual query and explain plan, etc. however, i am having trouble tying this back to the BW "report" which the u

  • Watermarks in Lightroom 4

    Hi. I have Lightroom 4 and was able to get my text watermark to export on my photos until I changed the resolution. Now, even after changing the resolution back, it still won't export the watermark. I've tried deleting and recreating the watermark an

  • Printing playlist cd covers---artwork prints black

    I always create playlists in itunes..... but I haven't in a few months.  I did upgrade itunes, and then went to print my playlist cd cover.... and the title/artist prints, but the area where all the artwork should be, doesn't print, it's just a big b

  • Modify content of Button Choice UI Element in Web Dynpro ABAP

    Hi experts, How can I modify the content of button choice in webdynpro abap ?? ( I want to delete one row  from the list). See the attachement below . Web dynpro component : /SAPSRM/WDC_DODC_PARTNER Cordialy