RE: Reproduce ORA-0600

Hello,

First of all, let me explain what the difference between ora-7445 and ora-600: We know ora-600 is oracle internal errors. ora-7445 is internal error, too. But ora-600 is catched by Oracle server. If Oracle server can not catch its internal errors, OS may catch and returns exception signals to Oracle. Then, Oracle throws ora-7445. In other words, ora-7445 does not always mean OS internal errors.

In your case, ORA-600 [3374] is due to block corruption detected in Cache Layer Component of block which is being prepared for write. Second argument of ORA-600 [3374] corresponds to the expected DataBlockAddress. They are 11206682 and 2617431000. The blocks in these DBA are corrupted. Let's convert DBA to corresponding (file#,block#). Run the followings:

select dbms_utility.data_block_address_file(<dba>) from dual; --- returns file number---

select dbms_utility.data_block_address_block(<dba>) from dual; --- returns block number---

Run the following SQL to find corrupted object:

       SELECT tablespace_name, segment_type, owner, segment_name
          FROM dba_extents
         WHERE file_id = <fileNumber>
           and <blockNumber> between block_id AND block_id + blocks - 1;

Try to use this object again by touching corrupted blocks. You will encounter same ora-600 [3374] if you can touch it.

If you can not visit corrupted block, you will never get ora-600 [3374] again. Perhaps, it's and rbs and Oracle may be getting another rbs. So, you may not get ora-600 [3374] again.

It's not possible to go further by alert.log. If you have trace file, you can upload it to iOraBugFinder. if you set 'Include relavent error', iOraBugFinder process relevant error in trace file. If iOraBugFinder doesn't return your bug, set 'eMail Sender' in iOraBugFinder and email support_at_unal-bilisim.com with uploaded trace file.

regards...

24/7/01 08:35:06, Danisment Gazi Unal (Unal Bilisim) <danisment.unal_at_unalbilisim. com> wrote:

>Hello,
>
>First of all, let me explain what the difference between ora-7445 and ora-600:
>
>We know ora-600 is oracle internal errors. ora-7445 is internal error, too.
But
>ora-600 is catched by Oracle server. If Oracle server can not catch its
>internal errors, OS may catch and returns exception signals to Oracle. Then,
>Oracle throws ora-7445. In other words, ora-7445 does not always mean OS
>internal errors.
>
>In your case, ORA-600 [3374] is due to block corruption detected in Cache
Layer
>Component of block which is being prepared for write. Second argument of ORA-
>600 [3374] corresponds to the expected DataBlockAddress. They are 11206682 and
>2617431000. The blocks in these DBA are corrupted. Let's convert DBA to
>corresponding (file#,block#). Run the followings:
>
>select dbms_utility.data_block_address_file(<dba>) from dual;
>--- returns file number---
>
>select dbms_utility.data_block_address_block(<dba>) from dual;
>--- returns block number---
>
>Run the following SQL to find corrupted object:
>
> SELECT tablespace_name, segment_type, owner, segment_name
> FROM dba_extents
> WHERE file_id = <fileNumber>
> and <blockNumber> between block_id AND block_id + blocks - 1;
>
>
>
>Try to use this object again by touching corrupted blocks. You will encounter
>same ora-600 [3374] if you can touch it.
>
>If you can not visit corrupted block, you will never get ora-600 [3374] again.
>Perhaps, it's and rbs and Oracle may be getting another rbs. So, you may not
>get ora-600 [3374] again.
>
>It's not possible to go further by alert.log. If you have trace file, you can
>upload it to iOraBugFinder. if you set 'Include relavent error', iOraBugFinder
>process relevant error in trace file. If iOraBugFinder doesn't return your
bug,
>set 'eMail Sender' in iOraBugFinder and email support_at_unal-bilisim.com with
>uploaded trace file.
>
>
>regards...
>
>24/7/01 07:40:55, "Smith, Ron L." <rlsmith_at_kmg.com> wrote:
>
>>Here are the error messages:
>>ORA-07445: exception encountered: core dump [11] [0] [0] [0] [] []
>>Mon Jul 2 08:03:19 2001
>>Thread 1 advanced to log sequence 304
>> Current log# 8 seq# 304 mem# 0: /u035/oradata/prod/redo08.log
>>Mon Jul 2 13:55:26 2001
>>Thread 1 advanced to log sequence 305
>> Current log# 5 seq# 305 mem# 0: /u032/oradata/prod/redo05.log
>>Mon Jul 2 14:02:27 2001
>>Errors in file /u002/app/oracle/admin/prod/udump/ora_11586.trc:
>>ORA-07445: exception encountered: core dump [11] [0] [0] [0] [] []
>>Mon Jul 2 14:06:20 2001
>>Errors in file /u002/app/oracle/admin/prod/bdump/dbwr_21336.trc:
>>ORA-00600: internal error code, arguments: [3374], [11206682], [825371952],
>>[875376697], [11824], [], [], []
>>Mon Jul 2 14:06:22 2001
>>Errors in file /u002/app/oracle/admin/prod/bdump/dbwr_21336.trc:
>>ORA-00600: internal error code, arguments: [3374], [2617431000],
>>[960050989], [32], [0], [32], [], []
>>ORA-00600: internal error code, arguments: [3374], [11206682], [825371952],
>>[875376697], [11824], [], [], []
>>Mon Jul 2 14:20:22 2001
>>
>>
>>-----Original Message-----
>>Sent: Tuesday, July 24, 2001 11:11 AM
>>To: Multiple recipients of list ORACLE-L
>>
>>
>>Hello,
>>
>>What was the first parameter of ora-600 ? We should unserstand if your
>>ora-600
>>are cause or consequence. if it's consequence( I guess it's in your case),
>>ignore it.
>>
>>24/7/01 06:10:53, "Lord, David - C&S" <David.Lord_at_hayscsg.com> wrote:
>>
>>>Try upgrading to 8.1.6, its great at throwing 600's ;-)
>>>
>>>-----Original Message-----
>>>Sent: 24 July 2001 15:31
>>>To: Multiple recipients of list ORACLE-L
>>>
>>>
>>>I had a production database become corrupt after an ORA-07445 and an
>>>ORA-0600 occurred. The instance would not come back up and had to be
>>>recovered. I can reproduce and correct the ORA-07445 (bad block) but it
>>>doesn't create the ORA-0600 or corrupt the database. I have tried adding
>>>rows, deleting rows, reading by the index by requesting all columns in the
>>>index, updating all columns in the index. Nothing seems to work. Any
>>ideas
>>>on how I can reproduce the error?
>>>
>>>Ron Smith
>>>rlsmith_at_kmg.com
>>>--
>>>Please see the official ORACLE-L FAQ: http://www.orafaq.com
>>>--
>>>Author: Smith, Ron L.
>>> INET: rlsmith_at_kmg.com
>>>
>>>Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
>>>San Diego, California -- Public Internet access / Mailing Lists
>>>--------------------------------------------------------------------
>>>To REMOVE yourself from this mailing list, send an E-Mail message
>>>to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
>>>the message BODY, include a line containing: UNSUB ORACLE-L
>>>(or the name of mailing list you want to be removed from). You may
>>>also send the HELP command for other information (like subscribing).
>>>--
>>>Please see the official ORACLE-L FAQ: http://www.orafaq.com
>>>--
>>>Author: Lord, David - C&S
>>> INET: David.Lord_at_hayscsg.com
>>>
>>>Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
>>>San Diego, California -- Public Internet access / Mailing Lists
>>>--------------------------------------------------------------------
>>>To REMOVE yourself from this mailing list, send an E-Mail message
>>>to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
>>>the message BODY, include a line containing: UNSUB ORACLE-L
>>>(or the name of mailing list you want to be removed from). You may
>>>also send the HELP command for other information (like subscribing).
>>>
>>>
>>>
>>
>>
>>
>>--
>>Please see the official ORACLE-L FAQ: http://www.orafaq.com
>>--
>>Author: Danisment Gazi Unal (Unal Bilisim)
>> INET: danisment.unal_at_unal-bilisim.com
>>
>>Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
>>San Diego, California -- Public Internet access / Mailing Lists
>>--------------------------------------------------------------------
>>To REMOVE yourself from this mailing list, send an E-Mail message
>>to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
>>the message BODY, include a line containing: UNSUB ORACLE-L
>>(or the name of mailing list you want to be removed from). You may
>>also send the HELP command for other information (like subscribing).
>>--
>>Please see the official ORACLE-L FAQ: http://www.orafaq.com
>>--
>>Author: Smith, Ron L.
>> INET: rlsmith_at_kmg.com
>>
>>Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
>>San Diego, California -- Public Internet access / Mailing Lists
>>--------------------------------------------------------------------
>>To REMOVE yourself from this mailing list, send an E-Mail message
>>to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
>>the message BODY, include a line containing: UNSUB ORACLE-L
>>(or the name of mailing list you want to be removed from). You may
>>also send the HELP command for other information (like subscribing).
>>
>>
>>
>
>

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Danisment Gazi Unal (Unal Bilisim)
  INET: danisment.unal_at_unal-bilisim.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).