Undo tablespace grew 15GB +

Hi Guys,
During one of the processes my UNDO tablespace grew to 15GB(reached it's limit) and it keeps growing. I have made the size to 20GB and it going to fill that too. Can someone suggest a way to fix this issue? Can I create a new TS and drop the old one something like this:
CREATE SMALLFILE UNDO TABLESPACE "UNDOTBS2" DATAFILE 'D:\ORACLE\ORADATA\NGS1\UNDOTBS02.DBF' SIZE 200M REUSE
alter system set undo_tablespace = undotbs2
DROP TABLESPACE UNDOTBS1
If I drop the old UNDO tablespace do I have to follow some prerequisite for example set undo_retention=0 etc. Please let me know.
Thanks

Hello,
Even if the transaction is commited the Undo Tablespace can keep Undo records ( you have the
parameter undo_retention ).
When you create a new Undo tablespace then, you have to switch the database to it by
using the parameter undo_tablespace.
This is a dynamic parameter but, I use to restart the database so as to be sure that the old
undo tablespace is not used anymore. So that I can drop it.
Of course the database should be shutdown cleanly so that there's no transaction to rollback when
you start it up.
Best regards,
Jean-Valentin

Similar Messages

  • Cannot shrink the undo tablespace

    Hello!
    I have run a very long procedure, which generated 15GB undo information. Now I can see in the enterprise manager, that the undo tablespace is empty again. I tried to resize the datafile, but I receive "*ORA-03297*: file contains used data beyond requested RESIZE value". How can I shrink the tablespace without dropping and recreating it?
    I tried also
    purge recyclebin;
    I still get ORA-03297 if I try to resize the datafile.
    I wanted to try something like
    ALTER TABLE xxxxx UNALLOCATE UNUSED;
    or
    ALTER TABLE xxxxx SHRINK SPACE;
    but are there any tables that save the undo information?
    Regards.

    Hi
    well, my transaction is ready! The undo tablespace has not more that 10M of information, the other 15G are free!
    Thanks for the answers, it seems that i still have recreate it ...
    Well, another quertion:
    Is it possible, that I just have to wait longer before I resize the undo data file? I have just succeeded in resizing the data file to 7 GB. I really wish I could shrink it to 100M or so, but still - from 15G to 7G is a lot better! 2 hours ago this action was not possible. Is it some automatic management, that needs to time-out before I can shrink the undo tablespace?
    Edited by: user10962462 on Apr 8, 2009 2:39 AM

  • Undo tablespace growing without reusing space

    Hi,
    I'm running an Oracle9i database on Solaris. I am using the automatic undo management and I have one undo tablespace. The UNDO_RETENTION value is 900. I have created the undo tablespace this way (clause in create database statement):
    UNDO TABLESPACE "UNDOTBS1" DATAFILE '/u04/oracle/oradata/my_dbname/undotbs01.dbf' SIZE 200M REUSE AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
    The undo tablespace datafile is now close to 3G. I have other servers running the same setup, and their undo datafile size is still 200M. There is currently no active transaction in the database. Any idea why this is happening? Is there any tables I can check for clues?
    Many thanks,
    Gloria

    Should Oracle automatically shrink the undo tablespace (datafile) when it is not needed anymore? Say at one point the database really needs 3G of undo tablespace, but afterwards only 10M is needed, would the datafile be 'shrunk' back?
    Also, how can I check if the database really needed the 3G of undo tablespace at one point? (I guess it's checking the level of activities in the database, but how do I do that for past data?)
    I'm trying to decide whether the undo tablespace really grew due to a need at some point or is it a case of Bug 2660394 (documented in metalink note271119.1). The bug basically says that "An auto extensible undo tablespace MAY grow before reusing expired extents leading to more space use than actually needed".

  • 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 $

  • 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.

  • 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

  • Select data from undo tablespace?

    Hi all,
    Can i select data from undo segments in undo tablespace?
    Thank you.
    Dan.

    This sort of thing could be considered to be selecting from an undo segment:orcl> select count(*) from emp;
      COUNT(*)
            14
    orcl> delete from emp;
    14 rows deleted.
    orcl> commit;
    Commit complete.
    orcl> select * from emp as of timestamp(sysdate - 5/1440);
         EMPNO ENAME      JOB              MGR HIREDATE                 SAL       COMM     DEPTNO
          7369 SMITH      CLERK           7902 17-12-80 00:00:00        800                    20
          7499 ALLEN      SALESMAN        7698 20-02-81 00:00:00       1600        300         30
          7521 WARD       SALESMAN        7698 22-02-81 00:00:00       1250        500         30
          7566 JONES      MANAGER         7839 02-04-81 00:00:00       2975                    20
          7654 MARTIN     SALESMAN        7698 28-09-81 00:00:00       1250       1400         30
          7698 BLAKE      MANAGER         7839 01-05-81 00:00:00       2850                    30
          7782 CLARK      MANAGER         7839 09-06-81 00:00:00       2450                    10
          7788 SCOTT      ANALYST         7566 19-04-87 00:00:00       3000                    20
          7839 KING       PRESIDENT            17-11-81 00:00:00       5000                    10
          7844 TURNER     SALESMAN        7698 08-09-81 00:00:00       1500          0         30
          7876 ADAMS      CLERK           7788 23-05-87 00:00:00       1100                    20
          7900 JAMES      CLERK           7698 03-12-81 00:00:00        950                    30
          7902 FORD       ANALYST         7566 03-12-81 00:00:00       3000                    20
          7934 MILLER     CLERK           7782 23-01-82 00:00:00       1300                    10
    14 rows selected.
    orcl>

  • Is there so call "dedicated" UNDO tablespace in Oracle 9i and higher?

    Since one of our applicaions needs to process large amounts of data, we have been using a dedicated rollback segment in order to avoid the "snapshot too old" problem.
    Recently our DB upgraded to Oracle 9i and DBA asked us to use "undo" tablespace.
    Based the Oracle 9i Doc., it only allows to select ONE undo tablespace at a time.
    If so, DBA has to make the only UNDO as large as our Cash large transactions
    need(adjust the UNDO_RENTION), which inevitably waste lots of space.
    Does Oracle 9i allow to have one dedicated UNDO tablespace for large transactions while another one for regular transactions just like we use the old rollback segments.
    Thanks in advance

    Why have multiple UNDO tablespaces? You can only use one at a time, and when the other one is not being used, it still consumes storage space.
    Spend a little time determining how much undo you need and size undo tablespace and undo retention around those values and you should be able to resolve the problems you are experiencing now.
    http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96521/undo.htm#9505

  • Error Oracle Mobile ORA-30023 Duplicate undo tablespace specification

    Hi,
    I have the following mobile application (Oracle Mobile 10g R3):
    - Win32 (Forms 6i) App.
    - snapshots (12 updateable, 36 read-only)
    I have a successfully compilation of my form connected to the mobile database. However when I put a value over a textitem, my WHEN-VALIDATE-ITEM trigger send me an error:
    ORA-30023 Duplicate undo tablespace specification
    How can I solve this???, It seems like there is a parameter that I have to change.
    The WHEN-VALIDATE-ITEM trigger only has a basic select over a "readonly" table.
    Please help.
    Regards,
    Santiago

    I think the problem is the following,
    I need to convert a date to julian format, example:
    to_char(sysdate,'j')
    The problem is that it seems like Oracle Mobile connot support this kind format convertion.
    So, How can I get the number of days between 01-jan-4712 BC and other date????
    I found this function TO_DATE('-4712-01-01', 'SYYYY-MM-DD'), but it doesn´t works on Oracle Mobile.
    If someone have any idea about how can I get the number of days between 01-jan-4712 BC and other day without using the format 'SYYYY'......please help

  • Cannot drop old undo tablespace. Cause: active rollback segment

    dear all.
    db: oracle 10.2.0.1
    os: rhel as version 5 64 bits.
    This is a testing database. And my database is online and open. But i can free the external usb disk that contains my ols undotbs.
    I want to drop old undo tablespace but this is not possible.
    1.- In order to open my database i had my datafile( '/mnt/hdext/back_plelds/undotbs02.dbf') offline drop, and then i can to open my database.
    2.- When i try to delete my old undo tablespace im getting this error:
    SQL> drop tablespace undotbs1 including contents and datafiles;
    drop tablespace undotbs1 including contents and datafiles
    ERROR at line 1:
    ORA-01548: active rollback segment '_SYSSMU1$' found, terminate dropping
    tablespace
    3.- My default undo_tablespace is another that i was created before step 1.
    SQL> sho parameter undo_ta
    NAME TYPE VALUE
    undo_tablespace string UNDOTMP
    SQL>
    Well i search in metalink ORA-01548 code error and in 18947.1 doc whows me that the solution is:
    Action: Shut down instances that use the active rollback segments in the
    tablespace and then drop the tablespace.
    4.- I try to shutdown but im getting:
    SQL> shutdown immediate;
    ORA-00376: file 10 cannot be read at this time
    ORA-01110: data file 10: '/mnt/hdext/back_plelds/undotbs02.dbf'
    SQL>
    This /mnt/hdext is an external USB disk and i have all permissions. I exported tables without any problem and i can read all files.
    i search un metalink again ora codes (ORA-00376 ORA-01110) and the doc id: 427801.1 shows in the solution:
    Drop the old undo tablespace instead of making it offline.
    but when i try to drop the tablespace it shows the error describe in the step 2.
    Facts:
    - my tablespace UNDOTBS1 is ONLINE. I put in offline and this is not the solution.
    - This is the status of my rollback segments:
    SQL> select segment_name, status from dba_rollback_segs where
    2 tablespace_name='UNDOTBS1';
    SEGMENT_NAME STATUS
    _SYSSMU1$                      NEEDS RECOVERY
    _SYSSMU2$                      NEEDS RECOVERY
    _SYSSMU3$                      NEEDS RECOVERY
    _SYSSMU4$                      NEEDS RECOVERY
    _SYSSMU5$                      NEEDS RECOVERY
    _SYSSMU6$                      NEEDS RECOVERY
    _SYSSMU7$                      NEEDS RECOVERY
    _SYSSMU8$                      NEEDS RECOVERY
    _SYSSMU9$                      NEEDS RECOVERY
    _SYSSMU10$                     NEEDS RECOVERY
    _SYSSMU11$                     OFFLINE
    SEGMENT_NAME STATUS
    _SYSSMU12$                     OFFLINE
    12 rows selected.
    SQL>
    - I have the note (Unable to drop und tablespace In this article describe the problem but this is not the same. The difference is that i cannot drop the rollback segment that describe in step 2.
    SQL> drop rollback segment "_SYSSMU1$";
    drop rollback segment "_SYSSMU1$"
    ERROR at line 1:
    ORA-30025: DROP segment '_SYSSMU1$' (in undo tablespace) not allowed
    in metalink the doc id: 173696.1 shows the solution:
    Action:     Check the undo segment name and reissue statement if necessary.
    i cannot drop the rollback_segment
    What can i do ???
    thanks a lot.

    in step 4 did you try with shutdown abort?
    If its still does not work then create another new table space with new file and then swtich to that tablespace http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/undo.htm#sthref1504Khurram

  • Cannot drop undo tablespace with Active extents but no active sessions

    Hi all,
    I am running on 10gr2 oracle database in a Linux 32 bit environment.
    I have a corrupted undo datafile. I've been able to recover the datafile but still the alert logs is still showing that it is corrupted.
    Now what I'm trying to do is to drop the old undo tablespace like the one discussed here Change undo tablespace in Oracle - Switch Oracle's Undo tablespace.
    My problem is I have an Active extent but no active session corresponding to it:
    SYS@ccasdb AS SYSDBA > SELECT a.name,b.status
    FROM   v$rollname a,v$rollstat b
    WHERE  a.usn = b.usn
    AND    a.name IN (
                      SELECT segment_name
                      FROM dba_segments
                      WHERE tablespace_name = 'UNDOTBS1'
                     );  2    3    4    5    6    7    8
    NAME                           STATUS
    _SYSSMU18$                     PENDING OFFLINE
    SYS@ccasdb AS SYSDBA > SELECT a.name,b.status , d.username , d.sid , d.serial#
      2  FROM   v$rollname a,v$rollstat b, v$transaction c , v$session d
      3  WHERE  a.usn = b.usn
      4  AND    a.usn = c.xidusn
      5  AND    c.ses_addr = d.saddr
      6  AND    a.name IN (
      7               SELECT segment_name
      8               FROM dba_segments
      9               WHERE tablespace_name = 'UNDOTBS1'
    10              );
    no rows selected
    but still cannot drop the undotablespace.
    SYS@ccasdb AS SYSDBA > drop tablespace UNDOTBS1 including contents and datafiles;
    drop tablespace UNDOTBS1 including contents and datafiles
    ERROR at line 1:
    ORA-30013: undo tablespace 'UNDOTBS1' is currently in use
    Regards,
    Tim

    Yes i was able to recover the datafile but the alert_log kept on prompting that it is still corrupted. The datafile's status is online.
    I want to kill the session/s contributing to the PENDING OFFLINE status of the rollback segment so I can already drop the undotablespace and so
    that the alert log will stop prompting for that corrupted datafile in that UNDOTABLESPACE.
    Can i Just alter the tablespace's datafiles to offline drop then just drop it. Then I drop the tablespace?

Maybe you are looking for