ORA-01555 - Tuning for the UNDO tablespace.

Similar Questions

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

• Changing data in the undo tablespace or db Oracle buffer cache

  Hello
  
  I have serious doubt in the feature of oracle architecture, when a user issues an update statement, the data blocks are transported to the db buffer cache and where the data changes are made? Made a copy data block is stored in the cache db pads and the changes are made to the block in the buffer cache? or the copy of the data block is stored in the undo tablespace and changes are made to the blocks in the undo tablespace?
  
  In singles, the changes to the data blocks are make to the db or undo tablespace buffer cache?
  
  
  Thanks in advance
  
  Kind regards
  007

  Did you have a look to the Internet for the answer?

  In short, if a trial Oracle wants to update a record in the table, it does:

  -Read the record to be changed in the buffercache
  -Audits (the record already locked, is the update allowed)
  -Put the folder (called image before) in a rollback in the UNDO tablespace segment
  -Writing redo information about this change in the UNDO tablespace
  -Lock the record
  -Write the change in registration in the buffer cache
  -Put the change also in the redo buffer
  S ' sit and wait... (for a commit or a rollback)

  When are committed:
  -Release the lock
  -Empty folder of restoration since the UNDO tablespace
  -Write a record of this change forward in the UNDO tablespace

  When rollback:
  -Release the lock
  -Rinse the record changed the buffercache
  -Read the original value
  -Empty folder of restoration since the UNDO tablespace
  -Write a record of this change forward in the UNDO tablespace

  It of here, some more specific complexity when a checkpoint occurs between the change and the commit / rollback or redo buffer has been emptied for redo files

  Please any other s/n, correct me if I'm wrong...

  See you soon
  FJFranken

• The UNDO tablespace and its data file cannot be removed

  I would like to delete an UNDO tablespace after you have created a new, but can't. I could follow a large number of instructions TOM and others, but tablepspace is still listed in the State to RECOVER. Please see what I've done below. Your help will be appreciated.
  

  SQL > drop tablespace UNDOTBS2;
  Drop tablespace UNDOTBS2
  *
  ERROR on line 1:
  ORA-01548: active rollback segment "_SYSSMU29_1272378969$" found, terminate
  drop the tablespace

  SQL > drop rollback segment "_SYSSMU29_1272378969$";
  Drop rollback segment "_SYSSMU29_1272378969$".
  *
  ERROR on line 1:
  ORA-30025: DROP segment ' _SYSSMU29_1272378969$ ' (in the undo tablespace) not
  permit

  Have you tried that
  http://arjudba.blogspot.com/2008/08/ora-01548-active-rollback-segment.html

• Impossible to drop the undo tablespace

  Hello
  
  ORACLE VERSION: 11.1.0
  OPERATING SYSTEM: WINDOWS XP
  
  I have been uable to drop the undo tablespace. Here I create a new undo tablespace and trying to drop the old undo tablespace.
  
  I had given alter system set UNDO_TABLESPACE = newundo tablespace.
  
  And try to drop the old one and get the error like this
  

  SQL> create undo tablespace undotbs02 datafile 'F:\APP\POORNAPRASADS\ORADATA\ORCL\UNDOTBS02.dbf' size 200m;
  
  Tablespace created.
  
  SQL> sho parameter undo
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  undo_management                      string      AUTO
  undo_retention                       integer     900
  undo_tablespace                      string      UNDOTBS1
  SQL> alter system set undo_tablespace=undotbs02;
  
  System altered.
  
  SQL> sho parameter undo
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  undo_management                      string      AUTO
  undo_retention                       integer     900
  undo_tablespace                      string      UNDOTBS02
  SQL> drop tablespace undotbs1 including contents and datafiles;
  drop tablespace undotbs1 including contents and datafiles
  *
  ERROR at line 1:
  ORA-30013: undo tablespace 'UNDOTBS1' is currently in use
  
  
  SQL> drop tablespace undotbs1 including contents and datafiles;
  drop tablespace undotbs1 including contents and datafiles
  *
  ERROR at line 1:
  ORA-30013: undo tablespace 'UNDOTBS1' is currently in use

  There are active sessions that use of old undo segments. I think you should kill these sessions in order to relase these segments

  - - - - - - - - - - - - - - - - - - - - -
  Kamran Agayev a. (10g OCP)
  http://kamranagayev.WordPress.com
  [Step by step installation Oracle Linux and automate the installation by using Shell Script | http://kamranagayev.wordpress.com/2009/05/01/step-by-step-installing-oracle-database-10g-release-2-on-linux-centos-and-automate-the-installation-using-linux-shell-script/]

• Bigfile tablespace for the system tablespace.

  I am trying to create a database with bigfile tablespace for the SYSTEM tablespace as well. Can I use dbca to create and define bigfile tablespace for the SYSTEM tablespace.

  How can I create system with the CREATE DATABASE statement bigfile tablespace?  Can be a help for syntax?

  Even if the normal tablespace is sufficient for the system, I just wanted to check if there is a syntax to create.

  Thank you

  Bigot

  The use of the clause 'SET DEFAULT BIGFILE TABLESPACE' in the CREATE DATABASE command - see creating and configuring an Oracle database

• How to reduce the UNDO Tablespace

  Hello
  We had an UNDO Tablespace to 22 GB but it's using just 2GB. How to shrink the undo tablespace. We use the database in production cluster 3 node 10.2.0.4
  Is there is way we can worry about UNDO Tablespace or should I create an UNDO tablespace and assign the undo tablespace to DB and let fall the old CANCEL?
  How to ensure that the transactions are done and free to abandon the old CANCEL?
  That's what we must restart all three nodes each node has its own UNDO Tablespace.
  
  Need help on this issue.
  
  would appreciate your quick response.
  
  
  Thank you

  No you have not.

  concerning
  Mohamed

• ORA-01111 name for the 10 data file is unknown

  Hello
  I created two new areas of storage (11 and 12) with 1 data file in each of them in my primary database,
  I forgot to set the parameter in the server backup standby_file_management = AUTO,
  auto standby server to create tablespace data file in D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\UNNAMED00010 11,
  Although there is no "UNNAMED00010" in D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\ file.
  in the tablespace $ v and v$ datafile, I can see that the entry was created in the control to the standby server file.
  Here is the list of the data file in my backup server
  
  TS # name
  ----- --------------------------------------------------------
  G:\OFSDB\OFS4\ORADATA\OFS4\SYSTEM01 0. DBF
  1 G:\OFSDB\OFS4\ORADATA\OFS4\UNDOTBS01. DBF
  G:\OFSDB\OFS4\ORADATA\OFS4\SYSAUX01 2. DBF
  G:\OFSDB\OFS4\ORADATA\OFS4\USERS01 4. DBF
  6 G:\OFSDB\OFS4\ORADATA\OFS4\DATA_SE. ORA
  7 G:\OFSDB\OFS4\ORADATA\OFS4\INDEX_SE
  8 G:\OFSDB\OFS4\ORADATA\OFS4\FLOW_1.DBF
  G:\OFSDB\OFS4\ORADATA\OFS4\CJHIT01 9. DBF
  G:\OFSDB\OFS4\ORADATA\OFS4\DBMON_TS 10. DBF
  11 D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\UNNAMED00010
  
  Someone knows how to fix this problem?
  
  Thank you

  Another way try this,

  1 put the tablespace that holds the database without name begin backup mode.

  SQL > alter tablespace mytbs begin backup;

  2 copy the missing data (copy of the OS) file to the location of the files of pending data.

  3. run the end backup command.

  SQL > alter tablespace mytbs end backup;

  4. create a controlfile for the use of the database pending,

  SQL > alter database create standby controlfile as ' / D:/oracle/stdcontrol.ctl';

  5. move the alos for standby server.

  In the standby mode,

  1 cancel the recovery mode.
  2 stop and change the controlfile.
  3. start the day before db in the editing phase.
  4 restore database pending.

  Thank you

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

• Issue during the import of metadata for the transportable tablespace

  Hello
  
  We are one of our databases of migration from linux to AIX (test phase). We are using the transportable tablespace for the same thing. All the steps are done and we are stuck during the import of metadata. When importing metadata, we need the full data file name which should be plugged. The number of data files is 309 and the name of all the data files must be in a single line. Now, if we try to write in a single line using the editor vi, the editor gives error ' ex: 0602-140'.
  
  Is there a way by which we can remedy this situation?
  
  Kind regards

  try to make option parfile a file from vi editor that contains the datafile option and 309 lines of datafile.this way you nned do not all put in the same line.

• Reclaim the storage space for the Index tablespace. The fastest approach

  Hello world
  My version of the database is 10.2.0.4
  I have a partitioned table that has divided the indexes that are found on a tablespace called INDEX01.
  the space allocated to the tablespace INDEX01 is about 10 terabytes, however the space used is about 1.5 tera-bytes.
  I need to recover to the level of the storage space. I decided to recreate the tablespace INDEX01.
  I did not create index scripts so I came with two approaches
  1. to move the index partitions in a different tablespace, drop the tablespace INDEX01, recreate the tablespace INDEX01 and then replace the index partitions.
  2. intentionally mark the unusable index partitions, drop the tablespace INDEX01, recreate the tablespace INDEX01 and then rebuild the index partitions.
  
  step 2 seems faster but I need to know if it would work and impact? (the tablespace would pass with the marked index unsable partitions) and I hope that the original table is not affected?
  
  concerning
  Samuel

  Samuel K wrote:
  Hello world
  My version of the database is 10.2.0.4
  I have a partitioned table that has divided the indexes that are found on a tablespace called INDEX01.
  the space allocated to the tablespace INDEX01 is about 10 terabytes, however the space used is about 1.5 tera-bytes.
  I need to recover to the level of the storage space. I decided to recreate the tablespace INDEX01.
  I did not create index scripts so I came with two approaches
  1. to move the index partitions in a different tablespace, drop the tablespace INDEX01, recreate the tablespace INDEX01 and then replace the index partitions.
  2. intentionally mark the unusable index partitions, drop the tablespace INDEX01, recreate the tablespace INDEX01 and then rebuild the index partitions.

  Since you're talking about the abolition of the index, I guess that you have application downtime. Since this is the case, you may want to consider the fact that an index rebuild can analyze the existing index in order to collect relevant data - provides the index is not unusable, and you do not have a reconstruction in line.

  The fastest option - if INDEX01 is a locally managed tablespace - would probably be:
  

  
  Find partitions of index holding at the beginning of the file and rebuild (nologging, parallel, perhaps for speed) in a different tablespace.
  Find the clues that are 'next' in the repository and rebuild in the same tablespace. If the tablespace is locally managed, then the index will fill the empty space at the beginning of the files.
  Work on the files gradually moving toward the front of the space of tables, indexes, and leaving the 'next' bit of the empty file.
  Finish by copying back the small number of partitions of index you rebuilt in the tablespace to spare (and drop this tablespace).
  Shrink the large tablespace.
  

  Concerning
  Jonathan Lewis

  p.s. I wrote a small script some time ago to report the measure ordering in a tablespace - it can help you to choose the order of rebuild.
  http://jonathanlewis.WordPress.com/2010/02/06/shrink-tablespace/

• UNDO Tablespace size

  Hello
  
  We have a production database with size 120 GB (DB Version 11.1.0.6), and our UNDO Tablespace size is 30 GB.
  
  For the last 4 days, the use of UNDO tablespace is more than 85%.
  
  We have disabled the AUTOEXTEND for the UNDO Tablespace.
  
  So that the UNDO RETENTION is calculated dynamically by Oracle itself and the value is now
  
  TUNED_UNDORETENTION
  -------------------------------------
  339183
  
  Please suggest how to solve this problem.
  
  Thank you!

  Salvation;

  Please see:
  New feature in Oracle 10 G - cancel retention Auto Tuning [311615.1 ID]

  Respect of
  HELIOS

• FLASH BACK TO THE WIDE FOR UNDO TABLESPACE?

  Hi all
  As my evryday increasingly, Undo tablespace 2 GB and NOW he reached 19.
  The database size is 6 GB
  
  using the Oracle 10 g Release 2 without patch Set (version 1002000100) on Hp-Unix OS
  
  Can I use the Undo tablespace with FLASHBACK OFF option?
  
  What are the consequences to extinguish the FLAME,
  
  Can we use this type of tablespace Undo with Flashback OFF?
  
  
  CREATE THE UNDO TABLESPACE UNDOTBS03 DATAFILE
  ' / app/oracle/product/oradata/prod/undotbs03.dbf' SIZE 1000 M AUTOEXTEND OFF
  ONLINE
  RETENTION NOGUARANTEE
  8K BLOCKSIZE
  FLASHBACK
  
  
  Thank you very much

  The (increasing) size of the Undo Tablespace has no impact on performance.

  One of the possibilities:
  He'll do backups take longer... so if you perform backups online, then the lengthy backup may be creeping in the moment of the request of the user.

• ORA-01555: snapshot too old: rollback segment number 7 with the name ' _SYSSMU7_1291102260$ ' too small

  
  Hello

  I get ORA-01555 error when performing the following procedure.

  CREATE OR REPLACE PROCEDURE proc1 (text in varchar2, varchar2 data type)
  AS

  L_STMT varchar2 (6000);
  number of l_exists;
  v_code NUMBER;
  v_errm VARCHAR2 (400);
  tabnam VARCHAR2 (100);
  colnam VARCHAR2 (100);
  
  cursor tab_cur is
  Select utc.table_name, utc.column_name, utc.data_type
  from user_tables utb, user_tab_columns utc
  where utc.table_name = utb. Table-name
  and NOT EXISTS (SELECT ' X'
  OF tl table_list
  WHERE the tl.table_name = utc.table_name)
  AND utc.data_type = 'VARCHAR2'
  ORDER OF THE UTC. TABLE_NAME;

  TYPE table_info_tt IS TABLE OF tab_cur % ROWTYPE;
  l_tab table_info_tt;

  BEGIN

  insert into m_log values (SYSTIMESTAMP, 'Start time');
  commit;

  OPEN tab_cur.
  LOOP
  
  Get the tab_cur COLLECT in BULK WITHIN the limits of the 1000 l_tab;
  
  FOR indx in 1.l_tab.count
  LOOP
  
  BEGIN
  
  L_STMT: = ' SELECT COUNT (1)
  OF ' | l_tab (indx). TABLE_NAME | ' WHERE ' | l_tab (indx). Column_name |' =: intext';
  run immediately L_STMT in l_exists using text;
  
  tabnam: = l_tab (indx). TABLE_NAME;
  colnam: = l_tab (indx). COLUMN_NAME;
  
  EXCEPTION
  
  WHILE OTHERS THEN
  
  L_STMT: = ' SELECT COUNT (1)
  OF ' | l_tab (indx). TABLE_NAME | » OÙ ' ||' » ' || l_tab (indx). COLUMN_NAME |' "' |' =: intext';
  run immediately L_STMT in l_exists using intext;
  
  tabnam: = l_tab (indx). TABLE_NAME;
  colnam: = l_tab (indx). COLUMN_NAME;
  END;
  
  IF (l_exists = 0) then
  
  null;
  
  on the other
  
  insert into ADM_TEXT_INFO
  values (l_tab (indx). Table_name, l_tab (indx). Column_name, text, data type);
  
  commit;
  
  END IF;
  
  END LOOP;
  
  EXIT WHEN l_tab.count = 0;
  
  END LOOP;
  
  CLOSE Tab_cur;
  
  insert into m_log values ("SYSTIMESTAMP," over time ");
  commit;
  exception
  while others then
  v_code: = SQLCODE;
  v_errm: = SUBSTR (SQLERRM, 1, 200);
  INSERT INTO VALUES error_log (v_code, v_errm, SYSTIMESTAMP);
  commit;
  DBMS_OUTPUT. Put_line (' error code:' | v_code |) ': ' || v_errm);
  
  END;
  /

  Details of database version are the following:

  Oracle Database 11 g Enterprise Edition Release 11.1.0.7.0 - 64 bit Production

  PL/SQL Release 11.1.0.7.0 - Production

  CORE Production 11.1.0.7.0

  AMT for Linux: Version 11.1.0.7.0 - Production

  NLSRTL Version 11.1.0.7.0 - Production

  
  SQL > show Cancel parameter

  VALUE OF TYPE NAME
  ------------------------------------ ----------- --------
  UNDO_MANAGEMENT string AUTO
  UNDO_RETENTION around 2000
  undo_tablespace string UNDOTBS1

  I changed the undo_retention and checked, it still gives the same error. The undo tablespace size is 23.7 GB (GB 23 is free, only 27 MB are used).

  Can anyone please suggest me, what could be the problem.

  Thank you

  SB2011

  Have a look here:

  Ask Tom & quot; SQL to retrieve a columns & quot;