Sql*Plus User’s Guide and Reference

Table 2–1
(Cont.) Parameters or Environment Variables influencing SQL*Plus
Parameter or Variable
Description

---

SQL*Plus Configuration
Configuring SQL*Plus
2-3
SQLPATH Registry Entry
The SQLPATH registry entry specifies the location of SQL scripts. SQL*Plus searches 
for SQL scripts in the current directory and then in the directories specified by the 
SQLPATH registry entry, and in the subdirectories of SQLPATH directories.
The HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME0 registry subkey (or 
the HOMEn directory for the associated ORACLE_HOME) contains the SQLPATH 
registry entry. SQLPATH is created with a default value of ORACLE_HOME\DBS. 
You can specify any directories on any drive as valid values for SQLPATH.
When setting the SQLPATH registry entry, you can concatenate directories with a 
semicolon (;). For example:
c:\oracle\ora12\database;c:\oracle\ora12\dbs
See the Registry Editor's help system for instructions on how to edit the SQLPATH 
registry entry.
SQL*Plus Configuration
You can set up your SQL*Plus environment to use the same settings with each session. 
There are two operating system files to do this:
■
The Site Profile file, glogin.sql, for site wide settings.
■
Additionally, the User Profile, login.sql, sets user specific settings. 
The exact names of these files is system dependent. 
Some privileged connections may generate errors if SET SERVEROUTPUT or SET 
APPINFO commands are put in the Site Profile or User Profile.
The following tables show the profile scripts, and some commands and settings that 
affect the Command-line user interface. 
Note:
The Site Profile and User Profile files are run after a successful 
Oracle Database connection from a 
SQLPLUS
or 
CONNECT
command, 
or where 
/NOLOG
is specified.
The Site Profile and User Profile files are not run when you switch to 
another PDB using 
ALTER SESSION SET CONTAINER
.