Re: Oracle on Win2k and async I/O

Marty,

A couple of things, maybe you already seen them too. Oracle has in previous releases experienced autoextend errors up to 4gig files sizes.

Is your file system NTFS or FAT or RAW. Some limits changed depending.

To be safe I would stop my filesize at 4gig. I like to keep them smaller for backups anyway.

Kevin Gillins

"Marty Egan" <martyegan_at_rocketmail.com> wrote in message news:74ca126c.0209170758.4e2db400_at_posting.google.com...
> I'm experiencing Oracle crashes that appear to be a problem with the
> Oracle async I/O interaction with the OS / array controller driver /
> array controller hardware. It appears that when Oracle goes to
> auto-extend (e.g. the temp tablespace) that it is then trying to write
> to a block inside the extended disk space before it actually has been
> created / extended.
> ===========================================
> === Here's the SQL and the log. ===
> === ===
> === (My system config is after the log ===
> === ===
> === init.ora is after the system config ===
> ===========================================
>
>
>
>
>
> SQL> CREATE INDEX STATS_INX ON STATS_IN(TIMEB) TABLESPACE ST_X;
>
> Index created.
>
> SQL> CREATE INDEX STATS_READERSX ON STATS_READERS(TIMEB) TABLESPACE
> ST_X;
>
> Index created.
>
> SQL> CREATE INDEX STATS_DETAILEDX ON STATS_DETAILED(TIMEB) TABLESPACE
> ST_DETAILX
> ;
>
> Index created.
>
> SQL> CREATE INDEX TWISTER_DEBUGX ON TWISTER_DEBUG(TIMET) TABLESPACE
> TW_DEBUGX;
> CREATE INDEX TWISTER_DEBUGX ON TWISTER_DEBUG(TIMET) TABLESPACE
> TW_DEBUGX
>
> From alert*.log *
> ERROR at line 1:
> ORA-00603: ORACLE server session terminated by fatal error
>
> Mon Sep 16 23:26:34 2002
> Errors in file C:\oracle\admin\NEWSDB01\udump\ORA02264.TRC:
> ORA-01114: IO error writing block to file 201 (block # 261557)
> ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
> OSD-04026: Invalid parameter passed. (OS 261572)
> ORA-01114: IO error writing block to file 201 (block # 261557)
> ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
> OSD-04026: Invalid parameter passed. (OS 261572)
> ORA-01114: IO error writing block to file 201 (block # 261557)
> ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
> OSD-04026: Invalid parameter passed. (OS 261572)
> ORA-01114: IO error writing block to file 201 (block # 261557)
> ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
> OSD-04026: Invalid parameter passed. (OS 261572)
>
> Mon Sep 16 23:26:42 2002
> Errors in file C:\oracle\admin\NEWSDB01\udump\ORA02264.TRC:
> ORA-00603: ORACLE server session terminated by fatal error
> ORA-01114: IO error writing block to file 201 (block # 261557)
> ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
> OSD-04026: Invalid parameter passed. (OS 261572)
> ORA-01114: IO error writing block to file 201 (block # 261557)
> ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
> OSD-04026: Invalid parameter passed. (OS 261572)
> ORA-01114: IO error writing block to file 201 (block # 261557)
> ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
> OSD-04026: Invalid parameter passed. (OS 261572)
> ORA-01114: IO error writing block to file 201 (block # 261557)
> ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
> OSD-04026: Invalid parameter passed. (OS 261572)
>
>
>
> ===================
> === Sys Config ===
> ===================
> Oracle 9x
> Win2k SP2 plus "critical" hotfixes.
> Compaq Proliant ML570
> Dual P3 Xeon with 1M cache
> Smart Array 5302 controller with 128M RAM
> 12-72Gig disk drives
> =6 drives on bus 1
> =6 drives on bus 2
> Array 1
> 72Gig = RAID 1 across bus 1 / id 1 and bus 2 / id 1
> OS, pagefile, temp space
> Array 2
> 271Gig = RAID 5 across bus 1 / id 2-6
> tablespace, roughly 2/3 capacity of array is filled
> Array 3
> 271Gig = RAID 5 across bus 2 / id 2-6
> tablespace, roughly 1/2 capacity of array is filled
>
>
>
> ===================
> === init.ora ===
> ===================
>

############################################################################

############################################################################