Full undo tablespace confusion

Similar Questions

• Undo Tablespace is not erasing in 11 GR 2 DB

  Hello
  
  There are 2 undo tablespace APPS_UNDOTS1 and APPS_UNDOTS2. APPS_UNDOTS2 is not used frequently while APPS_UNDOTS1 is used frequently.
  Problem is that these storage spaces are not deleted automatically. We even tried to bounce the database but no help. There are often increase the size of the tablespace by adding the data file.
  There is no work around for this problem? What should be the impact if we auto expand on these storage spaces?
  
  Here is the information:
  
  Operating system platform: IBM AIX 6.1.0.0, 64-bit
  Product: Oracle E-Business Suite R1212
  Database version: 11.2.0.1.0
  Is active RAC: Yes
  Is active ASM: Yes
  Database nodes: 2
  
  
  SQL > show Cancel parameter;
  VALUE OF TYPE NAME
  ------------------------------------ ----------- ------------------------------
  UNDO_MANAGEMENT string AUTO
  UNDO_RETENTION integer 900
  undo_tablespace string APPS_UNDOTS1
  
  SQL > SELECT DISTINCT STATUS, SUM (BYTES), COUNT (*)
  DBA_UNDO_EXTENTS GROUP OF STATUS;
  
  STATUS SUM (BYTES) COUNT (*)
  --------- ---------- ----------
  EXPIRED 89718784 1294
  RUN 3.2242E + 10 17929
  1773862912 2261 ASSETS
  
  Cancel the use of TBS:
  Nom_tablespace AVAIL USE % FREE opportunity
  ------------------------------ -------------------------------------
  15120 9875 5245 65.31 APPS_UNDOTS2
  
  28432 APPS_UNDOTS1 22823.6875 5608,3125 80.27
  
  Undo retention is dry and there is not sufficient 900 scopes CANCEL remaining, so no idea why Undo SCT is not having erased?
  
  
  Kind regards
  Purnima

  Normal and expected - behavior for an explanation see MOS Doc 413732.1 (Full UNDO Tablespace in gr 10, 2)

  Srini

• UNDO tablespace fills

  My undo tablespace fills due to no deletions by the jdbc thin client sessions.
  How can I solve this problem permanently?
  
  The undo tablespace size is 5.5 GB
  
  I am facing a complete problem of the undo tablespace
  Here are the sessions that may be causing the problem.
  
  
  Select s.sid,
  s.Serial #.
  s.sql_id,
  s.prev_sql_id,
  s.SCHEMANAME,
  s.OSUSER,
  s.Program,
  USED_UBLK, USED_UREC from v$ session s, v$ transaction t where order of s.taddr = USED_UREC t.addr;
  
  3909 30842 fgcp0qn1bqzx9 XLTDB5 xltwrk5 JDBC Thin Client 504 45257
  5133 53593 fgcp0qn1bqzx9 XLTDB5 xltwrk5 JDBC Thin Client 07 54482
  4525 35108 fgcp0qn1bqzx9 XLTDB10 xltwrk10 JDBC Thin Client 2381 192853
  4428 38484 fgcp0qn1bqzx9 XLTDB1 xltwrk1 JDBC Thin Client 8682 634540
  
  
  For this sql id: fgcp0qn1bqzx9 there are more than 14 executions k / hour.
  
  This is the query for this sql id:
  / * TJAPI_SubTrxTransient_deleteTrb1SubTrxTransient_0 * / REMOVE FROM TRB1_SUB_TRX_TRANSIENT
  
  Some other details
  ++++++++++++
  Oravle version: 11.1.0.7
  OS: SunOS
  ++++++++++++

  Details of the message from the database pl and OS versions. From 10 g 2, cancellation will still appear to be 'full' - which is normal.

  Doc 413732.1 - Full UNDO Tablespace in 10gr 2 MOS

  HTH
  Srini

• Undo tablespace full

  Hi all
  
  OS: Solaris
  DB: 10 G
  
  My undotablespace had a lot, I should directly resize it or is there something else I should do first?
  One last thing, if I take the bounce of the database, this will affect cancel it?
  
  Kind regards
  Sphinx

  If you have room for an other undo tablespace, why not make one you have more? Don't forget, one will not be removed until all transactions using this are made.

  There are a few reasons you may need more to cancel the space: you have people leaving the open sessions, you have poor code that uses too or shot himself in the foot, stand too close, autoextend to cancel gourmand or you really need the space.

  Tom Kyte has recommended to keep enough space around it for annual transactions of large batch if you have those. Unfortunately, this means that you do not have the other stuff stupid user. I take an intermediate point of view, keeping a great cancel (it is about half of my db), even though it is barely used most of the time and kill sessions where I can determine that they should not be left open (in other words, people who rarely run stuff from one day to the next day to ask, since most people don't).

  What are the exact errors are you seeing? If this is the code that self-destructs in the foot, no matter how cancel it y a. search for ora-1555 on asktom if that's what you see. What's your retention, what is your guarantee?

• Some confusion on undo tablespace

  I have discussed this table to undo in my previous thread space.
  
  and always had some doubts.
  

  SELECT segment_name, tablespace_name, status, SUM(bytes)
  FROM dba_undo_extents
  GROUP BY segment_name, tablespace_name, status;
  
  SEGMENT_NAME     TABLESPACE_NAME     STATUS     SUM(BYTES)
  _SYSSMU8$     UNDO                     EXPIRED     1179648
  _SYSSMU18$     UNDO_02                     UNEXPIRED     2228224
  _SYSSMU17$     UNDO_02                     EXPIRED     196608
  _SYSSMU13$     UNDO_02                     UNEXPIRED     131072
  _SYSSMU5$     UNDO                     EXPIRED     1179648
  _SYSSMU4$     UNDO                     EXPIRED     2228224
  _SYSSMU3$     UNDO                     EXPIRED     2228224
  _SYSSMU2$     UNDO                     EXPIRED     2228224
  _SYSSMU1$     UNDO                     EXPIRED     1179648
  _SYSSMU20$     UNDO_02                     EXPIRED     1179648
  _SYSSMU19$     UNDO_02                     UNEXPIRED     196608
  _SYSSMU14$     UNDO_02                     EXPIRED     1179648
  _SYSSMU11$     UNDO_02                     UNEXPIRED     131072
  _SYSSMU10$     UNDO                     EXPIRED     1179648
  _SYSSMU9$     UNDO                     EXPIRED     1179648
  _SYSSMU16$     UNDO_02                     EXPIRED     262144
  _SYSSMU15$     UNDO_02                     EXPIRED     2228224
  _SYSSMU7$     UNDO                     EXPIRED     2228224
  _SYSSMU12$     UNDO_02                     UNEXPIRED     65536
  _SYSSMU21$     UNDO_02                     EXPIRED     131072
  _SYSSMU12$     UNDO_02                      EXPIRED     65536
  _SYSSMU6$     UNDO                     EXPIRED     2228224

  and UNDO_02 is currently offline.
  
  Any advice?
  
  Thanks in advance.
  
  Nith

  user645399 wrote:
  How can I check that undo tablespace XXSMALLTABS tablespace does use?

  Please guide me.

  Thank you!

  Nith

  There is no such thing/mandate/matter. Undo tablespace (in automatic mode) in relation to the proceeding but no single tablespace.
  There are relationship instance<=> Cancel tablespace(its own) , and it is determined by UNDO_TABLESPACE.

• UNDO Tablespace backup-RMAN

  Hi/team champions,
  I'm confused in full DB Backup RMAN why CANCEL tablespce is included even we include also archive logs.
  in a Word?
  Why UNDO tablespace backup is necessary while taking backup RMAN?
  
  Kind regards
  Shitesh Shukla

  If I do not want to include the UNDO tablespce in my backup

  What happens if I took only backup files except CANCELLATION n TEMP

  NOT an option. You must include UNDO. 11g has optimization in order to safeguard an Undo tablespace.
  10 gr 2 what you pourriez do is

  1. create a new Undo Tablespace
  2. position yourself in the new Undo Tablespace
  3. check that the old Tablespace Undo is no longer in service - confirm that there is no transaction active in the inside undo segments
  4. remove the old Undo tablespace
  5. start your RMAN backup

  You run the risk of
  a. wait long to step 3
  b. ORA - 1555 s for users once you drop the Undo tablespace to step 4.

  Hemant K Collette
  http://hemantoracledba.blogspot.com

• It will frequently commit resolve ora-30036 (cannot extend the undo tablespace)

  I use 11.2.0.3 database. I confused on the use of validation to resolve ora-30036.

  I have the script in migration once that has many updates and I'm getting ORA-30036 (unable to extend segment by 4 in the "UNDOTBS" undo tablespace) .

  Our undo tablespace in NO mode autoextend and like this is just a one time event, we will not increase it.   He is currently 6 GB.

  We would commit determination ORA-30036 in my case? If not why? Is there a better solution to solve it.

  
  

  When I say commit frequent, I won't commit after each line, I just want to commit after may be million lines, so that my active cancellation extend turn into cancellation remaining will extend and Oracle will be able to use it in case of pressure of space.

  
  

  Note:

  UNDO_MANAGEMENT: AUTO

  UNDO_RETENTION: 2700

  Undo tablespace retention is NOGAURANTEE.

  I have the script in migration once that has many updates and I'm getting ORA-30036 (unable to extend segment by 4 in the "UNDOTBS" undo tablespace).

  Our undo tablespace in NO mode autoextend and like this is just a one time event, we will not increase it.   He is currently 6 GB.

  Why don't you increase it?

  You must use the correct size of UNDO necessary for the work that will be done.

  A lot of shops to create a for big lots new UNDO tablespace and then switch to it for batch processing. Once the task is completed, they switch back to the normal UNDO. That prevents the normal RETURN of autoextending far where it is normally necessary:

  ALTER SYSTEM SET UNDO_TABLESPACE

• Undo tablespace in oracle 10g

  Hi all;

  Hello!

  I'm confused about undo tablespace size.

  Under query showing my undo tablespace size is 120Mo.

  but DBA_TABLESPACE_USAGE_METRICS view showing the undo tablespace size is 4194302

  > > Check free space

  SQ > select t.tablespace, t.totalspace as ' TOTAL_SPACE (MB).

  round ((t.totalspace-fs.freespace), 2) as "USED_SPACE (MB)",
  FS. FreeSpace as "FREE_SPACE (MB).
  round (((t.totalspace-fs.freespace) /t.totalspace) * 100, 2) like "% used (s),"
  round ((fs.freespace/t.totalspace) * 100, 2) as "% free" of
  (select round (sum (d.bytes) /(1024 * 1024)) as totalspace,)
  tablespace dba_data_files d.tablespace_name d
  Group d.tablespace_name) t,.
  (select round (sum (f.bytes) /(1024 * 1024)) as freespace,)
  tablespace dba_free_space f.tablespace_name f
  Group of f.tablespace_name)
  FS where t.tablespace = fs.tablespace order of t.tablespace.

  
  

  TABLESPACE TOTAL_SPACE (MB) USED_SPACE (MB) FREE_SPACE (MB) % used free %

  ------------------------------ --------------- -------------- -------------- ---------- ----------

  EXAMPLE                                    100             68             32         68         32

  240 230 10 SYSAUX 95,83 4.17

  480 475 5 98.96 SYSTEM 1.04

  UNDOTBS1                                   120            120              0        100          0

  1005 75 930 USERS 7.46 92.54

  SQL > select * from dba_tablespace_usage_metrics, where nom_tablespace like '% UNDO;

  NOM_TABLESPACE USED_SPACE TABLESPACE_SIZE USED_PERCENT

  ----------------------------    ----------  ---------------  ------------

  UNDOTBS1                              440        4194302 .010490422

  This is because:

  Tablespace_size in DBA_TABLESPACE_USAGE_METRICS takes the maximum file size for CanGrow tablespace that matches maxblocks in dba_data_files.

  This is not the same value you can get from dba_data_files.

  DBA_TABLESPACE_USAGE_METRICS shows essentially the maximum size to which a data file can grow. And DBA_DATA_FILES (+ DBA_FREE_SPACE) the current size of the tablespace.

  Watch more document MOS (My Oracle Support):

  Difference in size of dba_data_files Tablespace and dba_tablespace_usage_metrics/V values $ Filespace_usage (Doc ID 455715.1)

• Undo tablespace filled with 95%

  Hi all
  
  We have R12.1 Instance with RDBMS 11.1.0.7.0.
  Undo table space here is got filled up to 95%, all the data files are not in AUTOEXTEND.
  
  In this case, I need to add a data file?
  If I add a file of data, is the performance database will be mediocre?
  
  Please suggest...
  
  
  Thank you
  Shaik

  Undo tablespace full when data files are not in mode autoextend is normal. PL see this Doc MOS

  UNDO tablespace full gr 10 2 [ID 413732.1]

  If you stop seeing any error ORA-01555, you don't have to do anything.

  HTH
  Srini

• Undo tablespace continues to grow

  Hello
  My undotbs grows to 14g (even if I have my undotbs actul size 9g) I try to resize the data files, but
  This may not work.
  
  So, I guess for this task
  
  >
  -Create a new as undo tablespace:
  SQL > create undo tablespace UNDOTBS2 datafile "< full file path >" size < small >;
  
  -Change the parameter UNDO_TABLESPACE
  SQL > alter system set UNDO_TABLESPACE = UNDOTBS2;
  
  -Remove UNDOTBS1
  SQL > drop tablespace UNDOTBS1 including content and data files; >
  
  but my question is, is he worthy of delete the undotbs1 whose having a lot of data and if I deleted
  These data (undotablespace), I won't be able to completely recover?
  
  db_version:10.2.0 (Linux)

  There is procedure to drop undo tablespace. If you already increase first then I suggest you to study why his is growing? Check with developers, to monitor the database

• Free tablespace on undo tablespace

  I have a 8Gig tablespace on database 94Gig which is used for the statement (this is DSS database). Retention of cancellation is set too high (it is 1080 about 3 h). I don't know what is the reason, but it space table undo is full all the time, because of this it is ETL jobs that suppose to run each night fail.
  
  I think bounce (restart database) to free up to undo tablespace.
  
  Do you propose to increase the undo tablespace tablespace or database rebound must release undo tablespace? Please suggest.

  In an SSD long requests are expected. You need your UNDO retention to be longer than your long query, so the 'too long' claim is rather subjective.

  Unless you have the cancellation retention set, Oracle will reuse space annulment, even crush UNDO for younger than retention committed transactions to meet the current requirements of the query.

  Even if you restart the database (which is a horrible idea, from the pit of Redmond) conditions that are initially complete you the UNDO and get errors are likely to come immediately.

  Refresh jobs fail with ORA-01555 or ORA-30036? For these solutions are very different.

  I agree with the first line... allocate more space to CANCEL is probably the solution here, but we cannot say that for sure without knowing the error (and Oracle version would be helpful, too).

  Relevant thread here...
  http://asktom.Oracle.com/pls/asktom/f?p=100:11:0:P11_QUESTION_ID:6894817116500

• UNDO Tablespace use

  Hi all
  My undo tablespace is full of 97%.
  Is it possible to check which process is using more undo tablespace.
  
  Thanks in advance for your answer.
  
  Kind regards
  Ashwani N.

  # UNDO tablespace usage
  
  select a.process, a.program, a.module, a.machine, b.USED_UREC, c.sql_text
  from v$sql c, v$session a, v$transaction b
  where b.addr = a.taddr
  and a.sql_address = c.address
  and a.sql_hash_value = c.hash_value
  order by b.USED_UREC;
  
  SELECT s.sid , s.username , t.used_ublk
  FROM v$transaction t
  , v$session s
  WHERE 1 = 1
  AND t.ses_addr = s.saddr
  
  column username format a15;
  column segment_name format a15;
  SELECT s.sid , s.username , t.used_ublk, round((t.used_ublk*8)/1024) size_in_MB_8kb_Block_size, round((t.used_ublk*16)/1024
  ) size_in_MB_16kb_Block_size
  FROM v$transaction t
  , v$session s
  WHERE 1 = 1
  AND t.ses_addr = s.saddr;
  
  SELECT distinct rpad(s.sid,3) "SID",S.USERNAME,
  E.SEGMENT_NAME,
  T.START_TIME "Start",
  rpad(T.STATUS,9) "Status",
  round((t.used_ublk*8)/1024) "Size(MB)"
  --T.USED_UBLK||' Blocks and '||T.USED_UREC||' Records' "Rollback Usage"
  FROM DBA_DATA_FILES DF,
  DBA_EXTENTS E,
  V$SESSION S,
  V$TRANSACTION T
  WHERE DF.TABLESPACE_NAME = E.TABLESPACE_NAME AND
  DF.FILE_ID = UBAFIL AND
  S.SADDR = T.SES_ADDR AND
  T.UBABLK BETWEEN E.BLOCK_ID AND E.BLOCK_ID+E.BLOCKS AND
  E.SEGMENT_TYPE in( 'ROLLBACK','TYPE2 UNDO'
  

  Source: -.
  http://blog.contractoracle.com/2008/08/undo-tablespace-usage.html

• Undo Tablespace queries

  Hi all
  
  I am little confused with reading on the undo tablespace. So I need some clarification
  
  1. There are 2 undo tablespace in our application. Could someone explain to me how the 2 undo tablespace? I've not found details about it.
  2. both the undo tablespace is used at 100%. Where the the new transaction will go? New operation will force the blocks used to be exceeded if necessary?
  3. what should be the ideal size of the tablespace undo compared to the total storage size?
  4. is the log archive associated with space undotable? If Yes, then when archiving logs getting generated?
  
  Thank you

  1. in a database of CARS, each Instance must have it's own Undo Tablespace.
  In a database not RAC (single instance), only one Undo Tablespace can be active at any time. The Undo Tablespace would be idle but can be switched by an ALTER SYSTEM SET UNDO_TABLESPACE command.

  2. even if an Undo Tablespace is 'used 100% ' Oracle can expire (and even drop) on old extents and segments that are no longer needed by the value of Undo_Retention. Thus, data undo for older transactions that are committed (more than Undo_Retention period has elapsed since the validation) will be overwritten.

  3. There is no "ideal size. Undo sizing is based on transaction volumes, fluctuations in the volume of transactions, query patterns etc.

  4. No, there is no direct relationship between the two. However, any cancellation that is generated is also written again - that is to say redo Undo catches as it captures changes made to Tables, indexes etc..

  I suggest you read the Oracle documentation concepts to
  http://download.Oracle.com/docs/CD/E11882_01/server.112/e16508/TOC.htm

  Hemant K Collette
  http://hemantoracledba.blogspot.com

• Problems with UNDO tablespace

  Hello
  
  DB_VERSION: 10.2.0.4
  OS_VERSION: Windows 2003 server
  
  SQL > show Cancel parameter
  
  VALUE OF TYPE NAME
  ------------------------------------ ----------- ----------------
  UNDO_MANAGEMENT string AUTO
  UNDO_RETENTION integer 900
  undo_tablespace string UNDOTBS1
  
  I know that UNDO tablespace stores the old image of o / old value when the cancellation of the user, the old value is returned to the user throgh UNDO.
  
  
  My UNDO tablespace grows up to 24GO as a developer frequently updates the database in the morning and in the evening.
  
  Basically, it runs a script to offset that includes the INSERT and UPDATE and it is important to extermely.
  
  Whenever the UNDO SCT is full, I create a new one with autoextend on, what happens if I do not autoextend?
  
  1. what would be the impact on queries, if I do like above I always created UNDO tablespace with autoextend 2Go on.
  
  2. What is the best time to drop the old UNDO tablespace?
  
  Thanks in advance.

  Dear user12000301,

  Firstly the undo tablespace is not just there to roll back the transaction. You can use the for recovery undo tablespace (roll back during the recovery of the instance), coherent reading and also for operations of blowback.

  If you have defined a tablespace undo with the goal of conservation of 15 minutes, but have fixed size then;

  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14231/undo.htm

  +"+
  + The following points explain the exact impact of the undo retention UNDO_RETENTION parameter: +.

  + The UNDO_RETENTION parameter is ignored for a fixed size undo tablespace. The database can overwrite the information to cancel remaining when the tablespace space becomes low. +

  + For a tablespace undo with the option enabled AUTOEXTEND, the database tries to honor the minimum retention specified by UNDO_RETENTION period. When space is low, instead of crushing the cancellation information remaining, the self-aggrandizing tablespace' extends. If the MAXSIZE clause is specified for an auto-croissant undo tablespace when the maximum size is reached, the database can begin to replace the cancellation information remaining. +
  +"+

  Be careful with the settings to cancel it. The size, before you add the new data files in the tablespace, undo or autoextending for your pain, you must consider the DML that caused the growing undo tablespace. Necessaryly should generate redo or cancel? If so, know the total amount of undo blocks through the relevant DML.

  If you have created a with 2 GB undo tablespace and mark as CanGrow that the data file can be up to 32 GB. The DBCA you will create a petit_fichier undo tablespace but you can create another like bigfile and pretend the tablespace default undo for the operation.

  The best time to drop an undo tablespace is to wait at least undo_retention period of time has elapsed to make sure you don't need to have the copy of the coherent image transactions are committed. I think that the solution could be achieved as underlined Chinar but be careful on the active rollback segments in your database. You can also dynamically change the default undo tablespace anytime if the database uses the spfile.

  Hope that helps.

  Ogan

• Unable to shrink/resize undo tablespace

  Hi Experts,
  
  I have the database Oracle 10.2.0.4 running on RHEL 4.7 in a production environment, my undo tablespace has grown to 32 GB, database is restarted, the tablespace is always full.
  
  I would like to shrink, resize the undo tablespace, please help me
  
  Little detail is as below
  
  display the parameter undo_retention
  VALUE OF TYPE NAME
  ------------------- ----------------- ----------------------
  UNDO_RETENTION integer 10
  
  Help, please
  
  Thank you
  
  Published by: user1687821 on July 9, 2010 09:27

  did you check the link I provided in my previous post? He answers most of your questions.