#1146 - Table 'Phpmyadmin.Pma_Tracking' Doesn't Exist

#1146 - Table 'phpmyadmin.pma__tracking' doesn't exist

All the phpMyAdmin tables are defined in the SQL dump that comes with the package in sql/create_tables.sql. You can import that file in it's entirety (will also re-create any other tables you might have dropped) or just create the missing table by running this query:

CREATE TABLE IF NOT EXISTS `pma__tracking` (
  `db_name` varchar(64) NOT NULL,
  `table_name` varchar(64) NOT NULL,
  `version` int(10) unsigned NOT NULL,
  `date_created` datetime NOT NULL,
  `date_updated` datetime NOT NULL,
  `schema_snapshot` text NOT NULL,
  `schema_sql` text,
  `data_sql` longtext,
  `tracking` set('UPDATE','REPLACE','INSERT','DELETE','TRUNCATE','CREATE DATABASE','ALTER DATABASE','DROP DATABASE','CREATE TABLE','ALTER TABLE','RENAME TABLE','DROP TABLE','CREATE INDEX','DROP INDEX','CREATE VIEW','ALTER VIEW','DROP VIEW') default NULL,
  `tracking_active` int(1) unsigned NOT NULL default '1',
  PRIMARY KEY  (`db_name`,`table_name`,`version`)
)
  COMMENT='Database changes tracking for phpMyAdmin'
  DEFAULT CHARACTER SET utf8 COLLATE utf8_bin;

Switch to the phpmyadmin database. You can then use the "SQL" tab to execute this query directly on the database.

#1146 - Table 'phpmyadmin.pma__tracking' doesn't exist how to disable manually?

I just tested this with the phpMyAdmin I have installed and even when I deleted the table manually and got the error message, I could clear it up by logging out and logging back in again. So my first suggestion is to make sure your phpMyAdmin is rather up to date, as this feature has received some improvements in recent versions.

Next, I suggest you log out, clear your browser cache (at least as it relates to the phpMyAdmin page), and log in again.

You can either fix the table or disable that feature.

Repairing the phpMyAdmin Configuration Storage

Simply run the create_tables.sql file included in the examples or sql folder of your phpMyAdmin installation. You should edit the file if you wish to use a non-default database name or table names.

This could be more difficult if, for some reason, your phpMyAdmin still doesn't let you log in. In that case, you can either do it from the mysql command line client or disable the feature (see below) in order to gain access. That shouldn't be necessary, though; phpMyAdmin should automatically disable the feature on login if the table is missing.

Then edit config.inc.php and make sure the values assigned for each table correspond to the table names you just created. See http://docs.phpmyadmin.net/en/latest/config.html#cfg_Servers_pmadb for the list if you have any question about the default values.

Disabling the feature outright

Simply edit config.inc.php and remove the line $cfg['Servers'][$i]['tracking']. This will disable the feature entirely so that phpMyAdmin doesn't look for the tracking table.

#1146 - Table 'phpmyadmin.pma_recent' doesn't exist

You have to run the create_tables.sql inside the examples/ folder on phpMyAdmin to create the tables needed for the advanced features. That or disable those features by commenting them on the config file.

phpmyadmin.pma_table_uiprefs doesn't exist

You are missing at least one of the phpMyAdmin configuration storage tables, or the configured table name does not match the actual table name.

See http://docs.phpmyadmin.net/en/latest/setup.html#phpmyadmin-configuration-storage.

A quick summary of what to do can be:

1. On the shell: locate create_tables.sql.
2. import /usr/share/doc/phpmyadmin/examples/create_tables.sql.gz using phpMyAdmin.
3. open /etc/phpmyadmin/config.inc.php and edit lines 81-92: change pma_bookmark to pma__bookmark and so on.

I need this baby in a month - send me nine women!

The exact circumstances are obviously very specific to your project ( e.g. development team, management style, process maturity, difficulty of the subject matter, etc.). In order to scope this a bit better so we can speak about it in anything but sweeping oversimplifications, I'm going to restate your question:

Under what circumstances, if any, can adding team members to a software development project that is running late result in a reduction in the actual ship date with a level of quality equal to that if the existing team were allow to work until completion?

There are a number of things that I think are necessary, but not sufficient, for this to occur (in no particular order):

• The proposed individuals to be added to the project must have:
  
  • At least a reasonable understanding of the problem domain of the project
  • Be proficient in the language of the project and the specific technologies that they would use for the tasks they would be given
  • Their proficiency must /not/ be much less or much greater than the weakest or strongest existing member respectively. Weak members will drain your existing staff with tertiary problems while a new person who is too strong will disrupt the team with how everything they have done and are doing is wrong.
  • Have good communication skills
  • Be highly motivated (e.g. be able to work independently without prodding)
• The existing team members must have:
  
  • Excellent communication skills
  • Excellent time management skills
• The project lead/management must have:
  
  • Good prioritization and resource allocation abilities
  • A high level of respect from the existing team members
  • Excellent communication skills
• The project must have:
  
  • A good, completed, and documented software design specification
  • Good documentation of things already implemented
  • A modular design to allow clear chunks of responsibility to be carved out
  • Sufficient automated processes for quality assurance for the required defect level These might include such things as: unit tests, regression tests, automated build deployments, etc.)
  • A bug/feature tracking system that is currently in-place and in-use by the team (e.g. trac, SourceForge, FogBugz, etc).

One of the first things that should be discussed is whether the ship date can be slipped, whether features can be cut, and if some combinations of the two will allow you to satisfy release with your existing staff. Many times its a couple features that are really hogging the resources of the team that won't deliver value equal to the investment. So give your project's priorities a serious review before anything else.

If the outcome of the above paragraph isn't sufficient, then visit the list above. If you caught the schedule slip early, the addition of the right team members at the right time may save the release. Unfortunately, the closer you get to your expected ship date, the more things can go wrong with adding people. At one point, you'll cross the "point of no return" where no amount of change (other than shipping the current development branch) can save your release.

I could go on and on but I think I hit the major points. Outside of the project and in terms of your career, the company's future success, etc. one of the things that you should definitely do is figure out why you were late, if anything could have been done alert you earlier, and what measures you need to take to prevent it in the future. A late project usually occurs because you were either:

• Were late before you started (more
  stuff than time) and/or
• slipped 1hr, 1day at time.

Hope that helps!

phpMyAdmin is looking in the wrong DB for PMA_Tracking etc

Exactly the same thing happened to me :0) I figured out that the settings are stored in cookies. Just use our browser inspection tools to delete all the pma_* cookies.

---

Related Topics