- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: lsnrctl command stops listener on another serv...
Operating System - HP-UX
1755758
Members
3476
Online
108838
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2003 05:50 AM
тАО01-07-2003 05:50 AM
lsnrctl appears to have the abiliby to issue commands to servers other then the one that the command is actually run on. How is this being facilitated? Is the fact that we have service guard running causing this? We have 2 HP-UX clusters running service guard, one is production and the second is a new cluster being setup for DR.
We want to avoid lsnrctl commands issued on the new DR cluster from being executed on the real production cluster until we implement the new cluster at our DR site.
Thanks!
We want to avoid lsnrctl commands issued on the new DR cluster from being executed on the real production cluster until we implement the new cluster at our DR site.
Thanks!
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2003 01:43 PM
тАО01-07-2003 01:43 PM
Solution
This happens because the listener.ora command is pointing to the second server. Your best options are to create a different listneer name for your DRP system, or set passwords on your listeners that are different for DRP and production. This will make the listener ask for the password before stopping, and should keep the production listener from being stopped by the DRP process.
Brian
Brian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2003 02:44 PM
тАО01-07-2003 02:44 PM
Re: lsnrctl command stops listener on another server
Thanks Brian, That looks like the problem, I made the wrong assumption that TNSNAMES was used, but it was the listener.ora file. A password on the listener is a great idea! Best Regards, Dave.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP