7/26/2019 Fixing a Corrupted SYSAUX Tablespace (Doc ID 950128.1)

1/1

Fixing a Corrupted SYSAUX Tablespace (Doc ID 950128.1)

In this Document

Goal

Solution

1- RMAN Block Recovery

2 - Restore and Recover the Corrupted Datafile(s)

3 - Recreate the Corrupted Object

4 - Export

References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and thereforehas not been subject to an independent technical review.

APPLIES TO:

Oracle Database - Enterprise Edition - Version 10.2.0.1 and laterInformation in this document applies to any platform.***Checked for relevance on 17-May-2013******Checked for relevance on 3-Jul-2015***

GOAL

How to fix/work-around a corrupted SYSAUX tablespace

SOLUTION

SYSAUX was introduced in 10g to store all auxiliary database metadata related to Oracle options andfeatures. This is a mandatory tablespace and cannot be dropped. Therefore it is important to have allobjects in this tablespace accessible at all times.

To find out what is stored in this tablespace, look at V$SYSAUX_OCCUPANTS:

SQL> select occupant_name, space_usage_kbytes from v$sysaux_occupants;

Throughout this document, we are assuming that the datafile 3, belonging to the SYSAUX tablespace, is

corrupted.

1- RMAN Block Recovery

RMAN block recovery is only possible if you have a backup and all archivelogs from prior to the time of thecorruption. Further, block recovery is only available for Oracle Enterprise Edition.

a) check for corruption

RMAN> backup validate check logical tablespace SYSAUX;

or

RMAN> backup validate check logical datafile 3;

Pgina 1 de 1Document 950128.1

10/12/2015https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=t9vjhrx6e_1...