UNDO Tablespace Issue - URGENT

I had issues with UNDO. Here is what happened -
SQL> alter tablespace UNDO
2 add datafile '/oracle/TESTDB/data04/TESTDB_undo_04.db' size 100M autoextend on maxsize 10000M;
SQL> select file_name,bytes/1024/1024 MB, maxbytes/1024/1024 MMB from dba_data_files where tablespace_name='UNDO';
FILE_NAME MB MMB
/oracle/TESTDB/data02/TESTDB_undo_01.dbf 6158 10240
/oracle/TESTDB/data01/TESTDB_undo_02.dbf 7703 0
/oracle/TESTDB/data03/TESTDB_undo_03.dbf 7636 0
/oracle/TESTDB/data04/TESTDB_undo_04.db 100 10000
But after some time this same query gave me this error -
SQL> select file_name,bytes/1024/1024 MB, maxbytes/1024/1024 MMB from dba_data_files where tablespace_name='UNDO';
FILE_NAME MB MMB
/oracle/TESTDB/data02/TESTDB_undo_01.dbf 6158 10240
/oracle/TESTDB/data01/TESTDB_undo_02.dbf 7703 0
/oracle/TESTDB/data03/TESTDB_undo_03.dbf 7636 0
/oracle/TESTDB/data04/TESTDB_undo_04.db
Users then started complaining about it.
Queries like this also started giving us these problems -
SQL> select file_id,file_name,bytes/1024/1024 MB, maxbytes/1024/1024 MMB,status from dba_data_files where tablespace_name='UNDO';
select file_id,file_name,bytes/1024/1024 MB, maxbytes/1024/1024 MMB,status from dba_data_files where tablespace_name='UNDO'
ERROR at line 1:
ORA-00376: file 67 cannot be read at this time
ORA-01110: data file 67: '/oracle/TESTDB/data04/TESTDB_undo_04.db'
Then I though of bouncing the database but then it also giving some problem -
SQL> shutdown immediate;
ORA-00376: file 67 cannot be read at this time
ORA-01110: data file 67: '/oracle/TESTDB/data04/TESTDB_undo_04.db'
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
TESTDB - /oracle/TESTDB/data03> sqlplus / as sysdba
SQL*Plus: Release 11.1.0.7.0 - Production on Fri Jul 30 09:27:24 2010
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected.
SQL> shutdown abort;
ORACLE instance shut down.
SQL> startup;
ORACLE instance started.
Total System Global Area 4175568896 bytes
Fixed Size 2160352 bytes
Variable Size 3137341728 bytes
Database Buffers 1023410176 bytes
Redo Buffers 12656640 bytes
Database mounted.
ORA-00376: file 67 cannot be read at this time
ORA-01110: data file 67: '/oracle/TESTDB/data04/TESTDB_undo_04.db'
Thought of recovering the this tablespace but still getting this error -
RMAN> recover tablespace "UNDO";
Starting recover at 30-JUL-10
starting full resync of recovery catalog
full resync complete
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=278 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=277 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/30/2010 09:34:17
ORA-00376: file 67 cannot be read at this time
ORA-01110: data file 67: '/oracle/TESTDB/data04/TESTDB_undo_04.db'
Will greatly appreciate if someone can give some advice here.

TESTDB - /oracle/TESTDB/data04> ls -ltr
total 25751072
drwxr-xr-x 2 oracle dba 256 Apr 9 10:09 lost+found
-rw-r----- 1 oracle dba 104865792 Jul 30 09:08 TESTDB_undo_04.db
-rw-r----- 1 oracle dba 104865792 Jul 30 09:50 TESTDB_paipas_idx_256k_a_01
-rw-r----- 1 oracle dba 104865792 Jul 30 09:50 TESTDB_cmwdgt_tab_1m_a_01
-rw-r----- 1 oracle dba 104865792 Jul 30 09:50 TESTDB_cmwdgt_idx_256k_a_01
-rw-r----- 1 oracle dba 104865792 Jul 30 09:50 TESTDB_cmpcc_idx_256k_a_01
-rw-r----- 1 oracle dba 232792064 Jul 30 09:50 TESTDB_cmcap_tab_1m_a_01
-rw-r----- 1 oracle dba 104865792 Jul 30 09:50 TESTDB_cmcap_idx_256k_a_01
-rw-r----- 1 oracle dba 504373248 Jul 30 09:50 TESTDB_cctlrpt_tab_1m_a_01
-rw-r----- 1 oracle dba 1356865536 Jul 30 09:50 TESTDB_ccstgrpt_tab_1m_a_01
-rw-r----- 1 oracle dba 4481622016 Jul 30 09:50 TESTDB_ccoprpt_tab_1m_a_01
-rw-r----- 1 oracle dba 653271040 Jul 30 09:50 TESTDB_ccindrpt_idx_256K_a_01
-rw-r----- 1 oracle dba 2752520192 Jul 30 09:50 TESTDB_cccnv_tab_1m_a_02.dbf
-rw-r----- 1 oracle dba 168828928 Jul 30 09:50 TESTDB_ccadmrpt_tab_1m_a_01
-rw-r----- 1 oracle dba 104865792 Jul 30 09:50 TESTDB_cmwos_idx_256k_a_01
-rw-r----- 1 oracle dba 104865792 Jul 30 09:50 TESTDB_cmgcd_idx_256k_a_01
-rw-r----- 1 oracle dba 104865792 Jul 30 09:50 TESTDB_cmfos_idx_256k_a_01
-rw-r----- 1 oracle dba 247472128 Jul 30 09:52 TESTDB_cmpcc_tab_1m_a_01
-rw-r----- 1 oracle dba 104865792 Jul 30 09:53 TESTDB_cmpe_tab_1m_a_01
-rw-r----- 1 oracle dba 104865792 Jul 30 09:53 TESTDB_cmpe_idx_256k_a_01
-rw-r----- 1 oracle dba 104865792 Jul 30 09:54 TESTDB_cmgcd_tab_1m_a_01
-rw-r----- 1 oracle dba 247472128 Jul 30 09:57 TESTDB_cmwos_tab_1m_a_01
-rw-r----- 1 oracle dba 364912640 Jul 30 09:58 TESTDB_cmfos_tab_1m_a_01
-rw-r----- 1 oracle dba 916004864 Jul 30 09:58 TESTDB_sysaux_02.dbf

Similar Messages

Undo tablespace issue

Hello,
I have a question regarding undo tablespace utilization. Currently there are no active transactions, all previous transactions have been commited, there is only one user session on my test database, undo retention is set to 900. I am trying to drop the old undo tablespace (I have created a new one, and switched to it - alter system undo_tablespace= new_undo;) but I get ORA-30013: undo tablespace 'old_undo' is currently in use.
I have bounced the database, but made no progress. dba_undo_extents stiil have active segments from the old_undo and dba_rollback_segs indicate there are two online segments from the old_undo.
Why is the old undo being used? WHo is using it?
Thank you and
Rgds

SQL> SELECT * FROM V$VERSION;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
SQL> select distinct status, segment_name, tablespace_name from dba_undo_extents where status='ACTIVE';
STATUS SEGMENT_NAME TABLESPACE_NAME
ACTIVE SYSSMU112241730627$ UNDOTBS8
ACTIVE SYSSMU161513093487$ UNDOTBS8
SQL> show parameter undo
NAME TYPE VALUE
undo_management string AUTO
undo_retention integer 900
undo_tablespace string UNDOTBS11
Thanks!

Switch undo tablespace issue

I want to swithch current undo tablespace to another current undo tablespace,how can i check whether all the sessions have finished and commited in current table space?

I don't think you really need to check because Oracle will handle the switch from old to new undo tablespace the following way:
>
The switch operation does not wait for transactions in the old undo tablespace to commit. If there are any pending transactions in the old undo tablespace, the old undo tablespace enters into a PENDING OFFLINE mode (status). In this mode, existing transactions can continue to execute, 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 completes successfully. A PENDING OFFLINE undo tablespace cannot be used by another instance, nor can it be dropped. Eventually, after all active transactions have committed, the undo tablespace automatically goes from the PENDING OFFLINE mode to the OFFLINE mode. From then on, the undo tablespace is available for other instances (in an Oracle Real Application Cluster environment).

Undo tablespace full even with no active transaction and undo_retention 10s

The 9.2.0.4 instance is AUM (auto undo management). The undo table space is 50G and is almost full.
I have set the undo_retention to 10, previously it was 10800 (3hours). I restart the database. Wait quite long time.
And search on the dba_undo_extents.
select sum(bytes/(1024*1024*1024)),status from dba_undo_extents d where d.tablespace_name='UNDOTBS2' group by status;
SUM(BYTES/(1024*1024*1024)) STATUS
.574447632 EXPIRED
45.5358887 UNEXPIRED
It is hard to explain. 10 seconds already passed, at least all the extents should be expired.
Why so many 45G is still unexpried.
Is there a bug for undo tablespace? how to fix it.
It is a rac instance, I am trouble shooting the undo tablespace issues.
The UNDOTBS2 is for node2 to use.

If you start the database in exclusive (one instance) mode then the database instance can have only one undo tablespace so I would not expect Oracle to do anything with the undo tablespace for the non-running instance.
Run you database as normal and generate undo. See if the status changes. If if does that would imply that Oracle does not expire undo unless the undo segments (rbs segments) are accessed. Please post back with results of what you see.
Between having batch production running on all my databases that use undo tablespaces and the fact we use uniform extent undo tabllespaces I am not in a position to try to duplicate what you are seeing.
HTH -- Mark D Powell --

Cannot drop undo tablespace

Hello:
I've created a new undo tablespace undotbs2. I've set it to the default undo tablespace. When I've tried to drop the old one, I get the following error:
SQL> conn / as sysdba
Connected.
SQL> DROP TABLESPACE undotbs1 INCLUDING CONTENTS AND DATAFILES;
DROP TABLESPACE undotbs1 INCLUDING CONTENTS AND DATAFILES
ERROR at line 1: ORA-01548: active rollback segment '_SYSSMU7$' found, terminate dropping tablespace
This is a production database. The service is down because the partition with the Oracle tablespaces: system, undo, temp, etc is full.
After shutting down the database the problem persist: I cannot drop the old undo tablespace because of the same error.
I've followed the note 1321093.1. Here the query results:
Select segment_name, status, tablespace_name, rs.segment_id
from dba_rollback_segs rs
where status not in ('ONLINE','OFFLINE');
_SYSSMU7$ PARTLY AVAILABLE UNDOTBS1 7
SELECT KTUXEUSN, KTUXESLT, KTUXESQN, /* Transaction ID */ KTUXESTA Status, KTUXECFL Flags
FROM x$ktuxe
WHERE ktuxesta !='INACTIVE' AND ktuxeusn =7;
7 47 382687 ACTIVE DEAD
SELECT LOCAL_TRAN_ID,GLOBAL_TRAN_ID,STATE,MIXED,COMMIT# FROM DBA_2PC_PENDING;
No rows
SELECT LOCAL_TRAN_ID,IN_OUT,DATABASE,INTERFACE FROM dba_2pc_neighbors;
No rows
As you can see, there is no pending transactions. No application is connected to the database (service is down), however the database is appling rollbacks since 2 days.
A lot of archivelogs are being created at rolling back (30 GB archivelogs per hour). Here a tail of the alertlog file:
Wed Apr 17 06:19:53 2013
Thread 1 advanced to log sequence 7382
Current log# 5 seq# 7382 mem# 0: /ora2/origlogs/webfrbr/redo05_m1.log
Current log# 5 seq# 7382 mem# 1: /ora3/mirrorlogs/webfrbr/redo05_m2.log
Wed Apr 17 06:21:16 2013
Thread 1 advanced to log sequence 7383
Current log# 6 seq# 7383 mem# 0: /ora2/origlogs/webfrbr/redo06_m1.log
Current log# 6 seq# 7383 mem# 1: /ora3/mirrorlogs/webfrbr/redo06_m2.log
Wed Apr 17 06:22:41 2013
Thread 1 advanced to log sequence 7384
Current log# 4 seq# 7384 mem# 0: /ora2/origlogs/webfrbr/redo04_m1.log
Current log# 4 seq# 7384 mem# 1: /ora3/mirrorlogs/webfrbr/redo04_m2.log
Wed Apr 17 06:24:02 2013
Thread 1 advanced to log sequence 7385
Current log# 5 seq# 7385 mem# 0: /ora2/origlogs/webfrbr/redo05_m1.log
Current log# 5 seq# 7385 mem# 1: /ora3/mirrorlogs/webfrbr/redo05_m2.log
Wed Apr 17 06:25:24 2013
Thread 1 advanced to log sequence 7386
Current log# 6 seq# 7386 mem# 0: /ora2/origlogs/webfrbr/redo06_m1.log
Current log# 6 seq# 7386 mem# 1: /ora3/mirrorlogs/webfrbr/redo06_m2.log
Wed Apr 17 06:26:46 2013
Thread 1 advanced to log sequence 7387
Current log# 4 seq# 7387 mem# 0: /ora2/origlogs/webfrbr/redo04_m1.log
Current log# 4 seq# 7387 mem# 1: /ora3/mirrorlogs/webfrbr/redo04_m2.log
Oracle Database - Enterprise Edition 10.2.0.3
Linux x86-64 Oracle Linux 5
Please, consider the output of the following queries too:
select * from V$FAST_START_TRANSACTIONS
USN 7 -- Undo segment number of the transaction
SLT 47 -- Slot within the rollback segment
SEQ 382687 -- Incarnation number of the slot
STATE RECOVERING --
UNDOBLOCKSDONE 0 -- Number of undo blocks completed on the transaction
UNDOBLOCKSTOTAL 2079151 -- Total number of undo blocks that need recovery
PID 15 -- ID of the current server it has been assigned to
CPUTIME 1153 -- Time for which recovery has progressed (in seconds)
PARENTUSN 0 -- Undo segment number of the parent transaction in PDML
PARENTSLT 0 -- Slot of the parent transaction in PDML
PARENTSEQ 0 -- Sequence number of the parent transaction in PDML
XID 07002F00DFD60500 -- Transaction ID
PXID 0000000000000000 -- Parent transaction ID
RCVSERVERS 1 -- Number of servers used in the last recovery
select * from x$ktuxe where ktuxecfl = 'DEAD';
ADDR 00002B3E808B9BD8
INDX 145
INST_ID 1
KTUXEUSN 7
KTUXESLT 47
KTUXESQN 382687
KTUXERDBF 2
KTUXERDBB 2080076
KTUXESCNB 424110769
KTUXESCNW 0
KTUXESTA ACTIVE
KTUXECFL DEAD
KTUXEUEL 3739
KTUXEDDBF 0
KTUXEDDBB 0
KTUXEPUSN 0
KTUXEPSLT 0
KTUXEPSQN 0
KTUXESIZ 2079151
select * from v$fast_start_servers;
RECOVERING 0 15 07002F00DFD60500
IDLE 0 16 0000000000000000
IDLE 0 17 0000000000000000
IDLE 0 18 0000000000000000
IDLE 0 19 0000000000000000
IDLE 0 20 0000000000000000
IDLE 0 21 0000000000000000
IDLE 0 22 0000000000000000
IDLE 0 25 0000000000000000
IDLE 0 26 0000000000000000
IDLE 0 27 0000000000000000
IDLE 0 28 0000000000000000
IDLE 0 29 0000000000000000
IDLE 0 30 0000000000000000
IDLE 0 31 0000000000000000
IDLE 0 32 0000000000000000
Any ideas to solve this issue?
Thank you in advance
Edited by: albrotar on Apr 17, 2013 1:48 AM
Edited by: albrotar on Apr 17, 2013 1:49 AM
Edited by: albrotar on Apr 17, 2013 1:51 AM
Edited by: albrotar on Apr 17, 2013 1:52 AM
Edited by: albrotar on Apr 17, 2013 1:54 AM

I've found some errors in alert log file occurred at shutting down the database:
+...+
Control autobackup written to DISK device
handle '/orabck/rman/webfrbr/ora_cfc-3587726327-20130414-00'
Completed: CREATE UNDO TABLESPACE undotbs2 DATAFILE '/orabck/undo/undotbs02.dbf'
SIZE 500M reuse autoextend ON NEXT 5M maxsize 32767M
Sun Apr 14 15:46:43 2013
Successfully onlined Undo Tablespace 5.
Undo Tablespace 1 moved to Pending Switch-Out state.
*** active transactions found in undo tablespace 1 during switch-out.
Sun Apr 14 15:46:44 2013
ALTER SYSTEM SET undo_tablespace='UNDOTBS2' SCOPE=BOTH;
Sun Apr 14 16:11:42 2013
ALTER ROLLBACK SEGMENT "_SYSSMU7$" offLINE
Sun Apr 14 16:11:42 2013
Completed: ALTER ROLLBACK SEGMENT "_SYSSMU7$" offLINE
Sun Apr 14 16:12:36 2013
DROP TABLESPACE undotbs1 INCLUDING CONTENTS AND DATAFILES
Sun Apr 14 16:12:36 2013
+...+
Thread 1 advanced to log sequence 5107
Current log# 4 seq# 5107 mem# 0: /ora2/origlogs/webfrbr/redo04_m1.log
Current log# 4 seq# 5107 mem# 1: /ora3/mirrorlogs/webfrbr/redo04_m2.log
Sun Apr 14 19:00:28 2013
Stopping background process CJQ0
Sun Apr 14 19:00:29 2013
Stopping background process QMNC
Sun Apr 14 19:00:31 2013
Stopping background process MMNL
Sun Apr 14 19:00:32 2013
Stopping background process MMON
Sun Apr 14 19:00:34 2013
Shutting down instance (immediate)
License high water mark = 31
Sun Apr 14 19:00:34 2013
Stopping Job queue slave processes
Sun Apr 14 19:00:34 2013
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Sun Apr 14 19:00:42 2013
ALTER DATABASE CLOSE NORMAL
Sun Apr 14 19:04:28 2013
+...+
Thread 1 advanced to log sequence 5118
Current log# 6 seq# 5118 mem# 0: /ora2/origlogs/webfrbr/redo06_m1.log
Current log# 6 seq# 5118 mem# 1: /ora3/mirrorlogs/webfrbr/redo06_m2.log
Sun Apr 14 20:11:21 2013
Errors in file /ora1/admin/webfrbr/bdump/webfrbr_smon_4629.trc:
+ORA-07445: exception encountered: core dump [_intel_fast_memcpy.A()+10] [SIGSEGV] [Invalid permissions for mapped object] [0x2B6B66003000] [] []+*
Sun Apr 14 20:11:21 2013
Errors in file /ora1/admin/webfrbr/bdump/webfrbr_smon_4629.trc:
ORA-00600: internal error code, arguments: [999], [0x107C14015], [], [], [], [], [], []*
+ORA-07445: exception encountered: core dump [_intel_fast_memcpy.A()+10] [SIGSEGV] [Invalid permissions for mapped object] [0x2B6B66003000] [] []+*
Sun Apr 14 20:11:22 2013
+...+
Sun Apr 14 20:11:48 2013
Errors in file /ora1/admin/webfrbr/bdump/webfrbr_pmon_4617.trc:
ORA-00474: SMON process terminated with error
Sun Apr 14 20:11:48 2013
+...+
The instance could start up, but after this, it is recovering undo and generating redo since 2 days

Question about Undo Tablespace?

Hello;
The size requirement of the undo tablespace is related to the number and size of transactions that occur on the database.But I dont need to query any of these transaction for a schema or table by using flashback so is there a way of disabling writing any transactions on a table or schema to undo tablespace ?
Edited by: Ecimen on 04.Mar.2013 03:50
Edited by: Ecimen on 04.Mar.2013 03:51

Rob_J wrote:
Hi,
No, that's not what I meant. What I meant was that if you say your logging tables are creating a lot of UNDO it must mean that you are writing/updating/deleting a lot of information from them. I was just throwing out the thought that if this is the cause of the issue, can you reduce the amount of data you write to these tables? In other words, do you need all this logging data? It's a question for the business and/or designers of your application to answer.
RobHello Rob;
i got it now , and yes we need to logging all this data because its production database occuring many transactions always...
Edited by: Ecimen on 04.Mar.2013 06:28
Edited by: Ecimen on 04.Mar.2013 06:31

Create tablespace issue

Hi;
I wanna learn one thing...
I have oracle ebs r11i wiht 10gr2 db, and its prod instance...
Issue is like this:
I have one tablespace lets us call it XXX and it has datafile like xx1.dbf,xx2.dbf..... I want to delete those dbf becouse their each size is 40 GB, and i want to create 2 new datafile which is each 10Gb.
Would you give me steps and command how i can do that?
Thanks

tablespace - XXX
datafile - xx1.dbf,xx2.dbf.....
you want to delete those dbf becouse their each size is 40 GB, and i want to create 2 new datafile which is each 10Gb.
1) If you want to delete 40 GB dbf's, you will loose data.
2) If you really do not want those data, you can go ahead by dropping and creating DBF with 10 GB.
steps and command how i can do that?
I have give below sample commands, go through it thoroughly and go ahead.
Best of Luck.
=================================================================
CREATING TABLESPACES
====================
CREATE TABLESPACE userdata DATAFILE '/u01/oradata/userdata01.dbf' SIZE 100M
AUTOEXTEND ON NEXT 5M MAXSIZE 200M;
Locally Managed Tablespaces
===========================
CREATE TABLESPACE userdata DATAFILE '/u01/oradata/userdata01.dbf' SIZE 500M
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 256K;
Dictionary Managed Tablespaces
==============================
CREATE TABLESPACE userdata DATAFILE '/u01/oradata/userdata01.dbf' SIZE 500M
EXTENT MANAGEMENT DICTIONARY DEFAULT STORAGE ( initial 1M NEXT 1M );
Undo Tablespace
===============
CREATE UNDO TABLESPACE undo1 DATAFILE '/u01/oradata/undo101.dbf' SIZE 40M;
Enabling Automatic Extension of Data Files
==========================================
ALTER DATABASE DATAFILE '/u01/oradata/userdata02.dbf' SIZE 200M AUTOEXTEND ON NEXT 10M MAXSIZE 500M;
SAMPLES
=======
SQL> CREATE TABLESPACE data01
2 DATAFILE '$HOME/ORADATA/u04/data01.dbf' SIZE 2M
3 EXTENT MANAGEMENT DICTIONARY;
Tablespace created.
SQL> CREATE TABLESPACE data02
2 DATAFILE '$HOME/ORADATA/u03/data02.dbf' SIZE 1M
3 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 100K;
Tablespace created.
SQL> CREATE TABLESPACE indx01
2 DATAFILE '$HOME/ORADATA/u02/indx01.dbf' SIZE 1M
3 AUTOEXTEND ON NEXT 500K MAXSIZE 2M
4 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 4K;
Tablespace created.
SQL> CREATE TABLESPACE ronly
2 DATAFILE '$HOME/ORADATA/u01/ronly01.dbf' SIZE 1M;
Tablespace created.
TO QUERY ALL TABLESPACES
========================
SELECT * FROM v$tablespace;
ALTER TABLESPACE
================
ALTER DATABASE DATAFILE '$HOME/ORADATA/u03/data02.dbf' RESIZE 1500K;

SYSTEM Tablespace issue (10.2.0.1 database)

Hi ,
Oracle database 10.2.0.1 (upgraded from 8.1.7.0 via 8.1.7.4)...successfully upgraded
Now when we open dbcontrol, we are getting alerts regarding the Tablespace.
It shows two critical alert messages as below :-
1) Tablesapace SYSTEM (dictionary managed) is 95.16 % full
2) 1 segment in SYSTEM tablespace is unable to extend.
Now how to deal with this type of issues ?
Can we extend the size of datafile of SYSTEM Tablespace which is dictionary managed ? or can we add another new datafile to system tablespace ? what is appropriate solution ?SYSTEM Tablespace
How to solve the point no. (2) as the TS is dictionary managed ?
With Regards

hi ,
Plz add the datafile to the system tablespace tp increase its size , and the conver the system tablespace from dictionary managed to local.
To Change SYSTEM tablespaces to locally managed follow the below procedures:
Before the SYSTEM tablespace can be migrated to locally managed format, you should ensure the following:
The database has a default temporary tablespace which is not SYSTEM
There are not any rollback segments in dictionary managed tablespaces
There is at least one online rollback segment in a locally managed tablespace, or an undo tablespace (if using automatic undo management mode) should be online.
All tablespaces other than the tablespace containing the undo space (undo tablespace or the tablespace containing the rollback segment) and the default temporary tablespace are in read-only mode.
There is a complete backup of the system.
The system is in restricted mode.
Notr, that we already have an UNDO Tablespace. The following query determines whether the SYSTEM tablespace is locally managed:
SQL> SELECT ts# FROM ts$ WHERE ts# = 0 AND bitmapped <> 0;
If 0 rows are returned, then the SYSTEM tablespace is dictionary managed. Otherwise, the SYSTEM tablespace is locally managed.
Steps to change SYSTEM tablespaces to locally managed
SQL> shutdown immediate
SQL> startup restrict
SQL> execute DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL ('SYSTEM');
ERROR at line 1:
ORA-10644: SYSTEM tablespace cannot be default temporary tablespace
ORA-06512: at "SYS.DBMS_SPACE_ADMIN", line 227
ORA-06512: at line 1
SQL> ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp;
SQL> execute DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL ('SYSTEM');
ERROR at line 1:
ORA-10647: Tablespace other than SYSTEM, UNDO, TEMP not
found in read only mode
ORA-06512: at "SYS.DBMS_SPACE_ADMIN", line 227
ORA-06512: at line 1
SQL> select tablespace_name from dba_tablespaces;
TABLESPACE_NAME
SYSTEM
TEMP
USERS
TAB
IDX
SYSAUX
UNDO
SQL> alter tablespace USERS read only;
SQL> alter tablespace TAB read only;
SQL> alter tablespace IDX read only;
SQL> execute DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL ('SYSTEM');
ERROR at line 1:
ORA-10648: Tablespace SYSAUX is not offline
ORA-06512: at "SYS.DBMS_SPACE_ADMIN", line 227
ORA-06512: at line 1
SQL> alter tablespace SYSAUX offline;
SQL> execute DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL ('SYSTEM');
PL/SQL procedure successfully completed.
Regards,
Mohd Mehraj Hussain
http://mehrajdba.wordpress.com

Segment shrinking and UNDO tablespace

When i issued
alter table <table_name> shrink space cascade;
I got the error 'Unable to extend UNDO ...by 8' . Does Segment shrinking consume space from UNDO tablespace?
Message was edited by:
for_good_reason

As Jonathan said, shrinking segment generates redo and undo data.
But, this phoenomenon of undo shortage is not normal case.
Shrinking segment might invole continous DML(deleting and re-inserting),
but it's transaction seems to be committed internally at regular intervals.
For this reason, shrinking operation should not hold undo area that long.
But have no knowledge on exact behavior of shrink operation.
Someone else will shed a light.
How big your table and indexes?
Some cases are reorted that shrinkage on big segment generates really large amount of undo data.
This might be related with your problem. But not sure.
Visit metalink note# 3888229.

TEST -- Active Undo Tablespace Drop

TEST
SUMMARY:-
When no active transactions are in UNDO tablespace, I can offline the undo datafile and subsequently drop the tablespace. No problems there.
Active Undo transactions combined with SHUTDOWN ABORT , I cannot open the database?
*****************SCREEN OUTPUT ************************
SQL>alter system set undo_tablespace='undotbs2' scope=spfile;
SQL> update mytst set table_name='jj';
1 row updated.
From another x-session I issued shutdown abort.
$mv undotbs02.dbf zz_undotbs02.dbf -- SImulate failure
SQL>ALTER DATABASE DATAFILE '/u02/app/oracle/oradata/HLCL/undotbs02.dbf' OFFLINE DROP ;
Database altered.
When i try to open the DB it gives
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
I tried to trace the error:-
alter system set "_smu_debug_mode"=1 scope=spfile;
alter system set event = "10015 trace name context forever, level 10" scope=spfile;
No pertinent information in trace file is generated either. Any pointers.

ARC0: STARTING ARCH PROCESSES COMPLETE
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC0: Becoming the heartbeat ARCH
ARC1 started with pid=17, OS id=4502
Thu Jun 22 17:58:28 2006
Errors in file /u02/app/oracle/admin/HLCL/udump/hlcl_ora_4498.trc:
ORA-00704: bootstrap process failure
ORA-00604: error occurred at recursive SQL level 2
ORA-00376: file 6 cannot be read at this time
ORA-01110: data file 6: '/u02/app/oracle/oradata/HLCL/undotbs02.dbf'
Thu Jun 22 17:58:28 2006
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 4498
ORA-1092 signalled during: ALTER DATABASE OPEN...
/u02/app/oracle/admin/HLCL/udump/hlcl_ora_4498.trc:
Hash table buckets = 32768
Longest hash chain = 0
Average hash chain = 0/0 = 0.0
Max compares per lookup = 0
Avg compares per lookup = 0/0 = 0.0
tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x1)
tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x1)
ORA-00704: bootstrap process failure
ORA-00604: error occurred at recursive SQL level 2
ORA-00376: file 6 cannot be read at this time
ORA-01110: data file 6: '/u02/app/oracle/oradata/HLCL/undotbs02.dbf'
Thanks for looking.

Drop undo tablespace

Tive que criar uma segunda undo tablespace, mas agora não preciso mais dela. Posso apagá-la normalmente com um drop tablespace ou tenho que fazer alguma verificação antes? Ela não é mais a undo tablespace da instância.

Tive que criar uma segunda undo tablespace, mas agora
não preciso mais dela. Posso apagá-la normalmente com
um drop tablespace ou tenho que fazer alguma
verificação antes? Ela não é mais a undo tablespace
da instância.Writing in a language different from english greatly reduces your chances to receive an answer. The official forum language is english. People here have made a great effort to reply to your post. You could try those on-line translators to translate from Portuguese to English, instead of letting the posters translate your request.
On the other hand, once you have created a second undo tablespace which is no longer requried, just drop the tablespace, assuming you have not declared this as your database undo tablespace at the UNDO_TABLESPACE instance parameter. You may issue the command:
drop tablespace yourUndoTablespace including contents and datafiles;
and you are done.
~ Madrid
http://hrivera99.blogspot.com/

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.

UNDO Tablespace size

Hi,
We have a production database with size 120GB (DB Version 11.1.0.6), And our UNDO Tablespace size is 30GB.
For the past 4 days the UNDO tablespace utilization is more than 85%.
We have disabled the AUTOEXTEND for the UNDO Tablespace.
So the UNDO RETENTION is dynamically calculated by Oracle itself and the value now is
TUNED_UNDORETENTION
339183
Please suggest how to fix this issue.
Thanks !

Hi,
The UNDO Tablespace size is still increasing. We dont have flashnack enabled for our database.
The database is 11.1.0.6 Standard Edition.
TABLESPACE TOTAL_SIZE_IN_MB FREE_SPACE_IN_MB % FREE %USED
UNDOTBS1 32152 4440 14 86.19
USERS 123784 23120 19 81.32
SYSTEM 1536 465 30 69.73
SYSAUX 1024 449 44 56.15
GGS_DATA 2048 1388 68 32.23
We enabled AUTOEXTEND on for one of the datafiles in UNDO Tablespace.
NAME TYPE VALUE
undo_management string AUTO
undo_retention integer 9000
undo_tablespace string UNDOTBS1
select to_char(begin_time, 'DD-MON-RR HH24:MI') begin_time,
to_char(end_time, 'DD-MON-RR HH24:MI') end_time, tuned_undoretention
from v$undostat order by end_time;
BEGIN_TIME END_TIME TUNED_UNDORETENTION
23-DEC-11 18:15 23-DEC-11 18:25 375077
23-DEC-11 18:25 23-DEC-11 18:35 375678
23-DEC-11 18:35 23-DEC-11 18:45 376278
23-DEC-11 18:45 23-DEC-11 18:51 376578
Please let me know how can i reduce the space consumed by UNDO Tablespace.

UNDO tablespace getting full

My undo tablespace is getting full because of uncommited deletes performed by jdbc thin client sessions.
How can I solve this problem permanently?
Size of undo tablespace is 5.5GB
I am facing an undo tablespace full issue
Below are the sessions which maybe 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 s.taddr=t.addr order by USED_UREC;
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 14k executions per hour.
Below is the query for this sql id:
/* TJAPI_SubTrxTransient_deleteTrb1SubTrxTransient_0 */ DELETE FROM TRB1_SUB_TRX_TRANSIENT
Some other details
++++++++++++
Oravle version:11.1.0.7
OS:SunOS
++++++++++++

Perhaps an interesting link:
http://oracledisect.blogspot.com/2008/05/who-is-using-your-undo-space.html
Perhaps you can use Oracle Resource Manager, create a resource plan and switch sessions to a different consumer group once they reach a certain treshold.
http://download.oracle.com/docs/cd/B28359_01/server.111/b28310/dbrm004.htm
Btw are these distributed transactions?
DBA commit other session's transaction?
Edited by: Markus Waldorf on Sep 9, 2010 7:57 PM

RMAN backup (no archivelogs) - undo tbsp issues

Hi guys,
Today I tried an inconsistent clone (from production to test DB) but it complained about the undo tablespace. Full message was:
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 2 needs more recovery to be consistent
ORA-01110: data file 2: '/ora/PPAHED01/data01/PPAHED01/datafile/undotbs1.dbf'
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/10/2013 15:40:17
RMAN-03015: error occurred in stored script Memory Script
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 2 seq 65710 lowscn 133872228360 found to restore
RMAN-06025: no backup of log thread 2 seq 65709 lowscn 133872193688 found to restore
RMAN-06025: no backup of log thread 1 seq 189087 lowscn 133872228359 found to restore
RMAN-06025: no backup of log thread 1 seq 189086 lowscn 133872226828 found to restore
RMAN-06025: no backup of log thread 1 seq 189085 lowscn 133872194295 found to restoreThe backup was of the control file and a full backup but there's an issue with the undo.
Can this issue be fixed by just removing the undo tablespace completely then creating one in mount? Or do I have to do lots of steps like here: http://sysinfo.bascomp.org/oracle/troubleshooting-for-startup-inconsistent-db/
I've not seen this issue when cloning before (although that was cloning an unused DB).
Mike

damorgan wrote:
To answer your question you can probably just create the UNDO tablespace ... no harm in trying.
But there is substantial harm in running a production system, as you are doing, and not being in archive log mode.
Unless your production database is a toy holding nothing more important than your mother's cookie recipes I highly recommend you don't even take the time to blink your eyes before you enable archive logging: What you have is the moral equivalent to performing surgery without first washing your hands.The production system is in archivelog mode, I just didnt want to FTP the log files over too as it doesn't have to be a completely recent backup. It doesn't even have to be from the last month.
Mike

UNDO Tablespace Issue - URGENT

Similar Messages

Maybe you are looking for