C.3 Control Parameters

Team-Fly    

 
Oracle Net8 Configuration and Troubleshooting
By Jonathan Gennick, Hugo Toledo
Table of Contents
Appendix C.  The listener.ora File


Control parameters allow you to specify various aspects of listener behavior. For example, you can control the directories and filenames used for log files and trace files. Most of these parameters are simple name /value pairs, and they are listed here in alphabetical order.

CONNECT_TIMEOUT_listener_name

 CONNECT_TIMEOUT_  listener_name  =  seconds  

Specifies the number of seconds that the listener waits once a connection request has been started. This wait usually involves the time needed to redirect the client's connection to a different port. If the redirect fails for some reason, the timeout causes the connect operation to terminate. The default value is 10 seconds. A value of 0 specifies an infinite timeout.

Example

 CONNECT_TIMEOUT_PRODLISTENER = 10 
LOG_DIRECTORY_listener_name

 LOG_DIRECTORY_  listener_name  =  directory_path  

Specifies the directory to which the listener's log file should be written. The default log directory is $ORACLE_HOME /network /log .

Examples

 LOG_DIRECTORY_PRODLISTENER = /s01/app/oracle/product/8.1.5/network/log LOG_DIRECTORY_PRODLISTENER = E:\Oracle\Ora81\NETWORK\LOG 
LOG_FILE_listener_name

 LOG_FILE_  listener_name  =  directory_path  

Specifies the name to use for the listener's log file. The default filename is listener.log .

Examples

 LOG_FILE_PRODLISTENER = PRODLISTENER.LOG LOG_FILE_DEVLISTENER = DEVLISTENER.LOG 
LOGGING_listener_name

 LOGGING_  listener_name  = {ON  OFF} 

Controls whether or not a listener even generates a log file. The default value is ON.

Examples

 LOGGING_PRODLISTENER = ON LOGGIN_DEVLISTENER = OFF 
PASSWORDS_listener_name

 PASSWORDS  _listener_name = (password [,password...])  

Specifies one or more passwords for a listener. The passwords are not encrypted. All passwords are equally usefulany one may be used to control the listener. See Chapter 4 for detailed information on password protecting a listener.

If you are specifying just one password, you can omit the parentheses.

Examples

 PASSWORDS_PRODLISTENER = (MYPASSWORD, YOURPASSWORD, THEIRPASSWORD) PASSWORDS_DEVLISTENER = ONLYONEPASSWORD 
SAVE_CONFIG_ON_STOP_listener_name

 SAVE_CONFIG_ON_STOP_  listener_name  = {TRUE  FALSE} 

Specifies whether or not a listener should save its current configuration back to the listener.ora file when you use the Listener Control utility's STOP command to stop the listener. The default value is FALSE. Use TRUE if you do want the configuration to be saved automatically.

Be aware that there are cases where SAVE_CONFIG_ON_STOP does not work. If the listener is killed from the operating-system prompt, or if you stop a Windows NT listener by shutting down its associated Windows NT service, the configuration is not saved. See Chapter 4 for more information on this feature.

Examples

 SAVE_CONFIG_ON_STOP_PRODLISTENER = TRUE SAVE_CONFIG_ON_STOP_DEVLISTENER = FALSE 
STARTUP_WAIT_TIME_listener_name

 STARTUP_WAIT_TIME_  listener_name  =  seconds  

Allows you to specify a delay, in seconds, between the time that a listener starts and the time at which it begins accepting connection requests . Normally, you should leave the delay at the default, which is seconds. However, you may find that when you boot your server, your listener starts before your database instances start. If, for some reason, that results in a problem, you can specify a delay long enough to cover the time needed for your database instances to start first.

Examples

 STARTUP_WAIT_TIME_PRODLISTENER = 30 STARTUP_WAIT_TIME_DEVLISTENER = 0 
TRACE_DIRECTORY_listener_name

 TRACE_DIRECTORY_  listener_name  =  directory_  path  

Specifies the directory to which any listener trace files should be written. The default trace directory is $ORACLE_HOME /network /trace .

Examples

 TRACE_DIRECTORY_PRODLISTENER = /s01/app/oracle/product/8.1.5/network/trace TRACE_DIRECTORY_PRODLISTENER = E:\Oracle\Ora81\NETWORK\TRACE 
TRACE_FILE_listener_name

 TRACE_FILE_  listener_name  =  directory_path  

Specifies the name to use for the listener's trace file. The default filename is listener.trc .

Examples

 TRACE_FILE_PRODLISTENER = PRODLISTENER.TRC TRACE_FILE_DEVLISTENER = DEVLISTENER.TRC 
TRACE_FILELEN_listener_name (new in Oracle8 i )

 TRACE_FILELEN_  listener_name  =  kilobytes  

Allows you to specify a maximum size, in kilobytes, for a listener trace file. The default is to place no limit on trace file size . If tracing is enabled, and the current trace file reaches the specified limit, the listener closes the current trace file and opens a new one. The filenames are numbered in sequence. The TRACE_FILENO parameter controls the maximum number of trace files that the listener is allowed to generate.

In order for TRACE_FILELEN to have any effect, you must set TRACE_FILENO to a value other than 1. If you don't, this parameter is ignored. The two parameters must be used together, or not at all.

Examples

 TRACE_FILELEN_PRODLISTENER = 1000 TRACE_FILENO_PRODLISTENER = 5 TRACE_FILELEN_DEVLISTENER = 10 TRACE_FILENO_PRODLISTENER = 50 
TRACE_FILENO_listener_name (new in Oracle8 i )

 TRACE_FILENO_  listener_name  =  number  

Specifies the maximum number of listener trace files to generate and use in a cyclical pattern. This parameter must be used in conjunction with the TRACE_FILELEN parameter. As each trace file reaches its size limit, a new file is opened. Sequence numbers are appended to the filenames in order to differentiate them. The TRACE_FILENO parameter specifies the maximum sequence number that may be used. When that file fills, the listener wraps around to the first trace file and reuses all the files in sequence.

Sequence numbers are only appended to trace files when the TRACE_FILENO and TRACE_FILELEN parameters are being used.

Examples

 TRACE_FILELEN_PRODLISTENER = 1000 TRACE_FILENO_PRODLISTENER = 5 TRACE_FILELEN_DEVLISTENER = 10 TRACE_FILENO_PRODLISTENER = 50 
TRACE_LEVEL_listener_name

 TRACE_LEVEL_  listener_name  = {  level_name   level_number  } 

Allows you to specify the listener trace level. The amount of information written to the trace file and the level of detail represented by that information are controlled by this parameter. The default value is OFF, which means that no trace information is generated.

You may specify trace levels by name or by number. The following names are valid (their corresponding numeric values are enclosed within parentheses):

OFF (0)

No trace output is generated.

USER (4)

User-level trace information is generated.

ADMIN (6)

Administrative-level trace information is generated.

SUPPORT (16)

Support-level trace information is generated.

When you use the SUPPORT trace level, your trace files get very large very quickly. SUPPORT is best used for a short period of time while you focus on a specific problem.

Examples

 TRACE_LEVEL_PRODLISTENER = ADMIN TRACE_LEVEL_DEVLISTENER = 16 
TRACE_TIMESTAMP_listener_name (new in Oracle8 i )

 TRACE_TIMESTAMP_  listener_name  = {{ON  TRUE}  {OFF  FALSE}} 

Allows you to specify that a timestamp (in the form dd-Month-yyyy hh:mi:ss) be added to each event logged in a listener's trace file. The default value is OFF, which means that no timestamp is generated. FALSE is the same as OFF. ON or TRUE cause timestamps to be written to the trace file.

USE_PLUG_AND_PLAY_listener_name

 USE_PLUG_AND_PLAY_  listener_name  = {ON  OFF} 

Specifies whether or not a listener should automatically register database information with available Oracle Names servers. The default value is OFF. Use ON if you want automatic registration to occur.

Examples

 USE_PLUG_AND_PLAY_PRODLISTENER = ON USE_PLUG_AND_PLAY_DEVLISTENER = OFF 

Team-Fly    
Top


Oracle Net8 Configuration and Troubleshooting
Oracle Net8 Configuration and Troubleshooting
ISBN: 1565927532
EAN: 2147483647
Year: 2000
Pages: 120

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net