- •Contents
- •Send Us Your Comments
- •Preface
- •1 Introduction to iSQL*Plus
- •What is iSQL*Plus?
- •iSQL*Plus Architecture
- •iSQL*Plus User Interface
- •Oracle HTTP Server
- •Oracle9i
- •2 Configuring iSQL*Plus
- •System Requirements
- •Web Browser (client tier)
- •Oracle HTTP Server (middle tier)
- •Oracle9i (database tier)
- •Installation
- •Configuring the Client Tier
- •Adding MIME Types
- •Adding Proxy Server Exceptions
- •Configuring the Middle Tier
- •Configuring the iSQL*Plus Server
- •Defining a Connection Identifier
- •Setting the iSQL*Plus Session TimeOut
- •Changing the Default Cascading Style Sheet
- •Enabling or Disabling iSQL*Plus
- •Configuring the Oracle HTTP Server
- •Testing the Oracle HTTP Server Configuration File
- •Starting and Stopping the Oracle HTTP Server
- •Configuring the Database Tier
- •iSQL*Plus Security
- •Using Administration Privileges
- •Enabling User Security
- •Adding Entries to an Oracle HTTP Server Authentication File
- •Logging In Using Oracle HTTP Server Authentication
- •Security Usage Notes
- •Configuring Globalization Support
- •Web Browser - client tier:
- •Oracle HTTP Server - middle tier:
- •Oracle9i - database tier:
- •3 The iSQL*Plus User Interface
- •The iSQL*Plus Log In Screen
- •Help Icon
- •Username:
- •Password:
- •Connection Identifier:
- •Privilege:
- •Clear
- •The iSQL*Plus Work Screen
- •Password Icon
- •Log Out Icon
- •Help Icon
- •Enter statements:
- •Script location:
- •Browse...
- •Load Script
- •Execute:
- •Output:
- •Clear Screen
- •Save Script
- •The Change Password Screen
- •Help Icon
- •Username:
- •Old password:
- •New password:
- •Retype new password:
- •Change Password
- •Clear
- •Cancel
- •4 Using iSQL*Plus
- •Running iSQL*Plus
- •Entering Statements
- •Loading Scripts
- •Entering Substitution Variables
- •The Define Substitution Variables Screen
- •Password Icon
- •Log Out Icon
- •Help Icon
- •Define Substitution Variables
- •Submit for Execution
- •Cancel
- •Creating Dynamic Reports
- •Using SET and COLUMN Commands
- •Getting Help
- •Exiting iSQL*Plus
- •5 Command Reference
- •SQL*Plus Command Summary
- •@ (“at” sign)
- •@@ (double “at” sign)
- •/ (slash)
- •ARCHIVE LOG
- •ATTRIBUTE
- •BREAK
- •BTITLE
- •CLEAR
- •COLUMN
- •COMPUTE
- •CONNECT
- •COPY
- •DEFINE
- •DESCRIBE
- •DISCONNECT
- •EXECUTE
- •HELP
- •LIST
- •PROMPT
- •RECOVER
- •REMARK
- •REPFOOTER
- •REPHEADER
- •SHOW
- •SHUTDOWN
- •START
- •STARTUP
- •TIMING
- •TTITLE
- •UNDEFINE
- •VARIABLE
- •WHENEVER OSERROR
- •WHENEVER SQLERROR
- •SQL*Plus Error Messages and Codes
- •iSQL*Plus Error Messages
- •COPY Command Messages
- •PRODUCT_USER_PROFILE Table
- •Creating the PUP Table
- •PUP Table Structure
- •Description and Use of PUP Columns
- •PUP Table Administration
- •Disabling SQL*Plus, SQL, and PL/SQL Commands
- •Creating and Controlling Roles
- •Disabling SET ROLE
- •Disabling User Roles
- •Glossary
- •Index
@ (“at” sign)
@ (“at” sign)
Syntax
@{uri|file_name[.ext] } [arg...]
Runs the SQL*Plus statements in the specified command file. The command file can be called from the local file system or from a web server. uri is only supported on Windows platforms in this release. Only the uri form is supported in iSQL*Plus.
Terms
Refer to the following for a description of the term or clause:
uri
Specifies the Uniform Resource Identifier of a script to run on the specified web server. SQL*Plus supports HTTP, FTP and gopher protocols.
file_name[.ext]
Represents the command file you wish to run. If you omit ext, SQL*Plus assumes the default command-file extension (normally SQL).
When you enter @ file_name.ext, SQL*Plus searches for a file with the filename and extension you specify in the current default directory. If SQL*Plus does not find such a file, SQL*Plus will search a sys- tem-dependent path to find the file. Some operating systems may not support the path search. See the Oracle installation and user’s manual(s) provided for your operating system for specific information related to your operating system environment.
arg...
Represent data items you wish to pass to parameters in the command file. If you enter one or more arguments, SQL*Plus substitutes the values into the parameters (&1, &2, and so forth) in the command file. The first argument replaces each occurrence of &1, the second replaces each occurrence of &2, and so forth.
The @ command DEFINEs the parameters with the values of the arguments; if you run the command file again in this session, you can enter new arguments or omit the arguments to use the current values.
Command Reference 5-5
@ (“at” sign)
Usage
In a command file, you can include any command you would normally enter interactively (typically, SQL, SQL*Plus commands, or PL/SQL blocks).
An EXIT or QUIT command used in a command file terminates SQL*Plus.
The @ command functions similarly to START.
If the START command is disabled, this will also disable the @ command. See START in this chapter for information on the START command.
SQL*Plus removes the SQLTERMINATOR (a semicolon by default) before the @ command is issued. If you require a semicolon in your command, add a second SQLTERMINATOR. See the SQLTERMINATOR variable of the SET command in this chapter for more information.
Examples
To run a command file named PRINTRPT with the extension SQL, enter
@PRINTRPT
To run a command file named WKRPT with the extension QRY, enter
@WKRPT.QRY
You can run a script named YEAREND specified by a Uniform Resource Indentifier, and pass values to variables referenced in YEAREND in the usual way:
@HTTP://HOST.DOMAIN/YEAREND.SQL VAL1 VAL2 @FTP://HOST.DOMAIN/YEAREND.SQL VAL1 VAL2 @GOPHER://HOST.DOMAIN/YEAREND.SQL VAL1 VAL2
On a web server configured to serve SQL reports, you could request SQL*Plus to execute a dynamic script by using:
@HTTP://HOST.DOMAIN/SCRIPTSERVER?ENDOFYEAR VAL1 VAL2
5-6 iSQL*Plus User’s Guide and Reference
@@ (double “at” sign)
@@ (double “at” sign)
Syntax
@@file_name[.ext]
Runs a command file. This command is identical to the @ (“at” sign) command. It is useful for running nested command files because it has the additional functionality of looking for the specified command file in the same path or uri as the command file from which it was called. uri is only supported on Windows platforms in this release. Only the uri form is supported in iSQL*Plus.
Terms
Refer to the following for a description of the term or clause:
file_name[.ext]
Represents the nested command file you wish to run. If you omit ext,
SQL*Plus assumes the default command-file extension (normally SQL).
When you enter @@file_name.ext from within a command file, SQL*Plus runs file_name.ext from the same directory as the command file.
When you enter @@file_name.ext interactively, SQL*Plus runs file_ name.ext from the current working directory or from the same uri as the command file from which it was called. If SQL*Plus does not find such a file, SQL*Plus searches a system-dependent path to find the file. Some operating systems may not support the path search. See the Oracle installation and user’s manual provided for your operating system for specific information related to your operating system environment.
Usage
You can include in a command file any command you would normally enter interactively (typically, SQL or SQL*Plus commands).
An EXIT or QUIT command used in a command file terminates SQL*Plus.
The @@ command functions similarly to START.
If the START command is disabled, this will also disable the @@ command. For more information, see the START command later in this chapter.
SQL*Plus removes the SQLTERMINATOR (a semicolon by default) before the @@ command is issued. A workaround for this is to add another SQLTERMINATOR.
Command Reference 5-7
@@ (double “at” sign)
See the SQLTERMINATOR variable of the SET command in this chapter for more information.
Examples
Suppose that you have the following command file named PRINTRPT:
SELECT DEPARTMENT_ID, CITY FROM EMP_DETAILS_VIEW WHERE SALARY>12000; @EMPRPT
@@ WKRPT
When you START PRINTRPT and it reaches the @ command, it looks for the command file named EMPRPT in the current working directory and runs it. When PRINTRPT reaches the @@ command, it looks for the command file named WKRPT in the same path as PRINTRPT and runs it.
Suppose that the same command file PRINTRPT was located on a web server and you ran it with START HTTP://HOST.DOMAIN/PRINTRPT. When it reaches the @ command, it looks for the command file named EMPRPT in the current local working directory and runs it. When PRINTRPT reaches the @@ command, it looks for the command file named WKRPT in the same uri as PRINTRPT and runs it.
5-8 iSQL*Plus User’s Guide and Reference