Содержание

Installation, Configuration, and Diagnostic Logs
D Troubleshooting the Oracle Database Client Installation
D.1 Verifying Requirements
D.2 What to Do if an Installation Error Occurs?
D.3 Reviewing the Log of an Installation Session
D.4 Silent-Mode Response File Error Handling
D.5 Troubleshooting Configuration Assistants
D.5.1 Configuration Assistant Failure
D.5.2 Irrecoverable Errors
D.6 Troubleshooting Inventory Issues
D.7 Cleaning Up After a Failed Installation
Windows oracle client log
TRACE_FILE_CLIENT
TRACE_UNIQUE_ CLIENT
TRACE_DIRECTORY_ CLIENT
LOG_FILE_CLIENT
LOG_DIRECTORY_ CLIENT
Server Trace and Log Parameter Descriptions
TRACE_LEVEL_SERVER
TRACE_FILE_SERVER
TRACE_DIRECTORY_ SERVER
LOG_FILE_SERVER
LOG_DIRECTORY_ SERVER
TNSPING Utility Trace Parameter Descriptions
TNSPING.TRACE_ LEVEL
TNSPING.TRACE_ DIRECTORY
Listener Trace and Log Parameter Descriptions
TRACE_LEVEL_ LISTENER
TRACE_FILE_LISTENER
TRACE_DIRECTORY_ LISTENER
LOG_FILE_LISTENER
LOG_DIRECTORY_ LISTENER
Connection Manager and Pump Trace and Log Parameter Descriptions
TRACE_LEVEL_ CMANAGER
TRACE_FILE_ CMANAGER
TRACE_DIRECTORY_ CMANAGER
LOG_FILE_CMANAGER
LOG_DIRECTORY_ CMANAGER
LOGGING_ CMANAGER
LOG_INTERVAL_ CMANAGER
Navigator Trace and Log Parameter Descriptions
TRACE_LEVEL_ NAVIGATOR
TRACE_FILE_ NAVIGATOR
TRACE_DIRECTORY_ NAVIGATOR
LOG_FILE_NAVIGATOR
LOG_DIRECTORY_ NAVIGATOR
LOGGING_ NAVIGATOR
LOG_LEVEL_ NAVIGATOR
Names Server Trace and Log Parameter Descriptions
NAMES.TRACE_ LEVEL
NAMES.TRACE_FILE
NAMES.TRACE_ DIRECTORY
NAMES.TRACE_ UNIQUE
NAMES.LOG_FILE
NAMES.LOG_ DIRECTORY
NAMESCTL Utility Trace Parameter Descriptions
NAMESCTL.TRACE_ LEVEL
NAMESCTL.TRACE_ FILE
NAMESCTL.TRACE_ DIRECTORY
NAMESCTL.TRACE_ UNIQUE

Installation, Configuration, and Diagnostic Logs

EPM System Installer, EPM System Configurator, and EPM System Diagnostics use the ODL logging format. See ODL Configuration.

Table 11. EPM System Installation, Configuration, and Diagnostics Log Files

common-install.log —Common Component files activity; for example, ODBC

common-ocm-install.log —Oracle Configuration Manager activity

common-ohs-install.log —Activity of Oracle HTTP Server

common-ohs-oui-out.log —Oracle Universal Installer information about Oracle HTTP Server installation, if Oracle HTTP Server is installed

Common-opmn-install.log —Oracle Process Manager and Notification Server installation messages

common-opmn-patchset-oui-out —OPMN installation patchset trace log messages

common-oracle-common-install —General log messages for appdev ( oracle_common ) installation

common-oracle-common-oui-out —OUI log messages for appdev ( oracle_common ) installation

common-product-install.log —Product common component files activity; for example, SDKs, CRS utility

common-staticcontent-install.log –—Static content files; for example, Help, for each product on the web server machine

common-wl-install.log —Embedded WebLogic installation activity

dotNetInstall.log —Messages for 32-bit .Net installation

dotNet35Install.log —.NET 3.5 installation messages

dotNetInstall64.log —64-bit .NET installation messages

dotNetRegister.log —Messages for 32-bit .NET registration

dotNetRegister64.log —Messages for 64-bit .NET registration

eas-install —Administration Services installation messages

EPM_EASConsoleInstallLog —Administration Services Console Windows client installer messages

EPM_SVCInstallLog —Smart View Windows installer messages

epma-register-profilereaderdll-stderr.log —Error log for registering HFMProfielReader.dll

epma-register-profilereaderdll-stdout.log —Trace log for registering HFMProfileReader.dll

epma-register-zlibdll-stderr.log —Error log for registering ZLib.dll

epma-register-zlibdll-stdout.log —Trace log for registering ZLib.dll

hfm-cacls-filetransfer-stderr.log —Error log for setting cacls on the file-transfer folder

hfm-cacls-filetransfer-stdout.log —Trace log for setting cacls on the file-transfer folder

hfm-cacls-lcmservice-stderr.log —Error log for setting cacls for lcm service folder

hfm-cacls-lcmservice-stdout.log —Trace log for setting cacls for lcm service folder

hfm-registerclientdlls64 —Errors for each 64-bit client DLL registration

hfm-registerclientdlls.log —Errors for each 32-bit client DLL registration

hfm-registercommondlls.log —Trace log for each client DLL registration

hfm-registerdlladmclient-stderr.log —Error log for each ADM client DLL registration

hfm-registerdlladmclient-stdout.log —Trace log for each ADM client DLL registration

hfm-registerdllclient-stderr.log —Error log for each client DLL registration

hfm-registerdllclient-stdout.log —Trace log for each client DLL registration

hfm-registerdllcommon-stderr.log —Error log for each common DLL registration

hfm-registerdllcommon-stdout.log —Trace log for each common DLL registration

hfm-registerserverdlls.log —Error log for each server DLL registration

hfm-regWinHttpErr.log —Error log for registering winhttp.dll

hfm-regWinHttpOut.log —Trace log for registering winhttp.dll

hfmsvcs-regAsyncCallback-stderr.log —Error log for registering AsyncCallback.dll

hfmsvcs-regAsyncCallback-stdout.log —Trace log for registering AsyncCallback.dll

hfm-updatereg-stderr.log —Error log for creating Financial Management Windows registry entries

hfm-updatereg-stdout.log —Trace log for creating Financial Management Windows registry entries

install-ocm-configCCR-output —Part 1 of Oracle Configuration Manager setup processing messages

install-ocm-output.log —Oracle Configuration Manager file information

install-ocm-configCCR-output —Part 2of Oracle Configuration Manager setup processing messages

installTool-install- DDD-MM.DD.YYYY-TIME .log —Main log written by EPM System Installer to log user activity

installTool-install-stderr.log —Errors filtered from console output

installTool-install-stdout.log —Console output

PRODUCT —install.log —Information about whether a product assembly installation fails. Each assembly has a log file. For example, hss-install.log for Shared Services.

installTool-summary- DDD-MM.DD.YYYY-TIME .log —Results of checks that EPM System Installer performs

irclient-fontreg-stderr.log —Error log for registering font files

irclient-fontreg-stdout.log —Trace log for registering font files

ismpEngine-install-stderr —Internal log file for InstallShield messages

wl_install_err.log —WebLogic install-time log, errors

wl_install_out.log —WebLogic install-time log, complete log

Product

Default Log Location

Log File Name and Contents

EPM System Installer

EPM_ORACLE_HOME /diagnostics/logs/install

EPM System Configurator

EPM_ORACLE_INSTANCE /diagnostics/logs/config

cmconfig.log —Trace information generated during Reporting and Analysis configuration from Reporting and Analysis (CMC) APIs called

configtool.log —Configuration task output and warning messages

configtool-http-ant.log —Trace from ant code executed during web server setup

ConfigTool-stdout.log —Console output

Configtool-appdeployment.log —Trace of deployment steps

configtool_summary.log —Summary status about pass/fail tasks

EssbaseExternalizationTask.log —Trace information for the Essbase externalization process executed during Essbase custom configuration

listener.log —Application listener messages generated on startup for each Java web application; one file for all applications

SharedServices_CMSClient.log —Shared Services CMS client trace, generated during configuration when CMS calls are made

ocm-config.log —Oracle Configuration Manager configuration log

registry.log —Trace of Shared Services Registry calls made during configuration

SharedServices_Security.log —Shared Services Registry registration log

EPM System Diagnostics also creates a validation tool report, instance_report_20110305_121855.html , in EPM_ORACLE_INSTANCE /diagnostics/reports .

EPM_ORACLE_INSTANCE /diagnostics/logs/validation

validation.log —Summary-level information for each check performed, indicating success or failure

A file name validation- n .log indicates that the log has rolled over because of size limits.

validationTool-stdout.log —Detail-level information for each validation check performed

validationTool-stderr.log —Error information generated during diagnostic utility execution

velocity.log —Diagnostic utility trace generated by Velocity component calls

Windows—WebLogic Server: EPM_ORACLE_INSTANCE /diagnostics/logs/services

UNIX—WebLogic Server: EPM_ORACLE_INSTANCE /diagnostics/logs/starter

A starter component .log file for each product component started by start.bat (Windows) or start.sh (UNIX)

A UNIX starter log contains the full start sequence trace.

A Windows starter log contains whatever the product components write to stdout .

D Troubleshooting the Oracle Database Client Installation

This appendix contains the following information about troubleshooting:

D.1 Verifying Requirements

Before you try any of the troubleshooting steps in this appendix, do the following:

Check that the system meets the requirements and that you have completed all of the preinstallation tasks specified in Chapter 2, «Oracle Database Client Preinstallation Requirements.»

Read the release notes for the product on your platform before installing it.You can find the latest version of the release notes on the Oracle Technology Network Web site:

D.2 What to Do if an Installation Error Occurs?

If you encounter an error during installation:

Do not exit Oracle Universal Installer.

If you clicked Next after you entered incorrect information about one of the installation windows, click Back to return to the window and correct the information.

If you encounter an error while Oracle Universal Installer is copying or linking files, then see «Reviewing the Log of an Installation Session» for interactive installations or «Silent-Mode Response File Error Handling» for silent or response file mode installations.

If you encounter an error while configuration assistant is running, then see Section D.5, «Troubleshooting Configuration Assistants.»

If you cannot resolve the problem, then remove the failed installation by following the steps listed in Section D.7, «Cleaning Up After a Failed Installation.»

D.3 Reviewing the Log of an Installation Session

When you run Oracle Universal Installer on a computer with no Oracle software installed, it creates a directory called:

During this first installation and all subsequent installations, Oracle Universal Installer saves all of the actions that it performs in a log file in this directory. If you encounter problems during the installation, review the log file for information about possible causes of the problem.

Log filenames for interactive installations take the form:

For example, if an interactive installation occurred at 9:00:56 A.M. on February 14, 2005, the log file would be named:

Do not delete or manually alter the Inventory directory or its contents. Doing so can prevent Oracle Universal Installer from locating products that you install on your system.

D.4 Silent-Mode Response File Error Handling

To determine whether a silent or response file mode installation succeeds or fails, check the silentInstallActions date_time .log file, located in the DRIVE_LETTER :\Program Files\Oracle\Inventory\logs directory.

A silent installation fails if:

You do not specify a response file.

You specify an incorrect or incomplete response file.

Oracle Universal Installer encounters an error, such as insufficient disk space.

Oracle Universal Installer or a configuration assistant validates the response file at run time. If the validation fails, the installation or configuration process ends.

«Reviewing the Log of an Installation Session» for information about interactive installation log files

D.5 Troubleshooting Configuration Assistants

To troubleshoot an installation error that occurs when a configuration assistant is running:

Review the specific configuration assistant log file located in the ORACLE_HOME \cfgtoollogs directory. Try to fix the issue that caused the error.

If you see the Fatal Error. Reinstall message, look for the cause of the problem by reviewing the log files. Refer to «Irrecoverable Errors» for further instructions.

D.5.1 Configuration Assistant Failure

Oracle configuration assistant failures are noted at the bottom of the installation window. The configuration assistant interface displays additional information, if available. The configuration assistant execution status is stored in the installActions date_time .log file.

The execution status codes are listed in the following table:

Status	Result Code
Configuration assistant succeeded	0
Configuration assistant failed	1
Configuration assistant canceled	-1

D.5.2 Irrecoverable Errors

If you receive an irrecoverable error while a configuration assistant is running:

Correct the cause of the irreoverable error.

Reinstall the Oracle software.

D.6 Troubleshooting Inventory Issues

If you face any of the following situations for Oracle home, then run the opatch lsinventory -detail command to list the contents of the inventory and see section «Recovering from inventory corruption» in the Oracle Universal Installer and OPatch User’s Guide for information about fixing the issue.

Oracle home is cloned without completing the inventory steps.

There is bad inventory.

Inventory is not available but it is created when the Oracle Enterprise Manager Agent is installed in a separate Oracle home.

D.7 Cleaning Up After a Failed Installation

If an installation fails, you must remove files that Oracle Universal Installer created during the attempted installation and remove the Oracle home directory. Follow the instructions in Chapter 5, «Removing Oracle Database Client Software» to run the Deinstallation tool.

Windows oracle client log

USER = End-user level: Trace to provide additional information to identify user-induced error conditions such as:

addressing errors

server installation errors

runtime show-stopper errors (for example, protocol stack not loaded)

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:

site configuration-specific failures (for example, lookup files)

protocol-specific errors

configuration inconsistencies

server installation errors

errors in interaction with third-party software

TRACE_FILE_CLIENT

Note: Unless a new value for the TRACE_FILE_CLIENT parameter is specified or the old trace file is renamed, or the TRACE_UNIQUE_CLIENT parameter (described next) is set to ON, the new trace output file replaces the old trace output file.

Configuration file: SQLNET.ORA
Default value: SQLNET
OK to change? yes
Ranges of values: valid filename

This example generates a trace file called CLIENTA.TRC

Note: On most operating systems, TNS appends the .TRC suffix to the trace filename, so there is no need to specify it in the configuration file.

TRACE_UNIQUE_ CLIENT

Configuration file: SQLNET.ORA
Default value: OFF
OK to change? yes
Ranges of values: ON|OFF or TRUE|FALSE

The format of the appended process identifier is platform specific and is described in the Oracle operating system-specific manual for your platform. For example, on a UNIX machine the format would be similar to the following:

Note: Trace files are usually very large. If this parameter is set to ON (or TRUE), the number of large trace files could interfere with machine performance. Therefore use it carefully.

TRACE_DIRECTORY_ CLIENT

Configuration file: SQLNET.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? yes
Ranges of values: valid directory

Example: See your Oracle platform-specific documentation.

LOG_FILE_CLIENT

Configuration file: SQLNET.ORA
Default value: SQLNET
OK to change? yes
Ranges of values: valid filename

This example generates a log file called CLIENT.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.

LOG_DIRECTORY_ CLIENT

Configuration file: SQLNET.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? yes
Ranges of values: valid directory

Example: See your Oracle platform-specific
documentation.

Server Trace and Log Parameter Descriptions

TRACE_LEVEL_SERVER

Configuration file: SQLNET.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:

addressing errors

server installation errors

runtime show-stopper errors (for example, protocol stack not loaded)

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:

site configuration-specific failures (for example, lookup files)

protocol-specific errors

configuration inconsistencies

server installation errors

errors in interaction with third-party software

TRACE_FILE_SERVER

Configuration file: SQLNET.ORA
Default value: SQLNET
OK to change? yes
Ranges of values valid filename

On a UNIX machine, this example might generate a trace file called SERVERA_5798.TRC.

Note: On most operating systems, TNS appends the .TRC suffix to the trace filename, so there is no need to specify it in the configuration file.

TRACE_DIRECTORY_ SERVER

Configuration file: SQLNET.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.

LOG_FILE_SERVER

Configuration file: SQLNET.ORA
Default value: SQLNET
OK to change? yes
Ranges of values: valid filename

This example generates a log file called SERVER.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.

LOG_DIRECTORY_ SERVER

Configuration file: SQLNET.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.

TNSPING Utility Trace Parameter Descriptions

TNSPING.TRACE_ LEVEL

Configuration file: SQLNET.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:

addressing errors

server installation errors

runtime show-stopper errors (for example, protocol stack not loaded)

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:

site configuration-specific failures
(for example, lookup files)

protocol-specific errors

configuration inconsistencies

server installation errors

errors in interaction with third-party software

TNSPING.TRACE_ DIRECTORY

Configuration file: SQLNET.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? yes
Range of values: valid directory

Listener Trace and Log Parameter Descriptions

TRACE_LEVEL_ LISTENER

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:

addressing errors

listener installation errors

runtime show-stopper errors (for example, protocol stack not loaded)

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:

site configuration-specific failures (for example, lookup files)

protocol-specific errors

configuration inconsistencies

listener installation errors

errors in interaction with third-party software

TRACE_FILE_LISTENER

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

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.

TRACE_DIRECTORY_ LISTENER

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.

LOG_FILE_LISTENER

Configuration file: LISTENER.ORA
Default value: LISTENER
OK to change? yes
Ranges of values: valid filename

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.

LOG_DIRECTORY_ LISTENER

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.

Connection Manager and Pump Trace and Log Parameter Descriptions

TRACE_LEVEL_ CMANAGER

Configuration file: INTCHG.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 = User level: The tracing at this level is limited.

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:

site configuration-specific failures (lookup files, and so on)

protocol-specific errors

configuration inconsistencies

Interchange installation errors

errors in interaction with third-party software

This parameter controls the trace output filename for a TNS client application. By default, the filename on most operating systems is SQLNET.TRC. A new trace output file is generated for each trace session. On most operating systems, each trace file automatically appends the process identifier of the current process to the filename so that previous files are not overwritten. The format of the appended process identifier is platform specific and is described in the Oracle operating system-specific manual for your platform.

TRACE_FILE_ CMANAGER

Configuration file: INTCHG.ORA
Default value: CMG
OK to change? yes
Range of values string

On a UNIX machine, this example might generate a trace file called CMANAGER_4321.TRC, and a pump trace file called PMP_3198.TRC.

Note: On most operating systems, the .TRC suffix is appended to the trace filename automatically, so there is no need to specify it in the configuration file.

Note: All pump trace properties are determined by the corresponding Connection Manager parameters, although a separate trace file is created for a pump. The default name for a pump trace file, PMP_pid.TRC, cannot be changed.

TRACE_DIRECTORY_ CMANAGER

Configuration file: INTCHG.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.

LOG_FILE_CMANAGER

Note: On most operating systems, the .LOG suffix is appended to the log filename automatically, so there is no need to specify it in the configuration file.

Configuration file: INTCHG.ORA
Default value: INTCHG
OK to change? yes
Range of values: string

This example generates a log file called CMANAGER.LOG.

Note: Pump statistics are included in the log file for the Connection Manager.

LOG_DIRECTORY_ CMANAGER

Configuration file: INTCHG.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? Not configurable using Network Manager
Range of values: valid directory

Example: See your Oracle platform-specific
documentation.

LOGGING_ CMANAGER

Configuration file: INTCHG.ORA
Default value: OFF
OK to change? Use Logging Level field in Network
Manager.
Ranges of values: [OFF | ON]

LOG_INTERVAL_ CMANAGER

Note: Setting the log interval to a low value adversely affects Interchange performance, and the log file may become quite large.

Configuration file: INTCHG.ORA
Default value: 60 minutes
OK to change? yes
Ranges of values: 1-99

Navigator Trace and Log Parameter Descriptions

TRACE_LEVEL_ NAVIGATOR

The Interchange is not intended to be traced by anyone other than an administrator; so the ADMIN level is recommended for Interchange modules.

Configuration file: INTCHG.ORA
Default value: OFF
OK to change? yes
Ranges of values: [OFF | USER | ADMIN]

OFF = No user-specified tracing. This value can be used to disable trace.

USER = User level: The tracing at this level is limited.

ADMIN = Administrator level: Trace to identify installation-specific problems, for substantiation of «finger pointing» in case of third-party stacks, and for following situations:

site configuration-specific failures (for example, lookup files)

protocol-specific errors

configuration inconsistencies

Navigator installation errors

errors in interaction with third-party software

Navigator queries and answers

TRACE_FILE_ NAVIGATOR

Configuration file: INTCHG.ORA
Default value: NAV
OK to change? yes
Ranges of values: string

On a UNIX machine, this example might generate a trace file called NAVTEST_5234.TRC.

Note: On most operating systems, the .TRC suffix is appended to the trace filename automatically, so there is no need to specify it in the configuration file.

TRACE_DIRECTORY_ NAVIGATOR

Configuration file: INTCHG.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.

LOG_FILE_NAVIGATOR

Configuration file: INTCHG.ORA
Default value: NAVGATR
OK to change? yes
Range of values: string

This example generates a log file called NAVIGATOR.LOG

Note: On most operating systems, the .LOG suffix is appended to the log filename automatically, so there is no need to specify it in the configuration file.

LOG_DIRECTORY_ NAVIGATOR

Configuration file: INTCHG.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? Not configurable using Network Manager
Range of values: valid directory Example: See your Oracle platform-specific
documentation.

LOGGING_ NAVIGATOR

Configuration file: INTCHG.ORA
Default value: OFF
OK to change? Use Logging Level field in Network
Manager.
Range of values: [OFF|ON]

LOG_LEVEL_ NAVIGATOR

Configuration file: INTCHG.ORA
Default value: ERRORS
OK to change? yes
Range of values: [ERRORS|ALL]

Names Server Trace and Log Parameter Descriptions

NAMES.TRACE_ LEVEL

Configuration file: NAMES.ORA
Default value: OFF
OK to change? yes
Ranges 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:

addressing errors

server installation errors

runtime show-stopper errors (for example, protocol stack not loaded)

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:

site configuration-specific failures (for example, lookup files)

protocol-specific errors

configuration inconsistencies

server installation errors

errors in interaction with third-party software

NAMES.TRACE_FILE

Configuration file: NAMES.ORA
Default value: names
OK to change? yes
Ranges of values valid filename

On a UNIX machine, this example might generate a trace file called NAMES_5798.TRC.

Note: On most operating systems, TNS appends the .TRC suffix to the trace filename, so there is no need to specify it in the configuration file.

NAMES.TRACE_ DIRECTORY

Note: You must set NAMES.TRACE_DIRECTORY in NAMES.ORA, then restart the Names Server. You cannot set this from NAMESCTL.

Configuration file: NAMES.ORA
Default value: names
OK to change? yes
Range of values: valid directory

Examples: See your Oracle platform-specific
documentation.

NAMES.TRACE_ UNIQUE

Note: Trace files are usually very large. If this parameter is set to ON (or TRUE), the number of large trace files could interfere with machine performance. Therefore use it carefully.

NAMES.LOG_FILE

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: NAMES.ORA
Default value: NAMES.LOG
OK to change? yes
Ranges of values: valid filename

This example generates a log file called NAMES_SERVER2.

NAMES.LOG_ DIRECTORY

Configuration file: NAMES.ORA
Default value: See your Oracle operating system
documentation.
OK to change? yes
Range of values: valid directory

Example: See your Oracle platform-specific
documentation.

NAMESCTL Utility Trace Parameter Descriptions

NAMESCTL.TRACE_ LEVEL

Configuration file: SQLNET.ORA
Default value: OFF
OK to change? yes
Ranges 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:

addressing errors

installation errors

runtime show-stopper errors (for example, protocol stack not loaded)

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:

site configuration-specific failures (for example, lookup files)

protocol-specific errors

configuration inconsistencies

installation errors

errors in interaction with third-party software

NAMESCTL.TRACE_ FILE

Configuration file: SQLNET.ORA
Default value: namesctl
OK to change? yes
Ranges of values valid filename

On a UNIX machine, this example might generate a trace file called NC_5684.TRC.

Note: On most operating systems, TNS appends the .TRC suffix to the trace filename, so there is no need to specify it in the configuration file.

NAMESCTL.TRACE_ DIRECTORY

Configuration file: SQLNET.ORA
Default value: none
OK to change? yes
Range of values: valid directory

Example: See your Oracle platform-specific
documentation.

NAMESCTL.TRACE_ UNIQUE

You must set the NAMESCTL_TRACE_UNIQUE parameter from the SQLNET.ORA configuration file. You cannot set it from NAMESCTL.

Note: Trace files are usually very large. If this parameter is set to ON (or TRUE), the number of large trace files could interfere with machine performance. Therefore use it carefully.