Results 1 to 4 of 4
  1. #1
    Join Date
    Jun 2005
    Location
    Waukesha WI
    Posts
    78

    Unanswered: not connected to ORACLE error

    Since the 9i Oracle Server was rebooted because of the Windows sercurity patch last week, we are getting a not connected to oracle error sporadically.

    I can replicate the error in the following manner:
    I utilize TOAD to connect to oracle.
    It sees everything fine.
    I look at the data of one of our tables (400K rows).
    If I try to sort on one of the columns (not indexed), I get the following:
    ORA-01114:IO error writing block to file %s(block#%s)

    When I click OK, the data does not appear.
    If I switch to another table to view the data, I get the error:
    ORA-03114:not connected to ORACLE
    If I click OK and then select another table, I can see the data. I can then switch back to the original table and see it as well.

    Although I dont know where to look for the problem, this seems like a timeout problem of some sort that perhaps has not been properly set up in an initialization file somewhere.

    Anyone have any ideas?

    Jerry

  2. #2
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    >ORA-01114:IO error writing block to file %s(block#%s)
    >this seems like a timeout problem of some sort
    I have NO idea how/why you might think this might be a timeout problem.
    IMO, this appears to be a file corruption/disk failure problem.
    If so, you should have additional clues in alert_SID.log file.
    MetaLink has articles how to find & work around bad blocks in Oracle datafiles.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  3. #3
    Join Date
    Apr 2007
    Posts
    2
    Quote Originally Posted by jer99
    Since the 9i Oracle Server was rebooted because of the Windows sercurity patch last week, we are getting a not connected to oracle error sporadically.

    I can replicate the error in the following manner:
    I utilize TOAD to connect to oracle.
    It sees everything fine.
    I look at the data of one of our tables (400K rows).
    If I try to sort on one of the columns (not indexed), I get the following:
    ORA-01114:IO error writing block to file %s(block#%s)

    When I click OK, the data does not appear.
    If I switch to another table to view the data, I get the error:
    ORA-03114:not connected to ORACLE
    If I click OK and then select another table, I can see the data. I can then switch back to the original table and see it as well.

    Although I dont know where to look for the problem, this seems like a timeout problem of some sort that perhaps has not been properly set up in an initialization file somewhere.

    Anyone have any ideas?

    Jerry
    When you say timeout do you mean TOAD session timeout?
    I know many situations when TOAD doesn't handle timeouts well. Leave uncomited transaction in one window. Select same table from another and you will have timeout which with high probability (at least for TOAD version 8.5) will give you an internal error message not related to database.

    So first do the same in sqlplus to rule out the TOAD bugs.

    - Roman

  4. #4
    Join Date
    Jun 2005
    Location
    Waukesha WI
    Posts
    78
    The simple answer...sometimes too simple.
    I believe that TOAD was still connected when the server was rebooted.
    This caused the sporadic activity since then.
    The reason I believe this was the problem is because once the server processes were stopped and started again, everything now works.

    We'll be watching it closely though.

    Thanks for the input.

    Jerry

Posting Permissions

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