Recreation of undo tablespace

hi
i'm using oracle 9i.whether frequent recreation of undo tablespace is essential.
if yes then what is the purpose
regards

There could be adhoc scenarios when re-creating simplies houskeeping work.
Say you have a day to day application which needs 4GB of undo and your undo tablespace is 5gb. The application will run without any issues. After 3 months say you a quarterly closure or financial year closure and you need to run heavy batch jobs certain other heavy dmls on database and you really dont know how much undo is needed in excess. You simply add further 4gb or leave the datafile to autoextned on to prevent your batch jobs from failing.
After a week your finacial closure is over, undo tablespace has grown to 10GB and for next 3 month you are not going to run that batch job and you will happy with 4gb of undo space.
In such scenario, if you want to release the 6 gb back to operating system , the simple way is to create new undo tablespace with 5gb and make it current and drop the old one.
Hope this explains...

Similar Messages

  • Dropping Undo Tablespace 9i

    Hey Folks,
    I really need some help here.
    I'm trying to drop/recreate the undo tablespace (currently 25gig) Oracle 9i
    When I try to drop the undo tablespace 'UNDOTBS1' I get the following error:
    “ORA-01548: active rollback segment '_SYSSMU1$' found, terminate dropping tablespace”
    Here's what I have tried so far:
    - Bounced the DB several times hoping to get rid of the reference to the active rollback segment. No luck.
    - Created a new undo table space
    - Tried 'Alter system set undo_tablespace=new_one' (noticed that 10 new rollback segs were created '_SYSMU11$..SYSMU20$' pointing to the new undo tablespace)
    - I then performed an offline drop of the undo tablespace data file. After the offline drop, the system rollback segs SYSMU01$..SYSMU10$ went offline as would be expected.
    - Even with the new undo tablespace, all other application tablespaces still use the old undo which due to the offline drop, no inserts, deletes, etc. will work.
    After all the above, I still get the same error when trying to drop the undo tablespace.
    Any ideas? Ideally I would like to be able to drop the undo tablespace and recreate it, but at this point I'd be happy to bring back the undo tablespace datafile so we can at least use the database again.
    Thanks in advance!!
    Colin

    SQL> show parameters undo
    undo_retention integer
    10800
    undo_suppress_errors boolean
    FALSE
    undo_tablespace string
    UNDOTBS03
    r.- The undo tablespace which the database is looking for is this one ( UNDOTBS03 )
    What is strange about the lines above is that I have
    all those params above commented out in my
    \pfile\init.ora file (and have bounced the db).
    I’m not sure why they are still showing up.
    r.- Perhaps your instance is started with the spfile instead of the init file
    Here's what we did after the UNDOTBS1 tablespace
    caused the disk to run out of space during a large
    import (from now on we are going to use commit = y):
    1. Created a new undo tablespace UNDOTBS03 - got
    errors so instead we to created it as a temp
    tablespace UNDOTBS03 which worked. r.- Yes, but that tablespace was created as a UNDO TABLESPACE ?
    2. Tried to drop UNDOTBS1 got the following error
    msg:
    ORA-01548: active rollback segment '_SYSSMU1$' found,
    terminate dropping tablespacer.- Of course, the database did not allow to drop it beacause there were pending transactions
    3. SQL> alter system set undo_tablespace =
    'UNDOTBS03' scope = both. Tried dropping UNDOTBS1.
    Same error as in #2 above.r.- There were still pending transactions with the older undo tablespace
    4. We then offline dropped the datafile associated
    with UNDOTBS1 hoping that would then allow us to drop
    UNDOTBS1. Same error as #2.r.- That was the worst you did. You can not drop a tablespace so...
    5. Then tried creating a undo tablespace again:
    Create UNDO tablespace undo_temp
    datafile 'D:\oracle\oradata\usbperf\undo_temp.DBF'
    size 25m autoextend on;
    Error on line 0
    Create UNDO Tablespace undo_temp
    datafile 'D:\oracle\oradata\usbperf\undo_temp.
    ORA-00604: error occurred at recursive SQL level 1
    ORA-00376: file 2 cannot be read at this time
    ORA-01110: data file 2:
    'D:\ORACLE\ORADATA\USBPERF\UNDOTBS01.DBF'
    So that’s where we are. I'm guessing that the
    original undo tablespace corrupted when it tried to
    extend and ran of disk space?
    Thanks again for the help.
    Colin ok I can guide to solve this but you have to do what I am going to tell you step by step. Is this a production database ?
    Joel Pérez
    http://www.oracle.com/technology/experts

  • Undo Tablespace

    Hi,
    For one of the database, Undo tablespace has reached upto 2.5GB. I have created one more undo tablespace. If users are frequently commiting the transactions, why it is increasing. It is a development database.
    Can I delete the undo tablespace, once I conclude that the transactions are using the new undo tablespace?
    Pls guide me.
    Thanks,
    Raj

    Hi,
    Before going to recreate the undo tablespace calculate the optimal sizing undo and create make changes as per nedd.
    Read below post.... This may helps you....
    Undo growth
    Regards,
    Karthik

  • Partial Recovery - Skip UNDO Tablespace

    Hi,
    I was performing a partial database recovery using skip tablespace option using RMAN. I was wondering if I can skip undo tablespace.
    I was not able to conclude whether I can do that? If not, why?
    As per my understanding,
    1. Datafiles are restored - If they have any uncommited data, then archive logs which will be applied for media recovery, will have the undo data to perform those roll backward.
    2. While performing media reccovery using archive logs, it will generate it's own undo data.
    Why do we need the stale undo data (generated till datafiles restoration point)?
    Thanks,
    Janak Agrawal

    Soli,
    Thread that you have specified, talks about datafiles which does not have any uncommitted data (As the database was normally shutdown). In this case, we can drop and recreate the undo tablespace.
    But I am talking about a past point-in-time recovery using RMAN, where the datafiles which will be restored may have the uncommitted data. To rollback these uncommited trnasactions, will we have data in next archivelogs, which will be used for media recovery or the data (needed to rollback) will have only in undo tablespace. Let me give you an example.
    At 9 am I want to restore the datbase till 8.15 AM. Full backup is available till 8 AM and then from 8 to 8:15 arvhive logs are available. While doing recovery, datafiles will be restored till 8 AM. If at 8 AM there is some uncommitted data in datafiles, will it require data from undo tablespace to rollback or first archive log after 8 AM w'd take care of roll back? If archive logs can take care of rollback, why can't I skip the undo tablespace while doing recovery?
    Santosh,
    As you mentioned, UNDO data will require for read-consistency. But the same data will be available in archive logs (which will require after datafiles restore) which can generate their own UNDO data.
    Please clarify. I am sorry if I am missing anything here.
    Thanks,
    Janak Agrawal

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

  • 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 file size is huge

    Have noticed that UNDO tablespace is eating the disk space of our server. Now, the size is 40GB. Can I recreate a new one with smaller size and drop the existing one? If yes, how?

    I have another problem
    SQL> startup
    ORACLE instance started.
    Total System Global Area 1367343104 bytes
    Fixed Size 1292468 bytes
    Variable Size 838862668 bytes
    Database Buffers 520093696 bytes
    Redo Buffers 7094272 bytes
    Database mounted.
    ORA-01092: ORACLE instance terminated. Disconnection forced
    As I checked the alert log:
    Mon Oct 04 13:47:18 2010
    Error 30012 happened during db open, shutting down database
    USER: terminating instance due to error 30012
    Mon Oct 04 13:47:19 2010
    Errors in file d:\oracle\product\10.2.0\admin\axphq01\bdump\axphq01_pmon_7572.trc:
    ORA-30012: undo tablespace '' does not exist or of wrong type
    Mon Oct 04 13:47:19 2010
    Errors in file d:\oracle\product\10.2.0\admin\axphq01\bdump\axphq01_reco_2168.trc:
    ORA-30012: undo tablespace '' does not exist or of wrong type
    Mon Oct 04 13:47:19 2010
    Errors in file d:\oracle\product\10.2.0\admin\axphq01\bdump\axphq01_smon_6552.trc:
    ORA-30012: undo tablespace '' does not exist or of wrong type
    Mon Oct 04 13:47:19 2010
    Errors in file d:\oracle\product\10.2.0\admin\axphq01\bdump\axphq01_lgwr_9108.trc:
    ORA-30012: undo tablespace '' does not exist or of wrong type
    Mon Oct 04 13:47:20 2010
    Errors in file d:\oracle\product\10.2.0\admin\axphq01\bdump\axphq01_ckpt_7152.trc:
    ORA-30012: undo tablespace '' does not exist or of wrong type
    Mon Oct 04 13:47:20 2010
    Errors in file d:\oracle\product\10.2.0\admin\axphq01\bdump\axphq01_psp0_3612.trc:
    ORA-30012: undo tablespace '' does not exist or of wrong type
    Mon Oct 04 13:47:20 2010
    Errors in file d:\oracle\product\10.2.0\admin\axphq01\bdump\axphq01_mman_6528.trc:
    ORA-30012: undo tablespace '' does not exist or of wrong type
    Mon Oct 04 13:47:20 2010
    Errors in file d:\oracle\product\10.2.0\admin\axphq01\bdump\axphq01_dbw0_7120.trc:
    ORA-30012: undo tablespace '' does not exist or of wrong type
    Instance terminated by USER, pid = 9204
    ORA-1092 signalled during: ALTER DATABASE OPEN...

  • Create undo tablespace while at mount state, possible?

    Oracle 10g (10.2.0.1.0), on RedHat 4 (both 64 bit)
    My test db’s undo tablespace is corrupt (no RMAN or user backups).
    DB fails to open, fails during "Doing block recovery for file 2 block 209910"Is there a way of creating undo tablespace while at mount state?
    I am pretty confident it’s not possible, also searched the net and found no fix, I thought I will ask.
    I get error:
    CREATE UNDO TABLESPACE UNDOTBS1_new DATAFILE  '/u01/oracle/oradata/TEST_DB1/undotbs2_01.dbf' SIZE 512M
    ERROR at line 1:
    ORA-01109: database not openp{code}As a last option, I will open the db with *'reset logs'*, wondering is any thing else I can try to fix the issue.
    Thanks for any input.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    your problem is not to create un UNDO, your problem is that your UNDO is corrupted ! ;)
    You must recover undo because it may contains needed data.
    As there is not backup, you may try to set undo to manual, and then open the db and recreate the undo
    but this may fail and you may have to allow undo corruption in initialization (_corrupted_rollback_segments), but this is an unsupported operation (hidden parameter)
    Could you contact support ?
    is your db a production one ?
    Edited by: Leo Anderson on 1 sept. 2008 15:25

  • Loss of Undo tablespace

    Hello Friends
    I am confuse about a snario, please clear it:
    What if we loss undo tablespace(data files), and all files remain safe(database in archive log 9i) and the tablespace have some active transactions at the time of failure. My question is that how oracle will recover ? and where the undo data for uncommited transaction will come from at the time of recovery.
    Sunil Kumar

    You can create new undo tablespace , though, is that there cannot be any active transactions in the Undo segments of the tablespace when it is time to actually drop it. In the case of data file corruption, uncommitted transactions in the database that have data in Undo segments can be extremely troublesome because the existence of any uncommitted transactions will lock the Undo segments holding the data so that they cannot be dropped. This will be evidenced by an "ORA-01548" error if this is attempted. This error, in turn, prevents the drop and recreation of the Undo tablespace, and thus prevents the successful recovery of the database.
    To overcome this problem, the transaction tables of the Undo segments can be traced to provide details on transactions that Oracle is trying to recover via rollback and these traces will also identify the objects that Oracle is trying to apply the undo to. Oracle Doc ID: 94114.1 may be referenced to set up a trace on the database startup so that the actual transactions that are locking the Undo segments can be identified and dropped. Dropping objects that contain uncommitted transactions that are holding locks on Undo segments does entail data loss, and the amount of loss depends on how much uncommitted data was in the Undo segments at the point of failure.
    Hope this hepls...

  • Undo tablespace reached to 99.99 %

    Hi all,
    I am using Oracle Apex 3.1 & Database oracle 10g Release 1002000100 on HP-Unix
    my Undo Tablespace is increasing Regularly, I turned off its auto Extent,
    On Querying thru v$Session
    user APEX_PUBLIC_USER,osuser Apache are
    logged on for 16 times,
    my Undo tablespace reached to 99.99 %
    I now added more 500 MB,
    Again it occupied to 99.99 %
    I didnt temper with Undo tablespace,
    usinG Default Settings except i did Auto EXTENT Turned off,
    please Suggest me the Fixing & cause for this
    many thanks
    -Khaja
    Edited by: ahuja on Feb 7, 2009 3:26 PM

    Hi all
    i tried with the Following
    SQL> SELECT SUM(a.bytes) "UNDO_SIZE"
    2 FROM v$datafile a,
    3 v$tablespace b,
    4 dba_tablespaces c
    5 WHERE c.contents = 'UNDO'
    6 AND c.status = 'ONLINE'
    7 AND b.name = c.tablespace_name
    8 AND a.ts# = b.ts#;
    UNDO_SIZE
    1.4680E+10
    SQL>
    SQL> SELECT MAX(undoblks/((end_time-begin_time)*3600*24))
    2 "UNDO_BLOCK_PER_SEC"
    3 FROM v$undostat;
    UNDO_BLOCK_PER_SEC
    59.7333333
    SELECT d.undo_size/(1024*1024) "ACTUAL UNDO SIZE [MByte]",
    SUBSTR(e.value,1,25) "UNDO RETENTION [Sec]",
    ROUND((d.undo_size / (to_number(f.value) *
    g.undo_block_per_sec))) "OPTIMAL UNDO RETENTION [Sec]"
    FROM (
    SELECT SUM(a.bytes) undo_size
    FROM v$datafile a,
    v$tablespace b,
    dba_tablespaces c
    WHERE c.contents = 'UNDO'
    AND c.status = 'ONLINE'
    AND b.name = c.tablespace_name
    AND a.ts# = b.ts#
    ) d,
    v$parameter e,
    v$parameter f,
    SELECT MAX(undoblks/((end_time-begin_time)*3600*24))
    undo_block_per_sec
    FROM v$undostat
    ) g
    WHERE e.name = 'undo_retention'
    AND f.name = 'db_block_size'
    ACTUAL UNDO SIZE [MByte] UNDO RETENTION [Sec] NEEDED UNDO SIZE [MByte]
    14000 900 420
    Now my Undo tablespace reached 99% Again, i wanted to know the what is eating my Undo tablespace Space
    Do I need to drop and recreate a new undo tablespace? I don't want to do this until I understand what is eating all the space. Please help me here
    please Help me out
    many many thanks
    - Khaja
    Edited by: ahuja on Feb 14, 2009 4:42 PM
    Edited by: ahuja on Feb 14, 2009 4:44 PM

  • Differance between Rollback Segements and Undo Tablespace/segments

    Hi everyone.
    I have some confusion that how Rollback Segements and Undo Tablespace/segments and different? Functionally they seem to be the same but why then Oracle recommends not using Rollback segments?...please explain. Kindly post any links useful in this regard.
    Thanks,
    Mukesh

    1.when does the changed data written to the undo tablespace?It never gets moved to the undo tablespace.
    The ORIGINAL data gets moved to the rollback/undo. Oracle assumes that most of the time the transaction is going to commit, so the change is made to the real block (in memory). At that time, enough information to roll back that change is written into the rollback segment.
    2.which process writes the changed data to the undo tbs?The server process. The one to which the user connects. The one the user gets by contascting the listener.
    3.What are the identifiactions which is used to undo the changes made(like SCN) ? plz...AFAIK, Transaction Id is the only thing used. SCN, a redo log construct, may be used to recreate the transaction ID in the rollback.

  • 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

Maybe you are looking for