Listener authentication error
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5

Thread: Listener authentication error

Hybrid View

  1. #1
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865

    Listener authentication error

    Hi,

    I have some problem with my listener configuration. Here is the scenario.

    I have two nodes A & B in veritas cluster.

    DB1 is active on node A and passive on node B
    DB2 is active on node B and passive on node A

    DB1 listener is configured as LISTENER and DB2 listener is configured as LISTENER_XXX

    listener.ora and tnsnames.ora are having same entries on both the nodes.

    from node B, when i check " lsnrctl status " it is giving the following error.

    TNS-01189: The listener could not authenticate the user

    If i give " lsnrctl status LISTENER_XXX " then it is giving result. I believe this is expected.

    My issue is, when I am trying to connect to node B Database from RMAN it is saying " TNS-12541: TNS:no listener "

    I believe RMAN is sending the request to LISTENER not LISTENER_XXX. Is there any way to tell RMAN that the listener name is LISTENER_XXX?

    I have gone thru the metalink note 285439.1 but I already have IPC configured.

    Any help is highly appreciated.


    Thanks,
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

  2. #2
    Join Date
    Aug 2009
    Posts
    1
    if it is not connecting to listener_XXX then change the initialization parameter LOCAL_LISTENER TO listener_xxx and check it out.so it'll connect to listener_xxx by default

  3. #3
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865
    Hi Vasanth,

    LOCAL_LISTENER init parameter is already set to proper listener name i.e 'LISTENER_XXX'. Even after it is throwing error.

    Thanks,
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

  4. #4
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865
    FYI - this issue has been resolved after changing the HOST = to HOST = in RMAN catalog TNS entry . I am not pretty sure how it makes the difference because ping for hostname & ip is returning alive.

    Thanks,
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

  5. #5
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865
    FYI - this issue has been resolved after changing the HOST = hostname to HOST = ip in RMAN catalog TNS entry . I am not pretty sure how it makes the difference because ping for hostname & ip is returning alive.

    Thanks,
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

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