Configuration file: LISTENER.ORA
Default value: OFF
OK to change? yes
Range of values: [OFF | USER | ADMIN]
OFF = No user-specified tracing. This value can be used to disable trace. | |
USER = End-user level: Trace to provide additional information to identify user-induced error conditions such as: | |
ADMIN = Administrator level: Trace to identify installation-specific problems, for substantiation of "finger pointing" in case of third-party stacks, and for the following situations: |
Note: On most operating systems, the .TRC suffix is automatically appended to the trace filename, so there is no need to specify it in the configuration file.
Configuration file: LISTENER.ORA
Default value: LISTENER
OK to change? yes
Range of values valid filename
Example:
TRACE_FILE_LISTENER = LSNRA
This example generates a trace file called LSNRA.TRC.
Note: If you use a name for the listener other than the default name for the listener (that is, LISTENER), the trace filename would be the name of the non-default listener; for example, LISNAGAIN.TRC.
Configuration file: LISTENER.ORA
Default value: See your Oracle platform-specific
documentation
OK to change? yes
Range of values: valid directory
Example: See your Oracle platform-specific
documentation.
Note: If you use a name for the listener other than the default name for the listener (that is, LISTENER), the trace filename would be the name of the non-default listener; for example, LISNAGAIN.TRC.
Configuration file: LISTENER.ORA
Default value: LISTENER
OK to change? yes
Ranges of values: valid filename
Example:
LOG_FILE_LISTENER = LSNR
This example generates a log file called LSNR.LOG
Note: On most operating systems, TNS appends the .LOG suffix to the log filename, so there is no need to specify it in the configuration file.
Configuration file: LISTENER.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? yes
Range of values: valid directory
Example: See your Oracle platform-specific
documentation.