ORA-30013 is the error reported when the specified Undo tablespace is in use. In other words, this implies there are some background processes still using the undo tablespace.
This error can be reported in both space management or transaction management.
Error ORA-30013 reported while dropping the Undo tablespace.
In this case, the Undo tablespace is used by other active transactions, leading to the error. In such cases, we have to wait until the transactions are committed or rolled back before dropping the Undo tablespace. This situation is similar to that of the ORA-1548 case.
Error ORA-30013 reported while bringing up the database.
This happens for RAC databases while the undo tablespace mentioned for an instance is already in use. The solution will be to set separate Undo tablespace for all instances.
Since undo_tablespace is an instance local parameter, we have to ensure that the "Alter system set undo_tablespace" is being invoked on a different instance than the one on which the "Alter system" command was issued.
alter system set undo_tablespace= <undo tablespace name> sid='<instance name>';
Diagnostic Information to be Collected While Raising a Service Request.
If the issue persists, please raise a Service Request with the following information
a. Provide the complete error message reported along with the trace files generated.
b. Provide the following outputs:
Select segment_name,status,tablespace_name from dba_rollback_segs where status not in ('ONLINE','OFFLINE') ;
select KTUXEUSN, KTUXESLT, KTUXESQN, KTUXESTA, KTUXECFL, KTUXESIZ
from x$ktuxe
where KTUXESTA='ACTIVE' and KTUXECFL='DEAD';
from x$ktuxe
where KTUXESTA='ACTIVE' and KTUXECFL='DEAD';
SELECT LOCAL_TRAN_ID,GLOBAL_TRAN_ID,STATE,MIXED,COMMIT# FROM DBA_2PC_PENDING;
SELECT LOCAL_TRAN_ID,IN_OUT,DATABASE,INTERFACE FROM dba_2pc_neighbors;
SELECT LOCAL_TRAN_ID,IN_OUT,DATABASE,INTERFACE FROM dba_2pc_neighbors;
show parameter undo
Comments
Post a Comment