Release 1.6
A63731-01
Library |
Product |
Contents |
Index |
| Oracle
Enterprise Manager Administrator's Guide
Release 1.6 A63731-01 |
|
This appendix describes the Server Manager DBA commands available
in line mode. These commands can also be used in a SQL Worksheet, although
some of these commands behave differently when used in a worksheet.
The DBA commands described in this appendix are:
If a reserved word is used as an object name in a DBA command,
it must be enclosed in quotes. For example, to start up a database that
is named with the reserved word V7, issue the command as follows:
STARTUP OPEN 'V7'
Run scripts containing SQL, PL/SQL, and DBA commands.
You must have previously created the script and stored it
as an operating system file.
@ command ::=
where:
The name of an operating system file that contains a script of statements recognized by Server Manager.If you omit the scriptname argument, you for are prompted
for the script name.
This command enables you to run scripts of statements. To
insert Comments in the script, use the REMARK command described in REMARK
on page -17 . To spool the output, use the SPOOL command before running
or within the script. The SPOOL command is described in SPOOL
on page -30.
Do not use the @ command alone within a script unless you
specify the full path name of the script.
To run other scripts from within a script, you can use the
@@ command. In the original script include the line @@second_scriptname
to run another script called second_scriptname. The @@ command indicates
that the second script is in the same directory as the original script.
Additional Information: For information about the standard file
selection dialog box for your system, see your operating system-specific
documentation.
Start or stop automatic archiving of online redo log files,
manually (explicitly) archive specified redo log files, or display information
about redo log files.
This command applies only to the current instance. To specify
archiving for a different instance or for all instances in a Parallel Server,
use the SQL command ALTER SYSTEM.
You must be connected to an open Oracle database as INTERNAL,
SYSOPER, or SYSDBA.
ARCHIVE LOG command ::=
where:
Requests a display that shows the range of redo log files to be archived, the current log file group's sequence number, and the current archive destination (specified by either the optional command text or by the initialization parameter LOG_ARCHIVE_DEST).If you are using both ARCHIVELOG mode and automatic archiving, the display might appear like:Database log mode Archive Mode Automatic archival Enabled Archive destination DISK9:ARCH Oldest online log sequence 30 Next log sequence to archive 33 Current log sequence 33
Because the log sequence number of the current log group
and the next log group to archive are the same, automatic archival has
archived all log groups up to the current one.
If you are using ARCHIVELOG but have disabled automatic archiving, the last three lines might look like:
Oldest online log sequence 30 Next log sequence to archive 30 Current log sequence 33
If you are using NOARCHIVELOG mode, the "next log sequence
to archive" line is suppressed.
The log sequence increments every time LGWR begins to write to another redo log file group; it does not indicate the number of logs being used. Every time an online redo log file group is reused, the contents are assigned a new log sequence number.
Disables automatic archival. If the instance is still in ARCHIVELOG mode and all redo log file groups fill, database operation is suspended until a redo log file is archived (for example, until you enter the command ARCHIVE LOG NEXT or ARCHIVE LOG ALL). Enables automatic archiving. Starts the background process ARCH, which performs automatic archiving as required. If ARCH is started and a filename is supplied, the filename becomes the new default archive destination.ARCH automatically starts on instance startup if the initialization parameter LOG_ARCHIVE_START is set to TRUE.
Manually archives the next online redo log file group that has been filled but not yet archived. Manually archives all filled, but not yet archived, online log file groups. Causes archival of the online redo log file group with log sequence number n. You can specify any redo log file group that is still online. An error occurs if the log file cannot be found online or the sequence number is not valid. This option can be used to re-archive a log file group.If not specified in the command line, the archive destination
is derived from the initialization parameter LOG_ARCHIVE_DEST. The command
ARCHIVE LOG START 'destination' causes the specified device or directory
to become the new default archive destination for all future automatic
or manual archives. A destination specified with any other option is a
temporary destination that is in effect only for the current (manual) archive.
It does not change the default archive destination for subsequent automatic
archives.
Additional Information: For information about specifying archive
destinations, see your platform-specific Oracle documentation.
If an online redo log file group fills and none are available
for reuse, database operation is suspended. The condition can be resolved
by archiving a log file group.
Starts up the archiver process and begins automatic archiving, using the archive destination specified in LOG_ARCHIVE_DEST.
ARCHIVE LOG STOP
Stops automatic archiving.
ARCHIVE LOG 1001 'DISK9:[TEMPARCH]TEMP'
Archives the log file group with the sequence number 1001
to the destination specified. 'TEMP' specifies the prefix of the filename
on the destination device; the remainder of the filename is dependent on
the initialization parameter LOG_ARCHIVE_FORMAT, which specifies the filename
format for archived redo log files.
Connect to a database using the specified username.
Only valid username/password combinations can successfully
connect. The AS clause allows users to connect to an instance with a default
schema of SYS for database administration. Users connecting as SYSOPER
or SYSDBA must have the necessary privileges to access the SYS schema.
CONNECT command ::=
where:
Any valid Oracle username for the current database. It can be a null string. If neither username nor INTERNAL is specified, you are prompted for a username and password. The password corresponding to the specified username. Password can be a null string. A valid specification for an instance/database combination. If an instance is specified, it becomes the current instance for the duration of the connection. It does not become the default instance for subsequent connections. The AS clause allows privileged connections by users who have been granted SYSOPER or SYSDBA system privileges, if using a password file, or their operating system equivalents, if using OS authentication. Uses operating system authentication. Connects as username SYS via keyword INTERNAL. Should be used rarely and only by the DBA for certain maintenance purposes; requires operating system privileges. CONNECT INTERNAL is supported for backwards compatibility only.If you omit the password, you are prompted for one.
If you omit both the username and password, you are prompted
for both.
If you omit the username argument, the Connect dialog
box displays.
If only the Oracle username is specified, the password is
requested using the prompt "Password:". The entered password is not echoed.
CONNECT can be used without a DISCONNECT to connect to another
username.
The connect is always accompanied by the opening of a cursor.
You can specify an instance path for a remote instance when
connecting. If you attempt a connection to a remote instance, authentication
occurs on the remote node, so you must have the appropriate privileges
on the remote node.
Non-Secure ConnectionConnecting as SYSOPER or SYSDBA over
a
To connect to Oracle as a privileged user over a non-secure connection, you must satisfy the following conditions:
For information about creating a password file, see the Oracle7
Server Concepts and the Oracle7 Server Administrator's Guide,
or Secure ConnectionConnecting as SYSOPER or SYSDBA over a Local
To connect to Oracle as a privileged user over a local or a secure connection, you must satisfy either of the following sets of conditions:
To connect to an instance on the current default node, enter:
CONNECT
To connect to an instance on the current node as username SCOTT with password TIGER, enter:
CONNECT scott/tiger
To use a password file to connect to an instance on the current node as a privileged user named SCOTT with password TIGER, enter:
CONNECT scott/tiger AS SYSDBA
Note that your default schema is now SYS, not SCOTT.
To perform the same connection using OS authentication, enter:
CONNECT / AS SYSDBA
To connect to an instance on a different node as username SCOTT with password TIGER, enter:
CONNECT scott/tiger@instance-path
Using Server Manager you can connect as INTERNAL to a release
7.0 database. CONNECT INTERNAL is supported for backwards compatibility
only. For information on how to use CONNECT INTERNAL, refer to your Oracle7
Server Administrator's Guide.
Describe a function, package, package body, procedure, table,
or view.
You must be currently connected to a database.
DESCRIBE command ::=
where:
The name of the object to describe.If you do not specify an object type, Server Manager attempts to determine the object type. For the statement
DESCRIBE emp
Server Manager describes the table or view if a table or
view with the name EMP exists. If no table or view with that name exists
in the user's schema, Server Manager will search for a PL/SQL function,
procedure, or package with that name and describe it.
The shorthand DESC is now equivalent to the command DESCRIBE. This means that DESC has been added to the list of Server Manager reserved words. If you have a database object named DESC, you need to place quotes around the name to show that it is an object name. For example:
INSERT INTO 'DESC' VALUES('onetwothree', 123); )
Some versions of PL/SQL allow the user to describe a package
by giving the package name, and some versions require the user to specify
an object in the package to describe. Server Manager supports package description
for those versions of PL/SQL which support this functionality.
A command like
DESCRIBE scott.addemp
produces output similar to the following example:
PROCEDURE SCOTT.ADDEMP (EMPNO INTEGER, ENAME VARCHAR2, SAL NUMBER(9,2))
The use of the object type is no longer required. If you do not specify an object type, Server Manager attempts to determine the object type. For the statement
DESCRIBE emp
Server Manager describes the table or view if a table or
view with the name EMP exists.
If no table or view with that name exists in the user's schema, Server Manager searches for a PL/SQL function, procedure, or package with that name and describes it. For the statement
DESCRIBE payroll.emp
Server Manager looks for a table or view in schema PAYROLL
with the name EMP.
If there is no PAYROLL schema or no EMP table/view in the
PAYROLL schema, Server Manager will search the current schema for a package
PAYROLL containing a function or procedure EMP.
If both a table EMP in schema PAYROLL and a package PAYROLL with function/procedure EMP in the current schema exist, the statement
DESCRIBE FUNCTION payroll.emp
This allows you to specify the type of the object you want
to describe.
Server Manager now has the capability to describe both functions
and procedures contained in packages. Previously only functions and procedures
not contained in packages could be described.
Some versions of PL/SQL allow the user to describe a package
by giving the package name, and some versions require the user to specify
an object in the package to describe. Server Manager supports package description
for those versions of PL/SQL which support this functionality.
Disconnect from an Oracle server.
You must be currently connected to a database.
DISCONNECT command ::=
Upon disconnection, line mode reverts to the current default
host machine after closing all open cursors and committing any uncommitted
transactions.
Executes a one-line PL/SQL statement.
You must be currently connected to a database. You must also
have privileges to use any stored procedures, packages, package variables,
and functions referenced with this command.
EXECUTE command ::=
You can execute only one line of PL/SQL code with the EXECUTE command. If you wish to execute a PL/SQL block with many lines, you must use the format:
BEGIN [PL/SQL BLOCK] END;
You can reference any command line mode bind variables in
PL/SQL statements by preceding the variable name with a colon. The example
below illustrates the use of bind variables with the VARIABLE, EXECUTE,
and PRINT commands.
VARIABLE balance NUMBER
EXECUTE :balance := get_balance(34056) PRINT balance BALANCE ---------- 4678.24
Exits Server Manager line mode or closes a SQL Worksheet.
EXIT command ::=
The EXIT command leaves line mode unconditionally, commits the current transaction, and returns to the operating system prompt.
The EXIT command commits the current transaction and closes
the worksheet.
Print the value of a variable defined with the VARIABLE command.
PRINT command ::=
where:
The name of a variable defined by the VARIABLE command.Bind variables referenced with the print command do not need
to be preceded by a colon. You can use the PRINT command to display variables
defined only in the current line mode session. The SET CHARWIDTH and SET
NUMWIDTH commands can affect the display of the PRINT command.
If no variable name is specified all currently defined variables
are printed.
PRINT balance
BALANCE ---------- 4687.24 SET CHARWIDTH 10 PRINT ename ENAME ---------- SCOTT
Performs media recovery on one or more tablespaces, one or
more datafiles, or the entire database.
You must be connected to the Oracle server as INTERNAL, SYSOPER,
or SYSDBA. You cannot use the RECOVER command when connected via the multi-threaded
server.
RECOVER command ::=
UNTIL clause ::=
PARALLEL clause ::=
where:
Specifies recovering the entire database. Specifies that a backup of the control file is being used instead of the current control file. Specifies recovering a particular tablespace. Tablespace is the name of a tablespace in the current database. You may recover up to 16 tablespaces in one statement. Specifies recovering a particular datafile. You can specify any number of datafiles. Specifies an incomplete, cancel-based recovery. Recovery proceeds by prompting you with the suggested filenames of archived redo log files, and recovery completes when you specify CANCEL instead of a filename. Specifies an incomplete, change-based recovery. The integer is the number of the SCN following the last change to which you wish to recover. For example, if you want to restore your database up to the transaction with an SCN of 9, you would specify UNTIL CHANGE 10. Specifies an incomplete, time-based recovery. Use single quotes, and use the following format: 'YYYY-MM-DD:HH24:MI:SS'. DEGREE specifies the number of recovery processes used to apply redo entries to datafiles on each instance. An integer specified for DEGREE overrides the initialization parameter RECOVERY_PARALLELISM. DEGREE DEFAULT indicates that twice the number of datafiles being recovered is the number of recovery processes to use.INSTANCES specifies the number of instances to use for parallel recovery. The number of recovery processes specified with DEGREE is used on each instance, thus the total number of recovery processes is the integer specified with DEGREE multiplied by the integer specified with INSTANCES. INSTANCES is only pertinent for the Oracle Parallel Server.INSTANCES DEFAULT or not including the INSTANCES keyword causes has operating system-specific consequences. Consult your Oracle operating system documentation for a description of the default behavior of the INSTANCES DEFAULT specification. Specifies that recovery is to proceed serially. Note that a specification of PARALLEL(DEGREE 1 INSTANCES 1) is equivalent to specifying the NOPARALLEL keyword.The PARALLEL keyword overrides the RECOVERY_PARALLELISM initialization
parameter. The number specified with the PARALLEL keyword is the number
of recovery processes used to apply redo entries to datafiles.
In a SQL Worksheet, if you issue the RECOVER command without
arguments, Server Manager brings up the Recover dialog box.
To perform media recovery on an entire database (all tablespaces),
the database must be mounted EXCLUSIVE and closed.
To perform media recovery on a tablespace, the database must
be mounted and open, and the tablespace must be offline.
To perform media recovery on a datafile, the database can
remain open and mounted with the damaged datafiles offline (unless the
file is part of the SYSTEM tablespace).
Before using the RECOVER command you must have restored good
copies of the damaged datafile(s) from a previous backup. Be sure you can
access all archived and online redo log files dating back to when that
backup was made.
When another log file is required during recovery, a prompt
suggests the names of files that are needed. The name is derived from the
values specified in the initialization parameters LOG_ARCHIVE_DEST and
LOG_ARCHIVE_FORMAT. You should restore copies of the archived redo log
files needed for recovery to the destination specified in LOG_ARCHIVE_DEST,
if necessary. You can override the initialization parameters by setting
the LOGSOURCE variable.
During recovery you can accept the suggested log name by
hitting return, cancel recovery by entering CANCEL instead of a log name,
or enter AUTO for automatic file selection without further prompting.
If you have enabled autorecovery (that is, SET AUTORECOVERY
ON), recovery proceeds without prompting you with filenames. Status messages
are displayed when each log file is applied.
When normal media recovery is done, a completion status is
returned.
For more information on recovery and the RECOVER command,
see the Oracle7 Server Administrator's Guide.
RECOVER DATABASE
RECOVER DATABASE UNTIL TIME 30-AUG-90:04:32:00 RECOVER TABLESPACE ts_one, ts_two RECOVER DATAFILE 'data1.db'
Enter a Comment, typically in SQL script files.
REMARK command ::=
Primarily for batch use of line mode. The Comment is ignored
by line mode and by Oracle. REMARK can be shortened to REM.
REM must be the first non-blank character string in the line.
Examples of valid Comments embedded in a SQL file follow:
REM This command file is used to create a REM database. Edit it to fill in file names REM and sizes, and invoke it from line mode. REM REM CREATE DATABASE dbname .... /* This is a SQL Comment */ ... ... ;
REMARKs are recognized by SQL*Plus, as well as by line mode.
They are used to put Comments between SQL statements, while SQL Comments
(/*...*/) are used to place comments within statements.
Set or change characteristics of the current command line
mode session.
See next page for sytax diagram.
where:
Registers the Server Manager application through the database's DBMS_APPLICATION_INFO package (Oracle 7.2 or later). By default, the APPINFO function is set to OFF.Application registration allows DBAs to see what software is currently running to better monitor resource utilization for database tuning. When APPINFO is turned on, application registration proceeds normally. If a SQL script is not being run, the default registration text string is "Oracle SQL Worksheet." Optionally, you can create a customized registration text string. If a script is being run through Server manager, the script name is used as the registration text string.SET APPINFO abc abc SET APPINFO abc def abc SET APPINFO "abc def" abc def SET APPINFO 'abc def' abc def SET APPINFO "abc def Error SET APPINFO 'abc def Error
OFF, the default option, requires that you enter the filenames manually or accept the suggested default filename given.
Sets the column display width for CHAR data. If entered with no argument, returns the setting to the default. The default is 80; the range of values is operating system-specific. Sets compatibility mode to V6, V7, or NATIVE. The compatibility mode setting affects the specification of character columns, integrity constraints, and rollback segment storage parameters. NATIVE matches the version of the database.CHAR Columns: When creating tables in Version 6 compatibility
mode, CHAR columns are variable length. In Oracle7, such column definitions
are fixed length.
Integrity Constraints: In Version 6 compatibility
mode, the Version 6 syntax is still recognized, and the Oracle7 syntax
is disabled. For V6 mode, table constraints on CREATE TABLE statements
are specified with V6 syntax:
CREATE TABLE {UNIQUE | PRIMARY KEY} CONSTRAINT ....
and specified constraints are disabled by default. For V7
mode, table constraints are specified with Oracle7 syntax:
CREATE TABLE CONSTRAINT .... {UNIQUE | PRIMARY KEY}
Rollback Segment Parameters: Version 6 compatibility
mode allows PCTINCREASE and MAXEXTENTS to be specified for rollback segments,
as well as for other segments. Although the specifications are ignored,
the syntax is allowed. (Use of these parameters is not recommended. They
exist only for backward compatibility.)
Bind Variables: Bind variables of type VARCHAR2 are given type CHAR in Version 6 compatibility mode.
Sets the column display width for DATE data. If entered with no argument, the setting returns to the default. The default is 9; the range of values is operating system-specific. ON enables echoing of commands entered from command files. OFF, the default, disables echoing of commands. Limits the number of rows returned by a query. Useful with ordered queries for finding the "top ten" items in a category, for example. Also used with unordered queries to find the "first n" records that satisfy a given criteria. integer must be in the range 1-999,999.In a SQL Worksheet the default is ECHO ON.
Changes the default instance for your session to the specified instance path. Does not connect to a database. The default instance is used for commands when no instance is specified.Any commands preceding the first use of SET INSTANCE communicate
with the default instance.
To reset the instance to the default value for your operating
system, you can either enter SET INSTANCE with no instance-name
or SET INSTANCE LOCAL. See your operating system-specific Oracle documentation
for a description of how to set the initial default instance.
This command may only be issued when SQL*Net is running. You can use any valid SQL*Net connect string as the specified instance path. See your operating system-specific Oracle documentation for a complete description of how your operating system specifies SQL*Net connect strings. The maximum length of the instance path is 64 characters.
Specifies the location from which archive logs are retrieved during recovery. The default value is set by the LOG_ARCHIVE_DEST initialization parameter. Issuing the SET LOGSOURCE command without a pathname restores the default location. Sets the column display width for LONG data. If entered with no argument, the setting returns to the default. The default is 80; the range of values is operating system-specific. Sets the maximum data size. Indicates the maximum data that can be received in a single fetch during a SELECT statement. The default is 20480 bytes (20K). The maximum is operating system-specific. Sets the column display width for NUMBER data. If entered with no argument, the setting returns to the default. The default is 10; the range of values is operating system-specific. Sets the number of tries that are attempted when the RETRY option is used with the STARTUP command. INFINITE, the default, specifies an infinite number of retries. ON enables debugging output from stored procedures that use DBMS_OUTPUT PUT and PUT_LINE commands. OFF disables output.You can specify the size in bytes of the message buffer using the syntax SIZE n. That is the total number of bytes of all messages sent that can be accumulated at one time. The minimum is 2,000 bytes. If the buffer fills before calls to the get-message routines make room for additional message bytes, an error is returned to the message-sending program.
Specifying ON indicates that if a command file is running and an error occurs, execution should terminate. OFF disables STOPONERROR. ON, the default, enables terminal output for SQL commands. OFF disables terminal output. Useful for preventing output to terminal when spooling output to files. Note that nothing appears on the terminal until SET TERMOUT ON is used. ON displays parse, execute, and fetch times (CPU and elapsed) for each SQL statement executed. OFF, the default, does not display timing information.SET INSTANCE D:DEV-PROD
SET TIMING ON SET LONGWIDTH 132 SET NUMWIDTH 20 SET CHARWIDTH 5
Either of the following commands can be used to revert to the initial default host:
SET INSTANCE SET INSTANCE LOCAL
Show settings currently in effect.
SHOW command ::=
where:
Shows all settings except for ERRORS, PARAMETERS, and SGA. Shows the current status (ON/OFF) and the application registration text. Shows the column display width for CHAR data. Shows the sessions compatibility mode: V6, V7, or NATIVE. Shows the column display width for DATE data. Shows whether or not commands from command files are echoed. Shows the errors generated from the last compilation of a procedure, package, or function, if any. This option displays the line number, column number, and the error message generated. Use the SHOW ERRORS command if line mode error 72 or 73 is returned after compiling a package.The SET CHARWIDTH command can be used to expand or truncate the display from the SHOW ERRORS command.
Shows the numerical limit set for the number of rows returned by a query. Shows the connect string for the default instance. SHOW INSTANCE returns the value LOCAL if you have not used SET INSTANCE or if you have used the LOCAL option of the SET INSTANCE command. Shows the current setting for archive log location. Displays DEFAULT if the default setting is in effect, as specified by the LOG_ARCHIVE_DEST initialization parameter. Shows the column display width for LONG data. Shows the maximum data size. Shows column display width for NUMBER data. Displays the current values for one or more initialization parameters. You can use a string after the command to see a subset of parameters whose names include that string. For example, if you enter:SHOW PARAMETERS COUNT
you would see:
NAME TYPE VALUE ------------------- ------- ----- db_file_multiblock_read_count integer 12 spin_count integer 0
The SHOW PARAMETERS command, without any string following the command, displays all initialization parameters.
Displays the number of retries that will be attempted when restarting an instance in parallel mode. Displays ON if output from stored procedures and functions is enabled. Otherwise, displays OFF. SERVEROUTPUT is reset to OFF if you issue a CONNECT command. Displays information about the current instance's System Global Area. If spooling is enabled, displays the name of the output spool file. Otherwise, displays OFF. Displays whether or not errors encountered during execution of command files should stop execution of the file. Shows if output to the terminal is enabled. Shows whether or not the parse, execute, and fetch times (CPU and elapsed) for each SQL statement executed are shown.SHOW with no arguments is the same as SHOW ALL.
returns a display such as:
Timing OFF SHOW ALL
returns a display like:
Instance local Spool OFF Timing OFF Termout ON Echo OFF Stoponerror OFF Autorecovery OFF Logsource <default> Maxdata 20480 Numwidth 10 Charwidth 80 Longwidth 80 Datewidth 9 Labwidth 32 Compatibility NATIVE Retries infinite Server Output OFF SHOW SGA
returns a display like:
Total Shared Global Area 4612820 bytes Fixed Size 36376 bytes Variable Size 4445372 bytes Database Buffers 122880 bytes Redo Buffers 8192 bytes SHOW ERRORS PACKAGE BODY name
returns a display like:
ERRORS FOR PACKAGE BODY name: LINE/COL ERRORS --------------------------------------------------------------- ...
Shut down a currently running Oracle instance, optionally
closing and dismounting a database.
You must be connected to a database as INTERNAL, SYSOPER,
or SYSDBA. You cannot be connected via a multi-threaded server.
SHUTDOWN command ::=
where:
Proceeds with the fastest possible shutdown. Does not wait for calls to complete or users to disconnect. Does not close or dismount the database, but does shut down the instance. Requires instance recovery on next startup. You must use this option if a background process terminates abnormally. Does not wait for current calls to complete, prohibits further connects, and closes and dismounts the database. Finally, shuts down the instance. Does not wait for connected users to disconnect. Does not require instance recovery on next startup. Waits for currently connected users to disconnect from the database, prohibits further connects, and closes and dismounts the database. Finally, shuts down the instance. Does not require instance recovery on next startup. NORMAL is theIn Server Manager, you can have several separate connections
open at any time in multiple windows. If you have any connections open,
remember to close them before performing a shutdown in normal mode. Otherwise,
the shutdown will not complete.
SHUTDOWN
Database closed. Database dismounted. Oracle instance shut down.
Enable or disable spooling of output to a specified file.
SPOOL command ::=
where:
Any valid name for a spool file. If not specified, the file type or file extension is LOG. If a file by the specified name exists, an error is generated. Closes the previously opened spool file.If you do not specify a file, Server Manager prompts you
for a filename.
Additional Information: The default filename is operating system
specific. Refer to your operating system-specific Oracle documentation
for the default filename on your operating system. To see whether you are
currently spooling, enter SHOW SPOOL.
When long lines of text (usually from a table query) are
written to a spool file or to a terminal, newline codes are inserted in
the text if the lines exceed the maximum line length for the platform.
To create a file named NOV2.LOG, enter:
SPOOL NOV2
Start an Oracle instance with several options, including
mounting and opening a database.
You must be connected to a database as INTERNAL, SYSOPER,
or SYSDBA. You cannot be connected via a multi-threaded server.
STARTUP command ::=
where:
Shuts down the current Oracle instance (if it is running) with SHUTDOWN mode ABORT, before restarting it. If the current instance is running and FORCE is not specified, an error results. FORCE is useful while debugging and under abnormal circumstances. It should not normally be used. Only allows Oracle users with the RESTRICTED SESSION system privilege to connect to the database. Later, you can use the ALTER SYSTEM command to disable the restricted session feature. Causes the specified parameter file to be used while starting up the instance. Mounts a database but does not open it. Mounts and opens the specified database. Causes the database not to be mounted upon instance startup. Cannot be used with SHARED, EXCLUSIVE, PARALLEL, MOUNT, or OPEN. Specifies that media recovery should be performed, if necessary, before starting the instance. STARTUP RECOVER has the same effect as issuing the RECOVER DATABASE command and starting an instance. Only complete recovery is possible with the RECOVER option.Recovery proceeds, if necessary, as if AUTORECOVERY is set
to ON, regardless of whether or not AUTORECOVERY is enabled. If a redo
log file is not found in the expected location, recovery continues as if
AUTORECOVERY is disabled, by prompting you with the suggested location
and name of the subsequent log files that need to be applied.
If recovery fails using the RECOVER option, the database remains mounted and closed.
The name of the database to mount or open. If no database name is specified, the database name is taken from the initialization parameter DB_NAME.To start an instance using the standard parameter file, mount and open the database, enter:
STARTUP
To shut down the current instance, immediately restart it without mounting or opening, and allow only database administrators to connect, enter:
STARTUP FORCE NOMOUNT RESTRICT
To start an instance using the parameter file TESTPARM without mounting the database, enter:
STARTUP PFILE=testparm NOMOUNT
To shut down a particular database, immediately restart and open it in parallel mode, allow access only to database administrators, and use the parameter file MYINIT.ORA. enter:
STARTUP OPEN databasename PFILE=myinit.ora FORCE SHARED RESTRICT
To start up an instance and mount but not open a database, you can use the following sequence of commands (the system's response is also shown):
CONNECT INTERNAL Connected. STARTUP NOMOUNT Oracle instance started. ALTER DATABASE MOUNT Statement processed.
At this point, you could run a maintenance command and then open the database, as shown in the following commands:
ALTER DATABASE ARCHIVELOG; Statement processed. ALTER DATABASE OPEN; Statement processed.
Declare a bind variable for use in the current session with
the EXECUTE or PRINT command, or for use with a PL/SQL block.
VARIABLE command ::=
where:
The name of the bind variable you wish to define. The datatype of the bind variable. The valid datatypes are NUMBER, CHAR, and VARCHAR2. You can specify a length from 1 to 255 for CHAR, and from 1 to 2,000 for VARCHAR2. If you do not specify a length, CHAR and VARCHAR2 default to the current setting of CHARWIDTH.Bind variables defined with the VARIABLE command exist until
the end of the session. Variables defined in your session cannot be accessed
or changed by a different session.
Warning:
CHAR variables are fixed length, padded with blanks. VARCHAR2
variables are variable length. You must use CHAR when passing a character
variable to a PL/SQL procedure that defines a CHAR parameter. Otherwise,
a conversion error results. A PL/SQL procedure that expects a VARCHAR2
variable, on the other hand, will automatically convert a CHAR parameter
to the proper form. (In general, it is a good idea to avoid the use of
CHAR variables in PL/SQL procedures unless blank-padding is an absolute
requirement.)
In V6 compatibility mode, a CHAR variable is variable length,
rather than fixed.
VARIABLE balance NUMBER
VARIABLE ename CHAR(20)
