3
Configuring SQL*Plus

This chapter explains how to configure your SQL*Plus command-line and iSQL*Plus environments. It has the following topics:

• SQL*Plus Configuration
• iSQL*Plus Configuration
• iSQL*Plus Extension for Windows Configuration

SQL*Plus Configuration

You may wish to set up your SQL*Plus environment in a particular way (such as showing the current time as part of the SQL*Plus command prompt) and then reuse those settings with each session. You can do this through two host operating system files, the Site Profile for site wide settings, and the User Profile for user specific settings. The exact names of these files is system dependent; see the Oracle installation and user's guide provided for your operating system for the precise name.

Site Profile

SQL*Plus supports a global Site Profile, a SQL*Plus script created by the database administrator. This file is generally named glogin.sql. SQL*Plus executes this script whenever any user starts SQL*Plus and SQL*Plus establishes the Oracle connection. The global Site Profile allows the DBA to set up SQL*Plus environment defaults for all users at a particular site; users cannot directly access the Site Profile.

The site profile file is $ORACLE_HOME/sqlplus/admin/glogin.sql. If a site profile already exists at this location, it is overwritten when you install SQL*Plus. If SQL*Plus is removed, the site profile file is deleted.

User Profile

SQL*Plus also supports a User Profile, executed after the Site Profile. This file is generally named login.sql. SQL*Plus searches for the user profile in your current directory, and then the directories you specify with the SQLPATH environment variable. SQL*Plus searches this colon-separated list of directories in the order they are listed.

You can add any SQL commands, PL/SQL blocks, or SQL*Plus commands to your user profile. When you start SQL*Plus, it automatically searches for your user profile and runs the commands it contains.

A user profile is ineffective in the iSQL*Plus user interface context, and cannot be used to control the initial settings or behavior of an individual iSQL*Plus session.

Modifying Your LOGIN File

You can modify your LOGIN file just as you would any other script. You may wish to add some of the following commands to the LOGIN file:

SET LINESIZE

SET NUMFORMAT

SET PAGESIZE

SET PAUSE

SET SQLPROMPT

SET TIME

See the SET command for more information on these and other SET command variables you may wish to set in your SQL*Plus LOGIN file.

Storing and Restoring SQL*Plus System Variables

You can store the current SQL*Plus system ("SET") variables in a host operating system file (a script) with the STORE command. If you alter any variables, this script can be run to restore the original values. This is useful if you want to reset system variables after running a report that alters them.

To store the current setting of all system variables, enter

STORE SET file_name

By default, SQL*Plus adds the extension "SQL" to the file name. If you want to use a different file extension, type a period at the end of the file name, followed by the extension. Alternatively, you can use the SET SUFFIX command to change the default file extension.

Restoring the System Variables

To restore the stored system variables, enter

START file_name

If the file has the default extension (as specified by the SET SUFFIX command), you do not need to add the period and extension to the file name.

You can also use the @ ("at" sign) or the @@ (double "at" sign) commands to run the script.

Example 3-1 Storing and Restoring SQL*Plus System Variables

To store the current values of the SQL*Plus system variables in a new script "plusenv.sql":

STORE SET plusenv



Created file plusenv

Now the value of any system variable can be changed:

SHOW PAGESIZE


PAGESIZE 24



SET PAGESIZE 60
SHOW PAGESIZE



PAGESIZE 60

The original values of system variables can then be restored from the script:

START plusenv
SHOW PAGESIZE



PAGESIZE 24

iSQL*Plus Configuration

Configuring iSQL*Plus is discussed in the following topics:

Configuring the Client Tier

This section discusses options for configuring your web browser to use iSQL*Plus.

Web Browser Setup

Your web browser needs to be configured to enable cookies. iSQL*Plus can be used without JavaScript, but you may find it better with JavaScript enabled.

Adding MIME Types

Some web browsers may require you to either remove a MIME type definition or application association for files with a .SQL extension, or to create a MIME type or application association for files with a .SQL extension in order to load scripts into iSQL*Plus.

Some browsers may require you to set up a MIME type to be able to save scripts to your local machine. If iSQL*Plus opens a new window when you click "Save Script" on the Work screen instead of prompting you to enter a filename to save the script, then set up a MIME type

application/vnd.oracle-isqlplus.script

and configure it to allow you to save to disk. Also add

application/vnd.oracle-isqlplus.output

to allow you to use the Save to file option accessed through the Interface Options screen of iSQL*Plus.

For example, to set up an application association for files with a SQL extension in Netscape Navigator 4.7 for Windows NT:

1. Select Preferences from the Edit menu.
2. Select Applications from the Navigator menu tree.
3. Click the New Type button. On the displayed form, enter

   Description of type: SQL files

   File extension: SQL

   MIME type: text/plain

   Application to use: notepad.exe

   Uncheck the "use this MIME as the outgoing default for this extension"

   If this is not set up in your web browser, you may get an error when you try to load scripts that iSQL*Plus cannot identify as text files.

Adding Proxy Server Exceptions

Some configurations of proxy servers may affect the ability of the iSQL*Plus user interface to connect with the iSQL*Plus Server. If you cannot connect with the iSQL*Plus Server, a browser alert "Document contains no data" or "Server Interrupt Error" is displayed when you try to load the iSQL*Plus Login screen. If the Oracle HTTP Server has been started and this situation occurs, you should reconfigure your proxy server or create a proxy exception in your browser for the Oracle HTTP Server running iSQL*Plus. There are two examples of setting proxy exceptions following:

To configure the proxy exceptions setting in Netscape Navigator 4.7 for Windows

1. Select Preferences from the Edit menu.
2. Select Proxies from the Advanced category.
3. Select the Manual proxy configuration radio button.
4. Click View. The Manual proxy configuration dialog is displayed.
5. Enter the Oracle HTTP Server domain for which you do not want to use a proxy in the Exceptions pane.

To configure the proxy exceptions setting in Microsoft Internet Explorer 5.0

1. Select Internet Options from the Tools menu.
2. Click Lan Settings in the Lan Settings pane on the Connections tab.
3. Click Advanced in the Proxy Server pane. This is only available if Use a proxy server is selected.
4. Enter "*." followed by the Oracle HTTP Server domain for which you do not want to use a proxy in the Exceptions pane. For example, to enter an exception for the Oracle HTTP Server domain, machine_name.domain, you must enter *.machine_name.domain.

Retained Session Settings

Certain settings from a session are either retained or automatically filled in the next time you log in to iSQL*Plus from the same workstation:

• Input area size
• Number of History entries

Your username, password and Output preference are not saved by iSQL*Plus.

Configuring the Middle Tier: iSQL*Plus Server

The iSQL*Plus Server is installed during Oracle9i Database installation on the middle tier. You can configure several parameters and settings in the iSQL*Plus Server.

Session Integrity

Each iSQL*Plus login is uniquely identified, so you can:

• Connect multiple times from the same machine
• Connect multiple times from different machines

iSQL*Plus supports this stateful behavior by storing session context information in the Oracle HTTP Server. You must ensure that your Oracle HTTP Server always routes HTTP requests to the same server, otherwise the session context will not be found. However, you may find it useful to start more than one Oracle HTTP Server to distribute user load across the multiple servers.

Editing the iSQL*Plus Configuration File

You can edit the isqlplus.conf configuration file directly to change settings for iSQL*Plus Server parameter settings such as:

• iSQLPlusNumberOfThreads
• iSQLPlusLogLevel
• iSQLPlusTimeOutInterval
• iSQLPlusHashTableSize
• iSQLPlusConnectIdList
• -idle-timeout

On Windows, the isqlplus.conf file is located in:

%ORACLE_HOME%\sqlplus\admin\isqlplus.conf

On UNIX, the isqlplus.conf file is located in:

$ORACLE_HOME/sqlplus/admin/isqlplus.conf

To change the value of an iSQL*Plus initialization parameter, edit the line associated with the parameter. The syntax of the line to be edited is shown in the following sections.

Setting the iSQL*Plus Threads Parameter

The iSQLPlusNumberOfThreads parameter sets the number of threads enabled in the iSQL*Plus Server. Because each thread enables an HTTP request to be handled, this value sets the maximum number of simultaneous HTTP requests that can be handled by the iSQL*Plus Server.

When many users are executing long running queries, increasing the iSQLPlusNumberOfThreads value may help performance. You can edit the iSQL*Plus configuration file, isqlplus.conf, to change the number of threads. The syntax of the line to change in the configuration file is:

FastCgiServer ... -initial-env iSQLPlusNumberOfThreads=n

Where n can have a minimum value of 1, and a maximum determined by machine resources. When no value is set, iSQLPlusNumberOfThreads defaults to 20.

Setting the iSQL*Plus Log Level

There should be no need to set iSQLPlusLogLevel to warn or debug unless instructed to by Oracle Support.

The iSQLPlusLogLevel parameter determines whether logging is enabled to record iSQL*Plus Server messages, and the level of logging. Logging is useful to help resolve user problems. Logging can be turned off, set to warn level or set to debug level, which provides the richest information.

iSQLPlusLogLevel defaults to warn if it is set to an invalid value or if it is not set. If the log file cannot be opened or written, it is set to off. The default logfile location is %ORACLE_HOME%\sqlplus\log\isqlplus\log.xml in Windows, and $ORACLE_HOME/sqlplus/log/isqlplus/log.xml in UNIX. A new log file is started when its size reaches 64 kilobytes. The old file is renamed with a unique name like log1006130580.xml. A maximum of 10 log files are kept, and older files are automatically deleted.

When logging is enabled, iSQL*Plus appends log data to an existing log file, or creates a new file if one does not exist. If there is any sort of write error that prevents writing to the logfile, iSQL*Plus starts, but does not create a log file or log any messages.

The log directory must be writable by iSQL*Plus. The log directory has owner write permissions. If iSQL*Plus is running as nobody and therefore cannot write to the log file, the iSQL*Plus administrator must manually give iSQL*Plus write permissions on the log file. It is not recommended to grant world write permission to the file except for temporary testing or tracing purposes.

Some abnormal errors may be written to the Oracle HTTP Server log file. These may include errors generated if the iSQL*Plus Server cannot be started. These errors are written even if iSQLPlusLogLevel is OFF.

When iSQLPlusLogLevel is set to debug, then process tracing information is logged.

You can edit the iSQL*Plus configuration file, isqlplus.conf, to change the log level. The syntax of the line to change in the configuration file is:

FastCgiServer ... -initial-env iSQLPlusLogLevel=[off|warn|debug]

Setting the iSQL*Plus Time Out Parameter

Timing out iSQL*Plus sessions helps to reduce machine load and to maximize resources. The time out interval is set by the iSQLPlusTimeOutInterval initialization parameter. It defines the time a session can be idle before it is expired. You can edit the iSQL*Plus configuration file, isqlplus.conf, to change the timeout interval. The syntax of the line to change in the configuration file is:

FastCgiServer ... -initial-env iSQLPlusTimeOutInterval=n

Where n is the number of whole minutes of idle time before the session times out. iSQLPlusTimeOutInterval has a default of 30 minutes. It can be set to any value from 1 to 1440 minutes. It should not be set so small that users do not get a chance to enter their scripts.

When a user tries to use a timed out iSQL*Plus session, the Login screen is displayed and the user is prompted to log in again and the following error is displayed:

SP2-0864: Session has expired.  Please log in again.

Setting the iSQL*Plus Hash Table Size Parameter

The number of hash table entries is defined by the iSQLPlusHashTableSize initialization parameter. Each user session consumes one entry in the hash table even if it is idle. Its default value is derived from the value of the iSQLPlusNumberOfThreads parameter value. However, iSQLPlusHashTableSize can be set independently to tune the system.

You can edit the iSQL*Plus configuration file, isqlplus.conf, to change the hash table size. The syntax of the line to change in the configuration file is:

FastCgiServer ... -initial-env iSQLPlusHashTableSize=n

Where n is the number of entries in the hash table.

Enabling or Disabling Restricted Database Access

The restricted database parameter limits the databases that users can access in iSQL*Plus. When enabled, a dropdown list of available databases is displayed in place of the Connection Identifier text field on the Login screen. This allows greater security for iSQL*Plus Servers in hosted environments. Connection identifiers are listed in the order defined in iSQLPlusConnectIdList.

You can edit the iSQL*Plus configuration file, isqlplus.conf, to restrict database access. The syntax of the line to change in the configuration file is:

FastCgiServer ... -initial-env "iSQLPlusConnectIdList=SID1, SID2,..."

where SID1, SID2,, ... is a comma separated list of Oracle Net connection identifiers specifying permitted databases. For example:

FastCgiServer ... -initial-env "iSQLPlusConnectIdList=ABC1, PROD2, DEV3"

Note the use of quotes in the example. The opening quote must occur before the iSQLPlusConnectIdList parameter name, the closing quote at the end of the list of SIDs.

For more information about restricted database access, see "Enabling or Disabling Restricted Database Access".

Setting the iSQL*Plus Idle Timeout

The FastCGI timeout parameter or idle timeout is the time the Oracle HTTP Server waits for results from iSQL*Plus. It is set to a value likely to prevent iSQL*Plus timing out before the web browser. It is sufficient for many long queries to return results before iSQL*Plus times out.

The idle timeout should not be confused with the iSQLPlusTimeOutInterval which manages the lifetime of a user's session.

You can edit the iSQL*Plus configuration file, isqlplus.conf, to change the idle timeout value. The syntax of the line to change in the configuration file is:

FastCgiServer ... -initial-env -idle-timeout=n

Where n is the number of seconds of the Oracle HTTP Server waits for results from iSQL*Plus. The default value is 3600 seconds.

Changing the Cascading Style Sheet

iSQL*Plus uses a cascading style sheet to control the format of the user interface. You can replace the default style sheet with your own style sheet. It is recommended that you do not delete the default style sheet, but rename it so that you can revert to it if necessary.

For example, to replace the cascading style sheet in Windows

1. Navigate to the %ORACLE_HOME%\sqlplus\admin\iplus\ directory.
2. Rename the existing style sheet from iplus.css to another name.
3. Copy your new style sheet to the %ORACLE_HOME%\sqlplus\admin\iplus\ directory.
4. Rename your new style sheet to iplus.css.
5. You may need to refresh your web browser display to see the effects of your new style sheet.

Enabling Server Authentication for Users

By default, Oracle HTTP Server authentication is required for SYSDBA and SYSOPER privileged users. You may also want to limit who can access iSQL*Plus by requiring Oracle HTTP Server authentication for normal user logins. See "Enabling Server Authentication for Users" for more details.

Enabling DBA Access

To connect with SYSDBA or SYSOPER privileges, or to generate the iSQL*Plus Server Statistics report, your username and password must be added to the iSQL*Plus authentication file for the Oracle HTTP Server. See "Enabling DBA Access" for more details.

Configuring the Middle Tier: Oracle HTTP Server

The Oracle HTTP Server is installed during Oracle9i Database installation on the middle tier. You can:

• Test the Oracle HTTP Server Configuration File
• Start and Stop the Oracle HTTP Server
• Enable or Disable iSQL*Plus

Additional iSQL*Plus configuration information must be included in the Oracle HTTP Server configuration file, httpd.conf, for the iSQL*Plus Server.

There are two layers of nested configuration files:

• httpd.conf includes the Oracle9i configuration file, oracle_apache.conf
• oracle_apache.conf includes the iSQL*Plus configuration file, isqlplus.conf.

Changes are usually only made to:

• isqlplus.conf to configure the iSQL*Plus Server.
• oracle_apache.conf to disable iSQL*Plus

After making changes to .conf files, check them to make sure there are no errors, and then stop and start the Oracle HTTP Server to implement the changes.

Testing the Oracle HTTP Server Configuration File

To check the Oracle HTTP Server configuration file, httpd.conf, and any included configuration files for errors. On Windows do the following steps:

1. Open a Windows Command Prompt.
2. Change directory to the Oracle HTTP Server home directory by entering:

   cd %ORACLE_HOME%\Apache\Apache\conf
   

3. Parse the Oracle HTTP Server httpd.conf configuration file by entering:

   apache -t
   

   Any errors in the configuration file are displayed. If there are any errors, edit the included configuration files, oracle_apache.conf or isqlplus.conf, again to correct them and then test again. If there are no errors, the message "Syntax OK" is displayed.

On UNIX, do the following steps:

1. Open a terminal.
2. Change directory to the Oracle HTTP Server home bin directory by entering:

   cd $ORACLE_HOME/Apache/Apache/conf
   

3. Parse the Oracle HTTP Server httpd.conf configuration file by entering:

   apachectl configtest
   

   Any errors in the configuration file are displayed. If there are any errors, edit the included configuration files, oracle_apache.conf or isqlplus.conf, again to correct them and then test again. If there are no errors, the message "Syntax OK" is displayed.

Starting and Stopping the Oracle HTTP Server

For changes to the Oracle HTTP Server configuration file, httpd.conf, and any included configuration files to take affect, you must stop and restart the Oracle HTTP Server if it is running. There is no convenient way to know how many users are currently accessing the server, so it is important to have the server down for the shortest time. When making changes to configuration files parse the httpd.conf configuration file and report any errors before starting and stopping the Oracle HTTP Server.

To stop and start the Oracle HTTP Server. On Windows do the following steps:

1. Open a Windows Command Prompt.
2. Change directory to the Oracle HTTP Server home directory by entering:

   cd %ORACLE_HOME%\Apache\Apache
   

3. Stop the running Oracle HTTP Server by entering:

   apache -k shutdown
   

4. Start the Oracle HTTP Server by entering

   apache -k start
   

On UNIX, do the following steps:

1. Open a terminal.
2. Change directory to the Oracle HTTP Server home bin directory by entering:

   cd $ORACLE_HOME/Apache/Apache/bin
   

3. Stop the running Oracle HTTP Server by entering:

   apachectl stop
   

4. Start the Oracle HTTP Server by entering

   apachectl start
   

   Warning: If the Oracle HTTP Server is started by a user who is a member of the "dba" or "oper" groups on UNIX, or who is a member of the ORA_DBA, ORA_OPER, ORA_SID_DBA, or ORA_SID_OPER groups on Windows, the iSQL*Plus DBA URL is automatically authenticated for Oracle9i by the operating system. To avoid this, start the Oracle HTTP Server as a user who is not a member of these operating system groups. Users of the iSQL*Plus DBA URL can authenticate for Oracle9i using '/ as sysdba' or '/ as sysoper'.

Enabling or Disabling iSQL*Plus

You can edit the Oracle HTTP Server configuration file to disable iSQL*Plus.

To disable iSQL*Plus

1. Stop the Oracle HTTP Server.
2. Change directory to the Oracle HTTP Server configuration directory by entering:

   On Windows:

   cd %ORACLE_HOME%\Apache\Apache\conf
   

   On UNIX:

   cd $ORACLE_HOME/Apache/Apache/conf 
   

3. Open the oracle_apache.conf configuration file.
4. Comment out the isqlplus.conf include line by inserting a # at the beginning of the line as follows:

   On Windows:

   # include "ORACLE_HOME\sqlplus\admin\isqlplus.conf"
   

   On UNIX:

   # include "ORACLE_HOME/sqlplus/admin/isqlplus.conf"
   

   Where ORACLE_HOME is the path of your Oracle home directory.

5. Save your oracle_apache.conf file.
6. Check your edits by parsing the edited configuration file. See "Testing the Oracle HTTP Server Configuration File"
7. When you next start the Oracle HTTP Server, iSQL*Plus is disabled.

To re-enable iSQL*Plus, reverse the edit to uncomment the include line in oracle_apache.conf and restart the Oracle HTTP Server.

Configuring the Middle Tier: Oracle Net

If you plan to connect to a remote database you need to ensure that you install and configure Oracle Net on the middle tier middle tier where the iSQL*Plus server is running. For further information about installing and configuring Oracle Net, see the Oracle9i documentation.

Configuring the Database Tier

Oracle9i is installed on the database tier. The database tier may be physically separate from the middle tier and accessed using Oracle Net, or it may be the same physical machine as used by the middle tier. If you are using Oracle Net to access the database, then make sure the database listener is configured and running. For further information about installing and configuring Oracle9i, see the Oracle9i documentation.

iSQL*Plus Extension for Windows Configuration

The iSQL*Plus Extension for Windows is accessed through extended menus in Windows platforms. The iSQL*Plus Extension for Windows extended menu is accessed by right clicking files with the .SQL file extension.

If you have installed the Oracle9i Server, iSQL*Plus Server entries for your Oracle HTTP Server are created by default. If you have installed the Oracle9i Client, no iSQL*Plus Server entries are created. You can use the Configuration dialog to configure the available iSQL*Plus Servers that you want.

Configuration Dialog

You can open the Configuration dialog by right clicking a .SQL file in Windows Explorer, then select iSQL*Plus Servers, and then Configure. The Configure iSQL*Plus Servers dialog is displayed.

When the column is narrower than the field it contains, tool tips show the full text in the field, but to edit or copy a field, make sure that the column width is wide enough to display the full field. You can widen the column by selecting and dragging the heading column separator.

You can sort the list of iSQL*Plus Servers in ascending or descending field name order by clicking the field name column heading. You can also manually sort the server definitions by using the up and down arrow buttons on the right side of the list of iSQL*Plus Servers.

Text description of the illustration iseconf.gif

URL

Enter a valid iSQL*Plus Server URL in the form:

http://host.domain/isqlplus

This field is mandatory.

Name

Enter a name for this iSQL*Plus Server. The name, if entered, is used in the context menu, otherwise the full iSQL*Plus Server URL is used.

Connect String

Enter a connect string to specify your username and password and the database you want to connect to. If you omit a username and password you are prompted for them when iSQL*Plus starts. If you omit a database connection identifier or Oracle Net alias, you are connected to the default database.

Execute

Clear the Execute checkbox to change the action performed on the selected file. The default action is Execute, the alternative is Load. Execute runs the selected file in the iSQL*Plus Server and displays the results in your browser. Load opens the iSQL*Plus Server and loads the selected file into the Input area.

Add

Click Add to add a new iSQL*Plus Server.

Remove

Click Remove to delete a selected iSQL*Plus Server definition.

File Association:

Enter a path and arguments for the application you want to associate with the .SQL file extension when you double click. The default application is Windows Notepad. This definition does not affect the iSQL*Plus Server definitions.

Browse

Click Browse to find an application you want to associate with the .SQL file extension when you double click.

Language:

Select a language you want to use in the iSQL*Plus Extension from the dropdown list of available languages:

Brazilian Portuguese
English
French/Canadian French
German
Italian
Japanese
Korean
Simplified Chinese
Spanish/LA Spanish
Traditional Chinese

This language setting only affects the iSQL*Plus Extension, not iSQL*Plus.

OK

Click OK to save your changes and close the Configure iSQL*Plus Servers dialog.

Cancel

Click Cancel to quit your changes and close iSQL*Plus Extension. You are prompted once more before your changes are lost.

When you first open the Configure iSQL*Plus Servers dialog, the OK button is unavailable and the Cancel button is labelled Close. Once you make changes, OK is enabled and Close is renamed Cancel.

Adding a Server

You must configure at least one iSQL*Plus Server before you can use the iSQL*Plus Server Extension. To add an iSQL*Plus Server, perform the following steps:

1. Right click on a .SQL file in Windows Explorer.
2. Select iSQL*Plus Servers to display the context menu options. Initially, there are the following options:
   • No iSQL*Plus Servers configured

     If you have installed Oracle9i Server, there are two iSQL*Plus Servers configured, one for the standard URL and one for the DBA URL.

   • Configure.
   • About iSQL*Plus Extension.
3. Click Configure. The Configure iSQL*Plus Servers dialog is displayed.
4. Enter an iSQL*Plus Server definition in the iSQL*Plus Servers: area. When you first open the dialog, the following syntax model is displayed to show you the expected field contents:

   URL: << http://host.domain/isqlplus >>
   Name: << host >>
   Connect String: << username/password@connect_identifier >> 
   

   You must enter a URL for your iSQL*Plus Server, the other fields are optional. This may be different if iSQL*Plus Servers have been configured during an Oracle9i Server installation.

5. Click OK to save your new server definition.

The new iSQL*Plus Server Name appears in the context menu. When you select a server from the context menu, the full iSQL*Plus Server URL is shown in the status bar.

Modifying a Server

To modify an iSQL*Plus Server, perform the following steps:

1. Right click on a .SQL file in Windows Explorer.
2. Select iSQL*Plus Servers to display the context menu options.
3. Click Configure. The Configure iSQL*Plus Servers dialog is displayed.
4. Select the server you wish to modify from the list of available servers.
5. Edit the server definition directly in the text fields and press Enter when you have finished editing each field. To edit or copy a field when the column is narrower than the field it contains, you need to widen the column by selecting and dragging the heading column separator.
6. Click OK to save your changes.

The modified iSQL*Plus Server name appears in the context menu.

Removing a Server

Select the server you wish to remove from the list of available servers. The server's details will appear in the following text boxes. Click the Remove button to remove it from the list of available servers.

To remove an iSQL*Plus Server, perform the following steps:

1. Right click a .SQL file in Windows Explorer.
2. Select iSQL*Plus Servers to display the context menu options.
3. Click Configure. The Configure iSQL*Plus Servers dialog is displayed.
4. Select the server you wish to remove from the list of available servers.
5. Click Remove.
6. Click OK to save your changes.

The iSQL*Plus Server is removed from the context menu.