So I contacted NFO about trying to import my databases from an old website to this one and it would give me an error, of course about not having access to the information_schema. I was told by them that NFO does not use that database, and so on. This means my databases are basically null and void for importing, and I'm kind of screwed. I really want to use NFO's web hosting because it'll save me from the other current website situation I'm in (trying to move from old host to NFO) and I thought I could make things easier by doing so.
Is there any possible way around this at all in any way?
If not, I will keep my NFO website plan but will attempt to find an extremely cheap host, or just a free mysql database host (I don't think that's a thing) - But if you guys know any if this is what it comes to, then please refer me to them so I can place my databases on there.
MySQL information_schema access
-
Jerpy
- A regular
- Posts: 37
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Fri Jan 30, 2015 10:08 am
Re: MySQL information_schema access
/thread
soja has resolved this completely by this point via other communication
soja has resolved this completely by this point via other communication
Re: MySQL information_schema access
As someone who often Googles for answers, I hate it when I come across a question somewhere with "I fixed it" as a follow-up but no explanation of how.
I've seen an error similar to this from customers who have an application that tries to find the status of its own running queries but is meant for older versions of MySQL with weaker security. If this was true for you, then updating the application or adjusting it to use the "show full processlist" command instead of attempting to access the table directly would be the fix.
If it's just an issue with importing, then you'd want to look at the .sql file and see what command is causing it to fail. It is possible that something was included in the export which shouldn't have been (such as the "mysql" database), and in that case, you could delete it by hand.
I've seen an error similar to this from customers who have an application that tries to find the status of its own running queries but is meant for older versions of MySQL with weaker security. If this was true for you, then updating the application or adjusting it to use the "show full processlist" command instead of attempting to access the table directly would be the fix.
If it's just an issue with importing, then you'd want to look at the .sql file and see what command is causing it to fail. It is possible that something was included in the export which shouldn't have been (such as the "mysql" database), and in that case, you could delete it by hand.
Re: MySQL information_schema access
The issue here was with his old database hosting. For some strange reason when trying to export the database it would only give a partial export. When exporting all databases associated with the account, information_schema as well as the partial database would be exported.
I do not know why the export wouldn't work, in phpmyadmin we tried exporting all of the tables by checking them and clicking export, as well as selecting the database and using the export tool. Ultimately we ended up going just using mysqldump on a remote linux machine to get the database. After we had the database backup that contained everything, importing worked fine, and based on preliminary testing the database works.
I do not know why the export wouldn't work, in phpmyadmin we tried exporting all of the tables by checking them and clicking export, as well as selecting the database and using the export tool. Ultimately we ended up going just using mysqldump on a remote linux machine to get the database. After we had the database backup that contained everything, importing worked fine, and based on preliminary testing the database works.
Not a NFO employee