Skip Headers

Oracle® OLAP DML Reference
10g Release 1 (10.1)

Part Number B10339-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Feedback

Go to previous page
Previous
Go to next page
Next
View PDF

LOG command

The LOG command starts or stops the recording of a session to a disk file. All lines of input and output are recorded.

Syntax

LOG [APPEND] {file-id|EOF|SAVE}

Arguments

APPEND

When file-id already exists, appends the record of your session to the end of its current contents. APPEND has no effect when the file does not already exist or when you specify EOF.

When file-id already exists and you omit APPEND, LOG replaces the contents of file-id with the new session record.

file-id

A file identifier that specifies a disk file in which to record the session. File-id is a text expression that represents the name of the file. The name must be in a standard format for a file identifier. When a log file is already open, specifying a new file-id closes the previous file. Enclose the file identifier in single quotes.

EOF

Stops recording of the session and closes any opened log record file.

SAVE

Forces Oracle OLAP to update the log file. Lines of input and output are not always written to disk as they are generated. Instead, the lines are stored temporarily then written to disk periodically. LOG SAVE effectively issues the LOG EOF and LOG APPEND file-id commands. This ensures that all appropriate lines are written to disk by closing the log file and reopening it. Additional lines of input and output are appended to the file.

Notes


Automatic Closing of a Log File

When you use LOG file-id to start recording in a disk file, LOG closes any log record file that is currently open. This happens even when the new file is not actually opened (as when you specify an invalid 'file-id' in the LOG command).

Examples

Example 16-30 Keeping a Log File

To record your session in a file called session.log, use a statement like the following.

LOG 'session.log'