Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Tablespace, Diskspace or sql abuse..
A quick check with oerr shows this :
oerr ora 27069
27069, 00000, "skgfdisp: attempt to do I/O beyond the range of the file"
// *Cause: internal error, the range of blocks being read or written is
// outside the range of the file, additional information
indicates
// the starting block number, number of blocks in I/O, and the
// last valid block in the file
// *Action: check for trace file and contact Oracle Support
I suspect that internally, Oracle 'thinks' the file is 'x; extents long, but the OS 'thinks' it is less than 'x'. End result, carnage !
You say that you are running a query, but the error is obtained writing to the file in question. I suspect that this could be a file in your temporary tablespace. Whatever it is, you should check for any trace files in BACKGROUND_DUMP_DEST and log an iTAR with support. Your DBA should be able to manage this - he hasn't been very helpful so far :o)
Cheers,
Norm.
Tel: 0113 289 6265 Fax: 0113 289 3146 URL: http://www.Lynx-FS.com -------------------------------------
-----Original Message-----
From: nikey11 [mailto:nikey11]On Behalf Of nikey11
Posted At: Tuesday, June 24, 2003 2:02 PM
Posted To: server
Conversation: Tablespace, Diskspace or sql abuse..
Subject: Tablespace, Diskspace or sql abuse..
Hi you'll,
I've encounered a problem that recieved the following error:
ORA-01114: IO error writing block to file 201 (block # 359561) ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file OSD-04026: Invalid parameter passed. (OS 359567) ORA-01114: IO error writing block to file 201 (block # 359561) ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file OSD-04026: Invalid parameter passed. (OS 359567) ORA-01114: IO error writing block to file 201 (block # 359561) ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file OSD-04026: Invalid parameter passed. (OS 359567)
My dba claimes that the problem is caused by a not logical query, I think it is a tablespace problem, maybe you can be the judge.
My query joins a table (of 1358453 rows) to itself :
The comparison fields are a date field and an int field when the date
field is joined with the ">" operator and the int field is joined by
equalization,
The query is again joined to my previous table when the join method is
that the last table date field is between the first table date field and
the second table date field.
Is this query unacceptable
-- Posted via http://dbforums.comReceived on Tue Jun 24 2003 - 08:51:36 CDT