Undo tablespace resize error

Total space occupied by UNDO tablespace is : 3G and used space for UNDO tablespace is only 512M , so approx 2.5G space is free. But when i tried to resize the undo tablespace to 1G then its showing the below error :
ORA-03297: file contains used data beyond requested RESIZE value
but the used data size is 512M only.
Kindly help me to resize the undo tablespace to 1G.
Database : Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bi
Kindly suggest.
Advance thanks !!

you can't resize undo tablespace. If you are trying to reduce the size.
then add a unod tablespace may like undotbs2 then set undotbs2 as default to your database. then drop the prvious undo tablespace
Anil Malkai

Similar Messages

Tablespace resize Error

Hi all
when i am trying to increase my undo tablespace Size
i go the Following Error?
i am doing this operation from Toad.
Having Enough Size on Disk,
this is the Problem on Production Database Server,
using Oracle 10g Rel 1002000100 on HP-Unix
SQL> ALTER DATABASE DATAFILE '/app/oracle/product/oradata/prod/undotbs02.dbf'
RESIZE 20480M
ALTER DATABASE DATAFILE '/app/oracle/product/oradata/prod/undotbs02.dbf'
RESIZE 20480M
Error at line 2
ORA-01237: cannot extend datafile 12
ORA-01110: data file 12: '/app/oracle/product/oradata/prod/undotbs02.dbf'
ORA-19502: write error on file "/app/oracle/product/oradata/prod/undotbs02.dbf", blockno 2534784 (blocksize=8192)
ORA-27072: File I/O error
Additional information: 4
Additional information: 2534784
Additional information: 655360
is this Serious Problem?
is the Error Related to os or Database
please Help me out
Many thanks

yeah,
they manged Some Space by Deleteing Few Spaces
Can We create the tablespaces in other Mount points
like in /backup where good space is remained
i wanted to create the Undo table space in /backup
and Space issue came coz the Undo is reaching highly,so far my Undo reached 19GB,
even after the Immediate Shutdown & Startup the Size is not Relased in Undo,
it is Remain 19GB,
many thanks for ur Kind information
oracle@prod: /app/oracle # df -k
/app (/dev/vg01/lvapp ) : 62309972 total allocated K
7816220 free allocated Kb
54493752 used allocated Kb
87 % allocation used
/backup (/dev/vgbackup/lvbackup) : 8748714 total allocated K
5296424 free allocated Kb
3452290 used allocated Kb
39 % allocation used
/home (/dev/vg00/lvol5 ) : 24576 total allocated K
16576 free allocated Kb
8000 used allocated Kb
32 % allocation used
/opt (/dev/vg00/lvol6 ) : 1717640 total allocated K
344208 free allocated Kb
1373432 used allocated Kb
79 % allocation used
/tmp (/dev/vg00/lvol4 ) : 814256 total allocated K
730424 free allocated Kb
83832 used allocated Kb
10 % allocation used
/usr (/dev/vg00/lvol7 ) : 2906912 total allocated K
1200720 free allocated Kb
1706192 used allocated Kb
58 % allocation used
/var (/dev/vg00/lvol8 ) : 4681752 total allocated K
3655096 free allocated Kb
1026656 used allocated Kb
21 % allocation used
/stand (/dev/vg00/lvol1 ) : 269032 total allocated K
189472 free allocated Kb
79560 used allocated Kb
29 % allocation used
/ (/dev/vg00/lvol3 ) : 204560 total allocated K
43824 free allocated Kb
160736 used allocated Kb
78 % allocation used
oracle@prod: /app/oracle #
thanks alot

Unable to extend segment by 8 in undo tablespace 'UNDOTBS1' error ?

I have added a new column to one of my tables,and I am migrating data to fill all the existing rows for this newly added column; but while executing the migration script I get the following error -
Error:ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS1'
Of whatever i searched on the net this error points to lack of space for the undo segment of oracle. is it possible to extend this space dynamically?
Any pointers to help me resolve the problem would be appreciated.
Thanks.

<snip>
How have you written your migration scripts? Does it include commits at suitable points in the script, or is it one large commit at the end?
</snip>
Actually, that is the case too. I have a one large commit at the end. To avoid this and introduce commits at some decent regular intervals, i will have to modify my script. I am trying to see if there is any other configuration solution possible :)
Thanks

UNDO tablespace resize/shrink.

Hi All ,
is it possible to shrink/resize undo tablespace.

Hi Shobhit!
I is correct that you're unable to set this parameter with ALTER SYSTEM. Please never use this parameter unless you are told to do so from oracle support. Maybe you're playing with your support if you set it by your self. To tune the size of your undo tablespace set the parameter undo_retention. Whit this parameter you tell your DB in seconds how long undo records should be kept within your undo tablespace. Automatic undotuning will be automatically activated if this parameter has a value greater than 0. To determine the correct size you need for your undotablespace use the following example:
Size of UNDO needed = UNDO_RETENTION x [UNDO block Generation per sec x DB_BLOCK_SIZE] + Overhead(30xDB_BLOCK_SIZE)
Out of these we know UNDO_RETENTION and DB_BLOCK_SIZE
All we need is to find out “UNDO Blocks per second”
Which can be easily fetched from v$undostat
SQL> SELECT (SUM(undoblks))/ SUM ((end_time - begin_time) * 24*60*60) "UPS"
2 FROM v$undostat;
UPS
8.11985583
V$undostat
stores data for every 10 mins and begin/end times are start/end time of
those intervals. We multiplied it with 24*60*60 because the difference
between two dates will be in days and to get to seconds, we need it to
multiply with 24hrs*60mins*60secs
So now we have all the values needed.
Undo size needed = [8.12 x 2000 x 8192] + [30 x 8192] = 133283840 bytes = 127.11 MB
Hope this helps!
yours sincerely

Doubt regarding ORA-30036: unable to extend segment by 8 in undo tablespace

I am using 11g Release 1 Database .
I have to analyze the performance of two tables of different designs which serve the same purpose and come up with the design which is efficient .
SQL> desc staging_dict
Name                                      Null?    Type
SNO                                                NUMBER
CODE_FRAGMENTS                                     CLOB
CODE_FRAGMENTS_U                                   CLOB
CODE_FRAGMENTS_D                                   CLOB
CODE_FRAGMENTS_DO                                  CLOB
SQL> desc staging_dict1
Name                                      Null?    Type
SNO                                                NUMBER
CODE_FRAGMENTS                                     CLOB
CODE_FRAGMENTS_UD                                  CLOB
CODE_TYPE                                          VARCHAR2(5 CHAR)Initially I tried inserting a few thousand records into both the tables . Then I did some conversion on one column and I populate the result on other column of the same table . So I update the table in bulk mode and I commit for every thousand records .
I have a undo tablespace of 2G with undo_retention=900 , retention guratantee is not set for the undo tablespace .
When I tried the conversion and update on the first table (STAGING_DICT) it took more time for around 2500 records compared to other table and when I increased the number of records to 10000 it threw an error
ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS'
But I didn't come across this error when I tried the conversion and update on the table for the same 2500 records (STAGING_DICT1) and it was also 10 times faster .
My doubt is does the error ORA-30036 occur because it is saving the undo image of all the four clob columns though I am doing conversion on one column and updating the other column (using only two columns in the update and only one column is affected by update command) ?
Also how is that having less CLOB rows prove more effective by adding one more VARCHAR column which differentiates the code_frament type in the STAGING_DICT1 table than having it as more CLOB columns as in STAGING_DICT table ?

Don't you think the error OP reported is kind of weird?
Because as you said, Oracle stores "undo" of lob in user tablespace not undo tablespace if the lob is stored out-of-line.
1. If the size of lob was small, small size of undo would be stored into undo tablespace,
and OP would'nt have undo tablespace shortage problem.
(How does small lob flood undo tablespace?)
2. If the size of lob was big, OP would have 01555 error on user tablespace not undo tablespace shortage error.
So, i think there are 2 theories that can explain this abnormality.
1. OP hit the bug of massive undo generation.
2. OP is using securefile which is 11g new feature.
Oracle documents says that undo for securefile lob is stored in "undo" tablespace, not user tablespace.
But unfortunately, i'm not sture about this coz i didn't try it myself

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

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

Unable to shrink/resize undo tablespace

Hi Experts,
I have Oracle 10.2.0.4 database running on RHEL 4.7 in production environment, my undo tablespace has grown upto 32 GB, database is rebooted, still the tablespace is full.
I want to shrink, resize the undo tablespace, please help me
Few details are as below
show parameter undo_retention
NAME TYPE VALUE
undo_retention integer 10
Please help
Thanks

This post is repeatedly executed by mistake, thread with same name is posted 2 minutes before this
Edited by: user1687821 on Jul 9, 2010 9:29 AM

Error while Droping Undo Tablespace.

Hi,
I come across following error while droping UNDO tablesapce-
ORA-01548: active rollback segment '_SYSSMU1$' found, terminate dropping tablespace
Before droping above tablespace I created a new tablespace and set UNDO_TABLESPACE=<new Tablespace>.
I even tried to drop the UNDO tablespace after restarting instance, but no vail.
Any workaround?
Thanks,

the problem's details :
SVRMGR> select segment_name,status,tablespace_name from dba_rollback_segs where
status='NEEDS RECOVERY';
SEGMENT_NAME STATUS TABLESPACE_NAME
OKRBS NEEDS RECOVERY TS_OKRBS
1 row selected.
SVRMGR> drop rollback segment OKRBS;
drop rollback segment OKRBS
ORA-01545: rollback segment 'OKRBS' specified not available
SVRMGR> select segment_name,status,tablespace_name from dba_rollback_segs;
SEGMENT_NAME STATUS TABLESPACE_NAME
SYSTEM ONLINE SYSTEM
RBS0 ONLINE RBS
RBS1 ONLINE RBS
RBS2 ONLINE RBS
RBS3 ONLINE RBS
RBS4 ONLINE RBS
RBS5 ONLINE RBS
RBS6 ONLINE RBS
ASTEK_RBS1 ONLINE TS_ROLLBKS
ASTEK_RBS2 ONLINE TS_ROLLBKS
ASTEK_RBS3 ONLINE TS_ROLLBKS
OKRBS NEEDS RECOVERY TS_OKRBS
12 rows selected.
SVRMGR> select file_name,TABLESPACE_NAME,status from dba_data_files;
FILE_NAME
TABLESPACE_NAME STATUS
/home/oracle/oradata/wil7/drsys01.dbf
DRSYS AVAILABLE
/home/oracle/oradata/wil7/indx01.dbf
INDX AVAILABLE
/home/oracle/oradata/wil7/users01.dbf
USERS AVAILABLE
/home/oracle/oradata/wil7/temp01.dbf
TEMP AVAILABLE
/home/oracle/oradata/wil7/rbs01.dbf
RBS AVAILABLE
/home/oracle/oradata/wil7/tools01.dbf
TOOLS AVAILABLE
/home/oracle/oradata/wil7/system01.dbf
SYSTEM AVAILABLE
/data1/oradata/907/INDEKS01.ORA
TS_INDEKS AVAILABLE
/data1/oradata/907/INDEKS02.ORA
TS_INDEKS AVAILABLE
/data2/oradata/907/IURAN01.ORA
TS_IURAN AVAILABLE
/data2/oradata/907/IURAN02.ORA
TS_IURAN AVAILABLE
/data2/oradata/907/JURNAL01.ORA
TS_JURNAL AVAILABLE
/data2/oradata/907/DATAPDK01.ORA
TS_PDK AVAILABLE
/data2/oradata/907/ROLLBKS01.ORA
TS_ROLLBKS AVAILABLE
/data1/oradata/907/SIMKJ01.ORA
TS_SIMKJ AVAILABLE
/data1/oradata/907/SIMKJ02.ORA
TS_SIMKJ AVAILABLE
/data2/oradata/907/TMPSIMKJ01.ORA
TS_TMPSIMKJ AVAILABLE
/data2/oradata/907/TMPSIMKJ02.ORA
TS_TMPSIMKJ AVAILABLE
/data2/oradata/907/UPAH01.ORA
TS_UPAH AVAILABLE
/data1/oradata/907/GLDATA01.ORA
TSGL_DATA AVAILABLE
/data1/oradata/907/GLBACKUP01.ORA
TSGL_BACKUP AVAILABLE
/data1/oradata/907/GLINDEX01.ORA
TSGL_INDEX AVAILABLE
/data2/oradata/907/SDM01.ORA
TS_PERSONALIA AVAILABLE
/data2/oradata/907/SDMIND01.ORA
TS_PERSOIND AVAILABLE
/data2/oradata/907/SDMPDK01.ORA
TS_PERSOPDK AVAILABLE
/data2/oradata/907/SDMROLL01.ORA
TS_PERSOROLL AVAILABLE
/data2/oradata/907/SDMTEMP01.ORA
TS_PERSOTEMP AVAILABLE
/data6/analisa/ANALISA.ORA
TS_ANALISA AVAILABLE
/data4/TS_OKTMP.ORA
TS_OKTMP AVAILABLE
/home/oracle/oradata/wil7/system02.dbf
SYSTEM AVAILABLE
/data4/TS_OKRBS.ORA
TS_OKRBS AVAILABLE
/data4/TS_OKIDX.ORA
TS_OKIDX AVAILABLE
/data5/TS_OKDTA1.ORA
TS_OKDTA AVAILABLE
/data5/TS_ODSSNP1.ORA
TS_ODSSNP AVAILABLE
/data6/TS_ODSSNP2.ORA
TS_ODSSNP AVAILABLE
/data6/TS_OKDTA2.ORA
TS_OKDTA AVAILABLE
/data2/oradata/907/ROLLBK02.ORA
TS_ROLLBKS AVAILABLE
/data1/oradata/907/SIMKJ03.ORA
TS_SIMKJ AVAILABLE
/data1/oradata/907/INVEN01.ORA
TS_INVEN AVAILABLE
/data2/oradata/907/INVENIND01.ORA
TS_INVENIND AVAILABLE
/data1/oradata/907/INVENTEMP01.ORA
TS_INVENTEMP AVAILABLE
/data1/oradata/907/GLBACKUP02.ORA
TSGL_BACKUP AVAILABLE
/data2/oradata/907/DATAPDK02.ORA
TS_PDK AVAILABLE
/data2/tssipa_data01.ora
TSSIPA_DATA AVAILABLE
/data2/tssipa_index01.ora
TSSIPA_INDEX AVAILABLE
/data2/tssipa_tmp01.ora
TSSIPA_TMP AVAILABLE
/data2/tssipa_backup01.ora
TSSIPA_BACKUP AVAILABLE
/data1/oradata/907/GLDATA02.ORA
TSGL_DATA AVAILABLE
/data1/oradata/907/GLINDEX02.ORA
TSGL_INDEX AVAILABLE
/data2/tsdpkp_data01.ora
TSDPKP_DATA AVAILABLE
/data2/tsdpkp_index01.ora
TSDPKP_INDEX AVAILABLE
/data2/TSKBL_DATA.ora
TSKBL_DATA AVAILABLE
/data2/TSKBL_INDEX.ora
TSKBL_INDEX AVAILABLE
/data2/TSKBL_BACKUP.ora
TSKBL_BACKUP AVAILABLE
/data2/SILHKDATA01.ORA
TS_SILHK_DATA AVAILABLE
/data2/SILHKINDEX01.ORA
TS_SILHK_INDEX AVAILABLE
/data2/SILHKPDK01.ORA
TS_SILHK_PDK AVAILABLE
/data2/tsdpkp_backup01.ora
TSDPKP_BACKUP AVAILABLE
58 rows selected.
SVRMGR>

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 problem

Hello, I was processing a batch job that commits every 5,000 records. I have the UNDO_RETENTION set to 10,800. UNDO_MANAGEMENT is set to AUTO. at some point the database shut down
with the following errors in the alert log:
ORA-1654: unable to extend index CRM.XIF35CUSTOMER by 16 in tablespace      RCRMCUSTIX01
ORA-1654: unable to extend index CRM.XIF35CUSTOMER by 16 in tablespace      RCRMCUSTIX01
ORA-1654: unable to extend index CRM.XIF35CUSTOMER by 16 in tablespace      RCRMCUSTIX01
ORA-1654: unable to extend index CRM.XIF35CUSTOMER by 16 in tablespace      RCRMCUSTIX01
Fri Jun 09 02:19:48 2006
KCF: write/open error block=0x1faa4f online=1
file=2 C:\ORACLE\ORADATA\CRMMGG\UNDOTBS01.DBF
error=27069 txt: 'OSD-04026: Invalid parameter passed. (OS 2075215)'
Fri Jun 09 02:19:48 2006
Errors in file c:\oracle\admin\crmmgg\bdump\crmmgg_dbw0_20680.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01114: IO error writing block to file 2 (block # 2075215)
ORA-01110: data file 2: 'C:\ORACLE\ORADATA\CRMMGG\UNDOTBS01.DBF'
ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
OSD-04026: Invalid parameter passed. (OS 2075215)
I noticed the the undo datafile is over 16GB. I reset the UNDO_RETENTION to 5 seconds. The undo tablespace data file is staying at 16GB. Is there any way to shring this file. It is a test DB so I can rebuild if necessary. What is the best way to recover from this? Thak you,
David

You are facing a generic problem on Windows platforms, when datafiles configured as AUTOEXTEND ON reach a 4GB boundary (4GB,8GB,...). The best way to avoid the problem is switch AUTOEXTEND to OFF and define the appropriate number of single datafiles for the tablespace. From metalink:
ALERT: Problems with Datafile AUTOEXTEND/RESIZE on NT/2000 Platforms
Doc ID:148894.1
Werner

Undo Tablespace and Temporary Tablespace - autoextend ?

- In general, should I allow the Undo Tablespace to grow (autoextend)?
- In general, should I allow the Temporary Tablespace to grow (autoextend)?

The size of undo tablespace should always keeps in mind otherwiase you eill get ORA-1555 or out of space errors.
This paper is to help DBA’s in calculating the size of UNDO tablespace by using a simple formula.
It is tough to know about the number of transactions and subsequently number of rows changed per second.
So I suggest having a “big undo tablespace” to start with and based on load, after doing some calculations and resize your UNDO tablespace.
In my case one of the applications was going to production (live), and I had no idea that how many transactions will happen against this database. All what I was told that there will be optimum (transactional) activity on this database.
So I started with UNDO tablespace with size of 3GB and datafiles with autoextend “on” .
Note:
In production, you must be very careful in using this (autoextend on) as the space may grow to inifinity very fast. So my advice is either dont use this option, or use with "maxsize" or continuously monitor space (which is tough).
I month later, I noticed the activity from V$undostat.
Here is the step by step approach:
Step 1: Longest running query.
SQL> select max(maxquerylen) from v$undostat;
MAX(MAXQUERYLEN)
1793
This gives you ideal value for UNDO_RETENTION. To be on the safer size you should add few more seconds to get the right value. So in my case, the size of undo retention should be say 2000 secs.
Step 2: Size of UNDO tablespace.
Size of UNDO needed = UNDO_RETENTION x [UNDO block Generation per sec x DB_BLOCK_SIZE] + Overhead(30xDB_BLOCK_SIZE)
Out of these we know UNDO_RETENTION and DB_BLOCK_SIZE
All we need is to find out “UNDO Blocks per second”
Which can be easily fetched from v$undostat
SQL> SELECT (SUM(undoblks))/ SUM ((end_time - begin_time) * 24*60*60) "UPS"
2 FROM v$undostat;
UPS
8.11985583
V$undostat stores data for every 10 mins and begin/end times are start/end time of those intervals. We multiplied it with 24*60*60 because the difference between two dates will be in days and to get to seconds, we need it to multiply with 24hrs*60mins*60secs
So now we have all the values needed.
Undo size needed = [8.12 x 2000 x 8192] + [30 x 8192] = 133283840 bytes = 127.11 MB

How can I flash back off on UNDO tablespace?

I have used flashback on ( oracle database), then I have flashed back off some tablespaces.
I have some question:
Can I flashback off on UNDO tablespace?
When I flashback on Undo tablespace, that'll impact to flashback feature or not?
Thank you.

TEST:
SQL> flashback database to timestamp to_timestamp('2008-05-20 19:13:00', 'YYYY-MM-DD HH24:MI:SS');
flashback database to timestamp to_timestamp('2008-05-20 19:13:00', 'YYYY-MM-DD HH24:MI:SS')
ERROR at line 1:
ORA-38753: Cannot flashback data file 5; no flashback log data.
ORA-01110: data file 5: '+DATA/testdb/datafile/example.1075.651074487'
ORA-38753: Cannot flashback data file 3; no flashback log data.
ORA-01110: data file 3: '+DATA/testdb/datafile/undotbs1.1086.651074273'
SQL> alter database datafile 5 oflfine;
alter database datafile 5 oflfine
ERROR at line 1:
ORA-01916: keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND or END/DROP expected
SQL> alter database datafile 5 offline;
Database altered.
SQL> flashback database to timestamp to_timestamp('2008-05-20 19:13:00', 'YYYY-MM-DD HH24:MI:SS');
flashback database to timestamp to_timestamp('2008-05-20 19:13:00', 'YYYY-MM-DD HH24:MI:SS')
ERROR at line 1:
ORA-38753: Cannot flashback data file 3; no flashback log data.
ORA-01110: data file 3: '+DATA/testdb/datafile/undotbs1.1086.651074273'
SQL> alter database datafile 3 offline;
Database altered.
SQL> flashback database to timestamp to_timestamp('2008-05-20 19:13:00', 'YYYY-MM-DD HH24:MI:SS');
Flashback complete.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
Process ID: 18585
Session ID: 115 Serial number: 5

Shrinking undo Tablespace

Shrinking undo Tablespace
What is the preferred why to shrink the UNDO Tablespace ?
1.     To create new UNDO TBS , order the DB to work whit it , and drop the oldest.
2.     To shrink (resize) the exists one .

Sagi wrote:
Shrinking undo Tablespace
What is the preferred why to shrink the UNDO Tablespace ?
1.     To create new UNDO TBS , order the DB to work whit it , and drop the oldest.
2.     To shrink (resize) the exists one .The first one would be a better approach as there may be users who are still using the old tablespace. So for all of them, you would see a Pending Offline status. Once all teh segments release the old information stored in them, you can remove the tablespace. By trying to shrink the tablespace, you actually would be increasing the chances to get the 1555 error and also, this won't be happening as already there is a used space in teh datafile.
HTH
Aman....

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 tablespace resize error

Similar Messages

Maybe you are looking for