Missing database function #_updcontroltable

11 years 11 months ago - 11 years 8 months ago #1 by geoffc
A problem has been identified where on a site restored from a backup the database function '#__updcontroltable' is not found in the database.

This is the same problem as explained in more detail in the 'Issue Tracker' Forum.

It is caused by the backup component not including the database function in the backup, hence when restored, the function cannot be found.

The backup component must be configured to backup up database procedures, functions and triggers, in order for them to be included in the backed up file.

In addition be aware that not all 'host' providers grant the appropriate database privileges to accounts, which means that the Joomla user connecting to the database may not even be able to see the function in order to back it up.

Read the thread in the Issue Tracker Forum for more details.

Regards
Geoff

Please Log in or Create an account to join the conversation.

11 years 8 months ago #2 by geoffc
A user has also recently reported this problem and they were using Akeeba backup, so this is to expand a little upon the earlier posting.

Note this problem is not an Akeeba Backup application problem, but more the way in which it is configured (or the impact of the permissions the web host provides to the backup process).

When Akeeba backup runs (or idead any backup program) it tries to back up all the tables, procedures, functions etc. Depending upon the web host and teh configuration, the backup prgram (Akeeba) may not be able to see the procedures and functions to back them up. The same thing happens with table triggers.

When Akeeba Kickstart does the restore it doesn't find the procedures in the backup because they were not placed there when the backup ran.

The easy solution is just to reinstall Password Control in the restored backup database and it will recreate the missing procedures etc. It will not effect any existing values or settings etc.

This does not however resolve any problems with the contents of the backup file(s).

To investigate further and confirm that the problem is backup related, one might want to check the settings that you are being used in the (Akeeba) backup program, as there is a parameter there which controls backup of procedures/functions etc.

Specifically for Akeeba Backup this is located in: Akeeba Configuration - Advanced Configuration - Database backup engine Configure , My SQL Settings, Checkmark Dump PROCEDUREs, FUNCTIONs and TRIGGERs

We are pleased that the user reporting the problem was able to change their backup settings and their problem was resolved.

As said earlier this will not resolve the problem if the web host doesn't permit procedures and functions to be seen by the backup process, even if the backup configuration parameters are correctly set up.

Our own particlar web host does not provide visibility of the procedures so they do not get into the backup file. On our internal hosts, where we have full control, we can see the procedures/functions written to the backup. Inspection of the log file created when the backup runs is worth checking to see if any procedures, functions or triggers are written to the backup file.

So to summarise, it is a feature (probably this, rather than the Akeeba parameter settings) that the web host from which the backup is taken, that is not permitting the Akeeba backup process to see the procedures/functions, hence they do not get written into the backup file.

We recommend that a good backup program is used on all sites, and we personally strongly recommend Akeeba Backup.

Regards
Geoff

Please Log in or Create an account to join the conversation.

Time to create page: 0.160 seconds
Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries