toc.htm

Debian中文参考手册,系统介绍了Debian系统

</tr></tbody>
</table><br />
</div>
</div class="sect3">
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="sthref23" name="sthref23"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Real Application Clusters Instance Management
</font>
</h4>
<p>After you have created a cluster database using DBCA, SYSDBA privileges are revoked for all users. As SYSDBA, you must grant SYSDBA privileges explicitly to the database user account that you plan to use for adding or deleting an instance to or from the cluster database. 
</p>
<p>For example, to grant SYSDBA privileges to the administrative user SYS, issue the following commands:
</p>
<pre>&#036; sqlplus "&#047; as sysdba"
SQL&gt; grant sysdba to sys;
SQL&gt; exit;
</pre>
</div class="sect3">
<div class="sect3"><a id="sthref24" name="sthref24"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Oracle Real Application Clusters and the IBM SP System
</font>
</h4>
<p>To ensure optimal performance of Oracle Real Application Clusters on an RS&#047;6000 node cluster using IBM&#039;s SP (Scalable POWERparallel) System, follow IBM&#039;s tuning instructions, which are available at the following Web sites:
</p>
<pre>http:&#047;&#047;www.rs6000.ibm.com&#047;support&#047;sp&#047;perf
http:&#047;&#047;www.ibm.com&#047;servers&#047;eserver&#047;pseries&#047;library&#047;wp&#095;clustering.html
</pre>
</div class="sect3">
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="sthref25" name="sthref25"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Additional Parameter Configuration for Real Application Clusters
</font>
</h4>
<p>To run Oracle Real Application Clusters, you must increase the UDP send buffer size to at least 32k (32768 bytes). To do this, become root and enter the following command:
</p>
<pre>&#036; &#047;etc no -udp&#095;sendspace&#061;32768

</pre>
<p>You must run this command after every system reboot. Review the current setting of the UDP send buffer size with the following command:
</p>
<pre>&#036; &#047;etc&#047;no -a&#124;grep udp&#095;sendspace
</pre>
</div class="sect3">
</div class="sect2">
</div class="sect1">
<div class="sect1">
<!--
infolevel=all
infotype=general
--><a id="i774797" name="i774797"></a>
<h2>
<font face="arial, helvetica, sans-serif" color="#330099">Post-Installation Issues
</font>
</h2>
<p>The following is a list of issues that can occur during post-installation:
</p>
<div class="sect2">
<!--
infolevel=all
infotype=general
--><a id="sthref26" name="sthref26"></a>
<h3>
<font face="arial, helvetica, sans-serif" color="#330099">
Control File Size Limits
</font>
</h3>
<p>In addition to the database, a number of other Oracle features use control files to record metadata. The maximum size of control files is limited by the size of the minimum data block size that your operating system permits. On AIX, the minimum data block size is 2048 bytes, and the maximum size of control files is 10000 database blocks.
</p>
</div class="sect2">
<div class="sect2">
<!--
infolevel=all
infotype=general
--><a id="sthref27" name="sthref27"></a>
<h3>
<font face="arial, helvetica, sans-serif" color="#330099">
How to Determine Whether Segments or Tablespaces are Using Compression
</font>
</h3>
<p>The following section provides additional information about database management.
</p>
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="sthref28" name="sthref28"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Segments and Compression Settings
</font>
</h4>
<p>To find out which database segments are using compression, log in to the database as the user SYS, and create the view <code>all&#095;segs</code> with the following create or replace view statement:
</p>
<pre>SQL&gt; create or replace view all&#095;segs
     (owner, segment&#095;name,
       partition&#095;name, spare1
as
select u.name, o.name, o.subname, s.spare1
from sys.user&#036; u, sys.obj&#036; o, sys.ts&#036; ts, sys.sys&#095;objects so,
     sys.seg&#036; s, sys.file&#036; f
where s.file&#035; &#061; so.header&#095;file
   and s.block&#035; &#061; so.header&#095;block
   and s.ts&#035; &#061; so.ts&#095;number
   and s.ts&#035; &#061; ts.ts&#035;
   and s.ts&#035; &#061; so.object&#095;id
   and o.owner&#035; &#061; u.user&#035;
   and s.type&#035; &#061; so.object&#095;type&#095;id
   and s.ts&#035; &#061; f.ts&#035;
   and s.file&#035; &#061; f.relfile&#035;
union all
select u.name, un.name, NULLL, NULL
from sys.user&#036; u, sys.ts&#036; ts, sys.undo &#036; un, sys.seg&#036; s,
     sys.file&#036; f
where s.file&#035; &#061; un.file&#035;
   and s.block&#035; &#061; un.block
   and s.ts&#035; &#061; un.ts&#035;
   and s.ts&#035; &#061; ts.ts&#035;
   and s.user&#035; &#061; u.user&#035;
   and s.type&#035; in (1, 10)
   and un.status&#036; !&#061; 1
   and un.ts&#035; &#061; f.ts&#035;
   and un.file&#035; &#061; f.relfile&#035;
union all
select u.name, to&#095;char(f.file&#035;)&#124;&#124; &#039;.&#039; &#124;&#124; to&#095;char(s.block&#035;), NULL, NULL
from sys.user&#036; u, sys.ts&#036; ts, sys.seg&#036; s, sys.file&#036; f
where s.ts&#035; &#061; ts.ts&#035;
   and s.user&#035; &#061; u.user&#035;
   and s.type&#035; not in (1, 5, 6, 8, 10)
   and s.ts&#035; &#061; f.ts&#035;
   and s.file&#035; &#061; f.relfile&#035;
&#047;

</pre>
<p>After creating this view, you can issue queries against the view to find out whether a segment currently is compressed, as illustrated in the following examples:
</p>
<ul>
<li type="disc">
<p>To determine if a segment is currently compressed, apply the following predicate in a query to the column <code>spare1</code>:
</p>
<pre>bitand(spare1, 2048) &gt; 0

</pre>
<p>For example, to see if segments currently are compressed, issue a statement similar to the following:
</p>
<pre>SQL&gt; select &#042; from all&#095;segs where bitand(spare1,2048) &gt; 0;

</pre>
</li>
<li type="disc">
<p>To determine if a segment contains any compressed blocks, apply the following predicate in a query:
</p>
<pre>bitand(spare1, 4096) &gt; 0

</pre>
<p>For example, to see which segments contain any compressed blocks, issue a statement similar to the following:
</p>
<pre>SQL&gt; select &#042; from all&#095;segs where bitand(spare1, 4096) &gt; 0;
</pre>
<p>
</p>
</li>
</ul>
</div class="sect3">
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="sthref29" name="sthref29"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Tablespaces and Compression Settings
</font>
</h4>
<p>When you want to determine compression settings on a table space, log in as SYS, and create the view <code>compression&#095;ts</code> with the following create or replace view statement:
</p>
<pre>SQL&gt; create or replace view compression&#095;ts (tablespace&#095;name, flags) as select ts.name, ts.flags from
sys.ts&#036; ts where ts.online&#036; !&#061;3;

</pre>
<p>After creating this view, you can issue queries against it to find out the compression state of tablespaces, such as determining if a tablespace is currently set as DEFAULT COMPRESS, or DEFAULT NOCOMPRESS, as illustrated in the following examples:
</p>
<ul>
<li type="disc">
<p>To determine if a tablespace is currently set as DEFAULT COMPRESS, use the following predicate:
</p>
<pre>bitand(flags, 64) &gt; 0

</pre>
<p>For example, to see which tablespaces are currently DEFAULT COMPRESS, issue a statement similar to the following:
</p>
<pre>SQL&gt; select &#042; from compression&#095;ts where bitand(flags, 64) &gt; 0

</pre>
</li>
<li type="disc">
<p>To determine if a tablespace is currently set as DEFAULT NOCOMPRESS, use the following predicate:
</p>
<pre>bitand(flags, 64) &#061;&#061; 0

</pre>
<p>For example, to see which tablespaces are currently DEFAULT NOCOMPRESS, issue a statement similar to the following:
</p>
<pre>select &#042; from compression&#095;ts where bitand(flags, 64) &#061;&#061; 0;
</pre>
</li>
</ul>
</div class="sect3">
</div class="sect2">
</div class="sect1">
<div class="sect1">
<!--
infolevel=all
infotype=general
--><a id="CHDHJHCH" name="CHDHJHCH"></a>
<h2>
<font face="arial, helvetica, sans-serif" color="#330099">Known Bugs
</font>
</h2>
<p>The following is a list of known bugs that affect Oracle9<em>i</em> release 2 (9.2.0.1.0): 
</p>
<div class="sect2">
<!--
infolevel=all
infotype=general
--><a id="sthref30" name="sthref30"></a>
<h3>
<font face="arial, helvetica, sans-serif" color="#330099">
Network Failover for Real Application Clusters
</font>
</h3>
<p>Due to a problem with the IBM clustering software (IBM tracking number PMR 23819, 550), network failover is not supported for this release with Real Application Clusters using HACMP&#047;ES CRM.
</p>
</div class="sect2">
<div class="sect2">
<!--
infolevel=all
infotype=general
--><a id="sthref31" name="sthref31"></a>
<h3>
<font face="arial, helvetica, sans-serif" color="#330099">
Error Installing OLAP CWMLITE Tablespace
</font>
</h3>
<p>During installation, if you select Online Analytic Processing (OLAP) services, perform multiple installations on the same system, and create new databases during these installations, then CWMLite may have an invalid OLAP CWMLITE tablespace registry. Oracle Corporation has assigned bug identification number 2359208 to track this problem.
</p>
<p>To work around this problem, use the following procedure after you have completed installation:
</p>
<ol type="1" start="1">
<li>
<p>Ensure that the database and the listener are running.
</p>
</li>
<li>
<p>Using the following command, start SQL&#042;Plus as the administrative user SYS:
</p>
<pre>sqlplus "&#047; as sysdba"

</pre>
</li>
<li>
<p>Using the following command, enable the display of text within the PL&#047;SQL block:
</p>
<pre>SQL&gt; set serveroutput on;

</pre>
</li>
<li>
<p>Using the following command, verify whether the OLAP CWMLITE tablespace is valid:
</p>
<pre>SQL&gt; execute dbms&#095;output.put&#095;line(sys.dbms&#095;registry.is&#095;valid(&#039;AMD&#039;));

</pre>
<p>If the preceding command returns <code>0</code>, then the OLAP CWMLITE tablespace is invalid. Go to step 5.
</p>
<p>If the preceding command returns <code>1</code>, then the OLAP CWMLITE tablespace is valid, and no further testing needs to be done.
</p>
</li>
<li>
<p>If the OLAP CWMLITE tablespace is invalid, turn on echoing with the following command:
</p>
<pre>SQL&gt; execute cwm2&#095;olap&#095;manager.Set&#095;Echo&#095;on;

</pre>
</li>
<li>
<p>Validate the OLAP CMWLITE tablespace with the following command:
</p>
<pre>SQL&gt; execute cwm2&#095;olap&#095;installer.Validate&#095;CWM2&#095;Install;

</pre>
<p>After entering the preceding command, the OLAP CWMLITE registry is validated. During this process, screen messages list database objects such as Dimension, Dimension Attribute, and Level, and where these objects are created.
</p>
</li>
<li>
<p>When the output stops, enter the following command to verify that the OLAP CWMLITE registry is now valid:
</p>
<pre>SQL&gt; execute dbms&#095;output.put&#095;line(sys.dbms&#095;registry.is&#095;valid(&#039;AMD&#039;));

</pre>
<p>If the preceding command returns <code>0</code>, then the OLAP CWMLITE registry is still invalid. Review your installation logs for other errors.
</p>
<p>If the preceding command returns 1, then the OLAP CWMLITE tablespace is valid, and no further testing needs to be done.
</p>
</li>
</ol>
</div class="sect2">
</div class="sect1">
</p>
</div>
<!-- Start Footer -->
<div>
<hr />
<table cellspacing="0" cellpadding="0" width="100%">
<tr>
<td valign="bottom" width="33%">
<table cellspacing="0" cellpadding="0">
<tr>
</tr>
</table>
</td>
<td align="center" width="34%">
<a href="../../dcommon/html/cpyr.htm">
<img src="../../dcommon/gifs/oracle.gif" alt="Oracle Logo" border="0"><br />
<font size="-2">Copyright&nbsp;&copy;&nbsp;2002&nbsp;Oracle&nbsp;Corporation</font></a>
<br />
<font size="-2">All&nbsp;rights&nbsp;reserved</font>
</td>
<td valign="bottom" align="right" width="33%">
<table cellspacing="0" cellpadding="0" width="144">
</tr>
</tr>
</table>
</td>
</tr>
</table>
</div>
</body>
</html>