- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Oracle listener and process
Operating System - HP-UX
1753469
Members
4998
Online
108794
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
тАО09-11-2005 07:36 PM
тАО09-11-2005 07:36 PM
Re: Oracle listener and process
Hello Shiv,
To answer ur question.
In explicit sense status both are different.
These can be treated as two separate components.
If db is open , the status is said to be open for all operations. (internal user aka sys doesn't need to have listener available to connect and work).
If listener is available, all the users will be able to connect (only if the description from listener and tnsnames.ora incase of c/s techno.. else description provided should match incase of a java client) or the client shall receive the famous tns-12* errors. Which doesn't mean that db is unavailable (problem with configuration etc,.)
listener process => waits for incoming requests from users as specified in listener.ora file located under ${ORACLE_HOME}/network/admin
Listener process is a server side network file used in TNS configuration. On the client side we have java jndi or tnsnames.ora etc,. which contains the description.
If listener process is not running on the server side and client makes a request , then we get TNS- no listener error...
DB Processes: As detailed by other members, these are server side database processes.
That's my two cents and if u need more details.. feel free.
Regards,
Ram
To answer ur question.
In explicit sense status both are different.
These can be treated as two separate components.
If db is open , the status is said to be open for all operations. (internal user aka sys doesn't need to have listener available to connect and work).
If listener is available, all the users will be able to connect (only if the description from listener and tnsnames.ora incase of c/s techno.. else description provided should match incase of a java client) or the client shall receive the famous tns-12* errors. Which doesn't mean that db is unavailable (problem with configuration etc,.)
listener process => waits for incoming requests from users as specified in listener.ora file located under ${ORACLE_HOME}/network/admin
Listener process is a server side network file used in TNS configuration. On the client side we have java jndi or tnsnames.ora etc,. which contains the description.
If listener process is not running on the server side and client makes a request , then we get TNS- no listener error...
DB Processes: As detailed by other members, these are server side database processes.
That's my two cents and if u need more details.. feel free.
Regards,
Ram
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-11-2005 07:43 PM
тАО09-11-2005 07:43 PM
Re: Oracle listener and process
Hi Shiv,
Oracle database server designed as client server.
On Server Oracle Database instance will be running, is identified by SID.
Locally db user access the database by
setting env ORACLE_SID=
$ sqlplus dbuser/pass@
If db user wants to access the Database across the network, Listener role is important. Listener provides the network tcp service to access the database via Oracle client and tnsnames.ora configuration.
How to check the listener status.
As a oracle user run
$ /oracle/app/ora9i/bin/lsnrctl status
OR
$ /oracle/app/ora9i/bin/lsnrctl status []
How to verify the listner is responding for database access.
As a oracle user
$ tnsping
where sid_name is defined in tnsnames.ora file. DB user connect/access to Database using this sid_name across the network.
Regards,
Rajesh
Oracle database server designed as client server.
On Server Oracle Database instance will be running, is identified by SID.
Locally db user access the database by
setting env ORACLE_SID=
$ sqlplus dbuser/pass@
If db user wants to access the Database across the network, Listener role is important. Listener provides the network tcp service to access the database via Oracle client and tnsnames.ora configuration.
How to check the listener status.
As a oracle user run
$ /oracle/app/ora9i/bin/lsnrctl status
OR
$ /oracle/app/ora9i/bin/lsnrctl status [
How to verify the listner is responding for database access.
As a oracle user
$ tnsping
where sid_name is defined in tnsnames.ora file. DB user connect/access to Database using this sid_name across the network.
Regards,
Rajesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-11-2005 10:39 PM
тАО09-11-2005 10:39 PM
Re: Oracle listener and process
The Oracle TNS Listener is the server-based process that provides basic network connectivity for clients, application servers, and other databases to an Oracle database. In addition to databases, the Listener can also be configured to support binary executables.
The Listener can be configured in one of three modes (as configured in listener.ora):
├в Database :Provides network access to an Oracle database instance
- PLSExtProc : Method for PL/SQL packages to access operating system executables
- Executable: Provides network access to operating system executables.
The ├в Database├в mode is the most widely used mode and is the standard mode used by every database for connectivity. ├в PLSExtProc├в allows PL/SQL database packages to access external programs and is configured by default for many instances. ├в Executable├в mode allows an external program to be defined and accessed through a TNS connection.
The Listener can be configured in one of three modes (as configured in listener.ora):
├в Database :Provides network access to an Oracle database instance
- PLSExtProc : Method for PL/SQL packages to access operating system executables
- Executable: Provides network access to operating system executables.
The ├в Database├в mode is the most widely used mode and is the standard mode used by every database for connectivity. ├в PLSExtProc├в allows PL/SQL database packages to access external programs and is configured by default for many instances. ├в Executable├в mode allows an external program to be defined and accessed through a TNS connection.
Kamal Mirdad
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-12-2005 12:49 AM
тАО09-12-2005 12:49 AM
Re: Oracle listener and process
Just wanted to a note re: James' post:
If you want to search for each listener by name - then use James' posting:
ps -ef | grep LISTEN
but, you can name your listeners (LISTENER is the default name), so searching for all tnslisteners, I use:
ps -ef | grep tns
or for more exact (in case there is a conflict with another program which has the word "tns" in it - but I doubt it)
ps -ef | grep tnslsnr
If you want to search for each listener by name - then use James' posting:
ps -ef | grep LISTEN
but, you can name your listeners (LISTENER is the default name), so searching for all tnslisteners, I use:
ps -ef | grep tns
or for more exact (in case there is a conflict with another program which has the word "tns" in it - but I doubt it)
ps -ef | grep tnslsnr
We are the people our parents warned us about --Jimmy Buffett
- « Previous
-
- 1
- 2
- Next »
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