Table of Contents
Advertisement
User's Guide
•
Record identifier (the word "session").
•
Status of the session. The status can be active, inactive, or invalid. A status
of invalid applies if any data file or error message file belonging to the
session has been deleted or if the session was terminated before its start
time was reached.
•
Byte offset to the next session record in the control file, from the start of
this record.
•
Session ID, a number that uniquely identifies the session among all
sessions that appear in this control file. Session IDs are integers assigned
sequentially in increasing order.
•
User name of the client who requested that the recording be made.
•
Start date and time of the recording session.
The start and end times in the control file reflect as closely as possible
when a recording session actually started and ended. These actual times
might differ slightly from the start_time and end_time parameter values
specified in the command. For example, start_time might be scheduled as
1 p.m., but because of a busy system, the session might actually start at
1:02 p.m.
•
End date and time of the recording session.
•
Name of the Adaptive Server monitored.
•
Name of Monitor Server that participated in the recording session.
•
Path name of the directory in which the monitoring files for the session are
stored.
•
Name of the error message file for the session.
•
Sample interval, in seconds, used during recording.
If this value is 0, it means that the session was created by playback with a
summarization_level of
sample, and there is no sample interval.)
•
Protection level in effect (
•
Error option (
continue
•
Type of script file created (
•
Encrypted password of the client that created the recording session.
•
If the session was created as a result of playback, the keyword
. (The entire session is represented in one
entire
/
).
public
private
/
if nonfatal error during recording).
halt
/
sybase_script
no_script
CHAPTER 5
Data Files
).
summary
.
93
Advertisement
Table of Contents
