| List: | Commits | « Previous MessageNext Message » | |
| From: | paul | Date: | May 19 2008 9:11pm |
| Subject: | svn commit - mysqldoc@docsrva: r10775 - in trunk: . it/refman-5.1 pt/refman-5.1 | ||
| View as plain text | |||
Author: paul Date: 2008-05-19 21:11:22 +0200 (Mon, 19 May 2008) New Revision: 10775 Log: r31508@frost: paul | 2008-05-19 14:09:48 -0500 Sync translations Modified: trunk/it/refman-5.1/errors-problems-core.xml trunk/pt/refman-5.1/errors-problems-core.xml Property changes on: trunk ___________________________________________________________________ Name: svk:merge - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31507 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31325 + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31508 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31325 Modified: trunk/it/refman-5.1/errors-problems-core.xml =================================================================== --- trunk/it/refman-5.1/errors-problems-core.xml 2008-05-19 19:11:15 UTC (rev 10774) +++ trunk/it/refman-5.1/errors-problems-core.xml 2008-05-19 19:11:22 UTC (rev 10775) Changed blocks: 16, Lines Added: 130, Lines Deleted: 62; 13793 bytes @@ -2293,6 +2293,32 @@ </section> + <section id="table-corruption"> + + <title>Table-Corruption Issues</title> + + <para> + If you have started <command>mysqld</command> with + <option>--myisam-recover</option>, MySQL automatically checks + and tries to repair <literal>MyISAM</literal> tables if they + are marked as 'not closed properly' or 'crashed'. If this + happens, MySQL writes an entry in the + <literal>hostname.err</literal> file <literal>'Warning: + Checking table ...'</literal> which is followed by + <literal>Warning: Repairing table</literal> if the table needs + to be repaired. If you get a lot of these errors, without + <command>mysqld</command> having died unexpectedly just + before, then something is wrong and needs to be investigated + further. + </para> + + <para> + See also <xref linkend="server-options"/>, and + <xref linkend="reproducible-test-case"/>. + </para> + + </section> + </section> <section id="installation-issues"> @@ -2576,8 +2602,8 @@ <title>Resetting the Root Password on Windows Systems</title> <para> - The procedure for resetting the MySQL root account's - password on Windows is as follows: + The procedure for resetting the password for any MySQL + <literal>root</literal> accounts on Windows is as follows: </para> <orderedlist> @@ -2611,15 +2637,29 @@ <listitem> <para> - Create a text file and place the following command - within it on a single line: + Create a text file and place the following statements in + it. Replace the password with the password that you want + to use. </para> <programlisting> -SET PASSWORD FOR 'root'@'localhost' = PASSWORD('MyNewPassword'); +UPDATE mysql.user SET Password=PASSWORD('MyNewPass') WHERE User='root'; +FLUSH PRIVILEGES; </programlisting> <para> + The <literal>UPDATE</literal> and + <literal>FLUSH</literal> statements each must be written + on a single line. The <literal>UPDATE</literal> + statement resets the password for all existing + <literal>root</literal> accounts, and the + <literal>FLUSH</literal> statement tells the server to + reload the grant tables into memory. + </para> + </listitem> + + <listitem> + <para> Save the file with any name. For this example, the file will be <filename>C:\mysql-init.txt</filename>. </para> @@ -2627,7 +2667,7 @@ <listitem> <para> - Open a console window to get to the DOS command prompt: + Open a console window to get to the command prompt: </para> <programlisting> @@ -2637,14 +2677,15 @@ <listitem> <para> - We are assuming that you installed MySQL to + We assume that you installed MySQL to <filename>C:\mysql</filename>. If you installed MySQL to another location, adjust the following commands accordingly. </para> <para> - At the DOS command prompt, execute this command: + Start the MySQL server with the special + <option>--init-file</option> option: </para> <programlisting> @@ -2652,21 +2693,19 @@ </programlisting> <para> - The contents of the file named by the - <option>--init-file</option> option are executed at - server startup, changing the <literal>root</literal> - password. + The server executes the contents of the file named by + the <option>--init-file</option> option at startup, + changing each <literal>root</literal> account password. </para> - </listitem> - <listitem> <para> - After the server has started successfully, delete - <filename>C:\mysql-init.txt</filename>. + You can also add the <option>--console</option> option + to the command if you want server output to appear in + the console window rather than in a log file. </para> <para> - If you install MySQL using the MySQL Installation + If you installed MySQL using the MySQL Installation Wizard, you may need to specify a <option>--defaults-file</option> option: </para> @@ -2696,21 +2735,27 @@ <listitem> <para> - Stop the MySQL server, then restart it in normal mode - again. If you run the server as a service, start it from - the Windows Services window. If you start the server - manually, use whatever command you normally use. + After the server has started successfully, delete + <filename>C:\mysql-init.txt</filename>. </para> </listitem> <listitem> <para> - You should be able to connect using the new password. + Stop the MySQL server, then restart it in normal mode + again. If you run the server as a service, start it from + the Windows Services window. If you start the server + manually, use whatever command you normally use. </para> </listitem> </orderedlist> + <para> + You should now be able to connect to MySQL as + <literal>root</literal> using the new password. + </para> + </section> <section id="resetting-permissions-unix"> @@ -2730,17 +2775,33 @@ </formalpara> <para> - In a Unix environment, the procedure for resetting the MySQL - <literal>root</literal> password is as follows: + In a Unix environment, the procedure for resetting the + password for any MySQL <literal>root</literal> accounts on + Unix follows. The following instructions assume that you + will start the server so that it runs using the same Unix + login account that you normally use for running the server. + For example, if you run the server using the + <literal>mysql</literal> login account, you should log in as + <literal>mysql</literal> before using the instructions. + (Alternatively, you can log in as <literal>root</literal> + and start <command>mysqld</command> with the + <option>--user=mysql</option> option. If you start the + server as <literal>root</literal> without using + <option>--user</option>, the server may create + <literal>root</literal>-owned files in the data directory, + such as log files, and these may cause permission-related + problems for future server startups. If that happens, you + must either change the ownership of the files to + <literal>mysql</literal> or remove them.) </para> <orderedlist> <listitem> <para> - Log on to your system as either the Unix - <literal>root</literal> user or as the same user that - the <command>mysqld</command> server runs as. + Log on to your system as the Unix + <literal>mysql</literal> user that the + <command>mysqld</command> server runs as. </para> </listitem> @@ -2753,7 +2814,7 @@ <filename>/var/lib/mysql/</filename>, <filename>/var/run/mysqld/</filename>, and <filename>/usr/local/mysql/data/</filename>. Generally, - the filename has the extension of + the filename has an extension of <filename>.pid</filename> and begins with either <filename>mysqld</filename> or your system's hostname. </para> @@ -2780,15 +2841,29 @@ <listitem> <para> - Create a text file and place the following command - within it on a single line: + Create a text file and place the following statements in + it. Replace the password with the password that you want + to use. </para> <programlisting> -SET PASSWORD FOR 'root'@'localhost' = PASSWORD('MyNewPassword'); +UPDATE mysql.user SET Password=PASSWORD('MyNewPass') WHERE User='root'; +FLUSH PRIVILEGES; </programlisting> <para> + The <literal>UPDATE</literal> and + <literal>FLUSH</literal> statements each must be written + on a single line. The <literal>UPDATE</literal> + statement resets the password for all existing + <literal>root</literal> accounts, and the + <literal>FLUSH</literal> statement tells the server to + reload the grant tables into memory. + </para> + </listitem> + + <listitem> + <para> Save the file with any name. For this example, the file will be <filename>/home/me/mysql-init</filename>. The file contains the password, so it should not be saved @@ -2798,8 +2873,8 @@ <listitem> <para> - Restart the MySQL server with the special - <option>--init-file=/home/me/mysql-init</option> option: + Start the MySQL server with the special + <option>--init-file</option> option: </para> <programlisting> @@ -2807,8 +2882,9 @@ </programlisting> <para> - The contents of the init-file are executed at server - startup, changing the root password. + The server executes the contents of the file named by + the <option>--init-file</option> option at startup, + changing each <literal>root</literal> account password. </para> </listitem> @@ -2819,17 +2895,16 @@ </para> </listitem> - <listitem> - <para> - You should be able to connect using the new password. - </para> - </listitem> - </orderedlist> <para> + You should now be able to connect to MySQL as + <literal>root</literal> using the new password. + </para> + + <para> Alternatively, on any platform, you can set the new password - using the <command>mysql</command> client(but this approach + using the <command>mysql</command> client (but this approach is less secure): </para> @@ -2838,9 +2913,7 @@ <listitem> <para> Stop <command>mysqld</command> and restart it with the - <option>--skip-grant-tables --user=root</option> options - (Windows users omit the <option>--user=root</option> - portion). + <option>--skip-grant-tables</option> option. </para> </listitem> @@ -2851,37 +2924,31 @@ </para> <programlisting> -shell> <userinput>mysql -u root</userinput> +shell> <userinput>mysql</userinput> </programlisting> </listitem> <listitem> <para> Issue the following statements in the - <command>mysql</command> client: + <command>mysql</command> client. Replace the password + with the password that you want to use. </para> <programlisting> -mysql> <userinput>UPDATE mysql.user SET Password=PASSWORD('<replaceable>newpwd</replaceable>')</userinput> +mysql> <userinput>UPDATE mysql.user SET Password=PASSWORD('MyNewPass')</userinput> -> <userinput>WHERE User='root';</userinput> mysql> <userinput>FLUSH PRIVILEGES;</userinput> </programlisting> - - <para> - Replace <quote><replaceable>newpwd</replaceable></quote> - with the actual <literal>root</literal> password that - you want to use. - </para> </listitem> - <listitem> - <para> - You should be able to connect using the new password. - </para> - </listitem> - </orderedlist> + <para> + You should now be able to connect to MySQL as + <literal>root</literal> using the new password. + </para> + </section> </section> @@ -5264,8 +5331,9 @@ <para> You can't use <quote><literal>_</literal></quote> or <quote><literal>%</literal></quote> with - <literal>ESCAPE</literal> in <literal>LIKE ... - ESCAPE</literal>. + <literal>ESCAPE</literal> in + <function role="sqlop" condition="like">LIKE ... + ESCAPE</function>. </para> </listitem> Modified: trunk/pt/refman-5.1/errors-problems-core.xml =================================================================== --- trunk/pt/refman-5.1/errors-problems-core.xml 2008-05-19 19:11:15 UTC (rev 10774) +++ trunk/pt/refman-5.1/errors-problems-core.xml 2008-05-19 19:11:22 UTC (rev 10775) Changed blocks: 16, Lines Added: 130, Lines Deleted: 62; 13793 bytes @@ -2293,6 +2293,32 @@ </section> + <section id="table-corruption"> + + <title>Table-Corruption Issues</title> + + <para> + If you have started <command>mysqld</command> with + <option>--myisam-recover</option>, MySQL automatically checks + and tries to repair <literal>MyISAM</literal> tables if they + are marked as 'not closed properly' or 'crashed'. If this + happens, MySQL writes an entry in the + <literal>hostname.err</literal> file <literal>'Warning: + Checking table ...'</literal> which is followed by + <literal>Warning: Repairing table</literal> if the table needs + to be repaired. If you get a lot of these errors, without + <command>mysqld</command> having died unexpectedly just + before, then something is wrong and needs to be investigated + further. + </para> + + <para> + See also <xref linkend="server-options"/>, and + <xref linkend="reproducible-test-case"/>. + </para> + + </section> + </section> <section id="installation-issues"> @@ -2576,8 +2602,8 @@ <title>Resetting the Root Password on Windows Systems</title> <para> - The procedure for resetting the MySQL root account's - password on Windows is as follows: + The procedure for resetting the password for any MySQL + <literal>root</literal> accounts on Windows is as follows: </para> <orderedlist> @@ -2611,15 +2637,29 @@ <listitem> <para> - Create a text file and place the following command - within it on a single line: + Create a text file and place the following statements in + it. Replace the password with the password that you want + to use. </para> <programlisting> -SET PASSWORD FOR 'root'@'localhost' = PASSWORD('MyNewPassword'); +UPDATE mysql.user SET Password=PASSWORD('MyNewPass') WHERE User='root'; +FLUSH PRIVILEGES; </programlisting> <para> + The <literal>UPDATE</literal> and + <literal>FLUSH</literal> statements each must be written + on a single line. The <literal>UPDATE</literal> + statement resets the password for all existing + <literal>root</literal> accounts, and the + <literal>FLUSH</literal> statement tells the server to + reload the grant tables into memory. + </para> + </listitem> + + <listitem> + <para> Save the file with any name. For this example, the file will be <filename>C:\mysql-init.txt</filename>. </para> @@ -2627,7 +2667,7 @@ <listitem> <para> - Open a console window to get to the DOS command prompt: + Open a console window to get to the command prompt: </para> <programlisting> @@ -2637,14 +2677,15 @@ <listitem> <para> - We are assuming that you installed MySQL to + We assume that you installed MySQL to <filename>C:\mysql</filename>. If you installed MySQL to another location, adjust the following commands accordingly. </para> <para> - At the DOS command prompt, execute this command: + Start the MySQL server with the special + <option>--init-file</option> option: </para> <programlisting> @@ -2652,21 +2693,19 @@ </programlisting> <para> - The contents of the file named by the - <option>--init-file</option> option are executed at - server startup, changing the <literal>root</literal> - password. + The server executes the contents of the file named by + the <option>--init-file</option> option at startup, + changing each <literal>root</literal> account password. </para> - </listitem> - <listitem> <para> - After the server has started successfully, delete - <filename>C:\mysql-init.txt</filename>. + You can also add the <option>--console</option> option + to the command if you want server output to appear in + the console window rather than in a log file. </para> <para> - If you install MySQL using the MySQL Installation + If you installed MySQL using the MySQL Installation Wizard, you may need to specify a <option>--defaults-file</option> option: </para> @@ -2696,21 +2735,27 @@ <listitem> <para> - Stop the MySQL server, then restart it in normal mode - again. If you run the server as a service, start it from - the Windows Services window. If you start the server - manually, use whatever command you normally use. + After the server has started successfully, delete + <filename>C:\mysql-init.txt</filename>. </para> </listitem> <listitem> <para> - You should be able to connect using the new password. + Stop the MySQL server, then restart it in normal mode + again. If you run the server as a service, start it from + the Windows Services window. If you start the server + manually, use whatever command you normally use. </para> </listitem> </orderedlist> + <para> + You should now be able to connect to MySQL as + <literal>root</literal> using the new password. + </para> + </section> <section id="resetting-permissions-unix"> @@ -2730,17 +2775,33 @@ </formalpara> <para> - In a Unix environment, the procedure for resetting the MySQL - <literal>root</literal> password is as follows: + In a Unix environment, the procedure for resetting the + password for any MySQL <literal>root</literal> accounts on + Unix follows. The following instructions assume that you + will start the server so that it runs using the same Unix + login account that you normally use for running the server. + For example, if you run the server using the + <literal>mysql</literal> login account, you should log in as + <literal>mysql</literal> before using the instructions. + (Alternatively, you can log in as <literal>root</literal> + and start <command>mysqld</command> with the + <option>--user=mysql</option> option. If you start the + server as <literal>root</literal> without using + <option>--user</option>, the server may create + <literal>root</literal>-owned files in the data directory, + such as log files, and these may cause permission-related + problems for future server startups. If that happens, you + must either change the ownership of the files to + <literal>mysql</literal> or remove them.) </para> <orderedlist> <listitem> <para> - Log on to your system as either the Unix - <literal>root</literal> user or as the same user that - the <command>mysqld</command> server runs as. + Log on to your system as the Unix + <literal>mysql</literal> user that the + <command>mysqld</command> server runs as. </para> </listitem> @@ -2753,7 +2814,7 @@ <filename>/var/lib/mysql/</filename>, <filename>/var/run/mysqld/</filename>, and <filename>/usr/local/mysql/data/</filename>. Generally, - the filename has the extension of + the filename has an extension of <filename>.pid</filename> and begins with either <filename>mysqld</filename> or your system's hostname. </para> @@ -2780,15 +2841,29 @@ <listitem> <para> - Create a text file and place the following command - within it on a single line: + Create a text file and place the following statements in + it. Replace the password with the password that you want + to use. </para> <programlisting> -SET PASSWORD FOR 'root'@'localhost' = PASSWORD('MyNewPassword'); +UPDATE mysql.user SET Password=PASSWORD('MyNewPass') WHERE User='root'; +FLUSH PRIVILEGES; </programlisting> <para> + The <literal>UPDATE</literal> and + <literal>FLUSH</literal> statements each must be written + on a single line. The <literal>UPDATE</literal> + statement resets the password for all existing + <literal>root</literal> accounts, and the + <literal>FLUSH</literal> statement tells the server to + reload the grant tables into memory. + </para> + </listitem> + + <listitem> + <para> Save the file with any name. For this example, the file will be <filename>/home/me/mysql-init</filename>. The file contains the password, so it should not be saved @@ -2798,8 +2873,8 @@ <listitem> <para> - Restart the MySQL server with the special - <option>--init-file=/home/me/mysql-init</option> option: + Start the MySQL server with the special + <option>--init-file</option> option: </para> <programlisting> @@ -2807,8 +2882,9 @@ </programlisting> <para> - The contents of the init-file are executed at server - startup, changing the root password. + The server executes the contents of the file named by + the <option>--init-file</option> option at startup, + changing each <literal>root</literal> account password. </para> </listitem> @@ -2819,17 +2895,16 @@ </para> </listitem> - <listitem> - <para> - You should be able to connect using the new password. - </para> - </listitem> - </orderedlist> <para> + You should now be able to connect to MySQL as + <literal>root</literal> using the new password. + </para> + + <para> Alternatively, on any platform, you can set the new password - using the <command>mysql</command> client(but this approach + using the <command>mysql</command> client (but this approach is less secure): </para> @@ -2838,9 +2913,7 @@ <listitem> <para> Stop <command>mysqld</command> and restart it with the - <option>--skip-grant-tables --user=root</option> options - (Windows users omit the <option>--user=root</option> - portion). + <option>--skip-grant-tables</option> option. </para> </listitem> @@ -2851,37 +2924,31 @@ </para> <programlisting> -shell> <userinput>mysql -u root</userinput> +shell> <userinput>mysql</userinput> </programlisting> </listitem> <listitem> <para> Issue the following statements in the - <command>mysql</command> client: + <command>mysql</command> client. Replace the password + with the password that you want to use. </para> <programlisting> -mysql> <userinput>UPDATE mysql.user SET Password=PASSWORD('<replaceable>newpwd</replaceable>')</userinput> +mysql> <userinput>UPDATE mysql.user SET Password=PASSWORD('MyNewPass')</userinput> -> <userinput>WHERE User='root';</userinput> mysql> <userinput>FLUSH PRIVILEGES;</userinput> </programlisting> - - <para> - Replace <quote><replaceable>newpwd</replaceable></quote> - with the actual <literal>root</literal> password that - you want to use. - </para> </listitem> - <listitem> - <para> - You should be able to connect using the new password. - </para> - </listitem> - </orderedlist> + <para> + You should now be able to connect to MySQL as + <literal>root</literal> using the new password. + </para> + </section> </section> @@ -5264,8 +5331,9 @@ <para> You can't use <quote><literal>_</literal></quote> or <quote><literal>%</literal></quote> with - <literal>ESCAPE</literal> in <literal>LIKE ... - ESCAPE</literal>. + <literal>ESCAPE</literal> in + <function role="sqlop" condition="like">LIKE ... + ESCAPE</function>. </para> </listitem>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r10775 - in trunk: . it/refman-5.1 pt/refman-5.1 | paul | 19 May 2008 |
© 1995-2008 MySQL AB. All rights reserved.
Page generated in 0.617 sec. using MySQL 5.1.14-beta-log