Scribd Logo
Upload

Welcome to Scribd!

  • 453 views

    Frequent CHECK TIMED OUT Status of Listener and DB Resources (Doc ID 1608197.1)

    Uploaded by

    elcaso34

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Frequent CHECK TIMED OUT Status of Listener and DB Resources (Doc ID 1608197.1)

    Uploaded by

    elcaso34
    453 views2 pages

    Original Title

    Frequent CHECK TIMED OUT status of listener and DB resources (Doc ID 1608197.1)

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    453 views2 pages

    Frequent CHECK TIMED OUT Status of Listener and DB Resources (Doc ID 1608197.1)

    Uploaded by

    elcaso34

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 2

    10/21/2020 Document 1608197.

    1
    Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.

    RAC: Frequent CHECK TIMED OUT status of listener and DB resources (Doc ID 1608197.1)

    In this Document

    Symptoms
    Cause
    Solution
    References

    APPLIES TO:

    Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.1 [Release 11.2 to 12.1]
    Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
    Oracle Database Cloud Schema Service - Version N/A and later
    Oracle Database Exadata Express Cloud Service - Version N/A and later
    Oracle Database Exadata Cloud Machine - Version N/A and later
    Microsoft Windows x64 (64-bit)

    SYMPTOMS

    Scan listener ONLINE INTERMEDIATE and in a state of CHECK TIMED OUT

    CAUSE

    This status may be encountered due to the known issue whereby the default timeout for LISTENER resources (30
    seconds) for 11.2.X RAC clusters on Windows is too aggressive.

    Reference: Bug 14593380 - CHECK TIMED OUT STATUS INTERMITTENTLY SEEN FOR LISTENER AND DATABASE
    RESOURCES

    SOLUTION

    1. Check the current value of the CHECK_TIMEOUT attribute of the SCAN listener resources by running the following
    commands from $GI_HOME/bin as a local Administrator:

    > crsctl status resource ora.LISTENER_SCAN1.lsnr -f


    > crsctl status resource ora.LISTENER_SCAN2.lsnr -f
    > crsctl status resource ora.LISTENER_SCAN3.lsnr -f

    Among the output for each of the listeners you will see an entry like this:

    > CHECK_TIMEOUT=nnn

    where nnn is some number.

    2. If this number is 60 or less then please change this as follows:

    > crsctl modify res <name of listener> -attr "CHECK_TIMEOUT=120"

    This will set the CHECK_TIMEOUT interval to 120. Values less than 120 seconds are not recommended for Windows.
    Repeat for all SCAN listeners and check that the values have been changed (sing the "crsctl status ... " commands above).

    https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=ezt0pef4m_4&id=1608197.1 1/2
    10/21/2020 Document 1608197.1

    3. Monitor for recurrence of the "CHECK TIMED OUT" messages. It may take some time for any existing messages to
    clear.

    Note: 1. If the local listeners are also encountering the CHECK TIMED OUT issue then modify them also.

    2. Although the bug referred here are for windows, the CHECK_TIMEOUT changes is applicable to all platforms. In
    12.1.0.2, CHECK_TIMEOUT is set to 120 for LISTENER resource by default.

    REFERENCES

    BUG:14593380 - CHECK TIMED OUT STATUS INTERMITTENTLY SEEN FOR LISTENER AND DATABASE RESOURCES
    BUG:20591664 - DB SERVICE IN INTERMEDIATE STATUS CHECK TIMED OUT AFTER KILLING PMON OF RAC
    Didn't find what you are looking for?

    https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=ezt0pef4m_4&id=1608197.1 2/2

    You might also like