Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • Convert multiple rows to single column Oracle
  • SQL Server Vs Oracle Architecture difference SQL Server
  • To find all disk io ( EMC as well as local) Linux/Unix
  • My Test Case On 21-OCT-2005 Oracle
  • ORA-1841 Error Connecting to Upgraded Database After Set PASSWORD_LIFE_TIME Oracle
  • plan10g.sql good1 Oracle
  • Privileges Required to Create Procedures and Functions that uses objects from other schema. Oracle
  • Find long Running Transaction Linux/Unix
  • Absolute file number and relative file number Oracle
  • checking redhat linux version Linux/Unix
  • Find sort details from Db find_sort.sql Oracle
  • Oracle vs MYSQL Architecture differences (For DBAs) MYSQL
  • findobj.sql Oracle
  • Jai Shree Ram Oracle
  • Python class import from different folders Python/PySpark

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

  • How to calculate PROCESSES parameter Oracle
  • Example of How To Resize the Online Redo Logfiles Note:1035935.6 Oracle
  • sql_plan9i.sql Oracle
  • proc.sql Oracle
  • Optimizer_Index init.ora parameter explaination. Oracle
  • longtx.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)
  • Django (0)
  • GIT (1)
  • Linux/Unix (149)
  • MYSQL (5)
  • Oracle (395)
  • PHP/MYSQL/Wordpress (10)
  • POSTGRESQL (1)
  • Power-BI (0)
  • Python/PySpark (7)
  • RAC (17)
  • rman-dataguard (26)
  • shell (150)
  • SQL scripts (343)
  • SQL Server (6)
  • Uncategorized (0)
  • Videos (0)

Recent Posts

  • prepfiles.sh for step by step generating pending statistics files10-Mar-2026
  • tracksqltime.sql05-Mar-2026
  • Complete Git Tutorial for Beginners25-Dec-2025
  • Postgres DB user and OS user.25-Dec-2025
  • 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

Archives

  • 2026
  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • configUOCIOTTO.ora Oracle
  • Good Site for Oracle Internals Oracle
  • Oracle Identifiers Oracle
  • Sending SQLPLUS output in HTML format Oracle
  • First Entry in RAC Oracle
  • This is im telling Kishore Oracle
  • To check whether standby is recovering properly or not?? Oracle
  • New OFA for 11g Oracle

Copyright © 2026 pvmehta.com.

Powered by PressBook News WordPress theme