Krydos

It looks like Johnny's postgresql configuration was overwritten at some point. Probably during an upgrade. Does it work now?

I logged in to your account and it worked fine on the first try for me. What browser are you using?

The databases listed should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected databases. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The databases listed should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected databases. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

Thanks! As a free service we don't have an advertising budget because we would rather invest all of the money that we do have into providing better service and improving the servers so we really appreciate the word of mouth recommendations that our satisfied users provide. Feel free to post about us on social media like twitter, facebook, hosting review sites, your personal websites or blogs, and anything else you can think of. As long as we have clients using our service Heliohost will continue to exist.

The database rulrok_wordpress should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

ALTER TABLE table_name ENGINE=MyISAM;

We always recommended Myisam because it's more stable and less prone to crashing and less prone to corruption, but you can use whatever you want. If you need some features that are specific to InnoDB that aren't available on Myisam then you don't have a choice. If your tables are already using InnoDB from the backup it's not that big of a deal to leave then that way for simplicity.

Did you delete the database first and recreate it?

It looks like gastenboek and the other broken tables haven't been changed since April 2012. Do you have a backup since then? EDIT: I just answered my own question. Sitting in your /home1/huulie home directory you have a full backup from July 2012. Try deleting that whole database, and restoring it from the .sql file backup. Let us know if you need assistance with this or further instruction on how to go about it. I suspect that your tables that don't work were using the InnoDB engine and since InnoDB was broken for so long my script isn't working to make them visible again to you. Since your backup is three months after the last change to those tables there should be no data loss.

The database vholtta_presents should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

What database engine does this table use?

MySQL strict mode has been disabled on all servers. Details can be found in the latest news post: http://www.helionet.org/index/topic/22545-mysql-strict-mode-disabled/

The database cbapps_wp312 should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The database oz_xohmz_wpdb should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

/home1/yolveiro/public_html/claro/sistemas/listado_productos_re.php It's causing ridiculous php and postgresql load on the database yolveiro_claro. Please fix it immediately or your account will likely be suspended again.

The databases listed should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected databases. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The databases listed should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected databases. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

@cbapps Your topic has been split to http://www.helionet.org/index/topic/22536-cbapps-phpmyadmin/

Thanks! As a free service we don't have an advertising budget because we would rather invest all of the money that we do have into providing better service and improving the servers so we really appreciate the word of mouth recommendations that our satisfied users provide. Feel free to post about us on social media like twitter, facebook, hosting review sites, your personal websites or blogs, and anything else you can think of. As long as we have clients using our service Heliohost will continue to exist.

Try backing up the database, delete the database entirely, recreate it, and restore the data from the backup. I suspect that since InnoDB was broken for so long and was recently reenabled the old broken InnoDB tables are still causing you issues.

The database huulie_MUSICONLINEdevriendschap should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

I was able to create it just fine mysql> create table j25_update_sites_extensions (id int(6) unsigned auto_increment primary key, data varchar(30) not null); Query OK, 0 rows affected (0.07 sec) mysql> describe j25_update_sites_extensions; +-------+-----------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +-------+-----------------+------+-----+---------+----------------+ | id | int(6) unsigned | NO | PRI | NULL | auto_increment | | data | varchar(30) | NO | | NULL | | +-------+-----------------+------+-----+---------+----------------+ 2 rows in set (0.19 sec) mysql> drop table j25_update_sites_extensions; Query OK, 0 rows affected (0.01 sec) What database user are you using to try to create the table?

The database allmovie_wp should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.