UNDO Tablespace usage

Hi All,
My undo tablespace is 97% full.
Is there any way to check which process is using more undo tablespace.
Thansk in Advance for your response.
Regards,
Ashwani N.

# UNDO tablespace usage
select a.process, a.program, a.module, a.machine, b.USED_UREC, c.sql_text
from v$sql c, v$session a, v$transaction b
where b.addr = a.taddr
and a.sql_address = c.address
and a.sql_hash_value = c.hash_value
order by b.USED_UREC;
SELECT s.sid , s.username , t.used_ublk
FROM v$transaction t
, v$session s
WHERE 1 = 1
AND t.ses_addr = s.saddr
column username format a15;
column segment_name format a15;
SELECT s.sid , s.username , t.used_ublk, round((t.used_ublk*8)/1024) size_in_MB_8kb_Block_size, round((t.used_ublk*16)/1024
) size_in_MB_16kb_Block_size
FROM v$transaction t
, v$session s
WHERE 1 = 1
AND t.ses_addr = s.saddr;
SELECT distinct rpad(s.sid,3) "SID",S.USERNAME,
E.SEGMENT_NAME,
T.START_TIME "Start",
rpad(T.STATUS,9) "Status",
round((t.used_ublk*8)/1024) "Size(MB)"
--T.USED_UBLK||' Blocks and '||T.USED_UREC||' Records' "Rollback Usage"
FROM DBA_DATA_FILES DF,
DBA_EXTENTS E,
V$SESSION S,
V$TRANSACTION T
WHERE DF.TABLESPACE_NAME = E.TABLESPACE_NAME AND
DF.FILE_ID = UBAFIL AND
S.SADDR = T.SES_ADDR AND
T.UBABLK BETWEEN E.BLOCK_ID AND E.BLOCK_ID+E.BLOCKS AND
E.SEGMENT_TYPE in( 'ROLLBACK','TYPE2 UNDO'source:-
http://blog.contractoracle.com/2008/08/undo-tablespace-usage.html

Similar Messages

  • UNDO-Tablespace-Usage :: "ACTIVE" vs. "USED"

    Hello,
    when I run this
    SELECT SUM(BYTES)/1024/1024/1024 "GB" ,STATUS
    FROM DBA_UNDO_EXTENTS
    GROUP BY STATUS;
    against my database, I get this
    MB STATUS
    ,008789063 UNEXPIRED
    ,094177246 EXPIRED
    *19,7614746* ACTIVE
    But when checking transactions with
    SELECT s.sid , s.username , t.used_ublk*8/1024/1024
    FROM v$transaction t
    , v$session s
    WHERE t.ses_addr = s.saddr;
    I get this
    SID USERNAME T.USED_UBLK*8/1024/1024
    109 TRAM_STAT *6,0405426*
    Where does this difference come from ???
    Regards,
    Mynz

    ACTIVE: transaction running, still need for rollback
    UNEXPIRED: transaction is not running, but still under UNDO_RETENTION period, so still needed.
    EXPIRED: transaction is not running, not under UNDO_RETENTION period. When more extents will be needed for active, this extensts will be overwritten.
    to check, how many undo are using a session, you can execute:
    set pages 100 lines 160
    col sid_serial for a20
    col orauser for a15
    col program for a30
    col undoseg for a15
    col undo for a10
    SELECT TO_CHAR(s.sid)||','||TO_CHAR(s.serial#) sid_serial,
    NVL(s.username, 'None') orauser,
    s.program,
    r.name undoseg,
    t.used_ublk * TO_NUMBER(x.value)/1024||'K' "Undo"
    FROM sys.v_$rollname r,
    sys.v_$session s,
    sys.v_$transaction t,
    sys.v_$parameter x
    WHERE s.taddr = t.addr
    AND r.usn = t.xidusn(+)
    AND x.name = 'db_block_size';

  • Undo tablespace space usage

    I am sorry If someone asked this question before
    Oracle version : 10.2.0.3.0
    OS : Linux
    Tablespace Name           Tablespace Size (in MB)       Used (in MB)       Free (in MB) Pct. Used
    UNDOTBS1                                    2,000              1,826                174        91
    SELECT tablespace_name TSPACE, status, COUNT(*) AS Segments, sum(bytes)/1024/1024 as "TOTAL_SIZE(MB)"
    FROM dba_undo_extents
    GROUP BY tablespace_name, status
    SQL> SQL>   2    3    4
    TSPACE               STATUS                 SEGMENTS TOTAL_SIZE(MB)
    UNDOTBS1             EXPIRED                     464      1825.9375My all undo segments are expired but undo tablespace shows as 91 % used. Is there any workaround for avoiding this?
    Thanks
    Nisanth V.S

    This could be a normal situation: see http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:676925300346249247#711734500346983254. A 2 GB undo tablespace is a small one and I would not worry about having a lot of expired undo segments.
    You can also use V$UNDOSTAT to check undo tablespace usage for the last 7 days.

  • Insert as select - why is it writing so much Undo tablespace data?

    Environment: Oracle 10g R2, Sun solaris, ASM
    I have table A with 92 million rows. Table B, which is identical to table A, has 5 million rows. Table A only has three index columns ( no composite indexes ) and the average row length is 109 bytes.
    I issued the command: insert into A select * from B; in order to append the rows from B to A. This command has been executing for over 4 hours. I've been watching the tablespace usage in EM and I can see the undo tablespace usage grow to over 9 GB's and the query is not finished. Meanwhile, the index tablespace has not grown at all. There is no other activity on this instance.
    I've performed similar inserts in the past and it hasn't taken nearly this long. According to my calculations, writing all of the 5 million rows to Undo would only require about half a gig. Also, we thought there might be a 'ghost' session or process that was causing problems earlier, so we shut everything down and rebooted the server. There is no other activity.
    Could anyone explain why it would write so much undo data? It's almost as if Oracle is making a copy of table A ( 92 million rows ) first.
    Thanks,
    BAH

    Thanks, based on the information from the last two posts, maybe it's starting to make sense. Here is the table ( the column names have been changed to protect the innocent...)
    TABLE A=
    col1 NUMBER not null,
    col2 NUMBER,
    col3 VARCHAR2(15),
    col4 NUMBER,
    col5 NUMBER,
    col6 FLOAT,
    col7 FLOAT,
    col8 FLOAT,
    col9 FLOAT,
    col10 FLOAT,
    col11 FLOAT,
    col12 FLOAT,
    col13 FLOAT,
    col14 NUMBER,
    col15 NUMBER,
    col16 NUMBER,
    col17 FLOAT,
    col18 FLOAT,
    col19 FLOAT,
    col20 NUMBER,
    col21 NUMBER,
    col22 FLOAT,
    col23 NUMBER(17,2),
    col24 NUMBER(17,2),
    col25 NUMBER(13,5),
    col26 NUMBER(13,5),
    col27 NUMBER(13,5),
    col28 NUMBER(13,5),
    col29 NUMBER(13,5),
    col30 VARCHAR2(1),
    col31 VARCHAR2(1),
    col32 VARCHAR2(1),
    col33 NUMBER
    pctfree 10
    initrans 1
    maxtrans 255
    storage
    initial 64K
    minextents 1
    maxextents unlimited
    Column 1 is indexed as the primary key. Columns 2 and 3 have separate indexes. I was not aware of the 'Append' hint - so thanks for that. In researching, I found that if you use the append hint, it places all the rows above the HWM. If not, it looks for places within the tablespace. So, based on the info in post #3, perhaps it is writing all of the used blocks out to undo that are being modified with the insert? My calculation was straight forward ( 109 bytes for row length * 5 million rows ). I knew there would be some overhead, but the undo ts is now over 13.3 GB.
    Thanks for the info.

  • Problem with UNDO tablespace

    Hi guys.
    Our database has 50GB of undo tablespace. I decided to create a second undo tablespace and switch to the new one. Since doing that yesterday, the size of the old undo is 49GB (was thinking that the values will drop to zero) and the new tablespace keeps increasing in size! Its size now is about 20GB. I do have the following question.
    a) If I restart the database, it the value of the old undo going to fall to zero?
    b) undo_retention=86400. Setting this value to a lesser value say 800seconds, it is going to act the performance of the database? Is it going to release the space on the old undo?
    Thanks and any help is appreciated.
    David

    The undo tablespace will not automatically shrink size, since you have a new undo tablespace in place. You can drop the old one if you don't plan to use it.
    Set lower undo_retention will certainly help to contain the undo space usage. However you should query v$undostat and v$rollstat to estimate the amount of undo space required for the current workload then size the undo tablespace accordingly. Turn off the auto extend on undo tablespace.

  • Unable to shrink undo tablespace... Help!

    Hi,
    I have problems to shrink the system undo tablespace, which has grown up to 14 GB.
    I use 9.2. Table space owner is 'SYSTEM', undo_management = AUTO.
    I tried to shrink the greatest rollback segments by the commands
    ALTER SESSION SET UNDO_SUPPRESS_ERRORS = TRUE;
    ALTER ROLLBACK SEGMENT "_SYSSMU6$" SHRINK TO 20 M;
    Oracle confirmed these commands, but nothing happened.
    What am I doing wrong?
    Hermann Mueller

    You have seen the discussion about the undo segments, on the temporary tablespaces, you should be aware that the sort segment of a given temporary tablespace is created at the time the first sort operation takes place. The sort segment continues to grow by means of extent allocation until the segment size has reached the total storage demands of all of the active sorts running on the instance. Oracle will keep on allocating temporary space on demand unless the physical limit states otherwise.
    Temporary segments are produced each time a sort operation (explicit -order by- or implicit -aggregation, reindexing-) requires to sort a set that cannot fit into memory. So if you detect excesive sort usage you should aim your monitors towards the sort operations (reports, reindexing, max, min, aggregations, order by ...). If your system has a DDS behaviour, this kind of operations are frequent as a massive sorting has to be peformed against millions of rows.
    A Temporary tablespace will almost always appear to be near 100% full, that's because once oracle has allocated temporary space it doesn't release it back to the free space, it keeps it allocated even when the sort operation has finished. Criteria behind this fact is similar to the one oracle used to have when the rollback segments were in use, Oracle only allocated space and the dba should perform manual actions to release space, and the criteria is performance. Once it has allocated space this big, there are possibilities that the same circumstances that raised the temporary usage high water mark to this level are repeated, so if oracle keeps the mamimum allocated space, it won't have to allocate the same storage once more.
    Main concern with temporary tablespace growth is not free space itself, but the reasons why this amount of space was allocated, so I suggest you to track the sql statements with sort operations. If you are certain the circumstances that motivated this amount of temporary resources to be allocated won't be repeated again, then you could think of resizing down your temporary tablespace. I suggest you to create a new temporary tablespace with the desired size, and alter the default tempoary tablespace to point to this newly crated temporary tablespace, and finally get rid of the original temporary TS.
    ~ Madrid

  • FLASHBACK OFF FOR UNDO TABLESPACE????

    Hi all
    As my Undo tablespace growing evryday 2 GB & NOW it reached 19,
    Database size is 6GB only
    using Oracle 10g Release 2 without patch Set (release 1002000100) on Hp-Unix OS
    Can i use the Undo tablespace with FLASHBACK OFF option?
    what are the Consequences for Turning off the FLASHBACK,
    Can we use this type of Undo tablespace with Flashback OFF???
    CREATE UNDO TABLESPACE UNDOTBS03 DATAFILE
    '/app/oracle/product/oradata/prod/undotbs03.dbf' SIZE 1000M AUTOEXTEND OFF
    ONLINE
    RETENTION NOGUARANTEE
    BLOCKSIZE 8K
    FLASHBACK OFF;
    THANKS ALOT

    Oracle Flashback Database: feature is similar to conventional point-in-time recovery in its results, allowing you to return a database to its state at a time in the recent past. It is, however, much faster than point-in-time recovery, because it does not require restoration of datafiles from a backup and it requires application of fewer changes from the archived redo logs.
    UNDO  Tablespace: Oracle db save the old value when a process change data in undo tablespace.
    I think that you can change de default UNDO tablespace as NO AUTOEXTEND, and
    Configure
    SET UNDO_MANAGEMENT=AUTO
    SET UNDO_RETENTION= ( second need for logger transaction )
    UNDO_RETENTION specifies (in seconds) the low threshold value of undo retention. For AUTOEXTEND undo tablespaces, the system retains undo for at least the time specified in this parameter, and automatically tunes the undo retention period to satisfy the undo requirements of the queries.
    For fixed- size undo tablespaces, the system automatically tunes for the maximum possible undo retention period, based on undo tablespace size and usage history, and ignores UNDO_RETENTION unless retention guarantee is enabled.

  • Oracle DB : UNDO tablespace filled 99%

    Hi,
    That's not a problem (I hope) but just a question on Livecycle ES DataBase.
    The Undo tablespace set to 4Gb, always filled 99%.
    Is it normal ? is there preconized size for it ? Does we have to maintain it ...
    The LiveCycle configuration is :
    ES (1) version 8.2.1 SP3, Jboss
    Oracle 10g
    The server is running on Windows Server 2003 Ent OS.
    Thank you for your response !

    It very much depends on the tool used to determine the usage of the UNDO tablespace. Many tools do not take into account that the UNDO tablespace and the TEMP tablespace may seem to be full (have correctly formatted blocks) while still having a lot of functional space available inside of those blocks.
    In other words, if the tool calculates the usage in the same way as data tablespaces, it will be reporting the wrong value. Ideally, the UNDO tablespace will always be close to 100% full using traditional calculation.
    Assuming the tool is doing it's calculation correctly, the second thing to note is that UNDO is the core to Oracle Consistent Read mechanism. (Which is, in turn, the core to many of the Flashback techniques.) The UNDO data, which is created at transaction time, must be available after the transaction has committed if a consistent read or flashback is invoked. The more UNDO, the further back in 'time' you can flash back.
    So the correct way to tune the UNDO is to specify the amount of time you require UNDO to exist. And you verify that using the DBA_UNDO_EXTENTS view and the STATUS column. Totally free space in the undo occurs when the STATUS is EXPIRED. If you have no EXPIRED extents, they can not be reused (except in a pinch) and the system will allocate more space to the UNDO tablespace if possible.
    A great reference is the thread at http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:6894817116500
    I am curious - is 4GB UNDO really an issue?

  • While dropping the old undo tablespace we get an error

    Hello friends ,
    i Cannot drop old undo tablespace. While dropping the old undo tablespace we get an error
    ERROR at line 1:
    ORA-01548: active rollback segment '_SYSSMU77$' found, terminate dropping
    tablespace
    SQL> select tablespace_name, status, segment_name from dba_rollback_segs where status != 'OFFLINE';
    TABLESPACE_NAME STATUS SEGMENT_NAME
    SYSTEM ONLINE SYSTEM
    APPS_UNDO NEEDS RECOVERY _SYSSMU77$
    Please help
    Thanks
    Edited by: Vicky C on Dec 23, 2012 9:23 AM

    Hi peter
    We not using rman backup only cold backup.. i tried using cold backup in ramn block media recovery but that recovery needs archive log
    RMAN> BLOCKRECOVER DATAFILE 158 BLOCK 48829;
    Starting blockrecover at 18-DEC-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=437 devtype=DISK
    channel ORA_DISK_1: restoring block(s) from datafile copy /var/undo/undo02.dbf
    starting media recovery
    media recovery failed
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of blockrecover command at 12/18/2012 16:45:11
    ORA-00604: error occurred at recursive SQL level 1
    ORA-01422: exact fetch returns more than requested number of rows
    ORA-00279: change 5975281035000 generated at 12/08/2012 06:00:58 needed for thread 1
    ORA-00289: suggestion : /prod/archlogs/1_465484_683651989.dbf
    ORA-00280: change 5975281035000 for thread 1 is in sequence #465484
    ORA-00278: log file '/prod/archlogs/1_465484_683651989.dbf' no longer needed for this re covery
    we did not have block media recovery needed archivelog
    Regards
    Vignesh C

  • Regarding Maxsize of Undo Tablespace

    Dear expetrs
    While executing a procedure i got error.
    Error In Insertion..ORA-30036: unable to extend segment by 16384 in undo tablesp
    ace 'UNDOTBS1'
    then i increase the size of the Undo Tablespace
    then again i got error.
    ORA-01144: File size (7680000 blocks) exceeds maximum of 4194303 blocks
    plz give me answer as soon as possible.
    thnaks.

    1) resize your datafile to 4194303 * db_block_size
    alter database datafile < path/filename > resize <4194303 * db_block_size> ;
    you find db_block_size by:
    sqlplus /nolog
    SQL> connect / as sysdba
    SQL> show parameter db_block_size
    or by simply have a look in the pfile (init<SID>.ora) in $ORACLE_HOME/dbs
    2) add another file to the undo tablespace:
    SQL>alter tablespace undotbs1 add datafile <path/filename> size <n> M;
    a tablespace may have up to 1022 datafiles.
    hope this helps
    roman

  • Undo tablespace recovery from RMAN backup

    Hi,
    Lets's assume we have RMAN backup and archivelog backups, and now
    my undo tablespace's disk crashed ,how can i recover?
    Can i recover while database is up?
    Thanks,
    Kumar.

    to recover UNDO tablespace from RMAN backup you must shutdown the database and start it in the MOUNT state to recover the missing files as follows
    rman target /
    RUN
    STARTUP MOUNT;
    ALLOCATE CHANNEL ch3 TYPE Disk;
    RESTORE datafile 'c:\u01\prod3\undo01.dbf';
    RECOVER datafile 'c:\u01\prod3\undo01.dbf';
    ALTER DATABASE OPEN;
    RELEASE CHANNEL ch3;
    hope this will help you

  • UNDO tablespace corrupted

    Hi!
    I have been having problems for the past couple days with restarting my database. For some reason when I shutdown, once I start it up again the undo tablespaces is offline and needs to be recovered. When the application tries to connect to the database it gives a "ora-01552 : cannot use system rollback segment for non-system tablespace." I do a recover on that tablespace and bring it back up, and it works fine... until the next restart.. Would anyone have an idea on what's the problem, and what I can do to fix it once and for all?
    Thanks
    Yazil Santoyo

    did you try metalink, there are lot of options / suggestions for your particular error.
    Is your database in Auto undo mode or manual undo?
    Thanks
    Gopal

  • ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type

    OS Version : AIX 6.1
    DB Version : 11.2.0.1
    I am duplicating database and got below error:
    contents of Memory Script:
       Alter clone database open resetlogs;
    executing Memory Script
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: fatal error during execution of command
    RMAN-10041: Could not re-create polling channel context following failure.
    RMAN-10024: error setting up for rpc polling
    RMAN-10005: error opening cursor
    RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
    RMAN-03002: failure of Duplicate Db command at 02/16/2013 17:20:02
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
    Process ID: 44040326
    Session ID: 65 Serial number: 3
    Error is because in target database undo tablespace is UNDOTBS_NEW and in auxiliary database undo tablespace name in init file is UNDOTBS. I followed the meatlink doc 433992.1 which suggest following steps to recover from above error:
    1) edit the parameter UNDO_MANAGEMENT to "MANUAL"
    2) start database again
    3) drop the UNDO tablespace
    4) recreate UNDO tablespace which matches to name in init file.
    5) shutdown & start DB again.
    Now, i edited init file and tried to start DB and got following error:
    oracore@cph-core-db01-s $ sqlplus /nolog
    SQL*Plus: Release 11.2.0.1.0 Production on Sat Feb 16 17:22:11 2013
    Copyright (c) 1982, 2009, Oracle.  All rights reserved.
    SQL> conn sys as sysdba
    Enter password:
    Connected to an idle instance.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 4275781632 bytes
    Fixed Size                  2213632 bytes
    Variable Size             822085888 bytes
    Database Buffers         3439329280 bytes
    Redo Buffers               12152832 bytes
    Database mounted.
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '/u04/oradata/CORE/CORE_DUP/system01.dbf'I don't want to run duplicate command with correct UNDO tablespace name. Any other work around for this ?

    STARTUP MOUNT
    RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
    CANCEL
    ALTER DATABASE OPEN RESETLOGS
    Above option is not working for CORE_DUP, i am getting very strange error, while trying to recover i am getting very strange error as below:
    oracore@cph-core-db01-s $ export ORACLE_SID=CORE_DUP
    SQL*Plus: Release 11.2.0.1.0 Production on Mon Feb 18 11:17:25 2013
    Copyright (c) 1982, 2009, Oracle.  All rights reserved.
    SQL> conn sys as sysdba
    Enter password:
    Connected to an idle instance.
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area 4275781632 bytes
    Fixed Size                  2213632 bytes
    Variable Size             822085888 bytes
    Database Buffers         3439329280 bytes
    Redo Buffers               12152832 bytes
    Database mounted.
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery
    SQL> recover database using backup controlfile until cancel;
    ORA-00283: recovery session canceled due to errors
    ORA-16433: The database must be opened in read/write mode.Primary database initfile:
    event="10298 trace name context forever, level 32"
    db_block_size=8192
    db_file_multiblock_read_count=16
    open_cursors=300
    db_name=CORE
    cursor_sharing='SIMILAR'
    global_names=FALSE
    diagnostic_dest=/u01/app/oracore/diag/CORE
    #background_dump_dest=/u01/app/oracore/diag/rdbms/bdump
    #core_dump_dest=/u01/app/oracore/diag/rdbms/cdump
    #user_dump_dest=/u01/app/oracore/diag/rdbms/udump
    control_files=("/u01/oradata/CORE/control01.ctl", "/u02/oradata/CORE/control02.ctl", "/u03/oradata/CORE/control03.ctl")
    log_archive_dest_1='LOCATION=/u05/oradata/CORE/'
    log_archive_format='CORE_%s%t%r.ARC'
    job_queue_processes=10
    compatible=11.2.0.1
    processes=150
    fast_start_mttr_target=300
    filesystemio_options='SETALL'
    pga_aggregate_target=500M
    recyclebin='OFF'
    remote_login_passwordfile='EXCLUSIVE'
    session_cached_cursors=100
    sga_target=4G
    undo_management='AUTO'
    undo_tablespace='UNDOTBS_NEW'
    nls_date_format='DD-MON-RRRR'
    nls_length_semantics='CHAR'initfile for CORE_DUP
    event="10298 trace name context forever, level 32"
    db_block_size=8192
    db_file_multiblock_read_count=16
    open_cursors=300
    db_name=CORE_DUP
    cursor_sharing='SIMILAR'
    global_names=FALSE
    diagnostic_dest=/u01/app/oracore/diag/CORE/CORE_DUP
    control_files=("/u01/oradata/CORE/CORE_DUP/control01.ctl", "/u02/oradata/CORE/CORE_DUP/control02.ctl", "/u03/oradata/CORE/CORE_DUP/control03.ctl")
    log_archive_dest_1='LOCATION=/u05/oradata/CORE/CORE_DUP/'
    log_archive_format='CORE_DUP%s%t%r.ARC'
    job_queue_processes=10
    compatible=11.2.0.1
    _compression_compatibility="11.2.0"
    processes=150
    fast_start_mttr_target=300
    filesystemio_options='SETALL'
    pga_aggregate_target=500M
    recyclebin='OFF'
    remote_login_passwordfile='EXCLUSIVE'
    session_cached_cursors=100
    sga_target=4G
    undo_management='AUTO'
    undo_tablespace='UNDOTBS'
    nls_date_format='DD-MON-RRRR'
    nls_length_semantics='CHAR'
    log_file_name_convert='/CORE','/CORE/CORE_DUP'
    db_file_name_convert='/CORE','/CORE/CORE_DUP'Duplicate steps are as:
    oracore@cph-core-db01-s $ rman target sys/zzzz@core catalog rmantst10/zzzzz@catdb auxiliary /
    Recovery Manager: Release 11.2.0.1.0 - Production on Mon Feb 18 15:50:00 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: CORE (DBID=913972022)
    connected to recovery catalog database
    connected to auxiliary database: CORE_DUP (not mounted)
    RMAN> duplicate target database to CORE_DUP;
    Starting Duplicate Db at 18-FEB-13
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=96 device type=DISK
    allocated channel: ORA_AUX_DISK_2
    channel ORA_AUX_DISK_2: SID=127 device type=DISK
    contents of Memory Script:
       sql clone "create spfile from memory";
    executing Memory Script
    sql statement: create spfile from memory
    contents of Memory Script:
       shutdown clone immediate;
       startup clone nomount;
    executing Memory Script
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area    4275781632 bytes
    Fixed Size                     2213632 bytes
    Variable Size                838863104 bytes
    Database Buffers            3422552064 bytes
    Redo Buffers                  12152832 bytes
    contents of Memory Script:
       sql clone "alter system set  db_name =
    ''CORE'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
       sql clone "alter system set  db_unique_name =
    ''CORE_DUP'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
       shutdown clone immediate;
       startup clone force nomount
       restore clone primary controlfile;
       alter clone database mount;
    executing Memory Script
    sql statement: alter system set  db_name =  ''CORE'' comment= ''Modified by RMAN duplicate'' scope=spfile
    sql statement: alter system set  db_unique_name =  ''CORE_DUP'' comment= ''Modified by RMAN duplicate'' scope=spfile
    Oracle instance shut down
    Oracle instance started
    Total System Global Area    4275781632 bytes
    Fixed Size                     2213632 bytes
    Variable Size                838863104 bytes
    Database Buffers            3422552064 bytes
    Redo Buffers                  12152832 bytes
    Starting restore at 18-FEB-13
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=96 device type=DISK
    allocated channel: ORA_AUX_DISK_2
    channel ORA_AUX_DISK_2: SID=127 device type=DISK
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: restoring control file
    channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5fo246k3_175_1
    channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5fo246k3_175_1 tag=LEVEL1
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
    output file name=/u01/oradata/CORE/CORE_DUP/control01.ctl
    output file name=/u02/oradata/CORE/CORE_DUP/control02.ctl
    output file name=/u03/oradata/CORE/CORE_DUP/control03.ctl
    Finished restore at 18-FEB-13
    database mounted
    contents of Memory Script:
       set until scn  1217601;
       set newname for datafile  1 to
    "/u04/oradata/CORE/CORE_DUP/system01.dbf";
       set newname for datafile  2 to
    "/u04/oradata/CORE/CORE_DUP/sysaux01.dbf";
       set newname for datafile  4 to
    "/u04/oradata/CORE/CORE_DUP/users01.dbf";
       set newname for datafile  5 to
    "/u04/oradata/CORE/CORE_DUP/users02.dbf";
       set newname for datafile  6 to
    "/u04/oradata/CORE/CORE_DUP/users03.dbf";
       set newname for datafile  9 to
    "/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf";
       restore
       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 18-FEB-13
    using channel ORA_AUX_DISK_1
    using channel ORA_AUX_DISK_2
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_AUX_DISK_1: restoring datafile 00004 to /u04/oradata/CORE/CORE_DUP/users01.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00005 to /u04/oradata/CORE/CORE_DUP/users02.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00006 to /u04/oradata/CORE/CORE_DUP/users03.dbf
    channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L0_CORE_16022013_55o246fe_165_1
    channel ORA_AUX_DISK_2: starting datafile backup set restore
    channel ORA_AUX_DISK_2: specifying datafile(s) to restore from backup set
    channel ORA_AUX_DISK_2: restoring datafile 00001 to /u04/oradata/CORE/CORE_DUP/system01.dbf
    channel ORA_AUX_DISK_2: restoring datafile 00002 to /u04/oradata/CORE/CORE_DUP/sysaux01.dbf
    channel ORA_AUX_DISK_2: restoring datafile 00009 to /u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
    channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/DF_L0_CORE_16022013_56o246fe_166_1
    channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/DF_L0_CORE_16022013_56o246fe_166_1 tag=LEVEL0
    channel ORA_AUX_DISK_2: restored backup piece 1
    channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:01:15
    channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L0_CORE_16022013_55o246fe_165_1 tag=LEVEL0
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:35
    Finished restore at 18-FEB-13
    contents of Memory Script:
       switch clone datafile all;
    executing Memory Script
    datafile 1 switched to datafile copy
    input datafile copy RECID=24 STAMP=807724355 file name=/u04/oradata/CORE/CORE_DUP/system01.dbf
    datafile 2 switched to datafile copy
    input datafile copy RECID=25 STAMP=807724355 file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf
    datafile 4 switched to datafile copy
    input datafile copy RECID=26 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users01.dbf
    datafile 5 switched to datafile copy
    input datafile copy RECID=27 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users02.dbf
    datafile 6 switched to datafile copy
    input datafile copy RECID=28 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users03.dbf
    datafile 9 switched to datafile copy
    input datafile copy RECID=29 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
    contents of Memory Script:
       set until scn  1217601;
       recover
       clone database
        delete archivelog
    executing Memory Script
    executing command: SET until clause
    Starting recover at 18-FEB-13
    using channel ORA_AUX_DISK_1
    using channel ORA_AUX_DISK_2
    channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    destination for restore of datafile 00001: /u04/oradata/CORE/CORE_DUP/system01.dbf
    destination for restore of datafile 00002: /u04/oradata/CORE/CORE_DUP/sysaux01.dbf
    destination for restore of datafile 00009: /u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
    channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5eo246k2_174_1
    channel ORA_AUX_DISK_2: starting incremental datafile backup set restore
    channel ORA_AUX_DISK_2: specifying datafile(s) to restore from backup set
    destination for restore of datafile 00004: /u04/oradata/CORE/CORE_DUP/users01.dbf
    destination for restore of datafile 00005: /u04/oradata/CORE/CORE_DUP/users02.dbf
    destination for restore of datafile 00006: /u04/oradata/CORE/CORE_DUP/users03.dbf
    channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5do246k2_173_1
    channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5eo246k2_174_1 tag=LEVEL1
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
    channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5do246k2_173_1 tag=LEVEL1
    channel ORA_AUX_DISK_2: restored backup piece 1
    channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:00:01
    starting media recovery
    archived log for thread 1 with sequence 1718 is already on disk as file /u05/oradata/CORE/CORE_17181807276264.ARC
    archived log for thread 1 with sequence 1719 is already on disk as file /u05/oradata/CORE/CORE_17191807276264.ARC
    archived log for thread 1 with sequence 1720 is already on disk as file /u05/oradata/CORE/CORE_17201807276264.ARC
    archived log for thread 1 with sequence 1721 is already on disk as file /u05/oradata/CORE/CORE_17211807276264.ARC
    archived log for thread 1 with sequence 1722 is already on disk as file /u05/oradata/CORE/CORE_17221807276264.ARC
    archived log for thread 1 with sequence 1723 is already on disk as file /u05/oradata/CORE/CORE_17231807276264.ARC
    archived log for thread 1 with sequence 1724 is already on disk as file /u05/oradata/CORE/CORE_17241807276264.ARC
    archived log for thread 1 with sequence 1725 is already on disk as file /u05/oradata/CORE/CORE_17251807276264.ARC
    archived log for thread 1 with sequence 1726 is already on disk as file /u05/oradata/CORE/CORE_17261807276264.ARC
    archived log for thread 1 with sequence 1727 is already on disk as file /u05/oradata/CORE/CORE_17271807276264.ARC
    archived log for thread 1 with sequence 1728 is already on disk as file /u05/oradata/CORE/CORE_17281807276264.ARC
    archived log for thread 1 with sequence 1729 is already on disk as file /u05/oradata/CORE/CORE_17291807276264.ARC
    archived log for thread 1 with sequence 1730 is already on disk as file /u05/oradata/CORE/CORE_17301807276264.ARC
    archived log for thread 1 with sequence 1731 is already on disk as file /u05/oradata/CORE/CORE_17311807276264.ARC
    archived log for thread 1 with sequence 1732 is already on disk as file /u05/oradata/CORE/CORE_17321807276264.ARC
    archived log for thread 1 with sequence 1733 is already on disk as file /u05/oradata/CORE/CORE_17331807276264.ARC
    archived log for thread 1 with sequence 1734 is already on disk as file /u05/oradata/CORE/CORE_17341807276264.ARC
    archived log for thread 1 with sequence 1735 is already on disk as file /u05/oradata/CORE/CORE_17351807276264.ARC
    archived log for thread 1 with sequence 1736 is already on disk as file /u05/oradata/CORE/CORE_17361807276264.ARC
    archived log for thread 1 with sequence 1737 is already on disk as file /u05/oradata/CORE/CORE_17371807276264.ARC
    archived log for thread 1 with sequence 1738 is already on disk as file /u05/oradata/CORE/CORE_17381807276264.ARC
    archived log for thread 1 with sequence 1739 is already on disk as file /u05/oradata/CORE/CORE_17391807276264.ARC
    archived log for thread 1 with sequence 1740 is already on disk as file /u05/oradata/CORE/CORE_17401807276264.ARC
    archived log for thread 1 with sequence 1741 is already on disk as file /u05/oradata/CORE/CORE_17411807276264.ARC
    archived log for thread 1 with sequence 1742 is already on disk as file /u05/oradata/CORE/CORE_17421807276264.ARC
    archived log for thread 1 with sequence 1743 is already on disk as file /u05/oradata/CORE/CORE_17431807276264.ARC
    archived log for thread 1 with sequence 1744 is already on disk as file /u05/oradata/CORE/CORE_17441807276264.ARC
    channel ORA_AUX_DISK_1: starting archived log restore to default destination
    channel ORA_AUX_DISK_1: restoring archived log
    archived log thread=1 sequence=1710
    channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/ARC_1HR_CORE_16022013_5jo24jp8_179_1
    channel ORA_AUX_DISK_2: starting archived log restore to default destination
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1711
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1712
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1713
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1714
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1715
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1716
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1717
    channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/ARC_1HR_CORE_18022013_5ko296uf_180_1
    channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/ARC_1HR_CORE_16022013_5jo24jp8_179_1 tag=ARC_1HR
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17101807276264.ARC thread=1 sequence=1710
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17101807276264.ARC RECID=3041 STAMP=807724360
    channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/ARC_1HR_CORE_18022013_5ko296uf_180_1 tag=ARC_1HR
    channel ORA_AUX_DISK_2: restored backup piece 1
    channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:00:08
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17111807276264.ARC thread=1 sequence=1711
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17111807276264.ARC RECID=3042 STAMP=807724362
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17121807276264.ARC thread=1 sequence=1712
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17121807276264.ARC RECID=3043 STAMP=807724363
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17131807276264.ARC thread=1 sequence=1713
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17131807276264.ARC RECID=3044 STAMP=807724367
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17141807276264.ARC thread=1 sequence=1714
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17141807276264.ARC RECID=3048 STAMP=807724367
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17151807276264.ARC thread=1 sequence=1715
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17151807276264.ARC RECID=3046 STAMP=807724367
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17161807276264.ARC thread=1 sequence=1716
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17161807276264.ARC RECID=3045 STAMP=807724367
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17171807276264.ARC thread=1 sequence=1717
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17171807276264.ARC RECID=3047 STAMP=807724367
    archived log file name=/u05/oradata/CORE/CORE_17181807276264.ARC thread=1 sequence=1718
    archived log file name=/u05/oradata/CORE/CORE_17191807276264.ARC thread=1 sequence=1719
    archived log file name=/u05/oradata/CORE/CORE_17201807276264.ARC thread=1 sequence=1720
    archived log file name=/u05/oradata/CORE/CORE_17211807276264.ARC thread=1 sequence=1721
    archived log file name=/u05/oradata/CORE/CORE_17221807276264.ARC thread=1 sequence=1722
    archived log file name=/u05/oradata/CORE/CORE_17231807276264.ARC thread=1 sequence=1723
    archived log file name=/u05/oradata/CORE/CORE_17241807276264.ARC thread=1 sequence=1724
    archived log file name=/u05/oradata/CORE/CORE_17251807276264.ARC thread=1 sequence=1725
    archived log file name=/u05/oradata/CORE/CORE_17261807276264.ARC thread=1 sequence=1726
    archived log file name=/u05/oradata/CORE/CORE_17271807276264.ARC thread=1 sequence=1727
    archived log file name=/u05/oradata/CORE/CORE_17281807276264.ARC thread=1 sequence=1728
    archived log file name=/u05/oradata/CORE/CORE_17291807276264.ARC thread=1 sequence=1729
    archived log file name=/u05/oradata/CORE/CORE_17301807276264.ARC thread=1 sequence=1730
    archived log file name=/u05/oradata/CORE/CORE_17311807276264.ARC thread=1 sequence=1731
    archived log file name=/u05/oradata/CORE/CORE_17321807276264.ARC thread=1 sequence=1732
    archived log file name=/u05/oradata/CORE/CORE_17331807276264.ARC thread=1 sequence=1733
    archived log file name=/u05/oradata/CORE/CORE_17341807276264.ARC thread=1 sequence=1734
    archived log file name=/u05/oradata/CORE/CORE_17351807276264.ARC thread=1 sequence=1735
    archived log file name=/u05/oradata/CORE/CORE_17361807276264.ARC thread=1 sequence=1736
    archived log file name=/u05/oradata/CORE/CORE_17371807276264.ARC thread=1 sequence=1737
    archived log file name=/u05/oradata/CORE/CORE_17381807276264.ARC thread=1 sequence=1738
    archived log file name=/u05/oradata/CORE/CORE_17391807276264.ARC thread=1 sequence=1739
    archived log file name=/u05/oradata/CORE/CORE_17401807276264.ARC thread=1 sequence=1740
    archived log file name=/u05/oradata/CORE/CORE_17411807276264.ARC thread=1 sequence=1741
    archived log file name=/u05/oradata/CORE/CORE_17421807276264.ARC thread=1 sequence=1742
    archived log file name=/u05/oradata/CORE/CORE_17431807276264.ARC thread=1 sequence=1743
    archived log file name=/u05/oradata/CORE/CORE_17441807276264.ARC thread=1 sequence=1744
    media recovery complete, elapsed time: 00:00:33
    Finished recover at 18-FEB-13
    contents of Memory Script:
       shutdown clone immediate;
       startup clone nomount;
       sql clone "alter system set  db_name =
    ''CORE_DUP'' comment=
    ''Reset to original value by RMAN'' scope=spfile";
       sql clone "alter system reset  db_unique_name scope=spfile";
       shutdown clone immediate;
       startup clone nomount;
    executing Memory Script
    database dismounted
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area    4275781632 bytes
    Fixed Size                     2213632 bytes
    Variable Size                838863104 bytes
    Database Buffers            3422552064 bytes
    Redo Buffers                  12152832 bytes
    sql statement: alter system set  db_name =  ''CORE_DUP'' comment= ''Reset to original value by RMAN'' scope=spfile
    sql statement: alter system reset  db_unique_name scope=spfile
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area    4275781632 bytes
    Fixed Size                     2213632 bytes
    Variable Size                838863104 bytes
    Database Buffers            3422552064 bytes
    Redo Buffers                  12152832 bytes
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CORE_DUP" RESETLOGS ARCHIVELOG
      MAXLOGFILES     32
      MAXLOGMEMBERS      4
      MAXDATAFILES      500
      MAXINSTANCES     1
      MAXLOGHISTORY     2298
    LOGFILE
      GROUP  1 ( '/u02/oradata/CORE/CORE_DUP/redo01a.log', '/u03/oradata/CORE/CORE_DUP/redo01b.log' ) SIZE 10 M  REUSE,
      GROUP  2 ( '/u02/oradata/CORE/CORE_DUP/redo02a.log', '/u03/oradata/CORE/CORE_DUP/redo02b.log' ) SIZE 10 M  REUSE,
      GROUP  3 ( '/u02/oradata/CORE/CORE_DUP/redo03a.log', '/u03/oradata/CORE/CORE_DUP/redo03b.log' ) SIZE 10 M  REUSE
    DATAFILE
      '/u04/oradata/CORE/CORE_DUP/system01.dbf'
    CHARACTER SET AL32UTF8
    contents of Memory Script:
       set newname for tempfile  1 to
    "/u04/oradata/CORE/CORE_DUP/temp01.dbf";
       switch clone tempfile all;
       catalog clone datafilecopy  "/u04/oradata/CORE/CORE_DUP/sysaux01.dbf",
    "/u04/oradata/CORE/CORE_DUP/users01.dbf",
    "/u04/oradata/CORE/CORE_DUP/users02.dbf",
    "/u04/oradata/CORE/CORE_DUP/users03.dbf",
    "/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf";
       switch clone datafile all;
    executing Memory Script
    executing command: SET NEWNAME
    renamed tempfile 1 to /u04/oradata/CORE/CORE_DUP/temp01.dbf in control file
    cataloged datafile copy
    datafile copy file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf RECID=1 STAMP=807724423
    cataloged datafile copy
    datafile copy file name=/u04/oradata/CORE/CORE_DUP/users01.dbf RECID=2 STAMP=807724423
    cataloged datafile copy
    datafile copy file name=/u04/oradata/CORE/CORE_DUP/users02.dbf RECID=3 STAMP=807724423
    cataloged datafile copy
    datafile copy file name=/u04/oradata/CORE/CORE_DUP/users03.dbf RECID=4 STAMP=807724423
    cataloged datafile copy
    datafile copy file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf RECID=5 STAMP=807724423
    datafile 2 switched to datafile copy
    input datafile copy RECID=1 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf
    datafile 4 switched to datafile copy
    input datafile copy RECID=2 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users01.dbf
    datafile 5 switched to datafile copy
    input datafile copy RECID=3 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users02.dbf
    datafile 6 switched to datafile copy
    input datafile copy RECID=4 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users03.dbf
    datafile 9 switched to datafile copy
    input datafile copy RECID=5 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
    contents of Memory Script:
       Alter clone database open resetlogs;
    executing Memory Script
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: fatal error during execution of command
    RMAN-10041: Could not re-create polling channel context following failure.
    RMAN-10024: error setting up for rpc polling
    RMAN-10005: error opening cursor
    RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
    RMAN-03002: failure of Duplicate Db command at 02/18/2013 15:53:50
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
    Process ID: 3670170
    Session ID: 33 Serial number: 7
    oracore@cph-core-db01-s $

  • Tablespace usage report generated with html tags instead of text

    Hi ,
    We have a unix shell script scheduled to find tablespace usage and sends the report to our mail id.
    For the past few weeks(no changes idone in the script) the report is coming with html tags instead of text as below.
    </head>
    <body>
    <p>
    <table border='1' width='90%' align='center' summary='Script output'>
    <tr>
    <th scope="col">
    TABLESPACE_NAME
    </th>
    <th scope="col">
    CUR_USE_MB
    </th>
    <th scope="col">
    CUR_SZ_MB
    </th>
    <th scope="col">
    CUR_PRCT_FULL
    </th>
    <th scope="col">
    FREE_SPACE_MB
    </th>
    <th scope="col">
    MAX_SZ_MB
    </th>
    <th scope="col">
    OVERALL_PRCT_FULL
    </th>
    </tr>
    <tr>
    <td>
    SYSTEM
    </td>
    <td align="right">
    268
    </td>
    <td align="right">
    500
    </td>
    <td align="right">
    54
    </td>
    Is this any settings issue or anything to be modified in the script.Could you please reply..
    Regards,
    Bharath.
    Edited by: 870384 on Jul 6, 2011 1:17 AM

    Hi Sven W,
    Please find the sql below that is generating the tablespace usage report. In the staring of the script markup is set to ON and at the end it is set to OFF.Do you suggest any changes to this..?
    SET ECHO OFF
    SET PAGES 999
    SET MARKUP HTML ON SPOOL ON
    col tablespace_name format a15 trunc
    col cur_use_mb for 999999999
    col cur_sz_mb for 999999999
    col free_space_mb for 999999999
    col max_sz_mb for 999999999
    compute sum of cur_use_mb on report
    compute sum of cur_sz_mb on report
    compute sum of free_space_mb on report
    compute sum of max_sz_mb on report
    break on report
    spool tablespace.html
    select tablespace_name,
    round(sum(total_mb)-sum(free_mb),2) cur_use_mb,
    round(sum(total_mb),2) cur_sz_mb,
    round((sum(total_mb)-sum(free_mb))/sum(total_mb)*100) cur_prct_full,
    round(sum(max_mb) - (sum(total_mb)-sum(free_mb)),2) free_space_mb,
    round(sum(max_mb),2) max_sz_mb,
    round((sum(total_mb)-sum(free_mb))/sum(max_mb)*100) overall_prct_full
    from (select tablespace_name,sum(bytes)/1024/1024 free_mb,0 total_mb,0 max_mb from DBA_FREE_SPACE group by tablespace_name
    union select tablespace_name,0 current_mb,sum(bytes)/1024/1024 total_mb,sum(decode(maxbytes, 0, bytes, maxbytes))/1024/1024 max_mb
    from DBA_DATA_FILES group by tablespace_name) a group by tablespace_name;
    select owner,segment_name,segment_type,bytes/(1024*1024) size_m
    from dba_segments
    where tablespace_name = 'SYSTEM' and segment_name='FGA_LOG$' order by size_m desc;
    spool off;
    SET MARKUP HTML OFF SPOOL OFF

  • How to recover undo tablespace in 9i

    How can i recover undo tablespace 9i.Can any provide step by step recovery process

    Doc ID 94114.1 on Metalink might be of interest to you

Maybe you are looking for

  • Adding a 2nd iPhone - 1 Apple ID or 2?

    Hey folks: I've done a fair bit of searching on this, but I still have some unanswered questions.  I have a 16GB iPhone 4 and we just ordered my wife an 8GB iPhone 4.  (We also have an iPad 2 in the household).  I'm probably going to start by just us

  • How do I start over with my mac book pro

    I used disk utility and found my hard drive to be corrupt. How do I start over and clean this up?

  • "There are no photos in this library."

    I recently upgraded to WIndows 7 Home Premium, updated my Apple TV to 3.0 and then 3.0.1. I am using iTunes 9.0.2. I can no longer stream photos to my television. I get a message that my library is loading and then "There are no photos in this librar

  • SD document clarification

    Please tell me if my understanding is correct. Please correct me. Thank you. 1. Open SO (Sales Order) are those which has no delivery order yet. to do this: use VA01 2. Open DO (Delivery Order) are those which goods are not actually delivered yet or

  • Problem getting music from Ipod to Itunes

    I have a 2nd Gen Nano and recently had to reinstall my operating system (Windows XP), which required me to back up my music. I had no external HD at the time and not enough discs so I sync'd my Ipod and stored all 812 songs to my 4GB Ipod. Now that I