Select Save Network Configuration from the File menu to save the changes. The listener uses the dynamic service information about the database and instance before using statically configured information in the listener. Configuration of static service information is necessary if you require remote database startup from a tool other than Oracle Enterprise Manager, or you have Oracle Database releases earlier than Oracle8 i.
Table describes static service settings in the listener. Table Static Service Settings in listener. The Oracle system identifier SID of the instance. If the client connect descriptor uses the SID parameter, then the listener does not attempt to map the values.
This parameter is primarily intended for configurations with Oracle8 databases where dynamic service registration is not supported for dedicated servers.
This parameter may also be required for use with Oracle8 i and later database services by some configurations. The Oracle home location of the instance. Without this setting, the listener assumes its Oracle home for the instance. On Microsoft Windows, this setting is ignored.
Select Listeners from the Administer list, and then select the Oracle home that contains the configuration files. Click the Static Database Registration tab, and then click Add. The following example shows an excerpt of a listener. Chapter 13, "Enabling Advanced Features of Oracle Net Services" for additional information about statically configuring the listener for external procedures and Heterogeneous Services.
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 can also be used for remote administration. Local administration of the listener is secure by default through the local operating system.
Therefore configuring a password is neither required nor recommended for secure local administration. However, a password can be configured for the listener to provide security for administrative operations, such as starting or stopping the listener, viewing a list of supported services, or saving changes to the Listener Control configuration.
Select Listeners from the Administer list, and then select the Oracle home that contains the location of the configuration files. Oracle Database Security Guide for additional information about minimum requirements for passwords. 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.
The listener uses the dynamic service information about the database and instance received through service registration before using statically configured information in the listener. Dynamic service registration is configured in the database initialization file. It does not require any configuration in the listener. However, listener configuration must be set to listen on the ports named in the database initialization file, and must not have parameters set that prevent automatic registration, such as COST parameters.
To ensure service registration works properly, the initialization parameter file should contain the following parameters:. If the listener configuration is synchronized with the database configuration, then PMON can register service information with a nondefault local listener or a remote listener on another node.
Synchronization occurs when the protocol address of the listener is specified in the listener. If a comma appears in the string, then the entire string must be enclosed in double quotation marks. For example, if the listener address "ab,cd" is entered, then it resolves to one listener address. If the address is entered as ab,cd , then it resolves to two listener addresses, ab and cd. In Example , a database resides on host sales1-server. On the host where the local listener resides, configure the listener.
For example:. A remote listener is a listener residing on one computer that redirects connections to a database instance on another computer.
You can configure registration to remote listeners, such as with Oracle RAC, for dedicated or shared server environments. In a dedicated server environment, you must enable the PMON background process to register with a remote listener.
Answer: Remember, there is only one listener. When finding the listener. You looked for your listener. Traditionally, the listener.
Connections through port are not limited. In the preceding example, the connection rates are enforced at the endpoint level. A maximum of 5 connections are processed through port every second. The limit for connections through port is 10 every second. That is, the listener refuses to accept SET commands that alter its parameters.
To change any of the parameters in listener. To enable the server to spawn a thread or process when a connection to the database is requested through the listener. To enable users to connect to the database without having to specify a service name from the client side.
In Oracle Database 12 c , when a client tries to connect to the database the connection request passes through the listener. The listener may be servicing several different databases. If a service name is configured in this parameter, then users may not necessarily need to specify a service name in the connect syntax. For container databases, the client must explicitly specify the service name.
If this parameter is not configured and a user does not specify a fully-qualified service name in the connect syntax, then the connection attempt fails. This parameter only accepts one value. To specify the time, in seconds, for the client to complete its connect request to the listener after the network connection had been established.
If the listener does not receive the client request in the time specified, then it terminates the connection. In addition, the listener logs the 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.
To specify the maximum number of concurrent registration and client connection sessions that can be supported by Oracle Net Listener. This number includes registration connections from databases, and ongoing client connection establishment requests. After a connection is established, the clients do not maintain a connection to the listener. This limit only applies to client connections that are in the initial connection establishment phase from a listener perspective.
To specify the maximum number of concurrent registration connection sessions that can be supported by Oracle Net Listener. The presence of a host name in the list results in the inclusion of all IP addresses mapped to the host name. The host name should be consistent with the public network interface. To secure registration requests through dedicated secure registration endpoints for SCAN listeners.
The registration endpoint is on a private network within the cluster. All remote registration requests coming in on normal listening endpoints are redirected to the registration endpoint. Any system which is not a part of the cluster cannot connect to the endpoint. This parameter is configured internally in the SCAN listener to restrict registrations to the private network. The value of this parameter should not be modified or specified explicitly. The only supported explicit setting is for turning this feature off by setting the value to OFF.
To specify whether runtime configuration changes are saved to the listener. 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.
As long as the listener configuration is synchronized with the database configuration, PMON can register service information with a nondefault local listener or a remote listener on another node. Synchronization is simply a matter of specifying the protocol address of the listener in the listener. You can then resolve listener1 in the local tnsnames. Registration to remote listeners, such as in the case of Oracle9 i Real Application Clusters, can be configured for shared server or dedicated server environments.
If you set the parameter to null with the statement that follows, then PMON de-registers information with the remote listener with which it had previously registered information. Oracle Net Manager does not enable you to configure a tnsnames.
Therefore, Oracle Corporation recommends that you manually modify the tnsnames. Multiple addresses are supported, but connect-time failover and client load balancing features are not supported. Chapter 15, "Enabling Advanced Features of Oracle Net Services" for further information about multiple address configuration.
An entry for the listener alias name can be made to an Oracle Names server through Oracle Net Manager:. Once the listener is configured, the listener can be administered with the Listener Control utility. This section describes some of the common administrative tasks for the listener, including the following topics:.
In addition to starting the listener, the Listener Control utility verifies connectivity to the listener. The STATUS command provides basic status information about a listener, including a summary of listener configuration settings, the listening protocol addresses, and a summary of services registered with the listener.
You can also obtain the status of a listener through the Oracle Enterprise Manager Console. Displays a summary of the services registered with the listener and the service handlers allocated to each service. Specifies the name of the instance associated with the service along with its status and number of service handlers associated with the service.
Identifies the name of the service handler. Dispatchers are named D through D Following this, additional information about the service handler displays, such as whether the service handler is a dispatcher, a local dedicated server, or a remote dedicated server on another node.
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. When you notice any of the following conditions, review and monitor the listener log file for the following:. Note: A version 9 listener is required for an Oracle9 i database.
0コメント