ORA-00600: internal error code, arguments: [12700]

[THoey]

I am starting to get this error repeatedly on one of my Oracle instances on an Win NT server.

I went to Metalink and researched it and it seems to be a corrupt index. Possible solutions are to drop and recreate all indexes. I would love to try this, but I don't have all of the names for the indexes. If I try to query all_indexes, I get the error again.

I wanted to place a TAR on Metalink, and their page seems to be acting up. Went through several pages to where they display threads that could possibly help you. Some were close but didn't give me all the information I wanted, so I selected continue with TAR creation. A blank page gets returned.

Any ideas how I can figure out all of my index names without using all_indexes? Or any other great ideas? Terry M. Hoey
th3856@txmail.sbc.com
While I don't mind e-mail messages, please post all questions in these forums for the benefit of all members.

 

[THoey]

An update. I only get the error when I query against all_indexes for one owner. I also get the error if I use Oracle DBA Studio and try to view the indexes owned by that user. Terry M. Hoey
th3856@txmail.sbc.com
While I don't mind e-mail messages, please post all questions in these forums for the benefit of all members.

 

[THoey]

Another update. I was able to do an end run to see the index names. I used Oracle DBA Studio and looked at the tables instead of the indexes.

I have narrowed it down to two indexes owned by an OPS$ account. That should be the only objects owned by that account. Shouldn't I be able to delete that account and it will drop those? I can then schedule them to be recreated this evening. Terry M. Hoey
th3856@txmail.sbc.com
While I don't mind e-mail messages, please post all questions in these forums for the benefit of all members.

 

[karluk]

Maybe I'm interpreting your error incorrectly, but I'm not convinced that recreating the indexes on the OPS$ id will fix your problem. The way you describe it, the only time you ever get the ORA-600 errors is when you query ALL_INDEXES. To me that strongly suggests that any index problems are on the catalog tables that ALL_INDEXES references. I checked and these are

sys.ts$ (index I_TS1)
sys.seg$ (no indexes)
sys.user$ (index I_USER1)
sys.obj$ (indexes I_OBJ1, I_OBJ2, I_OBJ3)
sys.ind$ (index I_IND1)

 

[THoey]

We kinda came to that conclusion too. I was able to login to SQL Plus as that user and drop the indexes and the problem still persists. I was also able to get my TAR submitted. Going to keep looking while I wait for an answer... Terry M. Hoey
th3856@txmail.sbc.com
While I don't mind e-mail messages, please post all questions in these forums for the benefit of all members.

 

[THoey]

I have been working with Oracle on this through Metalink. They wanted to know if the error was still duplicatable. I ran the SQL and immediately got a "PMON process has terminated". I shutdown and restarted the services and then ran my batch file that restarts the Oracle instance. It came back with the following message:

Connected to an idle instance.
ORACLE instance started.
Total System Global Area 7506628 bytes
Fixed Size 35760 bytes
Variable Size 7053076 bytes
Database Buffers 409600 bytes
Redo Buffers 8192 bytes
Database mounted.

ORA-01116: error in opening database file 6
ORA-01110: data file 6: 'E:\ORANT\DATABASE\USR2ORCL.ORA'
ORA-09203: sfofi: error opening file
OSD-04002: unable to open file
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Server Manager complete.

I posted this back to my TAR, but don't really have a couple hours to wait for a response. Any ideas?
Terry M. Hoey
th3856@txmail.sbc.com
While I don't mind e-mail messages, please post all questions in these forums for the benefit of all members.

 

[fuad]

Well one way is to see where you have placed you indexes if they are in a seperate tablesoace drop the tablespaces.
use dba_indexes or dba_objects to see exactly which objects are identified as indexes

 

[karluk]

I would try rebooting the server, especially if you are running under Windows. That seems to cure 95% of the problems.

 

[uparna]

Hi Terry ,
Are you using oracle version 8.1.6.x ? I suspect you are .

Even we were facing a number of problems of a similar sort when we were using this version. The instance would shutdown sporadically ,and when we went through the logs , we found a lot of ORA-600 messages displayed. Let me tell you that we were running the simplest of applications during this time.
After a very long correspondence with Oracle Support , we were finally told that this is an internal bug that has been solved in the latest release. You may not believe this , but after all the torture that we were put through , installing the latest version was the best cure. The database has not gone down even once and is performing marvelously!
Bythe way , you neednt worry , 8.1.7.0 comes as a free upgrade.....you have to just call them up and mention your TAR or CSI number. Also ask for the latest patch 8.1.7.1 .which is only available through a CD (It is not in metalink).
Hope this will help you.

Regards,
S. Jayaram Uparna .

If the need arises,you are welcome to mail me at oracguru@yahoo.com .I would be glad to help you out.