Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • DB Console Mainenance. Oracle
  • oracle tips… from http://www.bijoos.com/oracle/douknow.htm Oracle
  • How to find the real execution plan and binds used in that explain plan in Oracle 10g?? Oracle
  • eplan9i.sql Oracle
  • copying/removing directory with all its subdirectory Linux/Unix
  • CTAS with LONG Column for 9i and higher Oracle
  • V$CONTROLFILE_RECORD_SECTION reference notes. Oracle
  • Load testing on Oracle 19C RAC with HammerDB Oracle
  • Convert multiple rows to single column Oracle
  • All About oracle password and security from metalink Oracle
  • Good link for LIO in Oracle ( Logical IOs) Oracle
  • find_du.ksh to find # of files, their sizes in current folder and its subdolder Linux/Unix
  • compile_inv.sql Oracle
  • Changing Instance Name ( No DB_NAME) Oracle
  • OPENING A STANDBY DATABASE IN READ-ONLY MODE Oracle

V$ROLLSTAT status is Full

Posted on 13-May-2008 By Admin No Comments on V$ROLLSTAT status is Full

Problem Description:

====================

You receive the following error:

ORA-01562: “failed to extend rollback segment number %s”

Cause: Failure occurred when trying to extend rollback segment

Action: This is normally followed by another error message that caused

the failure. You may take the rollback segment offline to

perform maintainence. Use the alter rollback segment offline

command to take the rollback segment offline.

You check the “v$rollstat” view to find the status of rollback segment is

listed as FULL. What does this mean?

Solution Description:

=====================

A rollback segment is marked as FULL when an error ORA-1562 is signalled.

When the rollback segment is marked with a status of FULL, no new transactions

will use the rollback segment. The FULL status is intended to signal

transactions to use other valid rollback segments. All transactions in

that rollback segment must complete before the full status is cleared. This

means that all transactions must either be committed or rolled back.

If it is not possible to commit every transaction, possible workarounds are:

a. Taking the rollback segment offline and bringing back online should also

clear the full status. This could potentially take awhile if there are a

large number of transaction that need to be rolled back.

Alter rollback segment offline;

Alter rollback segment online;

b. Adding a datafile to the rollback segment tablespace so that the segment

can extend. You can then continue with the *current* txn (that caused the

rollback segment to get status FULL) and the status will then get reset to

ONLINE.

If you are unable to wait for the full status to be cleared, then bouncing

the database will clear the rollback segment.

Possible workaround is to use set transaction. This is supposed to override

the full flag and still use the full rollback segment.

Set transaction use rollback segment ;

Explanation:

============

The full status on a rollback segment is cleared when all transactions in the

rollback segment are completed (committed or rolled back) and it is determined

that the segment can wrap. It is also cleared if the number of active

transactions in the rollback segment is zero.

Oracle, SQL scripts

Post navigation

Previous Post: Rman Notes -1
Next Post: OEM-Commnds

Related Posts

  • Import and export statements Oracle
  • DBMS_Shared_pool pinning triggers Oracle
  • Find nth max and min. Oracle
  • findx.sql /* Find Indexes on specified USER.TABLE_NAME */ Oracle
  • Query to Generate aggregate on every 30 mins. Oracle
  • SQL Tracker by SID sqltrackerbysid.sql Oracle

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Categories

  • Ansible (0)
  • AWS (2)
  • Azure (1)
  • Linux/Unix (149)
  • MYSQL (5)
  • Oracle (393)
  • PHP/MYSQL/Wordpress (10)
  • POSTGRESQL (0)
  • Power-BI (0)
  • Python/PySpark (7)
  • RAC (17)
  • rman-dataguard (26)
  • shell (149)
  • SQL scripts (342)
  • SQL Server (6)
  • Uncategorized (0)
  • Videos (0)

Recent Posts

  • Trace a SQL session from another session using ORADEBUG30-Sep-2025
  • SQL Server Vs Oracle Architecture difference25-Jul-2025
  • SQL Server: How to see historical transactions25-Jul-2025
  • SQL Server: How to see current transactions or requests25-Jul-2025
  • T-SQL Vs PL/SQL Syntax25-Jul-2025
  • Check SQL Server edition25-Jul-2025
  • Checking SQL Server Version25-Jul-2025
  • Oracle vs MYSQL Architecture differences (For DBAs)24-Jul-2025
  • V$INSTANCE of Oracle in MYSQL24-Jul-2025
  • Day to day MYSQL DBA operations (Compared with Oracle DBA)24-Jul-2025

Archives

  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • Oracle GoldenGate lag monitoring shell script Linux/Unix
  • How to find where datafile is created dbf_info.sql Oracle
  • How To Limit The Access To The Database So That Only One User Per Schema Are Connected (One Concurrent User Per Schema) Oracle
  • Disbaling DBA_SCHEDULER_JOBS Oracle
  • Changing default shell Linux/Unix
  • Check Oracle installed products using one command Oracle
  • New Latest Param.sql for finding all hidden parameters also Oracle
  • Jai Shree Ram Linux/Unix

Copyright © 2025 pvmehta.com.

Powered by PressBook News WordPress theme