[otrs-cvs] doc-admin/en/content/installation upgrading.xml, 1.8, 1.9

"CVS commits notifications of OTRS.org" <[email protected]>
Newsgroups gmane.comp.otrs.cvs
Message-ID <[email protected]>
Comments:
Update of /home/cvs/doc-admin/en/content/installation
In directory lancelot:/tmp/cvs-serv17272/en/content/installation

Modified Files:
	upgrading.xml 
Log Message:
Added section on running otrs.CheckDB.pl to check for possible storage engine issues on MySQL.	

Author: mb

Index: upgrading.xml
===================================================================
RCS file: /home/cvs/doc-admin/en/content/installation/upgrading.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -2 -u -d -r1.8 -r1.9
--- upgrading.xml	22 Jan 2013 11:18:40 -0000	1.8
+++ upgrading.xml	24 Jan 2013 07:57:40 -0000	1.9
@@ -11,5 +11,5 @@
 <para>
     If you are running a lower version of OTRS you have to follow the upgrade path
-    to 3.0 first (1.1->1.2->1.3->2.0->2.1->2.2->2.3->2.4->3.0->3.1->3.2 ...)!
+    to 3.1 first (1.1->1.2->1.3->2.0->2.1->2.2->2.3->2.4->3.0->3.1->3.2 ...)!
 </para>
 <para>
@@ -134,8 +134,25 @@
         </para>
         <para>
+             Note: new tables created in the MySQL UPGRADING process will be created with the
+             default table storage engine set in your MySQL server.
+             In MySQL 5.5 the new default type is InnoDB.
+             If existing tables, e.g. "users", have the table storage engine e.g. MyISAM,
+             then an error will be displayed when creating the foreign key constraints.
+         </para>
+         <para>
+            You have two options: you can change the default storage engine of MySQL back to MyISAM
+            so that new tables will have the same engine as the existing tables,
+            or change the existing tables to use InnoDB as storage engine.
+        </para>
+        <para>
+            Any problems with regards to the storage engine will be reported by the
+            otrs.CheckDB.pl script, so please run it to check for possible issues.
+        </para>
+        <para>
             <screen>
 shell&gt; cd /opt/otrs/
 
 # MySQL:
+shell&gt; bin/otrs.CheckDB.pl
 shell&gt; cat scripts/DBUpdate-to-3.2.mysql.sql | mysql -p -f -u root otrs
 
@@ -148,16 +165,4 @@
         </para>
         <para>
-             Note: new tables created in the MySQL UPGRADING process will be created with the
-             default table storage engine set in your MySQL server.
-             In MySQL 5.5 the new default type is InnoDB.
-             If existing tables, e.g. "users", have the table storage engine e.g. MyISAM,
-             then an error will be displayed when creating the foreign key constraints.
-         </para>
-         <para>
-            You have two options: you can change the default storage engine of MySQL back to MyISAM
-            so that new tables will have the same engine as the existing tables,
-            or change the existing tables to use InnoDB as storage engine.
-        </para>
-        <para>
             Note: If you use PostgreSQL 8.1 or earlier, you need to activate the new legacy driver
             for these older versions. Do this by adding a new line to your <filename>Kernel/Config.pm</filename> like this:
---------------------------------------------------------------------
OTRS mailing list: cvs-log - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/cvs-log
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/cvs-log
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.