Execution of transactions without active Undo Tablespace

Similar Questions

• Block in the Undo tablespace corruption

  Dear all,
  
  
  I'm using oracle 10.1.0.2.0. Today because of the abnormal termination block corrouption in undo tablespace found and database will not open.
  In the alert log file
  
  Errors in the e:\oracle\product\10.1.0\admin\orc1\udump\orc1_ora_3188.trc file:
  ORA-01578: block ORACLE (corrupted file # 37, block # 25) data
  ORA-01110: data file 37: ' E:\ORACLE\PRODUCT\10.1.0\ORADATA\ORC1\UNDOTBS0. DBF'
  
  Sea Jul 07 10:18:42 2010
  1578 error happened during db open, close the database
  USER: termination litigation because of the 1578 error
  Sea Jul 07 10:18:43 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_arc3_3900.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:43 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_arc3_3900.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:43 2010
  Arc0: Assessment of the archive log 2 sequence of thread 1 479
  Sea Jul 07 10:18:43 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_dbw0_3692.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:43 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_ckpt_1552.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:43 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_mman_3912.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:44 2010
  Newspapers archived by another process
  Sea Jul 07 10:18:44 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_pmon_3744.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:44 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_arc1_3668.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:44 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_arc1_3668.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:45 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_reco_1076.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:45 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_smon_2660.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:45 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_lgwr_1796.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Instance of stopped by USER, pid = 3188
  ORA-1092 marked during: ALTER DATABASE OPEN...
  
  Concerning

  Errors in the e:\oracle\product\10.1.0\admin\orc1\udump\orc1_ora_3188.trc file:
  ORA-01578: block ORACLE (corrupted file # 37, block # 25) data
  ORA-01110: data file 37: ' E:\ORACLE\PRODUCT\10.1.0\ORADATA\ORC1\UNDOTBS0. DBF'

  You have rman or backup to hot/cold? If so try like:
  * 1.*

  sqlplus "/as sysdba"
  shutdown immediate;
  startup mount;
  /*restore undo datafile then*/
  recover datafile 37;
  alter database open;
  

  * 2 If you have backup rman, then try

  rman terget /
  blockrecover datafile 37 block 25;
  

  * 3.* If you don't have a backup, you can start your database without this undo tablespace.

  1. backup current database;

  2. change pfile (parameter file) change undo_tablespace and undo_management as:

  undo_management=manual
  undo_tablespace=UNDOTBS2
  

  If you do not use pfile create pfile from spfile as:

  sqlplus "/as sysdba"
  create pfile='pfilelocation' from spfile='spfilelocation';
  

  3. then start database as:

  Connected to:
  Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
  With the Partitioning, OLAP and Data Mining options
  
  SQL> shutdown immediate;
  Database closed.
  Database dismounted.
  ORACLE instance shut down.
  SQL> startup mount pfile D:\oracle\product\10.2.0\admin\TEST\pfile\init.ora.5162
  010113556
  SP2-0714: invalid combination of STARTUP options
  SQL> startup mount pfile= D:\oracle\product\10.2.0\admin\TEST\pfile\init.ora.516
  2010113556
  ORACLE instance started.
  
  Total System Global Area  138412032 bytes
  Fixed Size                  1288172 bytes
  Variable Size              62916628 bytes
  Database Buffers           67108864 bytes
  Redo Buffers                7098368 bytes
  Database mounted.
  SQL> alter database open;
  alter database open
  *
  ERROR at line 1:
  ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
  ORA-01110: data file 2: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\UNDOTBS01.DBF'
  
  SQL> select name from v$datafile;
  
  NAME
  --------------------------------------------------------------------------------
  
  D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\SYSTEM01.DBF
  D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\UNDOTBS01.DBF
  D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\SYSAUX01.DBF
  D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\USERS01.DBF
  
  SQL> alter database datafile
  'D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\UNDOTBS01.DBF' offline drop;
  
  Database altered.
  
  SQL> alter database open;
  
  Database altered.
  
  SQL> create undo tablespace UNDOTBS2
  datafile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\UNDOTBS2' size 200M;
  
  Tablespace created.
  
  SQL> create spfile from pfile;
  
  File created.
  
  SQL>
  

• Transaction is written to the log file and it is not written to undo tablespace. During a failure of the system how oracle rolls back the transaction.

  Hi all

  My question is:

  Transaction is written to the log file and it is not written to undo tablespace.

  During a failure of the system how oracle rolls back the transaction.

  I have already provided the answer, you ignored if well (you seem to only read the responses by people of your country).

  Redo log is always written * first * before * writing to the data block (redo log writing is much more aggressive). So it DOESN 'T MATTER if you lose these scriptures of rollback segment.

  Valuation: rear roller followed by roll forward, using redo log files and/or archive redo log files.

  Sybrand Bakker

  Senior Oracle DBA

• Undo tablespace to recover without backup

  Hello
  
  I put one of my data file that contains in the undo tablespace. Now, my database is in the editing stage, when I tried to open the database, it gives me the following error:
  
  
  SQL > alter database open;
  change the database open
  *
  ERROR on line 1:
  ORA-00376: 17 file cannot be read right now
  ORA-01110: data file 17: ' / misc/live_tbs/undotbstest.dbf'
  
  
  My database is in noarchive mode more I do not have a backup.
  
  
  Thank you for your cooperation.
  
  Kind regards
  
  Adnan Hamdus Salam.

  Adnan says:
  Hello

  I put one of my data file that contains in the undo tablespace. Now, my database is in the editing stage, when I tried to open the database, it gives me the following error:

  SQL > alter database open;
  change the database open
  *
  ERROR on line 1:
  ORA-00376: 17 file cannot be read right now
  ORA-01110: data file 17: ' / misc/live_tbs/undotbstest.dbf'

  My database is in noarchive mode more I do not have a backup.

  NOarachivelog mode and having no backup are, in fact, a perfect recipe for disaster. What happens when you transfer the file online in the editing phase?

  Aman...

• undo_segments in the undo tablespace

  (1) at least how undo_segments in undo tablespace?

  Is optimal?
  If I increase the size of the undo tablespace, undo_segments counts also have increased!

  Version of DB is 10g

  Hello

   

  The two time oracle maintains exactly 10 segments. (you can see nom_segment begins by _SYSSMU11)

  I'm not clear on what exactly 10 segments. I have undo tablespace of ~ 250 GB with 6676 stored in dba_rollback_segs.

  3) why undo tablespace with the only spaceMo 46,8125 '?

  
  

  (4) I mean why he is stiil 450Mo undo_retention even through time or same validation has occurred?

  Just Oracle - Doc

  Once a transaction is committed, the undo data are more necessary for purposes of recovery rollback or transaction. However, for consistent read purposes, long-running queries may require old undo information to produce older images of data blocks. In addition, the success of several Oracle Flashback features can also depend on the availability of the old cancellation information. For these reasons, it is desirable to keep the old information of cancellation for as long as possible.

  Introduction to the management of the automatic cancellation

  With undo tablespace, you would see extended with the status ACTIVE, EXPIRED, extents still to RUN.

  Active cancellation extended are used by transactions and will be always active, because they are needed for the restoration.

  Extensions has expired are not used by transactions, the data contained in these extended is committed and the time UNDO_RETENTION is passed, so it is not necessary for the coherence of reading and can be reused.

  Not expired extensions are extended no assets but honor UNDO_RETENTION. Transactions belonging to these bodies of cancellation are determined, but the retention time has failed, and it may be necessary for the coherence of reading!

  Paste the query result - below

  ! undo_extent_stat.SQL more

  status of collar for a30

  Select the State,

  round (sum_bytes / (1024 * 1024), 0) like MB,.

  Tour ((sum_bytes / undo_size) * 100, 0) as PERC

  Of

  (

  Select the State, sum (bytes) sum_bytes

  of dba_undo_extents

  Status group

  ),

  (

  Select sum (a.bytes) undo_size

  from dba_tablespaces c

  Join v$ tablespace b on b.name = c.tablespace_name

  Join v$ datafile on a.ts # b.ts = #.

  where c.contents = 'UNDO '.

  and c.status = 'ONLINE '.

  );

  Anand

• Undo tablespace recreation

  Hi all
  
  I use oracle 9i running in solaris 9.I having a called undotbs1 undo tablespace that is size approximately 8.5 GB and
  
  the UNDO_RETENTION setting * 10800 * I want to reduce to 2000 and I want to create a tablespace, undo size about 3 GB and the value in the default undo for the database tablespace.
  
  change the system undo_retention = 2000 scope = both set
  create the undo tablespace undotbs2 datafile 'posted' size 3 G
  ALTER system set undo_tablespace = undotbs2 scope = both
  
  Drop tablespace undotbs1 including content and data files
  
  Is there a problem if I... I ask because my current undo tablespace size is 8.5 GB?
  
  Thanks and greetings
  Yvon Das

  >
  change the system undo_retention = 2000 scope = both set
  create the undo tablespace undotbs2 datafile 'posted' size 3 G
  ALTER system set undo_tablespace = undotbs2 scope = both

  Drop tablespace undotbs1 including content and data files

  Is there a problem if I... I ask because my current undo tablespace size is 8.5 GB?
  >
  It won't be a problem, but you must change a step you gave.
  After the ALTER SYSTEM you will not be able to drop the old table space until it disconnects.

  Display deleted mosaic then you will need to have two tablespaces to cancel online and that means a sufficient for both disk space.
  >
  The database is online, while the switch operation is performed and user transactions can be executed while this command is running. When the switch operation completes successfully, all transactions started after the beginning of the switching operation are assigned to the transaction tables in the tablespace new undo.

  The switch operation does not wait for transactions in the old undo tablespace to commit. If there is any pending transactions in the old undo tablespace, the old undo tablespace concludes an offline pending (status). In this mode, existing transactions can continue to run, but undo records for new user transactions cannot be stored in this undo tablespace.

  An undo tablespace can exist in this pending offline mode, even after the switch operation. A cancellation pending offline tablespace cannot used by another instance, nor can it be moved. Finally, after all the active transactions have committed, the undo tablespace automatically goes to offline mode offline pending
  >

  See switching Undo tablespace in the Guide DBA 9i
  http://docs.Oracle.com/CD/B10501_01/server.920/a96521/undo.htm#9117

• 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 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

• 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 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

• Concept on Undo tablespace in RAC environment

  Why we need two different Undo tablespace for two different instances in RAC environment. What are the internal mechanisms behind it? No explanation of the concept will be great for me. What will be the scenario if we have same tablespace undo for two instances?

  Thanks in advance.

  Hello

  To reduce CONTENTION and the complexity of the software.aslo oracle instances share not undo tablespace using cancel separate increase the availability of data undo files.

  Note: all instances can still read that cancel all blocks for coherent reading purposes. In addition, any instance can update the any tablespace undo during the restoration of the transaction,

  as long as undo tablespace is not currently used by another instance to cancel generation or a recovery operation.

  HTH

  Tobi

• Need information on objects not expired undo tablespace

  We are facing a problem in our database for 3-4 days.

  The objects remaining in the database increases day after day. As our ts cancel autoextend enabled, it increases the storage space.

  Currently the following is the scenario.

  SQL > SELECT DISTINCT STATUS, SUM (BYTES) / 1024/1024/1024 GB, COUNT (*)

  2 GROUP OF DBA_UNDO_EXTENTS BY THE STATE;

  STATUS GO COUNT (*)

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

  61.5925903 10995 REST TO RUN

  3.33197021 356 EXPIRED

  ACTIVE 18.478515625

  Thus, the remaining data 61GB while active is only 478 MB and expired is 3.3 GB.

  My questions are

  1. How can I check the object or sql query or a program that contains the data to cancel "RUN" so. How can I find the names of these objects?

  2. If I turned off autoextend undo ts if this solves the problem and take the new space to cancel from space to cancel remaining?

  Help, please.

  1. the UNEXPIRED is not bound to a query, but the UNDO for UNDO Tablespace retention period. And the Undo retention is a value set automatically when the parameter UNDO_RETENTION is minium.

  The Oracle Documentation says:

  For an undo tablespace with the AUTOEXTEND option is enabled, the database tries to honor the specified minimum retention period by UNDO_RETENTION . 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.

  2. Yes this will fix the issue that now the calcution for UNDO retention is different.

• Question about Undo Tablespace?

  Hello;
  
  The necessary size of the undo tablespace is the number and size of the transactions that occur on the database. But I do not need to interview one of these transactions for a schema or table using flashback it is a way to disable transactions writing on a table or schema of undo tablespace?
  
  Published by: Ecimen on 04.Mar.2013 03:50
  
  Published by: Ecimen on 03:51 04.Mar.2013

  Ecimen wrote:

  Rob_J wrote:
  OK, it's fine, so what makes you say you build too UNDO? What is the problem you're trying to solve? Or you want to know if you could get back to CANCEL in writing?

  Our log tables generate too much to cancel because we need you connecting all these data (insert and update for the most part)... but we don't care about these log tables, we want to reduce the cancellation written for these tables logs so that we could use more flashback query timestamp older due to more space in the undo tablespace...

  I think I mentioned in my other two answers above that it is not possible to disable the generation of the cancellation, or at least I don't know that there is no way to do it! What you can do, if you are worried about the Undo tablespace grows, it is that make you a tablespace size Undo fixed by controlling the Undo data that are generated. You can use Cancel Advisor of the to do. With the Undo retention period of your proposed, she would like the size of the Undo tablespace tips and you can add about 20-30% extra size and you should be fine. But as I've already said too much, he has No way to stop generating cancellation.

  Aman...