Database Reference
In-Depth Information
Configuring LTOM Properties
Once the scripts have been installed, LTOM needs to be configured for database connectivity and also for starting
ltom in the background. The configuration parameters are stored in the
tom_deploy.properties
file located in the
init
directory under the
$TOM_HOME
location.
In this properties file the following are to be configured:
•
Connection parameters:
DB_CONNECT_STRING
parameter defines the connection mode and type. The default
type of connection uses the JDBC thin client. Because LTOM is configured to run on each
node in the cluster, instance-specific connection information should be provided.
•
The
INSTANCE
parameter defines the instance to monitor and collect statistics.
•
The
DB_USERID
parameter defines the LTOM user id used by LTOM to make a connection
to the database and collect appropriate statistics.
•
The
DB_CONNECT_STRING=jdbc:oracle:thin:@prddb1:1521:PRD_1
INSTANCE=PRD_1
DB_USERID= tom
System Profiler:
•
PROFILER=
enables background collection of information required by the profiler.
•
PFREQ=
is the frequency at which snapshots should be collected by the profiler.
•
SESSIONS=
defines the type of sessions that should be monitored by the process.
•
LEVEL=
determines the level of data to be captured. LTOM supports two levels for system
profiling of data:
•
•
Level 1 is the basic bare minimum data collected and includes data from
V$SESSION_WAIT
view.
•
Level 2 provides a much more detailed output and includes data collected from
V$SESSION_WAIT
,
V$SYSTEM_EVENT
and
V$SYSSTAT
.
CPU=
value is a Y/N value; when enabled, it profiles CPU-related statistics from the OS.
•
CSQL=
is the parameter that will help profile SQL statements currently being executed.
The values supported by this parameter include
•
I
- Inline at every snapshot.
•
R
- Generates a report at the end of profile collection.
•
N
- Disables profiling of data.
•
PROFILE_TOP
indicates if top process information should be profiled from the OS.
•
PROFILE_VMSAT
indicates if VMSTAT data from the O/S should be profiled.
•
PROFILE_IOSTAT
indicates if IOSTAT data from the O/S should be profiled.
•
Search WWH ::
Custom Search