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

Installation and Operation 6
Disable MxODM for a Single Database
This method is implemented on a per-database basis and requires you to
set an undocumented init.ora parameter called _disable_odm. When this
parameter is set to TRUE, the instance ignores the fact that there is a real
ODM library linked in and instead uses the standard Oracle code paths.
In the case of Real Application Clusters databases, it is important to
ensure that this setting is the same in all init.ora files or singularly in the
SPFILE.
Disable MxODM for All Databases
MxODM is a library pointed to by what is called the active library
symbolic link, which resides in the $ORACLE_HOME/lib directory. On
Oracle10gR2, the active library symbolic link is as follows:
$cd $ORACLE_HOME/lib
$ls -l libodm10.so
lrwxrwxrwx 1 root root 29 2005-12-16 01:48 libodm10.so ->
pmxs_odm/libodm.so.<version>
In all cases, the $ORACLE_HOME/lib/libodm10.so is the active library
symbolic link.
As long as all of the databases using MxODM are down, deactivating
MxODM is as simple as a symbolic link operation. Simply revert the
symbolic link to point to the symbolic link that was preserved by the
MxODM install procedure—the one with the .ORIG suffix.
Deactivation Steps
To deactive MxODM, follow these steps:
1. Use the mxodmstat -l command to check for running databases. It is
important to shut down any databases executing with MxODM before
deactivating MxODM. The -l argument to the mxodmstat command
returns process IDs and other information about any Oracle process
currently executing the library. If the command returns no
information, it is safe to deactivate MxODM.
2. Shut down all instances reported by mxodmstat.