PolyServe® MxS Oracle Database Solution Pack Release Notes PolyServe MxS Oracle Database Solution Pack Version 3.5.
Legal and notice information Copyright © 2004-2008 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents Installation and Operation Contents of the 3.5.3 Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restriction for MxODM 3.5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install MxODM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation and Operation The PolyServe MxS Oracle Database Solution Pack (MxODM) contains a shared library, libodm.so, that implements the Oracle Disk Manager (ODM) Version 2 interface for use with Oracle10g with, or without, the Real Application Clusters (RAC) option. Contents of the 3.5.3 Release MxODM version 3.5.3 provides a fix for the following issue: • Defect 16644. The CONTROLFILE AUTOBACKUP feature of RMAN fails with RMAN-03009 and ORA-17502 errors. Restriction for MxODM 3.5.
Installation and Operation 2 – The Linux Oracle user must be added to the pmxs group in the /etc/group file on each server in the Oracle cluster. When you are logged in as user oracle, the output from the id command then shows pmxs in the list of groups. For example: $ id uid=777(oracle) gid=777(dba) groups=777(dba),11(pmxs) You should also obtain the following information. The installation procedure will ask for these values if it cannot locate them in the environment. • The value of $ORACLE_HOME (e.g.
Installation and Operation 3 3. Install MxODM 3.5.3. (Be sure to install the RPM corresponding to your architecture.) Type the following command as user root: # rpm -ivh /odm-3.5.3-..rpm The installation procedure will verify that all of the prerequisites for the product are met. The verification step will notify you of any problems that it detects. If the verification is successful, you will see a message listing the actions to take place during the installation.
Installation and Operation 4 Very Large SGA Buffer Pools On 64-bit systems, MxODM is routinely tested for functionality and efficiency when performing I/O into very large SGA buffer pools. An SGA db block buffer cache size of 20GB has been tested with both Real Application Clusters (RAC) and non-RAC on systems configured with 32GB of main memory. Very Large Aggregate PGA for Parallel Query Option By setting the init.
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.
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.
Installation and Operation 7 3. Preserve the active library symbolic link currently pointing to the MxODM library by executing the mv(1) command. 4. Create a new active library symbolic link that points to the original “stub” ODM library provided by Oracle Corporation. Following is an example of deactivating MxODM. The mxodmstat -l command is first used to check for running databases. In the example, a database called ABCD was executing.
Installation and Operation 8 1. Shut down all databases executing out of the $ORACLE_HOME where you want to reactivate MxODM. 2. Remove the active library symbolic link with the rm(1) command. 3. Rename the preserved active library symbolic link from the deactivation stage using the mv(1) command. The following screen capture shows an example of reactivating MxODM. Uninstall MxODM Before uninstalling MxODM, be sure that there are no Oracle Instances running on any nodes in the matrix.
Installation and Operation 9 Open Issues When more than one DBWRITER is used and ODM is linked to Oracle, an issue in Oracle 10gR2 causes one of the DBWRITERs to maintain a reference to a file when it is dropped and deleted. The instance then needs to be stopped to reclaim the space from the deleted file. The workaround for this issue is to use only one DBWRITER. Oracle specifies that it is unnecessary to use more than one DBWRITER for most cases.
Customization Configuration File The default configuration of the PolyServe MxS Oracle Database Solution Pack (MxODM) should be suitable for most sites. However, the product includes a configuration file, $ORACLE_HOME/lib/pmxs_odm/odm.conf, that can be customized if necessary. The odm.conf configuration file contains directives that specify values for MxODM. Each directive, followed by its argument, appears on a separate line. Lines starting with # are comments. The file can also include blank lines.
Customization 11 Directives The directives that can appear in the odm.conf file are as follows. Directive Meaning logfile File where log messages are appended. Default: “log” shared_memory_key Key to access the node’s shared memory. Default: 0x4d445350 (PSDM) semaphore_key Key to access the node’s semaphores. Default: 0x4d444450 (PSSM) datafile_perm Permissions used to create database files. Default: 0660 max_async_io Maximum number of concurrent asynchronous I/O requests.
Customization 12 Directive Meaning 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.
Customization 13 Flag Description log thread stop Report in the log when threads are stopped. log file close Report in the log when files are closed to stay within the maximum number of file descriptors allowed. log all Report all of the above. trace Report ODM calls. Only calls with a meaningful context are reported (odm_discover() and odm_init() are not reported). traceio Log every odm_ioc structure before and after I/O (very verbose). trace ident Log every odm_idn structure returned.
Customization 14 The options are as follows: -d Detach and run as daemon -s Stop after the last client exits -p pidfile Write pid to file -l logfile Write timestamped log file -t traceflags Trace activities to log file (-l must be specified) Oracle init.ora Parameter for Oracle Disk Manager Although Oracle will function properly in conjunction with ODM without any modification to the init.ora (or spfile), it is recommended that care be taken to allow Oracle optimal Database Writer functionality.
