Problem with UNDO tablespace

Hi guys.
Our database has 50GB of undo tablespace. I decided to create a second undo tablespace and switch to the new one. Since doing that yesterday, the size of the old undo is 49GB (was thinking that the values will drop to zero) and the new tablespace keeps increasing in size! Its size now is about 20GB. I do have the following question.
a) If I restart the database, it the value of the old undo going to fall to zero?
b) undo_retention=86400. Setting this value to a lesser value say 800seconds, it is going to act the performance of the database? Is it going to release the space on the old undo?
Thanks and any help is appreciated.
David

The undo tablespace will not automatically shrink size, since you have a new undo tablespace in place. You can drop the old one if you don't plan to use it.
Set lower undo_retention will certainly help to contain the undo space usage. However you should query v$undostat and v$rollstat to estimate the amount of undo space required for the current workload then size the undo tablespace accordingly. Turn off the auto extend on undo tablespace.

Similar Messages

Problem with Undo manager using highlighting

Hello,
I am writing a little text editor with syntax highlighting, but I have a problem with the UndoManager.
Everytime I undo an action the UndoManager removes just the attributes of the text, not the text itself.
Does anybody know a way how to make the UndoManager not recognizing the attributes.
Thanks in advance.

In your UndoableEditListener, you can check the type of the edit, and ignore it if it's an attribute change:
    public void undoableEditHappened(UndoableEditEvent e) {
        UndoableEdit edit = e.getEdit();
        if (edit instanceof DefaultDocumentEvent &&
            ((DefaultDocumentEvent)edit).getType() ==
                DefaultDocumentEvent.EventType.CHANGE) {
            return;
        undoMgr.addEdit(edit);
    }

Character set problem with transportable tablespace

Hi,
I'm trying to import a transportable tablespace with data pump into a database with a different character set compared to the source database. I know this is by default not possible. But there's no violating data in the tablespace that could make it a problem when transfering the TS. So I issued 'ALTER SYSTEM SET "_tts_allow_nchar_mismatch"=true;' on the target to force the import. However; I still get the eror:
ORA-29345: can not plug a tablespace into a database using a different character set
How can I fix this?

Hi,
What're the character sets of the source and target database?
A general restriction of transportable tablespace is that the source and target databases must use the same database character set.
Regards
Nat

Problem with Temporary Tablespace in 8i

Hello friends,
I have the 8.1.7.4 version, with a 18GB Temporary Tablespace.
An external process (from Datawarehouse tool) is making a query over a 10.000.000 records.
It appeared the error:
SQL error 1652 occurred when accessing table XXX
It's supposed it occurs due to temporary tablespace is full
DWH tool makes different "big" queries.. but.. are the enough to grow up to 18GB???
Any idea?
[It's not possible to change sort_area_size or any other parameter in init.ora]
Apart form this: Which would be the best way to clean this temporary tablespace?
Thanks

Jose, I think you are right and the problem is that Oracle was unable to obtain additional temp tablespace extents for the query since you mention the problem occurred on a query.
The question is was the lack of free temp due to the combination of tasks running at the time or is the plan for the query in question the issue?
If you resubmit the query does the 01652 error re-occur. If it does then I suggest grabbing a copy of the contents of v$sort_usage and resubmitting the query. Monitor the sort usage every 30 seconds, minute, or several minutes depending on how long the query runs before returning the error. This will give you an idea of how much temp space the query wants and maybe why (see following).
Also get the explain plan and see where temp is being used. One query may use multiple allocations of temp space at a time such as one chunk to support hash joins, one to support aggregation, and one to support order by so the total sort space necessary may be a lot more than you would think just based on the result set size.
In the case where the query in question is using too much temp you have to ask if the plan is the issue or if you really need more temp. When the plan is not efficient then converting to using nested loops over hash joins might be one way to eliminate excess temp space usage.
HTH -- Mark D Powell --

Problem with undo/redo actions in a StyledDocument

Hello,
In my app i have a text area where each user can keep some notes.The document is serialized and saved in the database for later access as StyledDocument, in order to be saved with the formating the user has chosen(for example with certain fonts,text color and size).
What i want to do now is to give to the user the ability to undo/redo his actions. I have these methods implemented and everything worked fine when i was saving and loading simple text in my JTextPane (previously i was saving in the database what user typed as a simple string which meant that the formatting was lost). Now, after loading styled document (using the textPane.setStyledDocument(doc) code line) these actions do not work.
Are there any suggestions on how i can make this work? Is it possible?
I hope i made my problem clear enough
Thanks in advance

Seem like I found the answer to my issue: http://helpx.adobe.com/dreamweaver/using/whats-new-2014.html#Undo/Redo enhancements
Undo/Redo enhancements
All undo/redo actions are recorded at the HTML file-level. This means, any manual changes to a CSS file can be undone from ANY related file.
Someone called it Undo/Redo enhancements!? Damn this is the most stupid thing one can imagine about undo/redo! How the heck editing one source file affects the other!? Do whatever you want in Designer mode, but I'm editing SOURCE CODE and need to be able to undo/redo my actions on a file level.
With this change TextEdit or Notepad becomes a more suitable tool for editing HTML/CSS than Dreamweaver.

Jdeveloper - Problem with undo/redo

Hi,
I am facing a problem while using the Undo/Redo option in jdeveloper. When i press the CTRL+Z(undo) option for a lengthy changes, the CTRL+Y(redo) option is not working properly.
- Shankar S

In my experience of JDev, The correct keyboard shortcut for redo is Shift + Ctrl + Z .
Ctrl + Y deletes the current line.
I don't know if that can be changed.
Remi

Problems with "Undo"

Wow - I've never seen anything like this happen with a piece of software. Updated to 1.4.1 Windows. Working on a batch of photos. While adjusting the color of one photo (church with a combination of natural, incandescent and flourescent light - ouch!), I got to the point where I wanted to undo the changes that I made to the image. I clicked on the Edit, then "Undo Orange Hue Shift". After clicking this, Lightroom proceeded to undo everything that I had done during the session, then import 17 photos from a previous session into the current catalog! Really bizarre. Needless to say, I'm back to square-one after a two hour editing session, and a bit gun-shy about clicking on the undo button again.
Is this an 'undocumented feature' in this version of Lightroom, or did the bugs just decide to bite me today? BTW - No Virus's or Spyware, plenty of memory (2 gig) and drive space (300 gig). Intel Pentium IV 2.8 gHz processor, with hyperthreading. Catalog file was backed up and tested before session started.

I'm now running version 1.4.1 and have experienced this "multiple undo" bug for multiple versions. I sent Adobe Support a message about this several months ago but got no response. Maybe they sometimes monitor this forum . . . It seems that whatever triggers the bug undoes all my edits going back to the last image which I had deleted from my catalog - either/both 'deleted from disk', or just 'removed from the catalog.' I experienced this bug today, and was dismayed to watch it rapidly undoing maybe 50 edits across multiple images. Shortly afterwards, as I scrambled to repair the damage, I got an error message: --------------------------- Lightroom --------------------------- Database "D:\<snip>...Lightroom1.lrcat": unable to open database file Statement: SELECT id_local FROM Adobe_images WHERE masterImage = ? and was unable to access the Develop controls for several images. This message appeared every time I clicked the File menu, but Alt+F4 eventually succeeded in closing Lightroom; it seems OK once restarted.

9i on Linux. Problems with Temp tablespace cleanup

I am currently running Oracle 9i Enterprise on SUSE Linux 7.2.
I am executing queries against the new XMLType datatype and every query adds to the Temp tablespace, which doesn't get cleaned up. Eventually, the tablespace will run out of space and Oracle will issue and error:
ORA-01652: unable to extend temp segment by 128 in tablespace <name>
The only way to clean up the Temp tablespace seems to be by restarting the server.
Is that happening on other platforms as well? I would appreciate any help.

Hi
You can connect to the database as DBA (Sys or System) and make a bigger temporal tablespace. Or create a new bigger temporary tablespace and assign it to the user.
A10!
PS: Temporary tablespace is used when no memory available for the session, for example when a big ORDER BY is done. Try to increase the memory assigned, just look at initXXX.ora (sort_size)

Problems with resizing tablespace.

Hello
When I installed Oracle Application Express I use SYSAUX as default tablespace.
During unsuccessful transaction I increased this tablespace up to 5,5 Gb. After dropping all unneeded data I have 700 Mb of used space.
When I tried to alter database datafile ... resize 1 Gb, I received an error ORA-03297: file contains used data beyond requested RESIZE value .
Is there some way to defragment tablespace
Best Regards, Kostya Proskudin
P.S. I use 10g

Never use SYSAUX or SYSTEM tablespace as the default tablespace. Query dba_extents to find out which segments are located towards the end of the file, then move these segments to another tablespace and then you'll be able to shrink the datafile, unless of course, a sys or system extent is occupying the space.

Problem with full database backup.

This is what I got after execute backup full database statement
"RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/03/2009 14:15:15
ORA-19502: write error on file "/u01/app/oracle/backup/ORCL/ora_df680537660_s2_s1", blockno 25985 (blocksize=8192)
ORA-27072: File I/O error
Linux Error: 2: No such file or directory
Additional information: 4
Additional information: 25985
Additional information: 483328"
I have quite the same problem with create tablespace, I can't create tablespace 512m, but I can create the same tablespace only 100m.
I think it must be somethink with storage???

Starting backup at 03-MAR-09
using channel ORA_DISK_1
input datafile fno=00015 name=/u01/app/oracle/oradata/o2_mf_system_48fprop3_.dbf
input datafile fno=00003 name=/u01/app/oracle/oradata/ORCL/datafile/o1_mf_sysaux_48fpropg_.dbf
input datafile fno=00014 name=/u01/app/oracle/oradata/o2_mf_sysaux_48fpropg_.dbf
input datafile fno=00005 name=/u01/app/oracle/oradata/ORCL/datafile/o1_mf_example_48fpw04c_.dbf
input datafile fno=00017 name=/u01/app/oracle/oradata/ORCL/datafile/rcvcat01.dbf
input datafile fno=00002 name=/u01/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs1_48fprovo_.dbf
input datafile fno=00016 name=/u01/app/oracle/oradata/inventory03.dbf
input datafile fno=00011 name=/u01/app/oracle/oradata/ORCL/datafile/inventory01.dbf
input datafile fno=00012 name=/u01/app/oracle/oradata/ORCL/datafile/inventory02.dbf
input datafile fno=00006 name=/u01/app/oracle/oradata/ORCL/datafile/ts01.dbf
input datafile fno=00008 name=/u01/app/oracle/oradata/ORCL/datafile/ts02.dbf
input datafile fno=00001 name=/u01/app/oracle/oradata/ORCL/datafile/o1_mf_system_48fprop3_.dbf
channel ORA_DISK_1: specifying datafile(s) in backupset
channel ORA_DISK_1: starting full datafile backupset
input datafile fno=00009 name=/u01/app/oracle/oradata/ORCL/datafile/undo01.dbf
channel ORA_DISK_1: starting piece 1 at 03-MAR-09
input datafile fno=00013 name=/u01/app/oracle/oradata/ORCL/datafile/val01.dbf
input datafile fno=00007 name=/u01/app/oracle/oradata/ORCL/datafile/test_reorg0
input datafile fno=00004 name=/u01/app/oracle/oradata/ORCL/datafile/o1_mf_users_48fprowb_.dbf
input datafile fno=00010 name=/u01/app/oracle/oradata/ORCL/datafile/ts01b.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/03/2009 14:15:15
ORA-19502: write error on file "/u01/app/oracle/backup/ORCL/ora_df680537660_s2_s1", blockno 25985 (blocksize=8192)
ORA-27072: File I/O error
Linux Error: 2: No such file or directory
Additional information: 4
Additional information: 483328
Additional information: 25985
Directory exist because I can backup single tablespace, into the same directory, I just can't backup whole database.
Edited by: val75 on Mar 3, 2009 1:57 PM

Dropping Undo Tablespace

Hi,
I am running Oracle 9.2 on Solaris. I have Automatic undo management turned on and have a Undo tablespace by name UNDOTBS. It has a single datafile and has AUTOEXTEND feature turned on. My UNDO_RETENTION was set to 4 hours.
Presently, the size of UNDOTBS has grown to around 40G and has filled up the file system in which it resides. I need to clean up the file system. In order to do this, I followed the below procedure.
SQL> create undo tablespace UNDOTBS1 datafile '/u04/oradata/proddb/undo_00.dbf' size 1024M autoextend off;
SQ> alter system set undo_tablespace=undotbs1 scope=both;
SQL> alter system set undo_retention=3600 scope=both;
Now, i checked the alert log and it is offlining all the UNDO segments of the first undo tablespace UNDOTBS. It is taking time and has been more than 1.5 hours. I have a couple of questions here,
1. As i have issued "alter system undo_tablespace=undotbs1 scope=both", all the new transactions will use the new UNDOTBS1. No new transactions will be using the first undo tablespace UNDOTBS right?
2. Since, i have issued "alter system undo_retention=3600 scope=both", all the transactions in first undo tablespace UNDOTBS will be rolled back after 2 hours, no matter if it is commited or not. After this period, i am safe to drop the first undo tablespace using "drop tablespace UNDOTBS including contents and datafiles;". Did i get it right?
Any information will be of a great help.
THanks,
Harris.

Hi,
Thank you all for the replies. It has been two days since i switched the undo_tablespace to use the new tablespace(undotbs1) but my alert log is still being flooded with " Undo tablespace 1 moved to pending switch out state". I tried the following to see if there are any rows returne from the above query and it did 3 rows, showing some undo segments with the following output
SQL> select a.name, b.status from v$rollname a, v$rollstat b where a.name in (select segment_name from dba_segments where tablespace_name='UNDOTBS') and a.usn=b.usn;
Name Status
_SYSSMU15$      UNKNOWN
_SYSSMU33$      UNKNOWN
_SYSSMU9$        PENDING OFFLINE
I have seen gone through the metalink id: 341372.1 that speaks about this SWITCH-OUT state. How can i make sure what old transactions are still using the Undo segments in first undo tablespace and how can i go about killing them. Could anyone please let me know that i could use the following queries to find the correct sessions that are using the Old Undo tablespace.
SQL> select ADDR, XIDUSN,STATUS, START_TIME from v$transaction;
SQL> SELECT
a.usn,
a.name,
b.status,
c.tablespace_name,
d.addr,
e.sid,
e.serial#,
e.username,
e.program,
e.machine,
e.osuser
FROM
v$rollname a,
v$rollstat b,
dba_rollback_segs c,
v$transaction d,
v$session e
WHERE
a.usn=b.usn AND
a.name=c.segment_name AND
a.usn=d.xidusn AND
d.addr=e.taddr AND
b.status='PENDING OFFLINE';
Just wanted to make sure that the second query lists the PENDING OFFLINE segments of the first tablespace right?
This is a prod. box, so wanted to confirm with you guys before proceeding.
Thanks,
Harris.

Curropt Undo tablespace

Hi,
Was doing an exercise of bringing the database up if one of the datafile is curropt and the data on that data file is not required.
I did this:-
1. While the database is running I edited the datafile , dropped some junk in it.
2. Shutdown.
3. Startup mount
4. alter database datafile 'xxx' offline drop;
5. alter database open;
6. drop tablespace yyy.
7. create tablespace.
Worked ok.
But when I tried this for undo (just out of curiosity).
alter database datafile...
alter database open;
create undo tablspace new_undo;
alter system set undo_tablespae = new_undo;
drop old undo_tbs <<<< failed.
says active rollback segment exists.
Actually I tried this exercise twice first time I was able to drop the old undo tablespace but the second time it didn't.
Can somebody show how to open the database in this scenario i.e if the datafile asscoiated with undo tablespace is curropt.
Thanks.

Hi,
The size of the undo tablespace is related to the transaction activity and size and the setting of the undo_retention parameter.
You can use the undo advisor in OEM for setting an optimal value or size (see link).
http://www.oracle.com/technology/obe/10gr2_db_vmware/manage/undo/undoadv.htm#t4
Can you post the current size of thedatabase, the undo tablespace and the value of undo_retention?
Regards,
Tycho

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

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

Undo tablespace growing fast

Hello All
We are having issues with undo tablespace growing... the oracle version is 10.2.0.1.0
the table is holding around 400000000 records and this table is also partitioned by range
any reason for this undo tablespace growing by at an high rate
regards
Kedar

Undo tablespaces are special tablespaces used solely for storing undo information. You cannot create any other segment types (for example, tables or indexes) in undo tablespaces. Each database contains zero or more undo tablespaces. In automatic undo management mode, each Oracle instance is assigned one (and only one) undo tablespace. Undo data is managed within an undo tablespace using undo segments that are automatically created and maintained by Oracle.
Every Oracle Database must have a method of maintaining information that is used to roll back, or undo, changes to the database. Such information consists of records of the actions of transactions, primarily before they are committed. These records are collectively referred to as undo.
Undo records are used to:
Roll back transactions when a ROLLBACK statement is issued
Recover the database
Provide read consistency
Analyze data as of an earlier point in time by using Oracle Flashback Query
Recover from logical corruptions using Oracle Flashback features
When a ROLLBACK statement is issued, undo records are used to undo changes that were made to the database by the uncommitted transaction. During database recovery, undo records are used to undo any uncommitted changes applied from the redo log to the datafiles. Undo records provide read consistency by maintaining the before image of the data for users who are accessing the data at the same time that another user is changing it.
You confuse TEMP with UNDO tablespace.
Best Regards,
Francisco Munoz Alvarez
www.oraclenz.com

Problem with UNDO tablespace

Similar Messages

Maybe you are looking for