3.5.3 PolyServe MxS Oracle Database Solution Pack Release Notes (August 2008)

Customization 12
The configuration file can also include set and unset directives to set or
unset flags. The flags are as follows:
daemon If set, the ODM daemon will be started automatically
when the first instance of Oracle is booted. (The default
odm.conf file supplied with this release sets this
directive.)
Default: Daemon is not started automatically. The
daemon must be started before using ODM.
include Switches to reading the specified file for configuration
information and then switches back to the previous
file. Filenames can include escape sequences to allow
per-node configuration information to be included. It
is an error if the specified file cannot be read.
cond_include Similar to include, but if the specified file does not
exist, it is ignored.
batch Establishes a blocking factor for asynchronous I/O.
Asynchronous I/O handlers will be directed to service
N number of I/Os if this value is set. Handlers do not
wait for N I/O requests, but instead, if a number of
requests greater than N are in a request queue, the
handler will service N of these requests before moving
on to the others in the queue. This directive is typically
necessary only in extremely write-intensive
OLTP
environments.
The batch directive controls the behavior only of
Oracle foreground processes, Database Writers,
Checkpoint Process and Parallel Query Slaves. The
Log Writer process will always be serviced with high
priority, non-batched.
Default: 0
Flag Description
log thread limit Report in the log when the number of threads has
been limited.
log thread start Report in the log when threads are started.
Directive Meaning