📄 appd_tru.htm
字号:
<td headers="r3c1 r1c2" align="left" colspan="1" rowspan="1"><a id="sthref693" name="sthref693"></a><a id="sthref694" name="sthref694"></a>shm_allocate_striped
</td>
<td headers="r3c1 r1c3" align="left" colspan="1" rowspan="1">1 (default)
</td>
</tr>
<tr align="left" valign="top">
<td id="r4c1" headers="r1c1" align="left" colspan="1" rowspan="1">vm
</td>
<td headers="r4c1 r1c2" align="left" colspan="1" rowspan="1"><a id="sthref695" name="sthref695"></a><a id="sthref696" name="sthref696"></a>rad_gh_regions[0]<br />rad_gh_regions[1]...<br />and so on
</td>
<td headers="r4c1 r1c3" align="left" colspan="1" rowspan="1">Size of the Shared Global Area in MBs divided by the number of RADs on the system
</td>
</tr></tbody>
</table>
<p>There are 63 rad_gh_regions parameters in the vm subsystem in Tru64 V5.1. Set only the parameters for the total number of RADs on the system. For example, if there are 4 RADs on the system (a GS160) and the SGA size is 10 GB, then set rad_gh_regions[0], rad_gh_regions[1], rad_gh_regions[2], and rad_gh_regions[3] to 2500. Note that you might have to raise this value slightly to 2501 or 2502 to successfully start the instance.
</p>
<p>If CPUs and memory are taken off-line, Oracle9<em>i</em> continues to function, but loses performance. If you anticipate frequent off-lining of RADs or equi-partitioning is not feasible, Oracle Corporation recommends running Oracle9<em>i</em> Real Application Clusters, using one instance per RAD. Using Oracle9<em>i</em> Real Application Clusters, you can configure individual instances with different sets of initialization parameters to match the actual RAD configuration. You can also start up or shut down specific instances without affecting overall application availability.
</p>
</div class="sect2">
<div class="sect2">
<!--
infolevel=all
infotype=general
--><a id="sthref697" name="sthref697"></a>
<h3>
<font face="arial, helvetica, sans-serif" color="#330099">
Process Affinity to RADs
</font>
</h3>
<p>You can improve performance by directing the operating system to run the processes on specific RADs. If connections to the database are made through the Oracle Listener process, and there is a corresponding network interconnect adapter on the RAD, you can run a listener on each RAD. To run the listener on a particular RAD, enter the following command:
</p>
<pre>$ runon -r lsnrctl start [<em>listener_name</em>]
</pre>
<p>All Oracle shadow processes are automatically created on the same RAD as the Oracle listener.
</p>
</div class="sect2">
</div class="sect1"><a id="CACDHFGE" name="CACDHFGE"></a>
<div class="sect1"><a id="sthref698" name="sthref698"></a>
<h2>
<font face="arial, helvetica, sans-serif" color="#330099">Supporting Mixed CPU Systems
</font>
</h2>
<p>Compaq systems using Tru64 V5.1A or higher can have mixed CPU speeds and types. All CPUs in a single RAD must have the same speed and cache size. Another RAD can have a set of CPUs with a different speed and cache size.
</p>
<p>The performance of a mixed CPU system depends on the proportion of slower CPUs to faster CPUs. Also, performance is affected by the placement of Oracle processes on the system. In a high transaction Online Transaction Processing (OLTP) environment, placing the database writer and log writer processes on the slower CPUs can adversely affect performance. In a data warehousing or decision support environment, placing the database writer and log writer processes on the slower CPUs might not be noticeable at all.
</p>
<p>The ability to mix CPU systems enables you to protect your hardware investment. You can add faster and more powerful CPUs to a system without needing to replace older CPUs. Compaq and Oracle Corporation have tested and support mixed CPU systems.
</p>
<div align="center">
<br /><table summary="This is a layout table to format a note" title="This is a layout table to format a note" dir="ltr" border="1" width="80%" frame="hsides" rules="groups" cellpadding="3" cellspacing="0"><tbody>
<tr align="left" valign="top">
<td align="left" colspan="1" rowspan="1">
<p>
<font face="arial, helvetica, sans-serif">
<strong>Note:</strong>
</font>
</p>You should not expect the mixed CPU system to perform as well as a system made up entirely of the fastest CPUs of the mixed CPU system. However, a mixed CPU system should perform better than a system made up entirely of the slowest CPUs of the mixed CPU system. Contact Compaq for a complete list of rules and restrictions for mixed CPU systems.
</td>
</tr></tbody>
</table><br />
</div>
</div class="sect1"><a id="i639382" name="i639382"></a>
<div class="sect1">
<!--
infolevel=all
infotype=general
--><a id="sthref699" name="sthref699"></a>
<h2>
<font face="arial, helvetica, sans-serif" color="#330099">Gathering Database Statistics on Tru64
</font>
</h2>
<p>Oracle9<em>i</em> release 2 (9.2.0.1.0) runs only on Tru64 UNIX V5.1 or higher. This is because Compaq changed the size of the long double data type from 64 bits on Tru64 UNIX V4.0x to 128 bits on Tru64 UNIX V5.<em>x</em>. This change causes certain Oracle operations to perform with increased precision. One of these operations stores statistics in the data dictionary after a table or index is analyzed.
</p>
<p>The query optimizer within the Oracle server uses the statistics stored in the data dictionary to determine how best to execute a query. If a stored statistic does not match a statistic calculated by the query optimizer while it searches for the best plan, the query optimizer might use the wrong plan to execute the query. This can cause the query to perform poorly or fail.
</p>
<p>For this reason, after upgrading from Oracle8<em>i</em> release 8.1.7 or lower to Oracle9<em>i</em> release 2 (9.2.0.1.0) you should analyze all object statistics for each schema. There is no need to reanalyze any schemas after upgrading from Oracle9<em>i</em> release 1 (9.0.1) to Oracle9<em>i</em> release 2. You can use the DBMS_STATS.GATHER_SCHEMA_STATS procedure to perform the analysis to gather statistics for each schema. The DBMS_STATS package saves the current table or index statistics in a table in case the new statistics cause problems.
</p>
<div align="center">
<br /><table summary="This is a layout table to format a tip" title="This is a layout table to format a tip" dir="ltr" border="1" width="80%" frame="hsides" rules="groups" cellpadding="3" cellspacing="0"><tbody>
<tr>
<td align="left" colspan="1" rowspan="1">
<p>
<font face="arial, helvetica, sans-serif">
<strong>See Also:</strong>
</font>
</p><em>Oracle9i Supplied PL/SQL Packages and Types Reference for more information on gathering database statistics.</em>
</td>
</tr></tbody>
</table><br />
</div>
</div class="sect1"><a id="i639373" name="i639373"></a>
<div class="sect1">
<!--
infolevel=all
infotype=general
--><a id="sthref700" name="sthref700"></a>
<h2>
<font face="arial, helvetica, sans-serif" color="#330099">Oracle9<em>i</em> Real Application Clusters on Tru64
</font>
</h2>
<p>This section describes Oracle9<em>i</em> Real Application Clusters on Tru64.
</p>
<div class="sect2">
<!--
infolevel=all
infotype=general
--><a id="sthref701" name="sthref701"></a>
<h3>
<font face="arial, helvetica, sans-serif" color="#330099">
<a id="sthref702" name="sthref702"></a>Reliable Data Gram
</font>
</h3>
<p>Reliable Data Gram (RDG) is an IPC infrastructure for the Tru64 TruCluster platform. It is the default IPC method for Oracle9<em>i</em> on Tru64 and is optimized for Oracle9<em>i</em> Real Application Clusters environments.
</p>
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="sthref703" name="sthref703"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Requirements
</font>
</h4>
<p>RDG requires that the node be a member of the cluster and connected through the memory channel. Oracle Corporation recommends that you set the node-wide operating system parameters listed in <a href="#g640536">Table D-1</a> when using RDG.
</p><a id="sthref704" name="sthref704"></a><a id="g640536" name="g640536"></a>
<p><strong><em><font face="arial, helvetica, sans-serif">Table D-1 RDG Subsystem Operating System Parameter Settings
</font></em></strong></p>
<table title="RDG Subsystem Operating System Parameter Settings " summary="This table describes the RDG subsystem operating system parameter settings." dir="ltr" border="1" width="100%" frame="hsides" rules="groups" cellpadding="3" cellspacing="0">
<thead>
<tr align="left" valign="top">
<th id="r1c1" align="left" colspan="1" rowspan="1" valign="bottom">
<font face="Arial, Helvetica, sans-serif">
<strong>Parameter
</strong></font></th>
<th id="r1c2" align="left" colspan="1" rowspan="1" valign="bottom">
<font face="Arial, Helvetica, sans-serif">
<strong>Setting
</strong></font></th>
</tr>
</thead><tbody>
<tr align="left" valign="top">
<td id="r2c1" headers="r1c1" align="left" colspan="1" rowspan="1"><a id="sthref705" name="sthref705"></a><a id="sthref706" name="sthref706"></a>max_objs
</td>
<td headers="r2c1 r1c2" align="left" colspan="1" rowspan="1">At least 5 times the number of Oracle processes per node and up to the larger of 10240 or the number of Oracle processes multiplied by 70.
</td>
</tr>
<tr align="left" valign="top">
<td id="r3c1" headers="r1c1" align="left" colspan="1" rowspan="1"><a id="sthref707" name="sthref707"></a><a id="sthref708" name="sthref708"></a>msg_size
</td>
<td headers="r3c1 r1c2" align="left" colspan="1" rowspan="1">Equal to or greater than the maximum value of the DB_BLOCK_SIZE parameter for the database.
<p>Oracle Corporation recommends a value of 32768 because Oracle9<em>i</em> supports different block sizes for each tablespace.
</p>
</td>
</tr>
<tr align="left" valign="top">
<td id="r4c1" headers="r1c1" align="left" colspan="1" rowspan="1"><a id="sthref709" name="sthref709"></a><a id="sthref710" name="sthref710"></a>max_async_req
</td>
<td headers="r4c1 r1c2" align="left" colspan="1" rowspan="1">At least 100 or the operating system default, whichever is larger.
<p><strong>Note</strong>: A value of 1000 or greater might provide better performance.
</p>
</td>
</tr>
<tr align="left" valign="top">
<td id="r5c1" headers="r1c1" align="left" colspan="1" rowspan="1"><a id="sthref711" name="sthref711"></a><a id="sthref712" name="sthref712"></a>max_sessions
</td>
<td headers="r5c1 r1c2" align="left" colspan="1" rowspan="1">At least the number of Oracle processes plus 2.
</td>
</tr>
<tr align="left" valign="top">
<td id="r6c1" headers="r1c1" align="left" colspan="1" rowspan="1"><a id="sthref713" name="sthref713"></a><a id="sthref714" name="sthref714"></a>rdg_max_auto_msg_wires
</td>
<td headers="r6c1 r1c2" align="left" colspan="1" rowspan="1">Must be set to 0.
</td>
</tr></tbody>
</table>
</div class="sect3">
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="sthref715" name="sthref715"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Enabling <a id="sthref716" name="sthref716"></a>UDP IPC
</font>
</h4>
<p>With Oracle9<em>i</em>, RDG is the default IPC method on Tru64. When the Oracle9<em>i</em> Real Application Clusters option is enabled, the Global Cache Service (GCS), Global Enqueue Service (GES), Interprocessor Parallel Query (IPQ), and Cache Fusion use RDG. The User Datagram Protocol (UDP) IPC implementation is still available but you must enable it explicitly.
</p>
<p>You must enable the Oracle9<em>i</em> Real Application Clusters option before enabling UDP IPC. To enable the Oracle9<em>i</em> Real Application Clusters option, use the Oracle Universal Installer or enter the following commands:
</p>
<pre>$ cd $ORACLE_HOME/rdbms/lib
$ make -f ins_rdbms.mk rac_on
$ make -f ins_rdbms.mk ioracle
</pre>
<p>To make the Oracle IPC routines use the UDP protocol, you must relink the <code>oracle</code> executable. Before performing the following steps, shut down all instances in the cluster.
</p>
<p>To enable UDP IPC, enter the following commands:
</p>
<pre>$ cd $ORACLE_HOME/rdbms/lib
$ make -f ins_rdbms.mk ipc_udp
$ make -f ins_rdbms.mk ioracle
</pre>
<p>To disable UDP IPC and revert to the default implementation for Oracle9<em>i</em> Real Application Clusters, enter the following commands:
</p>
<pre>$ cd $ORACLE_HOME/rdbms/lib
$ make -f ins_rdbms.mk rac_on
$ make -f ins_rdbms.mk ioracle
</pre>
</div class="sect3">
</div class="sect2"><a id="CHDDJJCI" name="CHDDJJCI"></a>
<div class="sect2"><a id="sthref717" name="sthref717"></a>
<h3>
<font face="arial, helvetica, sans-serif" color="#330099">
CLUSTER_INTERCONNECTS Initialization Parameter (Formerly TRU64_IPC_NET)
</font>
</h3>
<p>In Oracle9<em>i</em> release 2 (9.2.0.1.0) on Tru64 UNIX, the TRU64_IPC_NET parameter is replaced by the CLUSTER_INTERCONNECTS parameter. This parameter requires the IP address of the interconnect instead of the device name. The CLUSTER_ INTERCONNECTS parameter allows your system to specify multiple IP addresses. Oracle9<em>i</em> Real Application Clusters traffic is distributed between all of the specified IP addresses.
</p>
<p>The CLUSTER_INTERCONNECTS parameter is useful only if Oracle9<em>i</em> Real Application Clusters and UDP IPC are enabled. They enable users to specify an interconnect for all IPC traffic that includes Oracle GCS, GES, and IPQ.
</p>
<p>Use the CLUSTER_INTERCONNECTS parameter when the Memory Channel interconnect is overloaded. Overall cluster stability and performance might improve when you force Oracle GCS, GES, and IPQ over a different interconnect by setting the CLUSTER_INTERCONNECTS parameter. For example, to use the first fiber distributed data interface (FDDI) network controller whose IP address is 129.34.137.212 for all GCS, GES, and IPQ IPC traffic, set the CLUSTER_INTERCONNECTS parameter as follows:
</p>
<pre>CLUSTER_INTERCONNECTS=129.34.137.212
</pre>
<p>Use the <code>/usr/sbin/ifconfig -a</code> command to display the IP address of a device. This command provides a map between device names and IP addresses. To determine the IP address of a device, enter the following command:
</p>
<pre>$ /usr/sbin/ifconfig -a
fta0: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX> inet 129.34.137.212 netmask fffffc00 broadcast 129.34.139.255 ipmtu 1500lo0: flags=100c89<UP,LOOPBACK,NOARP,MULTICAST,SIMPLEX,NOCHECKSUM> inet 127.0.0.1 netmask ff000000 ipmtu 4096 mc0: flags=1100063<UP,BROADCAST,NOTRAILERS,RUNNING,NOCHECKSUM,CLUIF> inet 10.0.0.1 netmask ffffff00 broadcast 10.0.0.255 ipmtu 7000 sl0: flags=10<POINTOPOINT> tun0: flags=80<NOARP>
</pre>
<p>In the preceding example, device fta0: has an IP address of 129.34.137.212 and device mc0: has an IP address of 10.0.0.1.
</p>
<p>Remember the following important points when using the CLUSTER_INTERCONNECTS initialization parameter:
</p>
<ul>
<li type="disc">
<p>The CLUSTER_INTERCONNECTS parameter is used only when UDP is enabled as the IPC implementation.
</p>
</li>
<li type="disc">
<p>The IP addresses specified for the different instances of the same database on different nodes should belong to network adaptors that connect to the same network. If you do not follow this rule, internode traffic may pass through bridges and routers or there may not be a path between the two nodes at all.
</p>
</li>
<li type="disc">
<p>Specify the CLUSTER_INTERCONNECTS parameter in the instance-specific initialization parameter file. Do not specify the CLUSTER_INTERCONNECTS parameter in the common initialization parameter file because the devices on different nodes connected to the same network have different IP addresses.
</p>
</li>
<li type="disc">
<p>If you specify multiple IP addresses for this parameter, list them in the same order for all instances of the same database. For example, if the parameter for instance 1 on node 1 lists the IP addresses of the alt0, fta0 and mc0 devices in that order, the parameter for instance 2 on node 2 should list the IP addresses of the equivalent network adaptors in the same order.
</p>
</li>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -