ORA-600 [17033]

21 October 1999

ORA-00600: internal error code, arguments: [17033], [509], [128], [], [], [], [], []

An entry is being generated every few seconds, and the trace files keep filling up the file system. For now I'm moving them off, but it looks like queries are being affected as well. This happened one other time earlier this summer, and bouncing the database took care of the problem. The only thing I can find on MetaLink is this reference to the _kgl_bucket_count parameter:

Bug 381193 defines a scenario where ORA-600 [17033] is signaled due to lack of resources for the library cache hash table. The workaround for this bug is to set _kgl_bucket_count = 4. Again, this should only be set if it has been determined that the ORA-600 is actually caused by this bug as it can be signaled for other reasons.

ORA-600 [2845]

24 November 1999

Core dumps

9 December 1999

Fractured block found

11 December 1999

Corrupt block relative dba: 0x26c085d6 file=155. blocknum=34262.
Fractured block found during buffer read
Data in bad block - type:6. format:2. rdba:0x26c085d6
last change scn:0x0000.00970ace seq:0x2 flg:0x00
consistency value in tail 0x00000001
check value in block header: 0x0, check value not calculated
spare1:0x0, spare2:0x0, spare2:0x0

Check the hardware diagnostic logs for the disk, and if you find any errors or warnings, I suggest you have it replaced.

Instance crashing

3 January 2000

ORA-600 [2667]

12 January 2000

ORA-600 [2103]

17 January 2000

ORA-7445

17 January 2000

ORA-07445: exception detected: core-dump [4] [9] [0] [0] [] []
----- Call Stack Trace -----
calling              call     entry                argument values in hex
location             type     point                (? means dubious value)
-------------------- -------- -------------------- ----------------------------
Error from U_get_previous_frame_x is 1
Stack is not Windable
Stack has no Unwind_descriptor

xdb $ORACLE_HOME/bin/oracle core

ORA-600 [4036]

20 January 2000

NetApp problems

28 January 2000

On several occasions all 6 database have crashed simultaneously, needing media recovery. This happened again last night. Oracle Support suggest that it may have been a hardware problem, but our system administrator has checked and the only problem was a full file system. A copy of the log writer trace file is attached. Is it possible for you to give me some explanations about this? My boss wants to know what really occurred. Is it Oracle, Solaris, NetApp or what?

ORA-00345: redo log write error block 99252 count 2
ORA-00312: online log 1 thread 1: '/oracle_logs/oradata/stage02/online_redo/stage02_redo01a.log'
ORA-27063: skgfospo: number of bytes read/written is incorrect
SVR4 Error: 28: No space left on device
Additional information: -1
Additional information: 1024
ORA-00346: log member marked as STALE
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [2745], [0], [], [], [], [], [], []

The instances crashed, because Oracle must mark any log file for which a write fails as STALE, and stop using it. Oracle did this, but then it had no valid online log file member to write to, so it crashed with [2745] which is the expected behaviour.

I've had a look at the NetApp site, and read their paper 3023 saying that it is supported with Oracle. Nevertheless, I am skeptical. Log files should already exist on disk, and should not hit file system full errors. Also, how does Oracle do synchronous writes over NFS? I don't know what special intelligence they have got there, but I strongly suspect that using a NetApp box for Oracle is a bad idea, despite the certification.

ORA-1578: ORACLE data block corrupted

2 February 2000

ORA-01578: ORACLE data block corrupted (file # 80, block # 2843)
ORA-01110: data file 5: '/oracle/PRD/saprawe4c/pool2d.data03'

select
  segment_name,
  segment_type
from
  dba_extents  
where
  file_id = 80 and
  2843 between block_id and block_id + blocks - 1
/

OSD-04008: WriteFile() failure

9 February 2000

KCF: write/open error block=0x4fd1 online=1
     file=3 D:\ORANT\DATABASE\USR1WIND.ORA
     error=27072 txt: 'OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.'
Instance terminating due to error 1242

ORA-600 [17034]

28 February 2000

alter session set events '600 trace name processstate forever, level 10';

SQL> create table emp(empno number(5), empname varchar2(30));

Table created.

SQL> alter table emp add constraint empl_pk primary key (empno);

Table altered.

SQL> create or replace trigger emp_bef_ins
  2  before insert on emp for each row
  3  begin null; end;
  4  /

Trigger created.

SQL> alter session set events '600 trace name processstate forever, level 10';

Session altered.

SQL> insert into emp values(1,'steve adams');

1 row created.

SQL> commit;

Commit complete.

SQL> insert into emp values(1,'steve adams');
insert into emp values(1,'steve adams')
            *
ERROR at line 1:
ORA-00600: internal error code, arguments: [17034], [2281304776], [0], [], [], [], [], []
ORA-00001: unique constraint (DEMO.EMPL_PK) violated

SQL> drop trigger emp_bef_ins;

Trigger dropped.

SQL>  insert into emp values(1,'steve adams');
insert into emp values(1,'steve adams')
             *
ERROR at line 1:
ORA-00001: unique constraint (DEMO.EMPL_PK) violated