The following conditions are true:. A database configured for dedicated server connections resides on host sales1-server. It is the only database in the network. A local listener resides on sales1-server and listens on nondefault port A remote listener named resides on host sales2-server and listens on port Another remote listener resides on host sales3-server and listens on port The following procedure describes how to register information with all listeners in a dedicated server environment:.
On the hosts where the remote listeners reside in this example, sales2-server and sales3-server , configure the listener. Set the parameters in the initialization file for the database on host sales1-server as follows:. In the tnsnames. For example, a listener can be defined in the init. To use an alias for the listener, it can be defined in the init. To use listener name aliases, Oracle recommends you modify the tnsnames.
Multiple addresses are supported, but connect-time failover and client load balancing features are not supported. The following errors occur:. Oracle Net Configuration Assistant configures the listening protocol address and service information for Oracle Database. During a Custom installation, Oracle Net Configuration Assistant prompts for the listener name and protocol address.
A listening IPC protocol address for external procedure calls is automatically configured, regardless of the installation type. Oracle Net Configuration Assistant also automatically configures service information for the external procedures in the listener. If you are using the IPC protocol, then you can improve performance by specifying the maximum number of concurrent IPC connection requests to match your expected connection requests. If the default or installed configuration is not adequate for a particular environment, then you can use Oracle Net Manager to customize the listener.
This technique can create listening endpoints that service IPv6 clients. The following procedure describes how to configure protocol addresses for the listener using Oracle Enterprise Manager Cloud Control:. The following procedure describes how to configure protocol addresses for the listener using Oracle Net Manager:. In the navigator pane, expand Local , and then select Listeners.
If you want to set send and receive buffer sizes, then click Show Advanced , and then enter the sizes in the appropriate fields. Select Save Network Configuration from the File menu to save the changes. By default, Oracle Net Listener permits only local administration for security reasons. As a policy, the listener can be administered only by the user who started it.
This is enforced through local operating system authentication. For example, if user1 starts the listener, then only user1 can administer it. Any other user trying to administer the listener gets an error. The super user is the only exception.
Oracle recommends that you perform listener administration in the default mode secure by means of local operating system authentication , and access the system remotely using a remote login. Oracle Enterprise Manager Cloud Control can also be used for remote administration. Listener registration should be restricted to valid nodes and subnets. Valid nodes and subnets can be specified for registration, and excluded nodes can also be specified for registration. By default, every incoming connection for registration at the listener is subjected to IP-based filtering.
A connection is only allowed if it originates from the local machine. If the other nodes and subnets are specified for registration, then the local machine and the ones specified are allowed. Oracle9i Net Services Administrator's Guide for further information about password security of the listener.
If the listener does not receive the client request in the time specified, then it terminates the connection. In addition, the listener logs IP address of the client and an ORATNS: listener has not received client's request in time allowed error message to the listener.
When specifying values for these parameters, consider the following recommendations:. If clients are unable to complete connections within the specified time due to system or network delays that are normal for the particular environment, then increment the time as needed. Oracle9i Net Services Administrator's Guide for information about configuring these parameters. When you set the parameter to true , any parameters that were modified while the listener was running using the Listener Control utility SET command are saved to the listener.
When you set the parameter to false , the Listener Control utility does not save the runtime configuration changes to the listener. The database server authenticates the client. Therefore, this value should be set to false. If this parameter is set to true , the listener attempts to authenticate the client, which can result in a failure. Oracle Advanced Security Administrator's Guide. This parameter is deprecated in Oracle9 i and will be desupported in a future release.
If you require this parameter to run the listener, please notify Oracle Support Services. When the size is met, the trace information is written to the next file. To show information about the services and instances from the command line, enter:.
This output shows that two database services, sales. Client connection requests to sales. All handlers have a status of ready , indicating that they are ready to receive connections. Client connection requests to hr. The listener blocks all connections to this instance. Therefore, the status is non known. The name of the service handler. Dispatchers are named D through D When you notice any of the following conditions, review the listener log file for error information:.
Unexpected shutdown of the listener that could indicate a denial-of-service attack. This does not cause a loss of security because authentication is enforced through local operating system authentication. See Also: Chapter 2, "Identifying and Accessing the Database" for a description of how the listener is used during an initial connection request Chapter 4, "Understanding the Communication Layers" for an architectural overview of the listener. Overview of Oracle Net Listener Note: The release of the listener must be the same as or later than the latest release of all Oracle databases being serviced through the listener.
Note: When services are configured statically, a listener starts a dedicated server when it receives a client request. If the instance is not up, then the server returns an Oracle not available error message.
Example Example listener. See Also: Oracle Database Net Services Reference for additional information about identifying listeners by unique names and creating multiple listener entries in the listener. Customizing Oracle Net Listener Configuration If the default or installed configuration is not adequate for a particular environment, then you can use Oracle Net Manager to customize the listener.
The Listener page appears. Click Edit. The Edit Listener page appears. You may be prompted to log in to the database server. In the Addresses section, configure protocol support: Click Add. The Add Address page appears. From the Protocol list, select the protocol on which the listener is configured to listen. In Port, enter the port number.
In Host, enter the host address. Click OK. The protocol address is added to the Addresses section. Repeat Step 3 for additional protocols. To specify the listener queue size, do the following: Specify the QUEUESIZE parameter at the end of the protocol address with its value set to the expected number of concurrent requests. Configuring Static Service Information The listener uses the dynamic service information about the database and instance before using statically configured information in the listener.
Note: You can also configure static service information with Oracle Net Manager. See Also: "Configuring Service Registration" for additional information about configuring dynamic service registration Oracle Databases Chapter 13, "Enabling Advanced Features of Oracle Net Services" for additional information about statically configuring the listener for external procedures and Heterogeneous Services Oracle Enterprise Manager Advanced Configuration for additional information about Oracle Enterprise Manager.
Configuring and Changing the Oracle Net Listener Password Local administration of the listener is secure by default through the local operating system. If the unencrypted password is not removed, then you are unable to set an encrypted password. Configuring Service Registration Service registration allows processes, such as an Oracle database, to identify their available services to the listener, which then acts as a port mapper for those services.
Example Registering a Local Listener in a Dedicated Server Environment On the host where the local listener resides, configure the listener. Registering Information with a Remote Listener A remote listener is a listener residing on one computer that redirects connections to a database instance on another computer. Registering Information with All Listeners in a Network A network may contain multiple local and remote listeners.
Example Using Two Networks on a Subnet Assume there are two distinct networks, network1 and network2. Example Configuring Multiple Listeners Assume that multiple listeners are listening on a network named sales-network.
The following conditions are true: A database configured for dedicated server connections resides on host sales1-server. To register information with all listeners in a dedicated server environment, do the following: On the hosts where the remote listeners reside in this example, sales2-server and sales3-server , configure the listener. See your operating system-specific documentation for details about establishing auto-restart. Active 1 year, 7 months ago. Viewed 2k times. All rights reserved.
I just need to test an entity framework application on oracle. The command completed successfully Is tnsnames malformed? Your services not registered in listener,login as sysdba alter system register and check lsnrctl status — user Add a comment. Active Oldest Votes. I tried localhost and the listener started, however now I am getting the error 'ra, tns:listener does not currently know of service requested in connect descriptor' details added to the question.
0コメント