So the situation is:
1. Server A had a MySQL database running from a mounted drive (a custom, not default location)
2. The mounted drive crashed, but fortunately the databases were saved elsewhere
3. The accounts from Server A were transferred to a new Server B
4. The databases were restored to the new Server B through the root account
The problem is:
The accounts on server B are not connecting to or showing the new databases when accessed via phpMyAdmin or any php script.
Further notes:
a. The databases DO show up on the CPanel of the accounts under "MySQL databases". CPanel shows the size correctly and all the tables correctly when trying to repair or check the tables directly through CPanel.
b. The mysql database location on the new server B is the default MySQL directory which is different from the location that was on Server A. And I think this is the problem. Is there any place where an account can have a specific mysql directory set that is different from that specified by my.cnf?
1. Server A had a MySQL database running from a mounted drive (a custom, not default location)
2. The mounted drive crashed, but fortunately the databases were saved elsewhere
3. The accounts from Server A were transferred to a new Server B
4. The databases were restored to the new Server B through the root account
The problem is:
The accounts on server B are not connecting to or showing the new databases when accessed via phpMyAdmin or any php script.
Further notes:
a. The databases DO show up on the CPanel of the accounts under "MySQL databases". CPanel shows the size correctly and all the tables correctly when trying to repair or check the tables directly through CPanel.
b. The mysql database location on the new server B is the default MySQL directory which is different from the location that was on Server A. And I think this is the problem. Is there any place where an account can have a specific mysql directory set that is different from that specified by my.cnf?