Oracle Network Products Troubleshooting Guide

Graphical Mode for UNIX

You can reach all the features of the Client Status Monitor through the main window.

Main Window

In graphical mode, the main window of the Client Status Monitor looks like that shown in Figure 4 - 1. From this window you can select the information or operations you wish.

Figure 4 - 1. Client Status Monitor - Main Window

Most of the windows display information about your system and are read-only.

Getting Help

Select the Help menu to get help at any time. From this menu you can choose to display the man page for the Client Status Monitor, or you can bring up the Help page. The Help page can stay open on your screen while you are using the Client Status Monitor, and it includes hypertext links that make it easy to find information about the various functions of the tool.

Client Status Monitor Menu Bar

The following sections describe the choices in the Client Status Monitor Menu Bar.

File Menu

There are two choices in this menu.

Print Report -- You can choose to print a page to fax to Oracle Customer Support that will assist the support analysts in helping you solve your connectivity problems. The Fax Report includes several categories of information about your system. You can see the information displayed by selecting the other menu items in the Status Monitor Window.

Note: Before printing the Fax Report to send to Oracle Customer Support, be sure that the Support Information has been entered.

Quit -- You can choose to close the Client Status Monitor by choosing Quit.

Support Info Menu

From this menu, you can display an editable window called CSI Editor (Customer Support Information Editor). Use this window to provide identifying information to give to Oracle Customer Support. An example is shown in Figure 4 - 2. In most cases, the system administrator who installs SQL*Net on the client machine will have provided this information. If no information appears in this window, your system administrator should be able to provide it.

Figure 4 - 2. Identifying Information for Oracle Customer Support

Enter the following information in the appropriate fields.

From Name of person at your location who is the liaison with Oracle Customer Support
Phone Phone number of the person at your location who is the liaison with Oracle Customer Support
Fax Number Fax number of the person at your location who is the liaison with Oracle Customer Support
Customer Support ID Identifying number that authorizes you to get help from Oracle Customer Support
Subject Optional field in which to explain the problem
Comment Optional field for additional information

To save the information in this window, select OK.

To print the Fax Report, which includes the information in this window as well as all the client information from the Client Status Monitor, select Print Report.

To cancel your entries on this window, select Cancel.

Environment Menu

This menu enables you to display information about your environment. All the windows you can select are read-only and cannot be edited.

Installed Products

Figure 4 - 3

Figure 4 - 3. Installed Products Window

SQL*Net Configuration Files

Figure 4 - 4

Figure 4 - 4. SQL*Net Configuration Files

Select one of the files and select View to display it. In this window, select the Print button to print the file to your default printer. Select OK to close the window.

UNIX Variables

Figure 4 - 5

Figure 4 - 5. Environmental Variables

Tools Menu

From this menu you can choose to resolve a service name and test a connection from the client to a server, and you can edit either the user-level or the system-level SQLNET.ORA file. The values for the parameters in the user SQLNET.ORA file override the values in the system SQLNET.ORA file. Note that you may not have write permission for the system-level SQLNET.ORA file.

Test Connection

Select this choice to display a window in which you can resolve a service name to its network address, and from which you can attempt a connection to that service. An example is shown in Figure 4 - 6.

Figure 4 - 6. Resolve Service Name

To use this window, enter the service name of the database you wish to reach, and select the Resolve button. The names resolution method appears in the Source field, and the address appears in the Resolved To field.

Note: The names resolution method should match the first method shown in the names resolution path field in the Name Resolution Services window.

You can see if a connection is possible to this service by running the TNSPING utility. To do so, select the Connect button. A connection will be attempted.

If you have selected a TNSPING trace level, the connection attempt will be traced. You can view the trace file by selecting the View button.

Note: You cannot turn on tracing and set the TNSPING trace level on this screen. Use the SQLNET.ORA Editor to set the trace level.

If you are missing required files, a message telling you so appears at the bottom of the window. An example of this is shown in Figure 4 - 6.

SQLNET.ORA Editor

From the Tools menu you can open the SQLNET.ORA Editor, from which you can edit many of the optional parameters in the SQLNET.ORA file. You can edit the user or the system file. Parameters in the user SQLNET.ORA file override those in the system SQLNET.ORA file.

The SQLNET.ORA files contain parameters that affect the behavior of the client. If created by Oracle Network Manager, the SQLNET.ORA file has values that are the same for all clients of a particular client profile, or client type. Once the SQLNET.ORA files are distributed to individual clients, however, they can be modified to reflect individual needs. The SQLNET.ORA Editor provides a convenient way to do this.

Note: Not all parameters in SQLNET.ORA can be modified using this editor. Specifically, not all parameters related to Authentication in Secure Network Services are available to this tool in this release. Also, you cannot use this tool to set preferred Names Servers.

The main SQLNET.ORA Editor window looks like that shown in Figure 4 - 7.

Figure 4 - 7. SQLNET.ORA Editor

Each of the buttons in the SQLNET.ORA Editor window brings up a window in which you can edit a number of parameters.

Attention: Be careful when using this tool. Many client parameters work in conjunction with server parameters which you cannot see with this tool. Do not change any parameters unless you are sure of the result.

There are three buttons at the bottom of each of the SQLNET.ORA Editor windows.

Select OK to save your changes into the SQLNET.ORA file.

Select CANCEL to lose your changes and leave the window.

Select HELP to get online information about the parameters in the window.

General

Select General to display a window in which you can edit a variety of optional parameters for the client.

Client LOG File Name You can change the existing name for the log file in this field. In most operating systems, the log filename is automatically appended with the suffix .LOG. You do not need to enter that suffix in the field.
Client LOG Directory You can change the existing directory to which the client log file is written in this field. Be sure that you have write permission to the directory you select.
Client Registration Enter an identifier for the client machine. This identifier will be passed to the listener with any connection request and included in the Audit Trail. The identifier can be any alphanumeric string up to 128 characters. A typical identifier might be a department name.
Default Domain The default domain is the domain to which most client connection requests are directed. In a hierarchical name space, the default domain should be the domain in which the most frequently contacted servers reside.

You can toggle the following features ON and OFF by selecting the buttons next to their names.

Automatic IPC Select this button if you want the client to try an IPC (internal) connection before trying other protocols. The default is for Automatic IPC to be ON.
Use Dedicated Server Select this button if you want to make a connection to a dedicated server rather than to use a multi-threaded server.
DISABLE Out of Band Breaks (OOB) Select this button if you want to disable out-of-band breaks.

For further information about these optional parameters, refer to the appropriate sections in Understanding SQL*Net.

Tracing

Select Tracing to display a window in which you can modify the parameters that affect tracing on the client. This window is shown in Figure 4 - 8.

Figure 4 - 8. Tracing Parameters

Client Trace Level Select a trace level from the scrolling list. Unless you are troubleshooting a particular problem, the trace level should be OFF. Other choices are USER, for a moderately detailed trace report, and ADMIN, for more extensive trace information.
Note: After troubleshooting your connection problem, turn trace level back to OFF. Leaving the trace facility on can impact performance.
Client Trace File Name Change the existing name for the trace file in this field. In most operating systems, the trace filename is automatically appended with the suffix .TRC. You do not need to enter that suffix in the field.
Client Trace Directory Change the existing directory to which the client trace file is written in this field. Be sure that you have write permission to the directory you select.
TNSPING Trace Level Trace the behavior of the TNSPING utility by selecting a trace level from the scrolling list. Unless you are troubleshooting a particular problem, the trace level should be OFF. Other choices are USER, for a moderately detailed trace report, and ADMIN, for more extensive trace information.
Note: After troubleshooting your connection problem, turn trace level back to OFF. Leaving the trace facility on can impact performance.
TNSPING Trace Directory Override the default location of the TNSPING trace file using this field. Be sure that you have write permission to the directory you select.

Encryption

Select Encryption to change any of the Secure Network Services encryption parameters for the client. An example of this window is shown in Figure 4 - 9.

Figure 4 - 9. Client Encryption Parameters

Client Seed Enter a new random number to act as a seed for encryption of client messages in this field. Enter a string of between 16 and 70 random characters.
Client Level Change the level of encryption the client requests using this field. Choices in the pop-up list are Accepted, Rejected, Requested, and Required. (Whether encryption is implemented in a client-server connection is determined by the level requested by both the client and the server.)
Client Type Select the type of encryption from the choices available in the pop-up list. (Do not select a type unless it has been installed. Even if a type appears in the list, it may not be installed in your system.)

S

Checksumming

elect Checksumming to change any of the Secure Network Services checksum parameters for the client. An example of this window is shown in Figure 4 - 10.

Figure 4 - 10. Client Checksum Parameters

Client Level Choose the client's requested level of checksumming from the pop-up list. Choices are Accepted, Rejected, Requested, and Required. (Whether checksumming is implemented in a client-server connection is determined by the level requested by both the client and the server.)
Client Type Select the type of checksumming from the choices available in the pop-up list. In this release, only MD5 is available. (Do not select a type unless it has been installed.)

Authentication

Select Authentication to change the authentication service the client requests. Do not select a service that has not been installed. Select one or more authentication services from the pop-up list. If more than one is selected, the first one that is also on the server's list is the one that is used. An example of this window is shown in Figure 4 - 11.

Figure 4 - 11. Client Authentication Parameter

Note: If you select CYBERSAFE or KERBEROS5, you may need to modify other parameters that are not accessible from the SQLNET.ORA Editor. Both these authentication adapters require other parameters to be set. If they are not already set in the SQLNET.ORA file, you must set them through Oracle Network Manager, or by using a text editor.

Name Resolution

Select Name Resolution to change the preferred method for resolving service names to addresses. The order in which the name resolution services appear in this list determines the order in which they are tried. For example, if you select ONAMES and then TNSNAMES, the client will request name resolution from Oracle Names rather than the SQL*Net configuration file TNSNAMES.ORA. An example of this window is shown in Figure 4 - 12.

Figure 4 - 12. Name Resolution Parameter

Client Status Monitor Read-Only Display Windows

Below the Menu Bar in the Client Status Monitor is an array of six buttons. Each button brings up a window that displays the current values for parameters in the SQLNET.ORA file.

Note: These windows are read-only. To change any of the values, use the SQLNET.ORA Editor.

General

Select this button to display some of the client SQL*Net properties set in the SQLNET.ORA file. An example is shown in Figure 4 - 13.

Figure 4 - 13. General Client Properties

To view any of the files listed in this window, select the file and select View. A scrollable window displaying the file appears. To print the file, select Print from the display window.

Network Protocol Adapters

Select this button to display the Oracle protocol adapters available on your client machine. Figure 4 - 14 shows an example of this window. The window is read-only.

Figure 4 - 14. Oracle Protocol Adapters

Checksumming Services

Select this button to display the Checksumming adapters available in Secure Network Services, and to show the specific services selected. Figure 4 - 15 shows an example of this window.

Figure 4 - 15. Checksumming Services

The fields in this window display the following information:

In the first field, all checksumming adapters available in Secure Network Services are listed.

In the Client Level field, the level of checksumming requested is listed.

In the Client Type field, the client's preference, if any, for a checksumming service is listed.

Encryption Services

Select this button to display the encryption services available in Secure Network Services, and the specific services selected. Figure 4 - 16 shows an example of this window.

Figure 4 - 16. Client Encryption Parameters

In the first field, all encryption services available in Secure Network Services are listed.

In the Client Seed field, the random number used as a starting point for the encryption algorithm is shown.

In the Client Level field, the level of encryption requested is listed.

In the Client Type field, the client's preference, if any, for encryption services is listed.

The client and the server to which it connects must have compatible encryption and checksum requirements. For example, if the client requires encryption and the server refuses encryption, the connection request will be rejected. Similarly, if the client has only RC4_40 encryption selected, and the server has only DES40, the connection request will fail.

Authentication Services

Select this button to display the authentication services that are part of Secure Network Services, and to show which ones are selected by the client. Figure 4 - 17 shows an example of this window.

Figure 4 - 17. Client Authentication

In the first field, all Authentication Adapters available in Secure Network Services are listed.

In the Authentication Selected field, all Authentication Adapters selected by the client are shown.

For further information about Secure Network Services, see the Secure Network Services Administrator's Guide. For information about setting the Secure Network Services parameters using Oracle Network Manager, see Chapter 5 in the Oracle Network Manager Administrator's Guide.

Name Resolution Services

Select this button to display the name resolution services available on your client. The name resolution services are used in the order listed in the Name Resolution Path field. For example, of the services listed in the example shown in Figure 4 - 18, the TNSNAMES.ORA file is the first method used to resolve a service name to an address, and Oracle Names is the second. If they are installed, native naming adapters such as NIS or DCE/CDS would be listed too.

Figure 4 - 18. Name Resolution Services

From	Name of person at your location who is the liaison with Oracle Customer Support
Phone	Phone number of the person at your location who is the liaison with Oracle Customer Support
Fax Number	Fax number of the person at your location who is the liaison with Oracle Customer Support
Customer Support ID	Identifying number that authorizes you to get help from Oracle Customer Support
Subject	Optional field in which to explain the problem
Comment	Optional field for additional information

Client LOG File Name	You can change the existing name for the log file in this field. In most operating systems, the log filename is automatically appended with the suffix .LOG. You do not need to enter that suffix in the field.
Client LOG Directory	You can change the existing directory to which the client log file is written in this field. Be sure that you have write permission to the directory you select.
Client Registration	Enter an identifier for the client machine. This identifier will be passed to the listener with any connection request and included in the Audit Trail. The identifier can be any alphanumeric string up to 128 characters. A typical identifier might be a department name.
Default Domain	The default domain is the domain to which most client connection requests are directed. In a hierarchical name space, the default domain should be the domain in which the most frequently contacted servers reside.

Automatic IPC	Select this button if you want the client to try an IPC (internal) connection before trying other protocols. The default is for Automatic IPC to be ON.
Use Dedicated Server	Select this button if you want to make a connection to a dedicated server rather than to use a multi-threaded server.
DISABLE Out of Band Breaks (OOB)	Select this button if you want to disable out-of-band breaks.

Client Trace Level	Select a trace level from the scrolling list. Unless you are troubleshooting a particular problem, the trace level should be OFF. Other choices are USER, for a moderately detailed trace report, and ADMIN, for more extensive trace information.
	Note: After troubleshooting your connection problem, turn trace level back to OFF. Leaving the trace facility on can impact performance.
Client Trace File Name	Change the existing name for the trace file in this field. In most operating systems, the trace filename is automatically appended with the suffix .TRC. You do not need to enter that suffix in the field.
Client Trace Directory	Change the existing directory to which the client trace file is written in this field. Be sure that you have write permission to the directory you select.
TNSPING Trace Level	Trace the behavior of the TNSPING utility by selecting a trace level from the scrolling list. Unless you are troubleshooting a particular problem, the trace level should be OFF. Other choices are USER, for a moderately detailed trace report, and ADMIN, for more extensive trace information.
	Note: After troubleshooting your connection problem, turn trace level back to OFF. Leaving the trace facility on can impact performance.
TNSPING Trace Directory	Override the default location of the TNSPING trace file using this field. Be sure that you have write permission to the directory you select.

Client Seed	Enter a new random number to act as a seed for encryption of client messages in this field. Enter a string of between 16 and 70 random characters.
Client Level	Change the level of encryption the client requests using this field. Choices in the pop-up list are Accepted, Rejected, Requested, and Required. (Whether encryption is implemented in a client-server connection is determined by the level requested by both the client and the server.)
Client Type	Select the type of encryption from the choices available in the pop-up list. (Do not select a type unless it has been installed. Even if a type appears in the list, it may not be installed in your system.)

Client Level	Choose the client's requested level of checksumming from the pop-up list. Choices are Accepted, Rejected, Requested, and Required. (Whether checksumming is implemented in a client-server connection is determined by the level requested by both the client and the server.)
Client Type	Select the type of checksumming from the choices available in the pop-up list. In this release, only MD5 is available. (Do not select a type unless it has been installed.)