[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now


corrupted index in system tablespace

Posted on 2004-08-03
Medium Priority
Last Modified: 2012-03-06
I have corrupted index in system tablespace:
Index Name:         I_OBJ1
Table Name:         OBJ$
Owner:                 SYS
Tablespace:          SYSTEM
How do I rebuild this index and waht are the potensial problems?
The corruption was found through trace file.
Question by:harlemit
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +3
LVL 35

Accepted Solution

Mark Geerlings earned 400 total points
ID: 11706867
Start with taking a backup that you can restore that if necessary, to at least get back to where things are now.

If you've been taking backups regulary and are running in archivelog mode, you could consider restoring an older backup and running through the archived redo logs up to the point in time when the corruption occured (if you can determine when that was).

Do a complete export.  That should give you everything you need to rebuild your database completely, and you may have to do that.

I'm sure you know that Oracle usually does not support users or DBA directly changing objects in the SYS schema (the SYS.AUD$ table is an exception - you can truncate or delete rows from that table).  Have you contacted Oracle support for their help on this?
LVL 35

Assisted Solution

johnsone earned 400 total points
ID: 11707083
As this is an index, I would think you should be able to rebuild it.  I would do it in restricted mode with no users on the database.

You would definitely want an opinion from Oracle though.  They may consider your database unsupported if you do that.
LVL 23

Expert Comment

ID: 11708524

The easiest way, run this script:


this will recompile all the invalid and corrupted objects.
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

LVL 35

Expert Comment

by:Mark Geerlings
ID: 11709015
To seazodiak,

That suggestion will not help.  Here is the documentation from the top of the "utlrp.sql" file:
Rem $Header: utlrp.sql 15-nov-2001.10:56:31 rburns Exp $
Rem utlrp.sql
Rem Copyright (c) 1998, 2001, Oracle Corporation.  All rights reserved.  
Rem    NAME
Rem      utlrp.sql - UTiLity script Recompile invalid Pl/sql modules
Rem     This is a fairly general script that can be used at any time to
Rem     recompile all existing invalid PL/SQL modules in a database.
-- (end of clip from file)

Note that it only re-compiles PL\SQL objects.  It does not rebuild indexes that have problems.

To harlemit:

Your best option is to contact Oracle technical support and follow their recommendations.  If that is not an option for you (like if you are running an Oracle database without paying for support) then you are unsupported anyway, so login as SYS and drop, then recreate that index.

Of course, before doing that, make a complete backup and if possible a complete export, so if dropping and rebuilding this index creates more problems, you can go back to where you are now.
LVL 23

Expert Comment

ID: 11709809

I guess it's true by saying "nothing is what it seems" ;-)

though what you said is absolutely correct, but UTLRP.sql do a lot more than pl/sql recompilation.
it recompiles all the invalid objects instead.

Here is the evidence:

In the Header comments of UTLRP.SQL : REad the last line

Rem    NAME
Rem      utlrp.sql - UTiLity script Recompile invalid Pl/sql modules
Rem     This is a fairly general script that can be used at any time to
Rem     recompile all existing invalid PL/SQL modules in a database.
Rem     If run as one of the last steps during migration/upgrade/downgrade
Rem     (see the README notes for your current release and the Oracle
Rem     Migration book), this script  will validate all PL/SQL modules
Rem     (procedures, functions, packages, triggers, types, views, libraries)


Now the story does not end here. if you look the contents below of this script, it will actually call another script:


In the header of this file:
Rem     This script provides a packaged interface to recompile all
Rem     existing invalid PL/SQL modules, Java classes, indextypes and
Rem     operators in a database sequentially or in parallel.

again look at  the last line, it even recompile the JAVA CLASS , not to mentiion the index types.

LVL 23

Assisted Solution

seazodiac earned 400 total points
ID: 11709833
I don't remember when, but I remembered
that Once I recompiled by invoking that script to recompile the invalid indexes in the database dictionary catalogs.

but I guess the poster's situation might be different.

I am not sure the word "corrupted" is the block corrupted physically or logically.

In the former case, he might need to rebuild the block or recover from the backup.

in the latter, he might be able to rebuild it manually.
LVL 13

Assisted Solution

anand_2000v earned 400 total points
ID: 11712214
Obviously the only option will be to recover using a backup file. A sys object should not be rebuilt as this will lead to other problems.  Markgeer's answer seems to be the best solution
LVL 48

Assisted Solution

schwertner earned 400 total points
ID: 11712615
Do a FULL export.
After that do import (only on SYS schema, I am not sure if it is possible, if not - do a full import).
But use
parameter and use also logfile parameter.
In the logfile you will have an section for creating indexes. Filter using text editor the name of the index and the creation statement. After that drop the index and recreate it using that script.
LVL 35

Expert Comment

ID: 11715652
I believe markgeer is pointing out that utlrp will not rebuild a corrupted index.  In fact, I would not be surprised if the status on the index was still VALID.

What is being described sounds like block corruption in an index.

If you don't have support, rebuild the index.  If you do, I would contact Oracle for their recommendation.

I don't see a need to rebuild a database for a corrupted index.  If this was user data and not dictionary, we would all just rebuild the index, not restore a backup.

Expert Comment

ID: 37684785
From SQL(DML) Level, You cannot rebuild OBJ$ about indexes, Even if you startup migrate/upgrade.

Featured Post

On Demand Webinar: Networking for the Cloud Era

Ready to improve network connectivity? Watch this webinar to learn how SD-WANs and a one-click instant connect tool can boost provisions, deployment, and management of your cloud connection.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Why doesn't the Oracle optimizer use my index? Querying too much data Most Oracle developers know that an index is useful when you can use it to restrict your result set to a small number of the total rows in a table. So, the obvious side…
Cursors in Oracle: A cursor is used to process individual rows returned by database system for a query. In oracle every SQL statement executed by the oracle server has a private area. This area contains information about the SQL statement and the…
This video explains at a high level with the mandatory Oracle Memory processes are as well as touching on some of the more common optional ones.
This video explains what a user managed backup is and shows how to take one, providing a couple of simple example scripts.

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question