本文共 34019 字,大约阅读时间需要 113 分钟。
This chapter provides a complete listing of the listener.ora
file configuration parameters.
This chapter contains these topics:
Oracle Net Listener configuration, stored in the listener.ora
file, consists of the following elements:
Name of the listener
Protocol addresses that the listener is accepting connection requests on
Database services
Dynamic , eliminates the need for static configuration of supported services. However, static service configuration is required if you plan to use Oracle Enterprise Manager.
Control parameters
By default, the listener.ora
file is located in the $ORACLE_HOME/network/admin
directory on UNIX operating systems and the %ORACLE_HOME%\network\admin
directory on Windows. listener.ora
can also be stored the following locations:
The directory specified by the TNS_ADMIN
environment variable or registry value
On UNIX operating systems, the global configuration directory. For example, on the Solaris Operating System, this directory is /var/opt/oracle
.
See Also:
Oracle operating system-specific documentationIt is possible to configure multiple listeners, each with unique name, in one listener.ora
file. Multiple listener configuration is possible because each of the top-level configuration parameters has a suffix of the listener name or is the listener name itself.
Note:
It is often useful to configure multiple listeners in onelistener.ora
file. However, Oracle recommends running only one listener for each node in most customer environments. shows a listener.ora
file for a listener named LISTENER
, which is the default name of the listener.
Example 7-1 Example listener.ora File
LISTENER= (DESCRIPTION= (ADDRESS_LIST= (ADDRESS=(PROTOCOL=tcp)(HOST=sale-server)(PORT=1521)) (ADDRESS=(PROTOCOL=ipc)(KEY=extproc))))SID_LIST_LISTENER= (SID_LIST= (SID_DESC= (GLOBAL_DBNAME=sales.us.example.com) (ORACLE_HOME=/oracle11g) (SID_NAME=sales)) (SID_DESC= (SID_NAME=plsextproc) (ORACLE_HOME=/oracle11g) (PROGRAM=extproc)))
This section lists and describes the listener.ora
file parameters. Listener configuration parameters fall into the following categories:
The section of the listener.ora
file defines the protocol addresses that the listener is accepting connection requests on. Discussed next are the most common parameters used in protocol addresses. Note that ADDRESS_LIST
is also supported.
See Also:
for information about theADDRESS_LIST
parameter This section lists and describes the following parameters:
Purpose
Use the ADDRESS
parameter to specify a single listener protocol address.
Embed this parameter under the DESCRIPTION
parameter.
See Also:
for descriptions of the correct parameters to use for each type of support protocolExample
listener_name= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=hr-server)(PORT=1521)) (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521)))
Purpose
Use the DESCRIPTION
parameter as a container for listener protocol addresses.
Example
listener_name= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=hr-server)(PORT=1521)) (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521)))
Purpose
If the user specifies a host name for the HOST
parameter in the ADDRESS line of the listener.ora
file, the listener listens on IN_ADDRANY
in case the host name is default host name. If the user wants the listener to listen on the first IP to which the specified host name resolves, the address must further be qualified with (IP=FIRST)
.
Default
This feature is disabled by default.
Example
listener_name= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=rancode1-vip)(PORT=1521)IP=FIRST))
Purpose
Use the QUEUESIZE
parameter to specify the number of concurrent connection requests that the listener can accept on a TCP/IP or IPC listening endpoint (protocol address).
Embed this parameter at the end of the protocol address with its value set to the expected number of concurrent connection requests.
Default
The default number of concurrent connection requests is operating system specific. Following are the defaults for the Solaris Operating System and Windows:
Solaris Operating System: 5
Windows NT 4.0 Workstation: 5
Windows NT 4.0 Server: 50
Usage Notes
See Also:
for information about configuring this parameterExample
listener_name= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=hr-server)(PORT=1521)(QUEUESIZE=20)))
Purpose
Use the RECV_BUF_SIZE
parameter to specify, in bytes, the buffer space for receive operations of sessions. This parameter is supported by the TCP/IP, TCP/IP with SSL, and SDP protocols.
Note:
Additional protocols might support this parameter on certain operating systems. Refer to operating-system specific documentation for information about additional protocols that support this parameter.Embed this parameter under the DESCRIPTION
parameter or at the end of the protocol address with its value set to the expected number of bytes.
Default
The default value for this parameter is operating-system specific. The default for the Solaris 2.6 Operating System is 32768 bytes (32 KB).
Usage Notes
See Also:
for information about configuring this parameterExample
listener_name= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521) (RECV_BUF_SIZE=11784)) (ADDRESS=(PROTOCOL=ipc)(KEY=extproc) (RECV_BUF_SIZE=11784)))listener_name= (DESCRIPTION= (RECV_BUF_SIZE=11784)) (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521) (ADDRESS=(PROTOCOL=ipc)(KEY=extproc)))
Purpose
Use the SEND_BUF_SIZE
parameter to specify, in bytes, the buffer space for send operations of sessions. This parameter is supported by the TCP/IP, TCP/IP with SSL, and SDP protocols.
Note:
Additional protocols might support this parameter on certain operating systems. Refer to operating-system specific documentation for information about additional protocols that support this parameter.Embed this parameter under the DESCRIPTION
parameter or at the end of the protocol address.
Default
The default value for this parameter is 8192 bytes (8 KB).
Usage Notes
See Also:
for information about configuring this parameterExample
listener_name= (DESCRIPTION= (ADDRESS_LIST= (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521) (SEND_BUF_SIZE=11280)) (ADDRESS=(PROTOCOL=ipc)(KEY=extproc) (SEND_BUF_SIZE=11280))))listener_name= (DESCRIPTION= (ADDRESS_LIST= (SEND_BUF_SIZE=11280)) (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521) (ADDRESS=(PROTOCOL=ipc)(KEY=extproc))))
You can use the SID_LIST
section of the listener.ora
to statically configure service information for the listener.
The SID_LIST
section is required for Oracle8 release 8.0 or Oracle7 database services, as well as calls and , and some management tools, including Oracle Enterprise Manager.
SID_LIST_listener_name= (SID_LIST= (SID_DESC= (GLOBAL_DBNAME=global_database_name) (SID_NAME=sid) (ORACLE_HOME=oracle_home)) (SID_DESC=...))
For later database releases, the listener uses the dynamic service information about the database and instance it has received through service registration before using statically configured information in the listener.ora
file. Therefore, the SID_LIST
is not required, unless Oracle Enterprise Manager is used to monitor an Oracle9i or Oracle8 database.
This section lists and describes the following parameters:
Purpose
Use the parameter ENVS
to specify environment variables for the listener to set prior to executing (as a child process) a dedicated server program or an executable specified with the parameter.
Embed this parameter under the SID_DESC
parameter.
Note:
This parameter in not supported on Windows. Any process started by the listener will simply inherit the listener's environment.Usage Notes
Enclose an environment variable and its value within double quotes ("
):
(ENVS="variable=value")
A list of environment variables and their values can be specified. Enclose the list within double quotes, from end to end, and separate environment variable definitions with commas and no space.
(ENVS="variable=value,variable=value")
Note:
Single quotes ('
) are supported for backward compatibility. The use of the following characters within the environment variable or its value definition (ENVS="
variable
=
value
")
are not supported:
Comma (,
)
Single quotes ('
)
Double quotes ("
)
Equal sign (=
)
Example
SID_LIST_listener_name= (SID_LIST= (SID_DESC= (SID_NAME=plsextproc) (ORACLE_HOME=/oracle11g) (PROGRAM=extproc) (ENVS="LD_LIBRARY_PATH=/oracle/11g/lib:/oracle/11g/ctx/lib")) (SID_DESC= (SID_NAME=test) (PROGRAM=/tmp/myexec) (ENVS="LD_LIBRARY_PATH=/private/xpm/lib:/private/mylibs,MYPATH=/usr/ucb:/usr/local/packages,APL_ENV_FILE=/apl/conf/env.txt")))
Purpose
Use the parameter GLOBAL_DBNAME
to identify the database service.
While processing a client connection request, the listener tries to match the value of this parameter with the value of the SERVICE_NAME
parameter in the client connect descriptor. 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 release 8.0 or Oracle7 databases (where dynamic service registration is not supported for dedicated servers). This parameter may also be required for use with Oracle9i and Oracle8 database services by some configurations and management tools.
The value for this parameter is typically obtained from the combination of the DB_NAME
and DB_DOMAIN
parameters (DB_NAME
.DB_DOMAIN
) in the initialization parameter file, but the value can also contain any valid name used by clients to identify the service.
Embed this parameter under the SID_DESC
parameter.
Example
SID_LIST_listener_name= (SID_LIST= (SID_DESC= (GLOBAL_DBNAME=sales.us.example.com) (SID_NAME=sales) (ORACLE_HOME=/usr/oracle)))
Purpose
Use the parameter ORACLE_HOME
to identify the Oracle home location of the service.
Embed this parameter under the SID_DESC
parameter.
Example
SID_LIST_listener_name= (SID_LIST= (SID_DESC= (SID_NAME=extproc) (ORACLE_HOME=/usr/oracle) (PROGRAM=extproc)))
Purpose
Use the parameter PROGRAM
to identify the service executable program name.
Embed this parameter under the SID_DESC
parameter.
Example
SID_LIST_listener_name= (SID_LIST= (SID_DESC= (SID_NAME=sales) (ORACLE_HOME=/usr/oracle) (PROGRAM=extproc)))
Purpose
Use the parameter SID_DESC
to specify service information for a specific database instance or a non-database service.
Embed this parameter under the SID_LIST
parameter.
Example
SID_LIST_listener_name= (SID_LIST= (SID_DESC=...) (SID_DESC=...))
SID_DESC
permits the following parameters:
Purpose
Use the parameter SID_LIST
to identify a list of SID descriptions.
Example
SID_LIST_listener_name= (SID_LIST= (SID_DESC=...) (SID_DESC=...))
Purpose
Use the parameter SID_NAME
to identify the of the instance. You can obtain the SID value from the INSTANCE_NAME
parameter in the initialization parameter file.
Embed this parameter under the SID_DESC
parameter.
Example
SID_LIST_listener_name= (SID_LIST= (SID_DESC= (GLOBAL_DBNAME=sales.us.example.com) (SID_NAME=sales) (ORACLE_HOME=/usr/oracle)))
Purpose
Use the parameter SDU
to instruct Oracle Net to optimize the transfer rate of data packets being sent across the network with the size you specify.
Embed this parameter under the SID_DESC
parameter.
Usage
See Also:
for information about configuring this parameterDefault
8192 bytes (8KB)
Values
512 bytes to 32767
Example
SID_LIST_listener_name= (SID_LIST= (SID_DESC= (SDU=8192) (GLOBAL_DBNAME=sales.us.example.com) (SID_NAME=sales) (ORACLE_HOME=/usr/oracle)))
The connection rate limiter feature in the Oracle Net Listener enables a to specify limits to the number of new connections handled by the listener. When this feature is enabled, the Oracle Net Listener imposes a user-specified maximum limit on the number of new connections handled by the listener every second.
Depending on the configuration, the rate can be applied to a collection of endpoints, or to a specific endpoint.
This feature is controlled through the following two listener.ora
configuration parameters:
Purpose
The CONNECTION_RATE_
listener name
parameter specifies a global rate that is enforced across all listening endpoints that are rate-limited. When this parameter is specified, it overrides any endpoint-level numeric rate values that might be specified.
Syntax
CONNECTION_RATE_listener_name=number_of_connections_per_second
Purpose
The RATE_LIMIT
parameter indicates that a particular listening endpoint is rate limited. The parameter is specified in the ADDRESS
section of the listener endpoint configuration.
Syntax
LISTENER= (ADDRESS_LIST= (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521)(RATE_LIMIT=yes)) )
There are two possible configurations:
When the RATE_LIMIT
parameter is set to yes
, the end-point is included in the enforcement of a listener-wide connection rate. This is used in conjunction with the CONNECTION_RATE_
listener_name
parameter.
When the RATE_LIMIT
parameter is set to a value greater than 0
, the rate limit is enforced at that endpoint level.
Examples
The following two scenarios are examples using the CONNECTION_RATE_
listener name
and RATE_LIMIT
parameters.
Scenario 1
CONNECTION_RATE_LISTENER1=10LISTENER= (ADDRESS_LIST= (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521)(RATE_LIMIT=yes)) (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1522)(RATE_LIMIT=yes)) (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1523)) )
In this configuration, the total number of new connections through ports 1521 and 1522 is capped at 10 every second. Connections through port 1523 are not limited and do not count towards the overall rate of 10 connections every second.
Scenario 2
LISTENER= (ADDRESS_LIST= (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521)(RATE_LIMIT=5)) (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1522)(RATE_LIMIT=10)) (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1523)) )
In this configuration, the connection rates are enforced at the endpoint level. A maximum of 5 connections are processed through port 1521 every second.
The limit for connections through port 1522 is 10 every second. Connections through port 1523 are not rate-limited.
Note:
The globalCONNECTON_RATE_
listener_name
parameter is not specified in this configuration. If it is specified, the limits on ports 1521 and 1522 are ignored, and the global value is used, instead. This section describes the following parameters that control the behavior of the listener:
Purpose
Use the ADMIN_RESTRICTIONS_
listener_name
parameter to restrict run-time administration of the listener.
Setting ADMIN_RESTRICTIONS_
listener_name
=on
disables the run-time modification of parameters in listener.ora
. That is, the listener will refuse to accept commands that alter its parameters. To change any of the parameters in listener.ora
, including ADMIN_RESTRICTIONS_
listener_name
itself, modify the listener.ora
file manually and reload its parameters (with the command) for the new changes to take effect without explicitly stopping and restarting the listener.
See Also:
for further information about password security of the listenerDefault
off
Example
ADMIN_RESTRICTIONS_listener=on
Purpose
By default, the Oracle Net listener notifies Cluster Ready Service (CRS) when it is started or stopped. These notifications allow CRS to manage the listener in an Oracle Real Application Clusters environment. This behavior can be prevented by setting the CRS_NOTIFICATION_
listener_name
parameter to off
.
Default
The default value is on
.
Values
on | off
Purpose
Use the DEFAULT_SERVICE_
listener_name
parameter to enable users to connect to the database without having to specify a service name from client side.
In Oracle Database 11g, 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, users may not necessarily need to specify a service name in the connect syntax. If a user specifies a service name, the listener will connect the user to that specific database, otherwise the listener will connect to the service name specified by the DEFAULT_SERVICE_
listener_name
parameter.
See Also:
for more information about the easy connect naming methodDefault
There is no default value for the DEFAULT_SERVICE_
listener_name
parameter. If this parameter is not configured and a user does not specify a fully qualified service name in the connect syntax, the connection attempt fails. This parameter only accepts one value.
Example
DEFAULT_SERVICE_LISTENER=sales.us.example.com
Purpose
Use the INBOUND_CONNECT_TIMEOUT_
listener_name
parameter 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 ORA-12525:TNS: listener has not received client's request in time allowed
error message to the listener.log
file.
To protect both the listener and the database server, Oracle recommends setting this parameter in combination with the parameter in the sqlnet.ora
file. When specifying values for these parameters, consider the following recommendations:
Set both parameters to an initial low value.
Set the value of the INBOUND_CONNECT_TIMEOUT_
listener_name
parameter to a lower value than the SQLNET.INBOUND_CONNECT_TIMEOUT
parameter.
For example, you can set INBOUND_CONNECT_TIMEOUT_
listener_name
to 2 seconds and INBOUND_CONNECT_TIMEOUT
parameter to 3 seconds. 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.
See Also:
Oracle Database Net Services Administrator's Guide for information about configuring these parametersDefault
60 seconds
Example
INBOUND_CONNECT_TIMEOUT_listener=2
Purpose
Use the PASSWORDS_
listener_name
parameter to store an encrypted password for a listener, so that certain privileges operations, such as and , used from the Listener Control utility are secure. An encrypted password can be set using either the Listener Control utility command or Oracle Net Manager.
See Also:
for further information about password security of the listenerExample
PASSWORDS_LISTENER=(2D6C48144CF753AC)
Purpose
Use the SAVE_CONFIG_ON_STOP_
listener_name
parameter to specify whether or not run-time configuration changes are saved into the listener.ora
file.
When you set the parameter to true
, any parameters that were modified while the listener was running using the Listener Control utility command are saved to the listener.ora
file when the command is issued. When you set the parameter to false
, the Listener Control utility does not save the run-time configuration changes to the listener.ora
file.
Default
false
Values
true | false
Example
SAVE_CONFIG_ON_STOP_listener=true
Purpose
Use the SSL_CLIENT_AUTHENTICATION
parameter to specify whether or not a client is authenticated using the .
Default
true
Values
true | false
Usage Notes
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.
See Also:
Example
SSL_CLIENT_AUTHENTICATION=true
Note:
This parameter is deprecated and will be desupported in a future release. If you require this parameter to run the listener, please notify Oracle Support Services.Purpose
Use the STARTUP_WAIT_TIME_
listener_name
parameter to set the number of seconds that the listener waits before responding to a Listener Control utility command.
Default
0
Example
STARTUP_WAIT_TIME_listener=5
Purpose
By default, the listener subscribes to the Oracle Notification Service (ONS) node down event on startup, if ONS is available. This subscription enables the listener to remove the affected service when it receives node down event notification from ONS. The listener uses asynchronous subscription for the event notification. Alter this behavior setting SUBSCRIBE_NODE_DOWN_EVENT_
listener_name
=off
in listener.ora
.
Default
on
Values
on | off
Purpose
Use the WALLET_LOCATION
parameter to specify the location of wallets. Wallets are certificates, keys, and trustpoints processed by SSL that allow for secure connections.
See Also:
Syntax
Oracle wallets on file system:
WALLET_LOCATION= (SOURCE= (METHOD=file) (METHOD_DATA= (DIRECTORY=directory) [(PKCS11=TRUE/FALSE)]))
Microsoft certificate store:
WALLET_LOCATION= (SOURCE= (METHOD=mcs))
Oracle wallets in the Windows registry:
WALLET_LOCATION= (SOURCE= (METHOD=reg) (METHOD_DATA= (KEY=registry_key)))
Entrust wallets:
WALLET_LOCATION= (SOURCE= (METHOD=entr) (METHOD_DATA= (PROFILE=file.epf) (INIFILE=file.ini)))
Subparameters
WALLET_LOCATION
supports the following subparameters:
SOURCE
: Specify the type of storage for wallets and storage location.
METHOD
: Specify the type of storage.
METHOD_DATA
: Specify the storage location.
DIRECTORY
: Specify the location of Oracle wallets on file system.
KEY
: Specify the wallet type and location in the Windows registry.
PROFILE
: Specify the Entrust profile file (.epf
).
INIFILE
: Specify the Entrust initialization file (.ini
).
Default
None
Usage Notes
The key/value pair for Microsoft's certificate store (MCS) omits the METHOD_DATA
parameter because MCS does not use wallets. Instead, Oracle PKI (public key infrastructure) applications obtain certificates, trustpoints and private keys directly from the user's profile.
If an Oracle wallet is stored in the Windows registry and the wallet's key
(KEY)
is SALESAPP
, the storage location of the encrypted wallet is HKEY_CURRENT_USER\SOFTWARE\ORACLE\WALLETS\SALESAPP\EWALLET.P12
. The storage location of the decrypted wallet is HKEY_CURRENT_USER\SOFTWARE\ORACLE\WALLETS\SALESAPP\CWALLET.SSO.
Examples
Oracle wallets on file system:
WALLET_LOCATION= (SOURCE= (METHOD=file) (METHOD_DATA= (DIRECTORY=/etc/oracle/wallets/databases)))
Microsoft certificate store:
WALLET_LOCATION= (SOURCE= (METHOD=mcs))
Oracle Wallets in the Windows registry:
WALLET_LOCATION= (SOURCE= (METHOD=REG) (METHOD_DATA= (KEY=SALESAPP)))
Entrust Wallets:
WALLET_LOCATION= (SOURCE= (METHOD=entr) (METHOD_DATA= (PROFILE=/etc/oracle/wallets/test.epf) (INIFILE=/etc/oracle/wallets/test.ini)))
This section is divided into those parameters used when is enabled (when DIAG_ADR_ENABLED_
listener_name
is set to on
) and those used when ADR is disabled (when DIAG_ADR_ENABLED_
listener_name
is set to off
). Non-ADR parameters listed in the listener.ora
file are ignored when ADR is enabled.
This section lists the parameters used when ADR is enabled (when DIAG_ADR_ENABLED_
listener_name
is set to on
):
ADR_BASE_listener_name
Purpose
Use the ADR_BASE_
listener_name
parameter to specify the base directory into which tracing and logging incidents are stored when ADR is enabled.
Default
The default is $ORACLE_BASE
, or $ORACLE_HOME/log
if $ORACLE_BASE
is not defined.
Values
Any valid directory path to a directory with write permission.
Example
ADR_BASE=/oracle/network/trace
DIAG_ADR_ENABLED_listener_name
Purpose
The DIAG_ADR_ENABLED_
listener_name
parameter indicates whether ADR tracing is enabled.
Usage
When the DIAG_ADR_ENABLED_
listener_name
parameter is set to OFF
, non-ADR file tracing is used.
Default
on
Values
on
or off
Example
DIAG_ADR_ENABLED=on
LOGGING_listener_name
Purpose
Use the LOGGING_
listener_name
parameter to turn logging on or off. This parameter is also applicable when non-ADR tracing is used.
Default
on
Values
on | off
Example
LOGGING_listener=on
TRACE_LEVEL_listener_name
Purpose
Use the TRACE_LEVEL_
listener_name
parameter to turn listener tracing on, at a specific level, or off. This parameter is also applicable when non-ADR tracing is used.
Default
off
or 0
Values
off
or 0
for no trace output
user
or 4
for user trace information
admin
or 10
for administration trace information
support
or 16
for Oracle Support Services trace information
Example
TRACE_LEVEL_listener=admin
TRACE_TIMESTAMP_listener_name
Purpose
When the parameter is set to a specific tracing level, you can use the TRACE_TIMESTAMP_
listener_name
parameter to add a time stamp in the form of dd-mon-yyyy hh:mi:ss:mil
to every trace event in the trace file for the listener. This parameter is also applicable when non-ADR tracing is used.
Default
on
Values
on
or true
| off
or false
Example
TRACE_TIMESTAMP_listener=true
This section lists the parameters used when ADR is disabled (when DIAG_ADR_ENABLED
listener_name
is set to off
):
Notes:
The following parameters are used whether ADR is enabled or not:
The default value of is on
. Therefore, the DIAG_ADR_ENABLED_
listener_name
parameter must explicitly be set to off
in order for non-ADR tracing to be used.
LOG_DIRECTORY_listener_name
Purpose
Use the LOG_DIRECTORY_
listener_name
parameter to specify the destination directory of the listener log file. Use this parameter when ADR is not enabled.
Default
The $ORACLE_HOME/network/log
directory on UNIX operating systems and the %ORACLE_HOME%\network\log
directory on Windows operating systems.
Example
LOG_DIRECTORY_listener=/oracle/network/admin/log
LOG_FILE_listener_name
Purpose
Use the LOG_FILE_
listener_name
parameter to specify the name of the log file for the listener. Use this parameter when ADR is not enabled.
Default
listener.log
Example
LOG_FILE_listener=list.log
TRACE_DIRECTORY_listener_name
Purpose
Use the TRACE_DIRECTORY_
listener_name
parameter to specify the destination directory of the listener trace file. Use this parameter when ADR is not enabled.
Default
The $ORACLE_HOME/network/trace
directory on UNIX operating systems and the %ORACLE_HOME%\network\trace
directory on Windows
Example
TRACE_DIRECTORY_listener=/oracle/network/admin/trace
TRACE_FILE_listener_name
Purpose
Use the TRACE_FILE_
listener_name
parameter to specify the name of the trace file for the listener. Use this parameter when ADR is not enabled.
Default
listener.trc
Example
TRACE_FILE_listener=list.trc
TRACE_FILELEN_listener_name
Purpose
Use the TRACE_FILELEN_
listener_name
parameter to specify the size of the listener trace files in kilobytes (KB). When the size is met, the trace information is written to the next file. The number of files is specified using the parameter. Use this parameter when ADR is not enabled.
Default
Unlimited
Example
TRACE_FILELEN_listener=100
TRACE_FILENO_listener_name
Purpose
Use the TRACE_FILENO_
listener_name
parameter to specify the number of trace files for listener tracing. When this parameter is set along with the parameter, trace files are used in a cyclical fashion. The first file is filled first, then the second file, and so on. When the last file has been filled, the first file is re-used, and so on.
The trace file names are distinguished from one another by their sequence number. For example, if the default trace file of listener.trc
is used, and this parameter is set to 3, the trace files would be named listener1.trc
, listener2.trc
and listener3.trc
.
In addition, trace events in the trace files are preceded by the sequence number of the file. Use this parameter when ADR is not enabled.
Default
1
Example
TRACE_FILENO_listener=3
The class of secure transports (COST) parameters specify a list of transports that are considered secure for administration and registration of a particular listener. Configuring these parameters is optional. The COST parameters are:
See Also:
for more information about COST parameters and listener securityPurpose
Use the SECURE_CONTROL_
listener_name
parameter to specify the transports on which control commands are to be serviced.
Syntax
SECURE_CONTROL_listener_name = [(]transport1[,transport2, ....,transportn)]
In the preceding example, transport1
, transport2
, and transport
n
are valid, installed transport protocol names.
Configuration
If the SECURE_CONTROL_
listener_name
parameter is configured with the list of transport names, the control commands will be serviced only if the connection is one of the transports listed. The connections arriving by other transport protocols are refused. For example:
SECURE_CONTROL_listener1 = (TCPS, IPC)
In the preceding example, administration requests are accepted only on TCPS and IPC transports.
If no values are entered for this parameter, the listener accepts any connection on any endpoint.
Example 7-2 SECURE_CONTROL_listener_name Parameter Configuration
LISTENER1= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521)) (ADDRESS=(PROTOCOL=ipc)(KEY=extproc)) (ADDRESS=(PROTOCOL=tcps)(HOST=sales-server)(PORT=1522)) ) SECURE_CONTROL_LISTENER1=tcps
In , control commands are accepted only on the TCPS transport.
Purpose
Use the SECURE_REGISTER_
listener_name
parameter to specify the transports on which registration requests are to be accepted.
Syntax
SECURE_REGISTER_listener_name = [(]transport1[,transport2, ....,transportn)]
In the preceding example, transport1
, transport2
, and transport
n
are valid, installed transport protocol names.
Configuration
If the SECURE_REGISTER_
listener_name
parameter is configured with the list of transport names, only the connections arriving on the specified transports will be able to register the service with the listener. The connections arriving by other transport protocols are refused. For example:
SECURE_REGISTER_listener1 = (TCPS, IPC)
In the preceding example, registration requests are accepted only on TCPS and IPC transports.
If no values are entered for this parameter, the listener accepts registration requests from any transport.
If this parameter and are configured, they override the parameter.
Example 7-3 SECURE_REGISTER_listener_name Parameter Configuration
LISTENER1= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521)) (ADDRESS=(PROTOCOL=ipc)(KEY=extproc)) (ADDRESS=(PROTOCOL=tcps)(HOST=sales-server)(PORT=1522)) ) SECURE_REGISTER_LISTENER1=tcps
In , service registrations are accepted only on the TCPS transport.
Purpose
Use the SECURE_PROTOCOL_
listener_name
parameter to specify the transports on which administration and registration requests are to be accepted.
Syntax
SECURE_PROTOCOL_listener_name = [(]transport1[,transport2, ....,transportn)]
In the preceding example, transport1
, transport2
, and transport
n
are valid, installed transport protocol names.
Configuration
If this parameter is configured with the list of transport names, the control commands and service registration can happen only if the connection belongs to the list of transports configured.
If this parameter is not present and neither nor are configured, all supported transports accept control and registration requests.
If the and parameters are configured, they override the SECURE_PROTOCOL_
listener_name
parameter.
Example 7-4 SECURE_PROTOCOL_listener_name Parameter Configuration
LISTENER1= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521)) (ADDRESS=(PROTOCOL=ipc)(KEY=extproc)) (ADDRESS=(PROTOCOL=tcps)(HOST=sales-server)(PORT=1522)) ) SECURE_PROTOCOL_LISTENER1=tcps
In , both service registrations and control commands are accepted only on the TCPS transport.
Purpose
Use the DYNAMIC_REGISTRATION_
listener_name
parameter to enable or disable dynamic registration. When set to on
, the listener accepts dynamic registration; when set to off
, the listener refuses dynamic registration. Static registrations are not affected.
Syntax
DYNAMIC_REGISTRATION_listener_name={on|off}
Default
The default value is on
. Unless this parameter is explicitly set to off
, all registration connections are accepted.
COST parameters can also be used in combination to further control which transports accept service registration and control commands.
Example 7-5 Combining COST Parameters
LISTENER1= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521)) (ADDRESS=(PROTOCOL=ipc)(KEY=extproc)) (ADDRESS=(PROTOCOL=tcps)(HOST=sales-server)(PORT=1522)) ) SECURE_CONTROL_LISTENER1=(tcps,ipc) SECURE_REGISTER_LISTENER1=ipc
In , control commands are accepted only on the IPC channel and the TCPS transport, and service registrations are accepted only on an IPC channel.
is another example of combining COST parameters.
Example 7-6 Combining COST Parameters
LISTENER1= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521)) (ADDRESS=(PROTOCOL=ipc)(KEY=extproc)) (ADDRESS=(PROTOCOL=tcps)(HOST=sales-server)(PORT=1522)) ) SECURE_CONTROL_LISTENER1=tcps SECURE_PROTOCOL_LISTENER1=ipc
In , control commands are accepted only on the TCPS transport and service registrations are accepted only on the IPC channel.
转载地址:http://usybx.baihongyu.com/