Arrghh!!

Fix one problem and then you run smack into another one.

Oracle 8.1.7.4 (32bit) on HP-UX B11.

Been getting this:
ORA-00600: internal error code, arguments: [711], [1], [1074596568], [kdiulk - prefix context], [], [], [], []

Traced it to a potential problem with compressed indexes. Rebuild indexes without compression. This error disappears...

...only to be replace with this shortly after: ORA-600 [25012] Metalink reports this as an index problem (bugs 1228658, 1138239, 1312233, 1297674, etc) - but all fixed with 8.1.6.2 latest.

I know that this should be TAR'ed.. but I'm pushing for a 9i upgrade on all our platforms anyway. And we're likely to see that before we see this problem patched (given that 8.1 is being desupported end of this year).

In the meantime I have production jobs that fail. Ones that never have failed before with an ORA-00600. The instance itself is unchanged. Been patched to 8.1.7.4 last year - no other changes (except dealing with larger volumes of data than before).

Bigger indexes on bigger tables, and using compression btw, on the _same_ instance work fine. Not a single ORA-00600 except for two specific tables on that instance.

Any ideas? DBMS_REPAIR? (will have to squeeze that into the production windows somehow and I dread doing things like that based on past nightmares running DBCC on SQL-Server.. many years ago... ;-)

--
Billy