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 selec-
tion dialog box for your system, see your operating system-specific doc-
umentation.
ARCHIVE LOG
Purpose Start or stop automatic archiving of online redo log files, manually
(explicitly) archive specified redo log files, or display information about redo log
files.
Note:
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.
DBA Command Reference
B-3
ARCHIVE LOG
Prerequisites You must be connected to an open Oracle database as INTERNAL,
SYSOPER, or SYSDBA.
Syntax ARCHIVE LOG command ::=
where:
LIST
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 modeArchive Mode
Automatic archivalEnabled
Archive destinationDISK9:ARCH
Oldest online log sequence30
Next log sequence to archive33
Current log sequence33
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 sequence30
Next log sequence to archive30
Current log sequence33
If you are using NOARCHIVELOG mode, the “next log sequence to archive” line is
suppressed.
B-4 Oracle Enterprise Manager Administrator’s Guide
ARCHIVE LOG
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.
STOP
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).
START
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.
NEXT
Manually archives the next online redo log file group that has been filled
but not yet archived.
ALL
Manually archives all filled, but not yet archived, online log file groups.
integer
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.
‘destination’
Specifies the destination device or directory in an operating system.
Specification of archive destination devices is installation-specific; see
your platform-specific Oracle documentation for examples of specifying
archive destinations. On many operating systems, multiple log files can
DBA Command Reference
B-5