MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:martin.brown Date:August 20 2009 12:28pm
Subject:svn commit - mysqldoc@docsrva: r16209 - in trunk: refman-5.1 refman-5.4 refman-6.0
View as plain text  
Author: mcbrown
Date: 2009-08-20 14:28:05 +0200 (Thu, 20 Aug 2009)
New Revision: 16209

Log:
Fixing Docs Bug #40843



Modified:
   trunk/refman-5.1/se-db2-core.xml
   trunk/refman-5.4/se-db2-core.xml
   trunk/refman-6.0/se-db2-core.xml


Modified: trunk/refman-5.1/se-db2-core.xml
===================================================================
--- trunk/refman-5.1/se-db2-core.xml	2009-08-20 12:19:17 UTC (rev 16208)
+++ trunk/refman-5.1/se-db2-core.xml	2009-08-20 12:28:05 UTC (rev 16209)
Changed blocks: 3, Lines Added: 18, Lines Deleted: 3; 1911 bytes

@@ -61,10 +61,11 @@
 
     <para>
       The engine is built as a dynamic plugin and so must be installed
-      by using the following command: INSTALL PLUGIN ibmdb2i SONAME
-      <literal>ha_ibmdb2i.so</literal>;
+      by using the following command:
     </para>
 
+<programlisting>mysql&gt; INSTALL PLUGIN ibmdb2i SONAME ha_ibmdb2i.so;</programlisting>
+
   </section>
 
   <section id="se-db2-configuration">

@@ -652,7 +653,7 @@
           <literal>INTEGER</literal> field. For most data types, this
           mapping is transparent. Data types which have restrictions
           unique to <literal>IBMDB2I</literal> are documented in
-          <literal>Notes and Limitations</literal>
+          <xref linkend="se-db2-notes"/>.
         </para>
 
       </section>

@@ -930,6 +931,20 @@
 
       <listitem>
         <para>
+          When using multiples instances of MySQL on a single i5 host
+          you should be aware that the two independent instances will
+          access the same database within the DB2 environment. This can
+          lead to namespace collisions and issues. To get round this
+          limitation, you should configure different IBM i independent
+          auxilliary storage pools (ISAPs) for each MySQL server, and
+          then use the <literal>ibmdb2i_rdb_name</literal> option to
+          MySQL to configure which IASP should be used for each MySQL
+          instance.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Indexes over <literal>VARBINARY</literal> columns may not
           provide accurate estimates the optimizer. Queries over such
           indexes may produce error 2027 in the error log but will


Modified: trunk/refman-5.4/se-db2-core.xml
===================================================================
--- trunk/refman-5.4/se-db2-core.xml	2009-08-20 12:19:17 UTC (rev 16208)
+++ trunk/refman-5.4/se-db2-core.xml	2009-08-20 12:28:05 UTC (rev 16209)
Changed blocks: 3, Lines Added: 18, Lines Deleted: 3; 1911 bytes

@@ -56,10 +56,11 @@
 
     <para>
       The engine is built as a dynamic plugin and so must be installed
-      by using the following command: INSTALL PLUGIN ibmdb2i SONAME
-      <literal>ha_ibmdb2i.so</literal>;
+      by using the following command:
     </para>
 
+<programlisting>mysql&gt; INSTALL PLUGIN ibmdb2i SONAME ha_ibmdb2i.so;</programlisting>
+
   </section>
 
   <section id="se-db2-configuration">

@@ -647,7 +648,7 @@
           <literal>INTEGER</literal> field. For most data types, this
           mapping is transparent. Data types which have restrictions
           unique to <literal>IBMDB2I</literal> are documented in
-          <literal>Notes and Limitations</literal>
+          <xref linkend="se-db2-notes"/>.
         </para>
 
       </section>

@@ -925,6 +926,20 @@
 
       <listitem>
         <para>
+          When using multiples instances of MySQL on a single i5 host
+          you should be aware that the two independent instances will
+          access the same database within the DB2 environment. This can
+          lead to namespace collisions and issues. To get round this
+          limitation, you should configure different IBM i independent
+          auxilliary storage pools (ISAPs) for each MySQL server, and
+          then use the <literal>ibmdb2i_rdb_name</literal> option to
+          MySQL to configure which IASP should be used for each MySQL
+          instance.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Indexes over <literal>VARBINARY</literal> columns may not
           provide accurate estimates the optimizer. Queries over such
           indexes may produce error 2027 in the error log but will


Modified: trunk/refman-6.0/se-db2-core.xml
===================================================================
--- trunk/refman-6.0/se-db2-core.xml	2009-08-20 12:19:17 UTC (rev 16208)
+++ trunk/refman-6.0/se-db2-core.xml	2009-08-20 12:28:05 UTC (rev 16209)
Changed blocks: 3, Lines Added: 17, Lines Deleted: 3; 1719 bytes

@@ -56,10 +56,11 @@
 
     <para>
       The engine is built as a dynamic plugin and so must be installed
-      by using the following command: INSTALL PLUGIN ibmdb2i SONAME
-      <literal>ha_ibmdb2i.so</literal>;
+      by using the following command:
     </para>
 
+<programlisting>mysql&gt; INSTALL PLUGIN ibmdb2i SONAME ha_ibmdb2i.so;</programlisting>
+
   </section>
 
   <section id="se-db2-configuration">

@@ -647,7 +648,7 @@
           <literal>INTEGER</literal> field. For most data types, this
           mapping is transparent. Data types which have restrictions
           unique to <literal>IBMDB2I</literal> are documented in
-          <literal>Notes and Limitations</literal>
+          <xref linkend="se-db2-notes"/>.
         </para>
 
       </section>

@@ -921,6 +922,19 @@
 
     <title>Notes and Limitations</title>
 
+    <listitem>
+      <para>
+        When using multiples instances of MySQL on a single i5 host you
+        should be aware that the two independent instances will access
+        the same database within the DB2 environment. This can lead to
+        namespace collisions and issues. To get round this limitation,
+        you should configure different IBM i independent auxilliary
+        storage pools (ISAPs) for each MySQL server, and then use the
+        <literal>ibmdb2i_rdb_name</literal> option to MySQL to configure
+        which IASP should be used for each MySQL instance.
+      </para>
+    </listitem>
+
     <itemizedlist>
 
       <listitem>


Thread
svn commit - mysqldoc@docsrva: r16209 - in trunk: refman-5.1 refman-5.4 refman-6.0martin.brown20 Aug