Undo tbs corrupted

i have oracle 9i release 2 on unix box. The database is up but the undo tablespace got corrupted which i can see using v$recover_file view. End users have begin performing DML activities but at the midst of the transaction undo got corrupted . I have a backup of undo .
what should i do shall i shutdown and recover at the mount mode or recover the undo tablespace online??
please help me
its very urgent

You don't need to go for offline recovery.Do you mind elaborating that.
Question, let us say undo is corrupted, can we do a online recovery?
My reserach says
rman>restore datafile '/u02/undotbs01.dbf';--will complain about enqueue.
Also, You cannot take a undo tablespace offline.
You cannot drop a undo tablespace while it is in use.
My thoughts :- Take the database to mount state. Restore/recover.

Similar Messages

Fragmentation in Undo TBS

Hi all experts,
I want to know if found fragmentation in undo tablespace.
Is it recommaned to treat it the same way as usual permanent non system fragmented TBSs.
i.e. do fragmentation
I wonder if temp/undo tbs needs to be defragmented.
Looking for your kind and professional advices and references.
Thanks

Being Locally Managed, TEMP and UNDO are self-managed by Oracle.
I also wonder if you are "de-fragmenting" other tablespaces. If they are Locally Managed and Allocation_Type is either UNIFORM or AUTO, you do not need to "de-fragment" them. If using UNIFORM, set the appropriate Extent Size when you create the Tablespace.
If your Tablespace has been converted from Dictionary Managed to Locally Managed, the Extent Management may appear as "USER" -- in which case you have odd-sized extents brought forward from DMT. Again, "fragmentation" is not an issue once they are Locally Managed.
You could consider rebuilding the tablespaces as LMT with UNIFORM or AUTO when you get an opportunity. (Obviously : TEST, TEST , TEST and measure the effort and downtime -- it may not be justifiable to even expend that effort).
Hemant K Chitale

Undo block corruption

Hallo,
I have an ORA-00600 with [4194] which indicates an undo block corruption (as far as I know).
Does anyone know how to deal with this ?
Regards,
Mynz

Hi Mynz,
But how does it help me to go on ?Here are my notes on repairing undo corruption:
http://www.dba-oracle.com/t_fix_undo_log_corruption.htm
I would open an SR and note that there are undocumented parms to help, BUT only when advised by Oracle tech support:
http://www.dba-oracle.com/t_8i_hidden_corruption_recovery_parameters.htm
Hope this helps. . .
Don Burleson
Oracle Press author

UNDO tbs requirement

How would I know what is the required UNDO tbs space for a job to run successfully.
I cannot view the code of the job.
How can I calculate the UNDO tbs requirement for that particular job.
Following is the error I am facing while running that job :
*** Starting go_ifs_gb_publish_data_det.sh at Fri Feb 12 14:13:21 EST 2010.
BEGIN fdw.gb_rpt_publish_data; END;
ERROR at line 1:
ORA-30036: unable to extend segment by 4 in undo tablespace 'UNDOTBS'
ORA-06512: at "FDW.GB_RPT_PUBLISH_DATA", line 140
ORA-06512: at line 1
Job Failed: go_ifs_gb_publish_data_det Error Code: 84
*** go_ifs_gb_publish_data_det.sh Ending at Fri Feb 12 20:49:56 EST 2010.

There is no thumb rule for setting size of the undo for any trasaction or transactions.
few suggestions : monitor for few days in peak time of usage of undo and adjust as per requirement.
: try to do a intermediate commit for transaction instead of running long transactions.
Below query will give you some help in tuning the undo tablespace and retention ( Check the feasiblity , as said there is no thumb rule )
SELECT d.undo_size/(1024*1024) "ACTUAL UNDO SIZE [MByte]",
SUBSTR(e.value,1,25) "UNDO RETENTION [Sec]",
(TO_NUMBER(e.value) * TO_NUMBER(f.value) *
g.undo_block_per_sec) / (1024*1024)
"NEEDED UNDO SIZE [MByte]"
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'
Regards,
Anil Malkai
if it is help ful or answered your query mark it as answered.
Edited by: Anil Malkai on Feb 15, 2010 3:32 AM

2 Undo Tablespace both ONLINE, How to drop previous undo tbs

Hello Team,
Undo management=auto
After Cloning :-
To reclaim space i created another undo tablespace, but now both are online, but as per oracle as soon as you switch undo tablespace, previous undo TBS gets in Pending offline mode,offline mode, (So that transaction get finished)
But in my case Both UNDO Tablespaces are online
Previous Undo TBS1:- 600 GB
New UNDo Tb2s:- 100GB
Please suggest how to drop this online undo TBS1
TABLESPACE_NAME ONLINE_
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS2 ONLINE
APPS_UNDOTS2 ONLINE
TABLESPACE_NAME ONLINE_
APPS_UNDOTS2 ONLINE

Hi As per
select segment_name,owner,tablespace_name,status from dba_rollback_segs where tablespace_name like 'UNDOTBS1';
All Are offline for UNDOTBS1(Previous)
SEGMENT_NAME OWNER TABLESPACE_NAME STATUS
SYSSMU49861044602693$ PUBLIC APPS_UNDOTS1 OFFLINE
SYSSMU4893847838046$ PUBLIC APPS_UNDOTS1 OFFLINE
SYSSMU48682660477388$ PUBLIC APPS_UNDOTS1 OFFLINE
SYSSMU47753309457002$ PUBLIC APPS_UNDOTS1 OFFLINE
SYSSMU47131240212364$ PUBLIC APPS_UNDOTS1 OFFLINE
434 rows selected.

Someone eating my UNDO tbs

Hello all,
I have 11gr2 with r12.
we have 60GB undo tbs, retention is 900s set.
since last 2 days our undo is showing 98% used, no recent changes done.
I googled, lots of sql's are there to know what is consuming UNDO, but the list what I am getting as an output result are in KB's.
for example:
select * from V$SYSMETRIC_HISTORY;
select
s.username
,s.sid
,s.serial#
,s.osuser
,s.logon_time
,s.status
,s.machine
,t.used_ublk
,t.used_ublk*8192/1024 undo_usage_kb
from v$session s
,v$transaction t
where t.addr = s.taddr;
above query is giving me num of sessions but all are in kb's, then where is undo been consumed.
Please help me to find out the culprit.
Thanks in ADV

DOA wrote:
Thanks for the prompted reply.
I was just wanted to know the transaction which are currently running are consuming how much UNDO space ?
second while checking EXPIRED I am getting around 3000 count.
Plz suggest.
Thanks!
Nothing is consuming any undo space if all the extents are EXPIRED. An extent in use by transaction is ACTIVE. An extent that was used by transaction that committed less recently than your undo_retention is UNEXPIRED. Clear?

What roolback trans is inside undo tbs

We got a ORA-30036 last night. UNDO tbs jump to 54 GB, it only has 1 datafile and has fillup the whole drive.
I want to know what exact transcation cause the fillup. Is there any system tables where I can see the rollback transcation in UNDO??
Thanks in Advanced
carlton

You can check V$UNDOSTAT to see whats the statistics for the particular undo. There would be 10 default undo segments created for any undo tablespace. For each of them you can see whether it has expired or not from DBA_ROLLBACK_SEGS.
From V$TRANSACTION, you can see the transaction id and lot other information about the transaction along with the ses_adr which you can combine with v$session to see who is using that transaction. in V$SESSION you have address and hash_value of the sessions latest sql which you can combine with V$SQLAREA or V$SQLTEXT to get the exact SQL which is performing the DML operation.
HTH

How to expdp table with a BLOB field when table is larger than UNDO tbs?

We have a 4-node RAC instance and are at 11.1. We have a 100 gig schema with a few hundred tables. One table contains about 80 gig of data. the table has pictures in it (BLOB column). Our 4 node RAC has 4 12 gig undo tablespaces.
We run out of undo when export a schema or just this table due to the size of the table.
According to metalink note ID 1086414.1 this can happen on fragmented tables. According to segment advisor, we are all good and not fragmented at all.
I also followed the troubleshooting advice in ID 833635.1 and ID 846079.1, but everything turned out ok.
LOBs and ORA-01555 troubleshooting [ID 846079.1]
Export Fails With ORA-02354 ORA-01555 ORA-22924 and How To Confirm LOB Segment Corruption Using Export Utility? [ID 833635.1]
initially we tried just to export it without special parameters.
expdp MY_SCHEMA/********@RACINSTANC DUMPFILE=MYFILE.dmp PARALLEL=8 directory=DATA_PUMP_DIR SCHEMAS=MY_SCHEMA
ORA-31693: Table data object "MY_SCHEMA"."BIGLOBTABLE" failed to load/unload and is being skipped due to error:
ORA-02354: error in exporting/importing data
ORA-01555: snapshot too old: rollback segment number 71 with name "_SYSSMU71_1268406335$" too small
then tried to export just the table into 8 files of 8G each (the failing table is about 90% of the schema size)
expdp MY_SCHEMA/******@RACINSTANCE DUMPFILE=MYFILE_%U.dmp PARALLEL=8 FILESIZE=8G directory=DATA_PUMP_DIR INCLUDE=TABLE:\"IN ('BIGLOBTABLE') \"
ORA-31693: Table data object "MY_SCHEMA"."BIGLOBTABLE" failed to load/unload and is being skipped due to error:
ORA-02354: error in exporting/importing data
ORA-01555: snapshot too old: rollback segment number 71 with name "_SYSSMU71_1268406335$" too small
We eventually resorted to exporting chunks out of the table by using the QUERY parameter
QUERY=BIGLOBTABLE:"WHERE BIGLOBTABLEPK > 1 AND BIGLOBTABLEPK <=100000"
and that worked but it is a kludge.
Since we will have to export this again down the road I was wondering if there is an easier way to export.
Any suggestions are appreciated.

Note that undo data for LOB is not stored in UNDO tablespace but in LOB segments. So I am not sure ORA-1555 is directly linked to LOB data.
What is your undo_retention parameter ?
How long does EXPDP run before getting ORA-1555 ?
You could try to increase undo_retention parameter to avoid ORA-1555.
Are you running Entreprise Edition ? If yes, trying to transport the tablespace storing the table could be a solution.

Undo file corruption(Undo segments)

Hello Friends
My database in archivelog mode(Oracle 9i). What if because of media failure my undo segments got corrupted ?
Can I recover the database upto failer point ?
Regards
Sunil Kumar

As Maran mentioned already that if you have sufficient good backups, there wont be any issues with the recovery. In addition to this, search over metalink for the use of the event *10015*. This would help to identify the corrupted undo segments.
HTH
Aman....

Undo tablespace corruption will terminate DB operation

Hi All,
Just for the concept, if undotablespace datafile got corrupted due to any reasion, will it force to terminate the DB operation.
O know this will happen with control file and SYTEM datafile only.
Please confirm.
Regards,
SS

Hmm what to check? It says the same, it is not mandatory that instance would surely get shut down with the loss of undo tablespace. But you MUST do the recovery of it when the database is closed. I guess that's what that doc is also saying.
Update:
See below where I would show the same thing happening. We would start from the undo tablespace getting deleted and would check the alert log for any message. Also we would check the status of teh database after the drop,
Session 1
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Aug 6 10:43:35 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size                  1218316 bytes
Variable Size              79694068 bytes
Database Buffers           83886080 bytes
Redo Buffers                2973696 bytes
Database mounted.
Database opened.
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size                  1218316 bytes
Variable Size              79694068 bytes
Database Buffers           83886080 bytes
Redo Buffers                2973696 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
Database altered.
SQL> select name from V$datafile;
NAME
--------------------------------------------------------------------------------/u01/app/oracle/oradata/orcl/system01.dbf
/u01/app/oracle/oradata/orcl/undotbs01.dbf
/u01/app/oracle/oradata/orcl/sysaux01.dbf
/u01/app/oracle/oradata/orcl/users01.dbf
SQL> !rm /u01/app/oracle/oradata/orcl/undotbs01.dbf
SQL> select status from V$instance;
STATUS
------------ <-- The database is open
OPEN
#At this time, in the alert log there was no message.
#Let's try some ddl/dmls.
SQL> create table t( a number);
Table created.
SQL> insert into t values(1);
1 row created.
SQL> commit;
Commit complete.
SQL> delete t;
1 row deleted.
#No problem so far. Let's issue a checkpoint, this would force oracle to check the file and its status.
SQL> alter system checkpoint;
System altered.
SQL>
Session-2(Alert log's tail)
Output snipped
ORA-01110: data file 2: '/u01/app/oracle/oradata/orcl/undotbs01.dbf'
Thu Aug 6 11:11:19 2009
Errors in file /u01/app/oracle/admin/orcl/bdump/orcl_pmon_4402.trc:
ORA-00376: file 2 cannot be read at this time
ORA-01110: data file 2: '/u01/app/oracle/oradata/orcl/undotbs01.dbf'
Thu Aug 6 11:11:19 2009
Errors in file /u01/app/oracle/admin/orcl/bdump/orcl_pmon_4402.trc:
ORA-00376: file 2 cannot be read at this time
ORA-01110: data file 2: '/u01/app/oracle/oradata/orcl/undotbs01.dbf'
Thu Aug 6 11:11:19 2009
Errors in file /u01/app/oracle/admin/orcl/bdump/orcl_pmon_4402.trc:
ORA-00376: file 2 cannot be read at this time
ORA-01110: data file 2: '/u01/app/oracle/oradata/orcl/undotbs01.dbf'
#Let's check the status again,
SQL> select stauts from V$isntance;
select stauts from V$isntance
ERROR at line 1:
ORA-00603: ORACLE server session terminated by fatal error
Its crashed now as db couldn't find the undo tablespace.
HTH
Aman....
Edited by: Aman.... on Aug 6, 2009 11:28 AM added demo.

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

Undo TBS

Hi all, I am using Oracle 10gR2 on Solaris 10.
The application using my DB does a lot of commits and rollbacks, because of which my undo tablespace is always full. I have a RAC with two nodes, so two undo tablespaces, which are always full. Now, when Oracle has no room to write into the undo, it stops processing the application processes, because of which there are a lot of INACTIVE sessions and they keep increasing because the application sends them to be processed but they are not.
NAME                                 TYPE        VALUE
undo_management                      string     AUTO
undo_retention                       integer     900
undo_tablespace                      string      UNDOTBS1Should I reduce my undo_retention so that Oracle does not keep the undo info for that long and it empties up space faster?
Regards.....

Generally the users ask DBA's before running such a long tansactions..Not being funny mate, but in my experience too often people have no idea about undo and the affect their changes have. But the DBA has to gently talk, cajole, persuade them to change their ways and not used 100GB of resource; "please please pretty please don't do that" then they do it again anyway.... Even if you resort to less polite methods....
Summing up for the OP yes you need to identify the users/batch using undo and attempt to change the usage of those.
Hope this helps, a script another DBA gave me;
no idea who the original author is....
but as it helped me I'm passing on to help others.
select distinct r.name rollname,
l.sid loc_sid,
s.sid session_sid,
l.addr lock_addr,
l.kaddr lock_kaddr,
nvl(s.username,'Internal') username,
decode(s.command,2,'Insert',3,'Select',6,'Update',7,'Delete',44,'Commit',45,'Rollback','Other') trans_type
from
v$lock l,
v$process p,
v$rollname r,
v$session s,
sys.user$ sysuser,
sys.obj$ sysobj
where l.sid = s.sid
and sysobj.obj# = decode(L.ID2,0,L.ID1,1)
and sysuser.user# = sysobj.owner#
and trunc(l.id1(+)/65536) = r.usn
and s.type != 'BACKGROUND'
order by r.name
/

RAC and corruption

Hi,
Version 10204 , RAC + ASM.
Is there an option that corrupted block from one instance will be replicate from the "infected" instance to the second instance ?
Thanks

Hi,
I would like to clarify my colleague description about our RAC configuration:
About the ASM configuration
===================
1. We have 2 storage machines in two different locations, the first one is in the company building and the second in our drp site (the distance between them is something like 1KM).
2. In each of the 2 locations (drp and comp) whe have one node (on linux servers).
3. We have 4 volumes on each storage machine for asm disks (1 for flash recovery area DG and 3 for the data DG).
4. Each of the 2 nodes have access to 8 volums for asm purpose, 4 volumes on each storage machine.
5. I've created the ASM with one DATA dg with twice 3 asmdisks (once in each storage) in 2 failure groups (normal redundancy) .
6. The FLASH_RECOVERY_AREA is also with 2 failure groups with one asmdisk each (normal redundancy) .
--- please look at the result of the select below.
7. After creating the DG's I've created the oracle RAC db with 2 instances (one on each server as mentioned before).
SQL> l
1 select d.GROUP_NUMBER DG#,dg.name DG_NAME, d.name DISK,d.FAILGROUP FAILGROUP
2 from v$asm_disk d, v$asm_diskgroup dg
3* where d.GROUP_NUMBER= dg.GROUP_NUMBER
SQL> /
       DG# DG_NAME              DISK                           FAILGROUP
         2 FLASH_RECOVERY_AREA RACSERV1_ARCHIVE1              ARCH_FG1
         1 DATA                 RACSERV1_DATA_1                DATA_FG1
         1 DATA                 RACSERV1_DATA_2                DATA_FG1
         1 DATA                 RACSERV1_DATA_3                DATA_FG1
         2 FLASH_RECOVERY_AREA RACSERV2_ARCHIVE1_101          ARCH_FG2
         1 DATA                 RACSERV2_DATA_1_101            DATA_FG2
         1 DATA                 RACSERV2_DATA_2_101            DATA_FG2
         1 DATA                 RACSERV2_DATA_3_101            DATA_FG2About the CRS configuration:
==================
OCR's
1 . We have one OCR on each of both storage machines (mentioned before).
2. Each of the nodes have access on both ocr's
Votedisks
1. 1 vote disk on each of the storage machines.
2. 1 vote disk on nfs (3th storage machine).
3. the 3 votedisks are accessible from each of he 2 nodes.
Now I think the configuration is clear enough, I would like to know if there is any way to prevent from logical corrupted blocks in one failgroup to be copied to the second one.
And regarding the previous questions:
We have 2 undo tbs and one system tbs.
Regards,
Thank you,
Edited by: Avi Apelbaum on Sep 13, 2009 3:50 AM
Edited by: Avi Apelbaum on Sep 13, 2009 3:51 AM

Query abort with ora-30036 after more than 20 hours and 180g of undo

Dear all,
A developper transmits me a query. It fails after more than 20 hours and an undotbs of 180g (i change undo-retention, size of undo tbs, without results). That query makes a lot of inserts. How can i rewrite it to be more performant (my database is on 10.2.0.3 and i can't change it).
here's the query :
set serveroutput on size unlimited
set pages 0
set trims on
set lines 1000
set feed off
set pagesize 50
set linesize 1000
set head off
set echo off
set verify off
set feedback off
WHENEVER SQLERROR EXIT SQL.SQLCODE
DECLARE
v_annee VARCHAR(4) := '2012';
v_dkm_id NUMBER := '108';
v_entretien NUMBER;
v_nb_feuilles_cr NUMBER := 0;
v_nb_etats_cr NUMBER := 0;
v_action_id NUMBER;
v_rm_id NUMBER;
v_personne_id NUMBER;
CURSOR c_evaluation IS
     SELECT E.ID# AS E_ID, W.ID# AS WF_ID , E.NATURE_ECHELON AS ECHELON
     FROM T_EVALUATION E
     JOIN T_DKM_LOCALE L ON L.ID#=E.DKM_LOCALE_ID
     JOIN T_WORKFLOW W ON (W.CODE=E.CODE_WORKFLOW_INITIAL AND W.ANNEE=v_annee )
     WHERE L.DKM_NAT_ID=v_dkm_id;
r_evaluation c_evaluation%ROWTYPE;
BEGIN
SELECT ID#
INTO v_personne_id
FROM T_PERSONNE
WHERE ID_FONCTIONNEL = 'herve.collin';
dbms_output.put_line('===== MAJ evaluations / statut_harmo_shd =============');
dbms_output.put_line('===== Creation des feuilles ==========================');
SELECT ID# MOTIF_ID
INTO v_entretien
FROM T_REF_MOTIF_TENUE_ENTRETIEN
WHERE CODE='PLA';
OPEN c_evaluation;
LOOP
     FETCH c_evaluation INTO r_evaluation;
     EXIT WHEN c_evaluation%NOTFOUND;
IF r_evaluation.ECHELON = 'T'
THEN
SELECT ID#
INTO v_rm_id
FROM T_REF_REDUCMAJO
WHERE ANNEE = v_annee
AND CATEGORIE_GRADE = 'ET'
AND CODE = 'V1';
END IF;
IF r_evaluation.ECHELON = 'F' OR r_evaluation.ECHELON = 'V'
THEN
SELECT ID#
INTO v_rm_id
FROM T_REF_REDUCMAJO
WHERE ANNEE = v_annee
AND CATEGORIE_GRADE = 'FV'
AND CODE = 'R1';
END IF;
UPDATE T_EVALUATION
SET STATUT_HARMO_SHD = 'C' , REF_REDUCMAJO_PROP_SHD_ID = v_rm_id
WHERE DKM_LOCALE_ID IN ( SELECT ID# FROM T_DKM_LOCALE WHERE DKM_NAT_ID = v_dkm_id );
INSERT INTO T_FEUILLE(ID#, REF_MOTIF_TENUE_ENT_ID, EVALUATION_ID, WORKFLOW_ID)
VALUES (S_FEUILLE.NEXTVAL , v_entretien , r_evaluation.E_ID, r_evaluation.WF_ID);
v_nb_feuilles_cr := v_nb_feuilles_cr + 1;
END LOOP;
CLOSE c_evaluation;
dbms_output.put_line(' -> '||v_nb_feuilles_cr||' feuilles crees');
COMMIT;
END;
set serveroutput off
exit
What is the bester choice ? drop the indexes on the table before insert, start the insert without fetching the data in cursor ?
nb: sorry for my bad english
Best regards
Catherine Andre
@mail: [email protected]

user4443606 wrote:
Thanks for your reply !
I'll try to grow the undo tbs space but i stay convinced that the problem is in the query.You can be convinced & wrong at the same time.
row by row INSERT is slow by slow.
It can be done as single INSERT; but that won't change the amount of UNDO that is required.

Drop Undo Tablespace taking more than 1 hr

Hi,
To give you background, I had given an "insert into .. select" command which was inserting 3 millions of rows of rowidth approx 5000 bytes. The window on which it was given, was closed by mistake.
After sometime when I checked the size of undo_tablespace, it was 5.5GB. I decided to create a new one and drop the old undo_tbsp.
I have successfully created new undo tablespace and changed the same in spfile also.
now when i am dropping the old undo tablespace, its taking long time. its almost an hour, but the tablespace has not been dropped yet.
I have given following command
drop tablespace undotbs_01 including contents;
Any idea, why is it taking so much time, and how long should I wait?
If someone can give me any other idea on how can I drop the tablespace, that will be great.
Regards,
Archana.

To give you background, I had given an "insert into .. select" command which was inserting 3 millions of rows of rowidth approx 5000 bytes. The window on which it was given, was closed by mistake.This could be the cause.
I wonder the killed/closed session doesn't hangup with a latch or lock.
Since the old undo tbs had active transaction, it might have to pending offline status. If so, you can drop it.
Jaffar

Undo tbs corrupted

Similar Messages

Maybe you are looking for