HP POLYSERVE SOFTWARE

You can read the recommendations in the user guide, the technical guide or the installation guide for HP POLYSERVE SOFTWARE. You'll find the answers to all your questions on the HP POLYSERVE SOFTWARE in the user manual (information, specifications, safety advice, size, accessories, etc.). Detailed instructions for use are in the User's Guide. User manual HP POLYSERVE SOFTWARE User guide HP POLYSERVE SOFTWARE Operating instructions HP POLYSERVE SOFTWARE Instructions for use HP POLYSERVE SOFTWARE Instruction manual HP POLYSERVE SOFTWARE

Manual abstract: 5.3 August 2008 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. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Oracle is a registered trademark of Oracle Corporation. Contents Installation and Operation Contents of the 3.5.3 Release... Restriction for MxODM 3.5.3..... Installation.... Prerequisites.... Install MxODM.. Relink Oracle with MxODM Installed..... Very Large Memory Systems... Very Large Files.... Log Messages. ODM Daemon

. Deactivate MxODM...... Disable MxODM for a Single Database....... Disable MxODM for All Databases..... Deactivation Steps.... Reactivate MxODM... Uninstall MxODM....... Open Issues... 1 1 1 1 2 3 3 4 4 5 5 6 6 6 7 8 9 Customization Configuration File...... Directives.... Start the ODM Daemon....

... Oracle init.ora Parameter for Oracle Disk Manager... 10 11 13 14 iii 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.3 MxODM supports a maximum of 1024 connections. Installation Prerequisites Before installing MxODM, the following software must be installed and configured on the matrix servers. Check the PolyServe Hardware and Software Compatibility Guide for the supported versions. A supported operating system. PolyServe Matrix Server. A supported version of Oracle. @@@@@@@@ The value of $ORACLE_HOME (e.g., /u01/app/oracle/product/9204). The Oracle user ID (e.g., oracle). The Oracle DBA group (e. g., dba). Install MxODM The recommended method for installing Oracle on Matrix Server is with a shared Oracle Home. As such, only one node in the matrix is used to install MxODM into the cluster filesystem. However, any node in the matrix can configure and execute the software. The installation places the MxODM package in the directory /opt/polyserve/odm and sets up $ORACLE_HOME/lib/pmxs_odm with the correct symbolic links for Oracle. This configuration enables all nodes in the matrix to use the package. NOTE: When you perform the installation, all Oracle database Instances must be shut down on all nodes in the matrix. To install MxODM 3.5. 3, complete these steps: 1. Uninstall the previous version of MxODM. The package must be uninstalled from the node where you installed it. # rpm -e odm-<version> 2. Mount the MxODM 3.5.3 CD or go to the location where you have downloaded the software. 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 <mountpoint>/odm-3.5.3-<xxxx>. <arch>.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. When you answer yes, the installation will proceed. MxODM includes two man pages. A separate RPM containing only the man pages is provided in the product distribution. If you want other servers in the cluster to have local copies of the man pages, install the man pages RPM on those servers. # rpm -i <mountpoint>/odm-man-3.5.3-<xxxx>.<arch>.rpm Relink Oracle with MxODM Installed If it becomes necessary to relink Oracle to apply a one-off Oracle patch or to enable a new database option, you must uninstall MxODM prior to the relinking operation. After the relinking is finished, simply re-install MxODM. Your site-specific modifications to such files as odm. conf will be preserved automatically during this operation. Very Large Memory Systems This release of MxODM has been tested on systems configured with 32GB RAM. For Oracle, Very Large Memory (VLM) systems are generally used in one of the following ways: Very large SGA buffer pools Very large aggregate PGA for Parallel Query Option Large numbers of users connecting as Dedicated Server processes 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.ora parameter "pga_aggregate_target" to 20000M, this release of MxODM has been tested with Parallel Query index creates on tables as large as 500GB on Oracle10g R2. Large Numbers of Users Connecting as Dedicated Server Processes This release of MxODM has a fixed limit of 1024 instantiations of the library on a server. This limit has been tested by setting the init.ora "processes" parameter to 950 and invoking Pro*C benchmark client processes using the dedicated server model. @@@@@@These messages describe library activities. Warning. These messages indicate that a problem may exist. Error. @@Usually the condition causes the ODM library to return an error code. BOTCH. @@@@@@@@@@@@In these situations, it is not necessary to uninstall MxODM. Instead, the installed MxODM can simply be deactivated.

Powered by TCPDF (www.tcpdf.org) @@This method is implemented on a per-database basis. @@@@@@@@@@@@Use the mxodmstat -l command to check for running databases. @@@@@@2. @@@@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 exet: 500 If set, ODM will always report a fixed elapsed time for I/Os. The time is expressed in microseconds. Default: -1 (the actual time is reported) semaphore_key datafile_perm max_async_io max_file_opens elapsed_time Customization 12 Directive daemon Meaning 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. 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. Similar to include, but if the specified file does not exist, it is ignored. 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 include cond_include batch The configuration file can also include set and unset directives to set or unset flags. The flags are as follows: Flag log thread limit log thread start Description Report in the log when the number of threads has been limited. Report in the log when threads are started. Customization 13 Flag log thread stop log file close log all trace Description Report in the log when threads are stopped. Report in the log when files are closed to stay within the maximum number of file descriptors allowed. Report all of the above. Report ODM calls. Only calls with a meaningful context are reported (odm_discover() and odm_init() are not reported). Log every odm_ioc structure before and after I/O (very verbose). Log every odm_idn structure returned. Select trace, traceio, and trace ident. Log high-water mark of outstanding requests. This flag is set by default. Report the results of the configuration. Some of the common files are set only by the first instance. This flag shows what is actually used and is set by default. Select all flags except abort. Abort the process when an internal error occurs. @@The set and unset directives are processed in order. @@@@@@Without ODM, it is common to configure a single Database Writer with the db_writer_processes parameter and multiple Database Writer slaves via the dbwr_io_slaves parameter. With ODM, it is mandatory that Database Writer slaves not be configured. Instead, the instance should be configured with a ratio of one true Database Writer slave per four processors. For example, on a fourprocessor system, the following is recommended: db_writer_processes = 1 dbwr_io_slaves = 0 All init.ora parameters that ordinarily control asynchronous I/O are essentially ignored when Oracle links with libodm.so. To that end, the parameters can remain unset. Examples of "ignored" parameters are: disk_async_io _lgwr_async_io _dbwr_async_io filesystemio_options.