Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    ue_01 gets "end-of-file on communication channel" errors

    • Article Type: General
    • Product: Aleph
    • Product Version: 16.02

    Description:
    The ODIN ue_01 processes frequentyl stop functioning, getting the message:

    Oracle error: io_commit
    ORA-03113: end-of-file on communication channel

    followed by:

    Oracle error: io_commit
    ORA-03114: not connected to ORACLE

    This is with the xxx30 Course Reserve libraries and the ILL libraries. There about 80 of these. Having to constantly be restarting these is a major inconvenience.

    Resolution:
    [From site:]

    I opened TAR#6174365.993 -- we've tried a lot of things.
    Results: the ue_01 applications appear to be losing a connection to the database when times between documents exceed 1 hour.
    I made a change which has fixed this problem. In sqlnet.ora, added parameter:

    ########################
    sqlnet.expire_time = 10
    ########################
    #
    #Possible values: 0-any valid positive integer! (in minutes)
    #Default: 0 minutes
    #Recommended value: 10 minutes
    #
    #Purpose: Indicates the time interval to send a probe to verify the
    # client session is alive (this is used to reclaim watseful
    # resources on a dead client)
    #
    #Supported since: v2.1

    Explanation:
    DCD(Dead COnnection Detection) is initiated on the server when a connection is established. At this time SQL*Net reads the
    SQL*Net parameter files and sets a timer to generate an alarm. The timer interval is set by providing a non-zero value in minutes(30) for the SQLNET.EXPIRE_TIME parameter in the sqlnet.ora file.

    When the timer expires, SQL*Net on the server sends a "probe" packet to the client. The probe is essentially an empty SQL*Net packet and does not represent any form of SQL*Net level data, but it creates data traffic on the underlying protocol and resets most internal network time

    Additional Information

    faq


    • Article last edited: 10/8/2013
    //doorbell.io feedback widged