This discussion is archived
1 2 Previous Next 17 Replies Latest reply: Jan 13, 2013 6:04 PM by 909525 RSS

"TNS-12535: TNS:operation timed out" error after listener restart

909525 Newbie
Currently Being Moderated
I have two related questions:

Scenario 1:

1. I have two remote Windows machines with database on each. One is Win 2003 Server (machine A) and another one is Win XP (machine B)
2. I can ping from A to B.
3. I can ping from B to A.
4. I can tnsping from A to B.
5. I CAN'T tnsping from B to A.
6. Windows Firewall on both machines are off.

What could be possible reason for point# 5?

Scenario 2:

Now, the second part:

1. I had an unwanted entry in tnsnames.ora on B which I removed.
2. Then I restarted the listener on B. Actually, I wanted to restart the one on A to check if that resolves issue mentioned in point# 5 above.
3. I tried tnsping from A to B but suprisingly it is also giving "operation timed out" error now. So now tnsping not working from either sides.

I didn't make any changes in listener.ora on B, just stopped it and started again. Only change made was removing unwanted entry in tnsnames.ora on B.

Why does that affected database connectivity from A to B which was working fine previously?

If any extra information needed please let me know, and thanks in advance for your answers.

- Ramesh
  • 1. Re: "TNS-12535: TNS:operation timed out" error after listener restart
    sb92075 Guru
    Currently Being Moderated
    Regardless of what you state, the most common cause for Timeout is FireWall on or between client & DB
  • 2. Re: "TNS-12535: TNS:operation timed out" error after listener restart
    909525 Newbie
    Currently Being Moderated
    Thanks for the reply. The tnsping from A to B was working fine previously, only after restarting listener on B, it stopped working. As mentioned, there is no change in listener.ora, only change was removing unwanted entry from tnsnames.ora, and I don't think that could affect listener in any way. There is also no change in firewall on B, it is still off, nothing has changed on B, only change is restarting of listener. I can confirm that just before listener restart, database on A was able to connect to database on B.
  • 3. Re: "TNS-12535: TNS:operation timed out" error after listener restart
    sb92075 Guru
    Currently Being Moderated
    Ramesh Samane wrote:
    Thanks for the reply. The tnsping from A to B was working fine previously, only after restarting listener on B, it stopped working. As mentioned, there is no change in listener.ora, only change was removing unwanted entry from tnsnames.ora, and I don't think that could affect listener in any way. There is also no change in firewall on B, it is still off, nothing has changed on B, only change is restarting of listener. I can confirm that just before listener restart, database on A was able to connect to database on B.
    what clues exist in Listener Log file?

    If you are serious about diagnosing & correcting this issue, then you need to packet sniff;
    using WireShark, Ethereal, etc to see where packet go & go missing.
  • 4. Re: "TNS-12535: TNS:operation timed out" error after listener restart
    jgarry Guru
    Currently Being Moderated
    How are you resolving the hostnames? This sounds like a DNS problem, where restarting the listener somehow enabled a name resolution configuration problem that was just waiting for a restart.

    I've seen this happen where some intermediate machine gets rebooted, and it picks up a wrong login profile, which gets the wrong ip's, and so on. When all else fails, blame the netadmin ;)
  • 5. Re: "TNS-12535: TNS:operation timed out" error after listener restart
    TSharma-Oracle Guru
    Currently Being Moderated
    What version of oracle is installed on the servers? Is there only one Oracle home installed or multiple homes?

    Edited by: TSharma on Jan 11, 2013 10:57 AM
  • 6. Re: "TNS-12535: TNS:operation timed out" error after listener restart
    909525 Newbie
    Currently Being Moderated
    Thanks everyone for great replies, I think the discussion is heading towards right direction, and I hope to resolve this issue with your help.

    @ sb92075
    listener log has one warning "subscription for node down event still pending", but I guess that has nothing to do in this case. This message was recorded even when everything was working fine. Apart from this there is no other clue.

    @ jgarry
    These machines are connected using LogMeIn Hamachi VPN. I am referring the machines by their names and not by IP addresses in all the Oracle network configuration files (listener.ora/tnsnames.ora). LogMeIn assigns it's own IPs to machines and uses network connections created by it. I believe the two machines were not rebooted for at least a month, and they are up all the time. LogMeIn servers however were down for maintenance few days ago (before I restarted listener). As mentioned, I can ping the machines from each other. Unfortunately, I can't blame netadmin because there is none and I am only resposible for handling these issues though I am myself not a network expert :(

    @TSharma
    Both machines are installed with 11gR2 (11.2.0). No other Oracle server installed, and both have only one Oracle home.
  • 7. Re: "TNS-12535: TNS:operation timed out" error after listener restart
    TSharma-Oracle Guru
    Currently Being Moderated
    It could be the DNS issue. Try connecting with IP address. This will eliminate the DNS issue.
  • 8. Re: "TNS-12535: TNS:operation timed out" error after listener restart
    909525 Newbie
    Currently Being Moderated
    Tried with IP address (changed hostname to IP both in tnsnames.ora and listener.ora), but no luck. I can still ping machines from each other using hostnames as well as IP addresses.
  • 9. Re: "TNS-12535: TNS:operation timed out" error after listener restart
    909525 Newbie
    Currently Being Moderated
    One observation:

    Listener status when restarted shows:

    Service "ORCL" has 1 instance(s)
    Instance "ORCL", status UNKNOWN...

    After few seconds, status shows:

    Service "ORCL" has 2 instance(s)
    Instance "ORCL", status UNKNOWN...
    Instance "orcl", status READY...

    ORCL is my local database. Does this something to do with this issue?
  • 10. Re: "TNS-12535: TNS:operation timed out" error after listener restart
    sb92075 Guru
    Currently Being Moderated
    Ramesh Samane wrote:
    One observation:

    Listener status when restarted shows:

    Service "ORCL" has 1 instance(s)
    Instance "ORCL", status UNKNOWN...

    After few seconds, status shows:

    Service "ORCL" has 2 instance(s)
    Instance "ORCL", status UNKNOWN...
    Instance "orcl", status READY...

    ORCL is my local database. Does this something to do with this issue?
    NO! it is just that the DB registered itself with the listener; which is does once every 60 seconds
  • 11. Re: "TNS-12535: TNS:operation timed out" error after listener restart
    TSharma-Oracle Guru
    Currently Being Moderated
    What are the names of the databases on both machines? Also post your listener files content... I think we are close to resolve the issue.

    Edited by: TSharma on Jan 11, 2013 1:22 PM
  • 12. Re: "TNS-12535: TNS:operation timed out" error after listener restart
    909525 Newbie
    Currently Being Moderated
    DB names on both machines: ORCL

    listener.ora on B (Win XP) - This was working before listener restart, I mean, I was able to connect to DB on B from A.

    --------------------
    # listener.ora Network Configuration File: C:\app\Test\product\11.2.0\dbhome_1\NETWORK\ADMIN\listener.ora
    # Generated by Oracle configuration tools.

    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = CLRExtProc)
    (ORACLE_HOME = C:\app\Test\product\11.2.0\dbhome_1)
    (PROGRAM = extproc)
    (ENVS = "EXTPROC_DLLS=ONLY:C:\app\Test\product\11.2.0\dbhome_1\bin\oraclr11.dll")
    )
    (SID_DESC =
    (GLOBAL_DBNAME = ORCL)
    (ORACLE_HOME = c:\app\Test\product\11.2.0\dbhome_1)
    (SID_NAME = ORCL)
    )
    )

    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
    )
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = testpc)(PORT = 1521))
    )
    )

    ADR_BASE_LISTENER = C:\app\Test
    --------------------

    listener.ora on A (Win 2003 Server) - Never able to connect to DB on this machine from A.

    --------------------
    # listener.ora Network Configuration File: D:\app\Administrator\product\11.2.0\dbhome_1\NETWORK\ADMIN\listener.ora
    # Generated by Oracle configuration tools.

    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = CLRExtProc)
    (ORACLE_HOME = D:\app\Administrator\product\11.2.0\dbhome_1)
    (PROGRAM = extproc)
    (ENVS = "EXTPROC_DLLS=ONLY:D:\app\Administrator\product\11.2.0\dbhome_1\bin\oraclr11.dll")
    )
    (SID_DESC =
    (GLOBAL_DBNAME = ORCL)
    (ORACLE_HOME = D:\app\Administrator\product\11.2.0\dbhome_1)
    (SID_NAME = ORCL)
    )
    )

    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
    )
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = NRDBSVR.delldomain1.netreachasia.com)(PORT = 1521))
    )
    )

    ADR_BASE_LISTENER = D:\app\Administrator
    --------------------

    NOTE:
    Machine A = NRDBSVR.delldomain1.netreachasia.com (Win 2003 Server)
    Machine B = testpc (Win XP)
  • 13. Re: "TNS-12535: TNS:operation timed out" error after listener restart
    909525 Newbie
    Currently Being Moderated
    @sb92075 : Thanks for this info.
  • 14. Re: "TNS-12535: TNS:operation timed out" error after listener restart
    jgarry Guru
    Currently Being Moderated
    Ramesh Samane wrote:
    One observation:

    Listener status when restarted shows:

    Service "ORCL" has 1 instance(s)
    Instance "ORCL", status UNKNOWN...

    After few seconds, status shows:

    Service "ORCL" has 2 instance(s)
    Instance "ORCL", status UNKNOWN...
    Instance "orcl", status READY...

    ORCL is my local database. Does this something to do with this issue?
    What's this lower case orcl? Be sure the ORACLE_SID case is the same everywhere.
1 2 Previous Next

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points