Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • findobj.sql Oracle
  • All About oracle password and security from metalink Oracle
  • Export Import with QUERY Oracle
  • How to connect to Oracle Database with Wallet with Python. Oracle
  • Example of How To Resize the Online Redo Logfiles Note:1035935.6 Oracle
  • V$CONTROLFILE_RECORD_SECTION reference notes. Oracle
  • Pending Transaction Neighbors Script Oracle
  • Creating never expiring DB user accounts in Oracle Oracle
  • upload.html PHP/MYSQL/Wordpress
  • Single character replacement in Unix Linux/Unix
  • longtx.sql Oracle
  • load SPM baseline from cursor cache Oracle
  • How does one SELECT a value from a table into a Unix variable? From SQL to Shell Linux/Unix
  • DBMS_UTILITY.ANALYZE_SCHEMA Oracle
  • T-SQL Vs PL/SQL Syntax SQL Server

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

  • 272332.1 CRS 10g Diagnostic Collection Guide Oracle
  • 276434.1 Modifying the VIP or VIP Hostname of a 10g or 11g Oracle Clusterware Node Oracle
  • Proc Compilation Oracle
  • Import and export statements Oracle
  • runon_allcdbs_find_pdbs.sh Linux/Unix
  • pvm_rbs1.sql (to collect rbs info from db) 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 (150)
  • MYSQL (5)
  • Oracle (403)
  • PHP/MYSQL/Wordpress (10)
  • POSTGRESQL (1)
  • Power-BI (0)
  • Python/PySpark (7)
  • RAC (18)
  • rman-dataguard (26)
  • shell (151)
  • SQL scripts (349)
  • SQL Server (6)
  • Uncategorized (5)
  • Videos (0)

Recent Posts

  • Key Management in Oracle: The Core Issue: Missing Master Key12-May-2026
  • SAT Mathematics 10 questions and answer at the end.30-Apr-2026
  • top 10 AI news today30-Apr-2026
  • runon_allpdbs_show_conname.sh23-Apr-2026
  • runon_allcdbs_find_pdbs.sh23-Apr-2026
  • Running PDB on single node in RAC09-Apr-2026
  • find_arc.sql09-Apr-2026
  • pvm_pre_change.sql08-Apr-2026
  • find_encr_wallet.sql08-Apr-2026
  • find_pdbs.sql08-Apr-2026

Archives

  • 2026
  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • Sample WW22 listener.ora Oracle
  • pvm_metric.sql for gathering report from vmstat tables Oracle
  • Optimizer_Index init.ora parameter explaination. Oracle
  • TRUNCATE table and disabling referential constraints. Oracle
  • Good Site for Oracle Internals Oracle
  • Oracle Internal Good Websites 1 Oracle
  • create database link syntax Oracle
  • CTAS with LONG Column for 7.x and 8 and 8i Oracle

Copyright © 2026 pvmehta.com.

Powered by PressBook News WordPress theme