DBAsupport.com Forums - Powered by vBulletin
Results 1 to 6 of 6

Thread: ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file

  1. #1
    Join Date
    Nov 2000
    Posts
    440
    ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file

    Hi, the status off one of my datafile is at recover.
    I did a recover, here's the output:

    SQL> recover datafile 'D:\DATAFILE\INTE01.ORA';
    ORA-00283: recovery session canceled due to errors
    ORA-01115: IO error reading block from file 2 (block # 1048482)
    ORA-01110: data file 2: 'D:\DATAFILE\INTE01.ORA'
    ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
    OSD-04026: Invalid parameter passed. (OS 1048482)



    Windows NT Version 4.0 Service Pack 5, CPU type 586
    Oracle8i Enterprise Edition Release 8.1.6.0.0 - Production
    With the Partitioning option
    JServer Release 8.1.6.0.0 - Production
    Windows NT Version 4.0 Service Pack 5, CPU type 586

  2. #2
    Join Date
    May 2002
    Posts
    2,645
    Wow, I didn't know there was an error message that high.

    Error: ORA-27069
    Text: 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

  3. #3
    Join Date
    Nov 2000
    Posts
    440
    I did post on metalink, but response time is long there, here is faster, anyone have any idea?

  4. #4
    Join Date
    May 2002
    Posts
    2,645
    I saw the posting from John B. (your post?). If you have MetaLink access, you also have TAR support - call Oracle or submit a TAR.

  5. #5
    Join Date
    Nov 2000
    Posts
    440
    How do i open a tar?
    We are oracle partner, i have all info i need(partner number, etc...) but im alone at work, and the guy that open tar, is not there, ive look on meta-link and can only access the tar profile.

  6. #6
    I am afraind that you hit some bug.
    Check metalink notes about 4GB boundary.
    YOu are in trouble.
    Open a tar, seems hard to recover through it.
    www.cnoug.org

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width