RE: anyone awake out there...ORA-00600: ...[kteuPropTime-2]..any ideas, thoughts...have a tar open...Note:233864.1

I would definitely work with Oracle on this one. If your production system(s) are down, you must escalate this TAR for immediate assistance. I know this sounds rather trite, but Oracle's support model is setup to give the squeakiest wheel the most grease. If they are not helping you with this (and believe me, they DO have workarounds), you are not making it painful enough for them.

On this particular issue:

We have had similar situations. For the most part, UNDO has given us better performance than ROLLBACK, but we've upgraded our major databases to 9.2.0.4 or greater for quite some time. Anything less than that is very precarious. Take heed!

• "Marquez, Chris" <cmarquez_at_collegeboard.org> wrote:

> Well not TAR update...sev 1...we are down. :0|
>
> Amazing what a little "pain" from you client and
> lack of sleep does for ones "self motivation".
>
> Google (the other Oracle Support) produced this;
>
>

http://www.oracleadvice.com/BUGBUSTER/bug_autoundo.htm
> A great doc...makes sense and I have (sadly)
> recovered from corrupt RBS/UNDO before.
>
> Once / If, I get the database up again, looks like
> my options are;
> - Upgrade to 9206
> - Use one-off patch for 9203 Bug: 2431450 - START
> EXTENT NUMBER NOT UPDATED CORRECTLY, FOR COMMITTED
> TXNS WHICH HAVE NTP SET
>
> But I wonder and hope that maybe I can just *not*
> use UNDO and go backup to old school RBS and *avoid*
> the problem/bug?
>
> ok...I'm rambling.
>
> Chris Marquez
> Oracle DBA
>
>
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org on behalf of
> Marquez, Chris
> Sent: Sun 7/17/2005 3:14 AM
> To: oracle-l_at_freelists.org
> Subject: anyone awake out there...ORA-00600:
> ...[kteuPropTime-2]..any ideas, thoughts...have a
> tar open...Note:233864.1
>
> ???
>
> Oracle has encountered an error propagating Extent
> Commit Times in
> the Undo Segment Header / Extent Map Blocks, for
> System Managed Undo
> Segments
>
> The extent being referenced is not valid.
>
>
>
> Sun Jul 17 01:25:14 2005
> ARC0: Completed archiving log 1 thread 1 sequence
> 14
> Sun Jul 17 01:25:51 2005
> Errors in file /oracle//bdump/orcl_j001_115070.trc:
> ORA-00600: internal error code, arguments:
> [kteuPropTime-2], [], [], [], [], [], [], []
> Sun Jul 17 01:25:55 2005
> Errors in file /oracle//bdump/orcl_j001_115070.trc:
> ORA-00600: internal error code, arguments:
> [kteuPropTime-2], [], [], [], [], [], [], []
> ORA-12008: error in materialized view refresh path
> ORA-00600: internal error code, arguments:
> [kteuPropTime-2], [], [], [], [], [], [], []
> Sun Jul 17 01:25:56 2005
> Error 600 trapped in 2PC on transaction 2.9.24787.
> Cleaning up.
> Error stack returned to user:
> ORA-00600: internal error code, arguments:
> [kteuPropTime-2], [], [], [], [], [], [], []
> ORA-12008: error in materialized view refresh path
> ORA-00600: internal error code, arguments:
> [kteuPropTime-2], [], [], [], [], [], [], []
> Sun Jul 17 01:25:56 2005
> Errors in file /oracle//bdump/orcl_j001_115070.trc:
> ORA-00603: ORACLE server session terminated by fatal
> error
> ORA-00600: internal error code, arguments:
> [kteuPropTime-2], [], [], [], [], [], [], []
> ORA-12008: error in materialized view refresh path
> ORA-00600: internal error code, arguments:
> [kteuPropTime-2], [], [], [], [], [], [], []
> Sun Jul 17 01:26:31 2005
> Errors in file /oracle//udump/orcl_ora_648044.trc:
> ORA-07445: exception encountered: core dump [] [] []
> [] [] []
> Sun Jul 17 01:26:31 2005
>
>
>

--
http://www.freelists.org/webpage/oracle-l