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
Similar Messages
-
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 -
SYSAUX tablespace resize/shrink
Hi All,
I'm using 11g SE on Linux, and SYSAUX tablespace has grown too large (32Gb). I've reclaimed a space and the question is Is there any chance to resize this tablespace back to small size (let's say to 5Gb)?
I'll appreciate any help.
Thank you.Hi,
Here it is an output. I've removed some stuff to fit the message limit.
~~~~~~~~~~~~~~~
AWR INFO Report
~~~~~~~~~~~~~~~
Report generated at 10:36:09 on May 29, 2013 ( Wednesday ) in Timezone +01:00
Warning: Non Default AWR Setting!
Snapshot interval is 60 minutes and Retention is 8 days
DB_ID DB_NAME HOST_PLATFORM INST STARTUP_TIME LAST_ASH_SID PAR
* 182010396 PROD db01p2.db.mydomain.com - Linux x86 6 2 14:54:16 (03/26) 0 YES
4-bit
(I) AWR Snapshots Information
(1a) SYSAUX usage - Schema breakdown (dba_segments)
|
| Total SYSAUX size 1,790.6 MB ( 5% of 32,768.0 MB MAX with AUTOEXTEND ON )
|
| Schema SYS occupies 1,245.0 MB ( 69.5% )
| Schema XDB occupies 157.6 MB ( 8.8% )
| Schema PERFSTAT occupies 151.8 MB ( 8.5% )
| Schema APEX_030200 occupies 77.4 MB ( 4.3% )
| Schema MDSYS occupies 65.8 MB ( 3.7% )
| Schema SYSMAN occupies 45.3 MB ( 2.5% )
| Schema SYSTEM occupies 13.7 MB ( 0.8% )
| Schema ORDDATA occupies 13.6 MB ( 0.8% )
| Schema OLAPSYS occupies 5.1 MB ( 0.3% )
| Schema DBSNMP occupies 4.1 MB ( 0.2% )
| Schema EXFSYS occupies 3.6 MB ( 0.2% )
| Schema CTXSYS occupies 3.6 MB ( 0.2% )
| Schema WMSYS occupies 3.5 MB ( 0.2% )
| Schema ORDSYS occupies 0.4 MB ( 0.0% )
|
(1b) SYSAUX occupants space usage (v$sysaux_occupants)
|
| Occupant Name Schema Name Space Usage
| -------------------- -------------------- ----------------
| SM/AWR SYS 888.0 MB
| SM/OPTSTAT SYS 266.6 MB
| XDB XDB 157.6 MB
| STATSPACK PERFSTAT 151.8 MB
| SDO MDSYS 65.8 MB
| EM SYSMAN 45.3 MB
| AO SYS 36.3 MB
| XSOQHIST SYS 36.3 MB
| ORDIM/ORDDATA ORDDATA 13.6 MB
| LOGMNR SYSTEM 12.3 MB
| SM/ADVISOR SYS 11.3 MB
| JOB_SCHEDULER SYS 9.9 MB
| SM/OTHER SYS 7.1 MB
| XSAMD OLAPSYS 5.1 MB
| EM_MONITORING_USER DBSNMP 4.1 MB
| EXPRESSION_FILTER EXFSYS 3.6 MB
| TEXT CTXSYS 3.6 MB
| WM WMSYS 3.5 MB
| SMON_SCN_TIME SYS 3.3 MB
| SQL_MANAGEMENT_BASE SYS 1.7 MB
| PL/SCOPE SYS 1.6 MB
| LOGSTDBY SYSTEM 1.4 MB
| STREAMS SYS 1.0 MB
| ORDIM ORDSYS 0.4 MB
| AUTO_TASK SYS 0.3 MB
| AUDIT_TABLES SYS 0.0 MB
| ORDIM/ORDPLUGINS ORDPLUGINS 0.0 MB
| ORDIM/SI_INFORMTN_SC SI_INFORMTN_SCHEMA 0.0 MB
| TSM TSMSYS 0.0 MB
| ULTRASEARCH WKSYS 0.0 MB
| ULTRASEARCH_DEMO_USE WK_TEST 0.0 MB
|
| Others (Unaccounted space) 59.4 MB
|
(1c) SYSAUX usage - Unregistered Schemas
| This section displays schemas that are not registered
| in V$SYSAUX_OCCUPANTS
|
| Schema APEX_030200 occupies 77.4 MB
|
| Total space 77.4 MB
|
(1d) SYSAUX usage - Unaccounted space in registered schemas
|
| This section displays unaccounted space in the registered
| schemas of V$SYSAUX_OCCUPANTS.
|
| Unaccounted space in SYS/SYSTEM -18.1 MB
|
| Total space -18.1 MB
|
(2) Size estimates for AWR snapshots
|
| Estimates based on 60 mins snapshot INTERVAL:
| AWR size/day 53.0 MB (2,262 K/snap * 24 snaps/day)
| AWR size/wk 371.1 MB (size_per_day * 7) per instance
| AWR size/wk 1,484.4 MB (size_per_day * 7) per database
|
| Estimates based on 12 snaps in past 24 hours:
| AWR size/day 26.5 MB (2,262 K/snap and 12 snaps in past 24 hours)
| AWR size/wk 185.6 MB (size_per_day * 7) per instance
| AWR size/wk 742.2 MB (size_per_day * 7) per database
|
(3a) Space usage by AWR components (per database)
COMPONENT MB % AWR KB_PER_SNAP MB_PER_DAY MB_PER_WEEK TABLE% : INDEX%
FIXED 860.8 96.9 2,193 25.7 179.9 55% : 45%
SPACE 18.1 2.0 46 0.5 3.8 59% : 41%
EVENTS 3.5 0.4 9 0.1 0.7 50% : 50%
SQL 2.9 0.3 7 0.1 0.6 37% : 63%
ASH 1.5 0.2 4 0.0 0.3 50% : 50%
RAC 0.6 0.1 2 0.0 0.1 50% : 50%
SQLTEXT 0.1 0.0 0 0.0 0.0 50% : 50%
SQLPLAN 0.1 0.0 0 0.0 0.0 50% : 50%
SQLBIND 0.1 0.0 0 0.0 0.0 50% : 50%
(3b) Space usage within AWR Components (> 500K)
COMPONENT MB SEGMENT_NAME - % SPACE_USED SEGMENT_TYPE
FIXED 336.0 WRH$_SYSMETRIC_HISTORY - 12% TABLE
FIXED 296.0 WRH$_SYSMETRIC_HISTORY_INDEX - 18% INDEX
FIXED 88.0 WRH$_SYSMETRIC_SUMMARY - 10% TABLE
FIXED 42.0 WRH$_SYSMETRIC_SUMMARY_INDEX - 18% INDEX
FIXED 24.0 WRH$_WAITCLASSMETRIC_HISTORY - 21% TABLE
FIXED 21.0 WRH$_WAITCLASSMETRIC_HIST_IND - 17% INDEX
FIXED 16.0 WRM$_SNAPSHOT_DETAILS_INDEX - 80% INDEX
FIXED 10.0 WRM$_SNAPSHOT_DETAILS - 92% TABLE
SPACE 0.9 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12506 - 82% TABLE PARTITION
SPACE 0.9 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12530 - 84% TABLE PARTITION
SPACE 0.8 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12458 - 89% TABLE PARTITION
SPACE 0.8 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12650 - 88% TABLE PARTITION
SPACE 0.8 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12626 - 87% TABLE PARTITION
SPACE 0.8 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12602 - 86% TABLE PARTITION
SPACE 0.8 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12578 - 87% TABLE PARTITION
SPACE 0.8 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12482 - 89% TABLE PARTITION
SPACE 0.8 WRH$_SEG_STAT.WRH$_SEG_ST_182010396_12554 - 89% TABLE PARTITION
SPACE 0.7 WRH$_SEG_STAT_OBJ - 46% TABLE
SPACE 0.6 WRH$_SEG_STAT_OBJ_INDEX - 22% INDEX
SPACE 0.6 WRH$_SEG_STAT_OBJ_PK - 26% INDEX
SPACE 0.5 WRH$_SEG_STAT_PK.WRH$_SEG_ST_182010396_12554 - 63% INDEX PARTITION
SPACE 0.5 WRH$_SEG_STAT_PK.WRH$_SEG_ST_182010396_12626 - 51% INDEX PARTITION
(4) Space usage by non-AWR components (> 500K)
COMPONENT MB SEGMENT_NAME SEGMENT_TYPE
NON_AWR 104.0 SYS.I_WRI$_OPTSTAT_H_OBJ#_ICOL#_ST INDEX
NON_AWR 80.0 SYS.WRI$_OPTSTAT_HISTGRM_HISTORY TABLE
NON_AWR 53.2 XDB.SYS_LOB0000057465C00025$$ LOBSEGMENT
NON_AWR 50.0 SYS.I_WRI$_OPTSTAT_H_ST INDEX
NON_AWR 18.0 MDSYS.SYS_LOB0000064008C00006$$ LOBSEGMENT
NON_AWR 16.1 SYS.SYS_LOB0000065858C00004$$ LOBSEGMENT
NON_AWR 13.0 SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY TABLE
NON_AWR 9.0 SYS.I_WRI$_OPTSTAT_HH_OBJ_ICOL_ST INDEX
NON_AWR 8.0 XDB.XDB$RESOURCE TABLE
NON_AWR 7.2 SYS.SYS_LOB0000065843C00004$$ LOBSEGMENT
NON_AWR 7.0 MDSYS.SDO_CS_SRS TABLE
NON_AWR 5.0 SYS.SCHEDULER$_EVENT_LOG TABLE
NON_AWR 5.0 APEX_030200.WWV_FLOW_DICTIONARY$CAPED INDEX
NON_AWR 5.0 PERFSTAT.STATS$SQL_PLAN TABLE
NON_AWR 5.0 PERFSTAT.STATS$SQL_PLAN_USAGE TABLE
NON_AWR 5.0 PERFSTAT.STATS$SQLTEXT TABLE
NON_AWR 5.0 APEX_030200.WWV_FLOW_PAGE_PLUGS TABLE
NON_AWR 5.0 APEX_030200.WWV_FLOW_STEP_ITEMS TABLE
NON_AWR 4.2 SYS.SYS_LOB0000065848C00004$$ LOBSEGMENT
NON_AWR 4.0 APEX_030200.WWV_FLOW_DICTIONARY$ TABLE
NON_AWR 4.0 SYSTEM.SYS_LOB0000001147C00009$$ LOBSEGMENT
NON_AWR 4.0 SYS.SCHEDULER$_INSTANCE_PK INDEX
NON_AWR 4.0 SYS.I_WRI$_OPTSTAT_HH_ST INDEX
NON_AWR 3.2 SYS.SYS_LOB0000065838C00004$$ LOBSEGMENT
NON_AWR 3.0 XDB.XDB$H_INDEX TABLE
(5a) AWR snapshots - last 50
Total snapshots in DB 182010396 Instance 3 = 201
Total snapshots in DB 182010396 Instance 2 = 201
DBID SNAP_ID INST FLUSH_ELAPSED ENDTM STARTUP_TIME STATUS ERRCNT
182010396 12678 2 +00000 00:00:00.1 08:00:41 (05/29) 14:54:16 (03/26) 0 0
182010396 12678 3 +00000 00:00:00.5 08:00:41 (05/29) 14:56:33 (03/26) 0 0
182010396 12679 2 +00000 00:00:00.1 09:00:59 (05/29) 14:54:16 (03/26) 0 0
182010396 12679 3 +00000 00:00:00.1 09:00:59 (05/29) 14:56:33 (03/26) 0 0
182010396 12680 2 +00000 00:00:00.9 10:00:10 (05/29) 14:54:16 (03/26) 0 0
182010396 12680 3 +00000 00:00:00.1 10:00:10 (05/29) 14:56:33 (03/26) 0 0
(5b) AWR snapshots with errors or invalid
no rows selected
(5c) AWR snapshots -- OLDEST Non-Baselined snapshots
DBID INST SNAP_ID ENDTM STATUS ERROR_COUNT
182010396 2 12480 02:00:25 (05/21) 0 0
(6) AWR Control Settings - interval, retention
DBID LSNAPID LSPLITID LSNAPTIME LPURGETIME FLAG INTERVAL RETENTION VRSN
182010396 12680 12671 05/29 10:00:11 05/29 01:13:59 2 +00000 01:00:00.0 +00008 00:00:00.0 5
(7a) AWR Contents - row counts for each snapshots
SNAP_ID INST ASH SQL SQBND FILES SEGST SYSEVT
12656 2 0 0 0 0 104 0
12679 2 0 0 0 0 107 0
SNAP_ID INST ASH SQL SQBND FILES SEGST SYSEVT
12679 3 0 0 0 0 113 0
12680 2 0 0 0 0 110 0
12680 3 0 0 0 0 109 0
(7b) AWR Contents - average row counts per snapshot
SNAP_COUNT INST ASH SQLSTAT SQLBIND FILES SEGSTAT SYSEVENT
201 3 0 0 0 0 108.27 0
201 2 0 0 0 0 109.23 0
(7c) AWR total item counts - names, text, plans
SQLTEXT SQLPLAN SQLBMETA SEGOBJ DATAFILE TEMPFILE
0 0 0 2784 0 0
(II) Advisor Framework Info
(1) Advisor Tasks - Last 50
OWNER/ADVISOR TASK_ID/NAME CREATED EXE_DURATN EXE_CREATN HOW_C STATUS
SYS/SQL Tuning 1/SYS_AUTO_SQL_TUNING_TASK 09:52:13 (09/17) AUTO INITIAL
SYS/Segment Ad 10161/SYS_AUTO_SPCADV_5215001005 00:15:52 (05/10) 2,925 2,925 CMD COMPLETED
2013
SYS/Segment Ad 10162/SYS_AUTO_SPCADV_3804011005 01:04:38 (05/10) 50 50 CMD COMPLETED
(2) Advisor Task - Oldest 5
OWNER/ADVISOR TASK_ID/NAME CREATED EXE_DURATN EXE_CREATN HOW_C STATUS
SYS/Segment Ad 9980/SYS_AUTO_SPCADV_04002329042 23:00:04 (04/29) 426 427 CMD COMPLETED
013
SYS/Segment Ad 9990/SYS_AUTO_SPCADV_16002330042 23:00:16 (04/30) 5,519 5,519 CMD COMPLETED
013
SYS/Segment Ad 9991/SYS_AUTO_SPCADV_16320001052 00:32:17 (05/01) 2,831 2,831 CMD COMPLETED
013
SYS/Segment Ad 9992/SYS_AUTO_SPCADV_29190101052 01:19:29 (05/01) 80 80 CMD COMPLETED
013
SYS/Segment Ad 10000/SYS_AUTO_SPCADV_1300230105 23:00:13 (05/01) 445 445 CMD COMPLETED
2013
(3) Advisor Tasks With Errors - Last 50
OWNER/ADVISOR TASK_ID/NAME CREATED EXE_DURATN EXE_CREATN HOW_C STATUS
TASK_DESC
ERROR_MSG
SYS/SQL Tuning 1/SYS_AUTO_SQL_TUNING_TASK 09:52:13 (09/17) AUTO INITIAL
Description: Automatic SQL Tuning Task
Error Msg :
(III) ASH Usage Info
(1a) ASH histogram (past 3 days)
(1b) ASH histogram (past 1 day)
(2a) ASH details (past 3 days)
(2b) ASH details (past 1 day)
(2c) ASH sessions (Fg Vs Bg) (past 1 day across all instances in RAC)
Foreground %
Background %
MMNL %
End of Report -
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
ThanksThis 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 -
Unable to shrink undo tablespace... Help!
Hi,
I have problems to shrink the system undo tablespace, which has grown up to 14 GB.
I use 9.2. Table space owner is 'SYSTEM', undo_management = AUTO.
I tried to shrink the greatest rollback segments by the commands
ALTER SESSION SET UNDO_SUPPRESS_ERRORS = TRUE;
ALTER ROLLBACK SEGMENT "_SYSSMU6$" SHRINK TO 20 M;
Oracle confirmed these commands, but nothing happened.
What am I doing wrong?
Hermann MuellerYou have seen the discussion about the undo segments, on the temporary tablespaces, you should be aware that the sort segment of a given temporary tablespace is created at the time the first sort operation takes place. The sort segment continues to grow by means of extent allocation until the segment size has reached the total storage demands of all of the active sorts running on the instance. Oracle will keep on allocating temporary space on demand unless the physical limit states otherwise.
Temporary segments are produced each time a sort operation (explicit -order by- or implicit -aggregation, reindexing-) requires to sort a set that cannot fit into memory. So if you detect excesive sort usage you should aim your monitors towards the sort operations (reports, reindexing, max, min, aggregations, order by ...). If your system has a DDS behaviour, this kind of operations are frequent as a massive sorting has to be peformed against millions of rows.
A Temporary tablespace will almost always appear to be near 100% full, that's because once oracle has allocated temporary space it doesn't release it back to the free space, it keeps it allocated even when the sort operation has finished. Criteria behind this fact is similar to the one oracle used to have when the rollback segments were in use, Oracle only allocated space and the dba should perform manual actions to release space, and the criteria is performance. Once it has allocated space this big, there are possibilities that the same circumstances that raised the temporary usage high water mark to this level are repeated, so if oracle keeps the mamimum allocated space, it won't have to allocate the same storage once more.
Main concern with temporary tablespace growth is not free space itself, but the reasons why this amount of space was allocated, so I suggest you to track the sql statements with sort operations. If you are certain the circumstances that motivated this amount of temporary resources to be allocated won't be repeated again, then you could think of resizing down your temporary tablespace. I suggest you to create a new temporary tablespace with the desired size, and alter the default tempoary tablespace to point to this newly crated temporary tablespace, and finally get rid of the original temporary TS.
~ Madrid -
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 -
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.... -
Segment shrinking and UNDO tablespace
When i issued
alter table <table_name> shrink space cascade;
I got the error 'Unable to extend UNDO ...by 8' . Does Segment shrinking consume space from UNDO tablespace?
Message was edited by:
for_good_reasonAs Jonathan said, shrinking segment generates redo and undo data.
But, this phoenomenon of undo shortage is not normal case.
Shrinking segment might invole continous DML(deleting and re-inserting),
but it's transaction seems to be committed internally at regular intervals.
For this reason, shrinking operation should not hold undo area that long.
But have no knowledge on exact behavior of shrink operation.
Someone else will shed a light.
How big your table and indexes?
Some cases are reorted that shrinkage on big segment generates really large amount of undo data.
This might be related with your problem. But not sure.
Visit metalink note# 3888229. -
Hello,
We had a UNDO Tablespace of 22Gb but it is using just 2GB. How to shrink undo tablespace. we are using clustered 3 node production database 10.2.0.4
Is there is way that we can shrink UNDO Tablespace or do i need to create a UNDO tablespace and assign the undo tablespace to DB and drop the old UNDO?
How to ensure that transactions are done and free to drop the old UNDO?
Is it something we need to restart all the three nodes as each node has its own UNDO Tablespace.
Need Help on this issue.
would appreciate your quick response.
Thanksif i am in your place i will do the following:
<pre class="jive-pre">1-Query DBA_DATA_FILES to determine the name of the datafiles of the UNDO</pre>
2. Create a new UNDO tablespace.
<pre class="jive-pre">CREATE UNDO TABLESPACE undo_ts2 DATAFILE '/directory/undo_ts2_01.dbf' SIZE xxxM;</pre>
3. Modify the database parameter to use the new UNDO tablespace.
<pre class="jive-pre"> ALTER SYSTEM SET undo_tablespace=undo_ts2 SCOPE=BOTH; </pre>
4-The Drawback:
<pre class="jive-pre">New transactions will begin using the new undo tablespace. After some time passes (at least the number of seconds specified by the UNDO_RETENTION initialization parameter), you can drop the old UNDO tablespace. The downside to this approach is that for a short time period, your database will have two UNDO tablespaces</pre>
Regards
Mohamed -
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 -
Hi guys.
Our database has 50GB of undo tablespace. I decided to create a second undo tablespace and switch to the new one. Since doing that yesterday, the size of the old undo is 49GB (was thinking that the values will drop to zero) and the new tablespace keeps increasing in size! Its size now is about 20GB. I do have the following question.
a) If I restart the database, it the value of the old undo going to fall to zero?
b) undo_retention=86400. Setting this value to a lesser value say 800seconds, it is going to act the performance of the database? Is it going to release the space on the old undo?
Thanks and any help is appreciated.
DavidThe undo tablespace will not automatically shrink size, since you have a new undo tablespace in place. You can drop the old one if you don't plan to use it.
Set lower undo_retention will certainly help to contain the undo space usage. However you should query v$undostat and v$rollstat to estimate the amount of undo space required for the current workload then size the undo tablespace accordingly. Turn off the auto extend on undo tablespace. -
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,
DavidYou 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 -
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 thanksyeah,
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 -
How the undo tablespace grows very fast., how can we control on it. When I try to resize it did not allow me, what exact action can i take it.
>> How the undo tablespace grows very fast., how can we control on it.
It’s all depending on the DML transaction activities on your database i.e. frequent inserts,updates, and deletes.
>> When I try to resize it did not allow me, what exact action can i take it.
How/What you tried to resize it. Can you show the details??
Moreover, Do take a look at the Oracle Documentation on "Managing the Undo Tablespace"
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/undo.htm
Regards,
Sabdar Syed.
Added the link.
Message was edited by:
Sabdar Syed -
hello
my database version is 11.2.0.1.0
My undo tablespace was around 36 gb and around 4gb was free.
But now the size is decreasing and it is decreasing fast. What should i do. I increased it by another 2gb. How do i monitor it so that i can tune it without resizing it again.
please guide me.
Thanks in advance.user12045405 wrote:
hello
my database version is 11.2.0.1.0
My undo tablespace was around 36 gb and around 4gb was free.
But now the size is decreasing and it is decreasing fast. What should i do. I increased it by another 2gb. How do i monitor it so that i can tune it without resizing it again.
please guide me.
Thanks in advance.Decreasing or increasing? It's not an issue but a normal thing since 10g onwards. Please see MOS Doc 413732.1 .
HTH
Aman....
Maybe you are looking for
-
For years I have used Apple's recommended standard technique whenever I wanted to download a Flash video embedded in a YouTube page to my hard drive: - Open a YouTube page and click on the video's "play" button to get it started; - Press command-opti
-
I have attempted to download a movie from iTunes several times over the past several days. Initially received an err= 8008 code. Submitted ticket to Apple and was told that they would put it back in my Available Downloads and was told to try again.
-
Can someone explain to me output differences between the above two? Thanks, n point will be awarded
-
How to create soap envelope structure
Hello Friends, I am working on a RFC to webservice sync scenario.Here I am getting response from webservice in soap envelope form which is not matching with my wsdl response structure. I have tried to create the envelope structure manually but i din
-
Can't access HD, please help!!
I know this is more for peripherals (and I posted there too), but I am desperate, and working under a deadline! Hi everyone, I have a 120 GB Western Digital external Hard Drive. I've only had it about two years, and until now haven't had any problems