Repair Critical System Index
RoarkJul 21 2010 — edited Jul 21 2010First, The actual error code is below:
SQL> create table foo (data varchar2(100));
Table created.
SQL> drop table foo;
Table dropped.
SQL> purge recyclebin
2 ;
Recyclebin purged.
SQL>
SQL> create table foo(id number primary key);
create table foo(id number primary key)
*
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-08102: index key not found, obj# 49, file 1, block 57390 (2)
OK, now I will explain to the best of my ability, the situation:
This error message is associated with an error in the core database product. The problem is NOT in the Apex product itself. There is a damaged Oracle database dictionary, damaged file/ index. We need a fix to repair the specific System index that is damaged. The problem we are having is that the index is a critical index. When we attempt to rebuild the damaged index we are told the damaged index is necessary for a warm restart of the database. At this point we are stuck. If we cannot repair the specific System index we will have to wipe the system and reinstall Apex. If we do this we will have to rebuild all of our tables and more. This represents weeks of work or more. So we would like to have help repairing the specific damaged critical index as opposed to wiping everything.
Specifically, we cannot create tables that have a primary key (cannot create an index). When we attempt to create a table with a primary key the message above is the message we receive. We can create a table that does not have a primary key.
History: FYI
About six weeks ago we upgraded our Apex from version 3.1 to version 3.2. The first attempt failed the second attempt succeeded. In order to get the update to work we had to allocate more file space for the tables so there would be more storage space for the tables to utilize.
We are dead in the water until we resolve this issue. Please help.