Fatal error: Can’t open and lock privilege tables: Table ‘mysql.host’ doesn’t exist(we can find this info in /var/log/mysqld.log)

Follow the following steps, MySQL will be installed(all wrt Linux)

1. shell > rm -rf /var/lib/mysql

2. Install mysql rpms.

3. Go to directory where mysql binaries are installed(mysqld_safe, mysql etc)

4. ./mysql_install_db –user=mysql –ldata=/mysqldata (where mysqldata is my data directory for MySQL database. datadir can be specified in /etc/my.cnf file, then we can ignore here)

If it gives a message that hostname is not set or conflict in hostname, then use
./mysql_install_db –user=mysql –ldata=/mysqldata –force

5. MySQL is installed, start MySQL server now,
./mysqld_safe –user=mysql &

Congrats, MySQL is up and running….

When MySQL is Installed, MySQL client does not have any password. It will contain four users, root@localhost, root@localhost.localdomain, ”@localhost, ”@localhost.localdomain(” – anonymous user).
Delete all users at localhost.localdomain and all anonymous users. Set password for root@localhost using

shell > mysql

mysql > drop user root@localhost.localdomain;

mysql > drop user ”@localhost;

mysql > drop user ”@localhost.localdomain;

mysql > set password for root@localhost = password(‘mysqlroot’);

mysql > flush privileges;

mysql > \q

shell >

Flush Privileges will tell server that password is set for root.

MySQL is installed and password is set for mysql client.

Some times, One Year seems to be very big, but some times, I feel, its OK. Here, are two sides of working in a startup company.

Pros

1. Scope to learn/work (as much as you can – there is no question that, you are not given any work, especially in product development companies)

2. Chance to learn about Resource Management. Team will be small, so you see how they are handled.

3. Growth factor - Here also, willing to learn plays major role.

4. Ownership of module – You are given a module, You are sole proprietor of module. You are free to design in whichever way you like, as long as you are good enough to make people to buy your design.

5. You develop more than one skill in a start up and you become master in your specialization.

6. Better rapport with team members as team is small.

Cons

1. Getting a Leave every now and then is Tough.

2. Have to Google for many things. ( Train yourself )

3. Some times, get bugged with work.

I am both In (70%) and Out (30%) for working for a start up.

Relevant to the above is this blog post by Kamla bhatt. Make sure you do read the comments too.

MySQL Errors like 1062(Duplicate Entry), 2002(Server is not started), 2006(Server has gone away) are easy to identify and solve. 2013 signifies lost connection to server in midst of query execution.

2013 is frustrating because, you can’t produce it again for same sequence of actions. So you never know when it will come or when it won’t.

Finally, I have come up with few points to look for when MySQL Error 2013 occurs.

1. check for MySQL Status
shell> mysql -u root -p -e “\s” | grep Uptime

It will give uptime of MySQL Server. If it is less than 1 min, then server must have gone down and started again. So, you have look for Status Variable wait_timeout. By default, wait-timeout will be 28800 sec (8 Hours). Developer can change it while starting a server(change has to be done in my.cnf file) or by setting parameter “CLIENT_INTERACTIVE” in “mysql_real_connect()”. If Uptime is not less than a min, then there is a problem with Query.

Query can be too long or it is syntactically correct but not semantically.

Example: I am running a stored procedure spLogin(uname, pword, status). Here uname and pword are input parameters and status output parameter. To supply input to this stored procedure, I use user defined variables.

So, order of queries will be
mysql > SET @user = ’sarma’, @passwd = ’sarma’;
mysql > call spLogin(@username, @password, @status);
There is a chance that it will give an error 2013, as query is syntactically correct, but values passed to query are garbage.

Remedy will be
mysql> call spLogin(@user, @passwd, @status);
query Success(if stored procedure is correct).

But as I said earlier, it is tough to reproduce Error 2013. Care should be taken in passing inputs to either Queries or Stored Procedures and wait_timeout should be atleast 4 Hrs.

I question them what is the advantage of working in a MNC which is not in a start-up. They told me that when you are swicthing from one job to other job, there will be less risk and you need not to advertize about your company, you carry a brand name, if you work in a MNC. My reasoning to them is, Why should I think of swicthing my job before joining in that? If I am not satisfied with the work I am doing or If I am not fit into the team , then only I think of swicthing job. So doing work is my priority, which I certainly get in a start-up. I am not sure whether I’ll be assigned work from Day 1, if I join in a MNC. I am not against working in MNCs, they have their own headaches. Its true that Resource Management is the toughest thing. The reason, I opted for start-up is if I work for some time, then I can get job in MNC at any time. But if join in a MNC and happened to be on bench (or member of Freepool), then it would be tough.

Working in a start-up gives you the next best chance to see how a company shapes up.(Best chance to see is to start a company). Working in a start-up has other advantage, you can watch the building process of a company very closely,you know ups and downs in making it Big. More importantly, every one’s voice is heard in a start-up, so u can raise your voice, you can take part in design discussions, brain storming sessions. This is all happens in MNCs also, but you need to gain some experience, before raising your voice.