User Tools

Site Tools


daily_issues

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

daily_issues [2010/09/07 17:16]
k2patel
daily_issues [2020/08/10 02:35]
Line 1: Line 1:
-==== Mysql Upgrade Issue ==== 
- 
-==== Easy Command List ==== 
- 
-== How to check Type of Table == 
-You can use any of the following command to determine table type. 
- 
-<code mysql> 
-SHOW TABLE STATUS WHERE Name = '​table_name';​ 
-OR 
-SHOW CREATE TABLE '​table_name';​ 
-OR 
-SHOW TABLE STATUS; 
-</​code>​ 
- 
- 
- 
-==== MySQL Cluster information gathering ==== 
- 
-=== How to find which master log slave reading === 
-<code mysql> 
-cat slaves | while read i ; do echo $i; mysql -h$i -e "SHOW SLAVE STATUS \G" | grep "​Relay_Master_Log_File";​ done 
-</​code>​ 
- 
-=== How continue with the next statement in the replication === 
- 
-NOTE : Make sure you run the query manually on slave if it is query issue. 
- 
-<code mysql> 
-STOP SLAVE; SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1;​ START SLAVE; 
-</​code>​ 
- 
-==== Issue / Solutions ==== 
- 
- 
-== Â appeared after upgrade == 
- 
- This issue is appeared due to the default character set.\\ 
- As Both version of database diff. character set. 
- To get rid of that character try to following steps. 
- 
-<code text> 
-  1. insert following line to your my.cnf 
-     ​set-variable=character-set-server=UTF8 
-  2. re-import database should fix the issue. 
-</​code>​ 
- 
-== mysqldump does not save stored procedure / functions / triggers. == 
- 
-By default mysqldump only store triggers not procedures/​functions. 
- 
-In order to include to your mysqldump there is switch \\ 
--R, --routines ​     Dump stored routines (functions and procedures). 
- 
-In order to include triggers to your mysqldump there is switch \\ 
---triggers ​ Dump triggers for each dumped table 
- 
-<code mysql> 
-mysqldump -R -u <​username>​ -p<​password>​ <​database>​ 
-</​code>​ 
- 
- 
-== After upgrade from 4.0 to 4.1 see issue on charset == 
- 
-Use following line in your my.cnf will resolve the issue. 
-as latin1 is default character set in 4.0 and 4.1 has utf8 
- 
-<code text | my.cnf> 
- ​set-variable=character-set-server=latin1 
-</​code>​ 
- 
- 
  
daily_issues.txt · Last modified: 2020/08/10 02:35 (external edit)