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

Installation and Operation 5
The log includes the following types of messages:
• Comment. These messages describe library activities.
• Warning. These messages indicate that a problem may exist.
• Error. These messages are the most serious and are also written to
standard error. Usually the condition causes the ODM library to
return an error code.
• BOTCH. These messages are for internal errors and are also written to
standard error. If a BOTCH message is reported, contact PolyServe
Technical Support for assistance.
ODM Daemon
MxODM uses an ODM daemon (odmd) to communicate between
instances of ODM on the various nodes in the matrix. The daemon must
be running while any Oracle instance is active on the node.
A directive in the default configuration file for MxODM causes the ODM
daemon to start automatically on each node. You can modify the file so
that the ODM daemon does not start automatically; however, if the
deamon dies you will then need to restart it manually. See “Start the
ODM Daemon” on page 13 for more information.
Deactivate MxODM
After MxODM has been installed, it may become necessary, for testing or
other reasons, to perform a database operation without activating
MxODM. In these situations, it is not necessary to uninstall MxODM.
Instead, the installed MxODM can simply be deactivated.
The following methods can be used to execute Oracle instances without
ODM even though ODM is installed:
• Set an undocumented init.ora parameter. This method is implemented
on a per-database basis.
• If using an undocumented init.ora parameter is not acceptable, you
can disable MxODM for all databases executing out of the Oracle
Home where MxODM is being deactivated.