Support

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:

Hi
I've been asked to migrate and update an old 1.5 website from a backup made with joomlapack.

It all seems to work OK until right at the end of the database restoration, when it stops with the following error:

Error at the line 193: CREATE OR REPLACE ALGORITHM=UNDEFINED VIEW `#__jf_languages` AS select `l`.`lang_id` AS `lang_id`,`l`.`lang_code` AS `lang_code`,`l`.`title` AS `title`,`l`.`title_native` AS `title_native`,`l`.`sef` ... MySQL: MySQL query failed with error 1054 (Unknown column 'l.lang_id' in 'field list'). The query was:CREATE OR REPLACE ALGORITHM=UNDEFINED VIEW `jos_jf_languages` AS select `l`.`lang_id` AS `lang_id`,`l`.`lang_code` AS `lang_code`,`l`.`title` AS `title`,`l`.`title_native` AS `title_native`,`l`.`sef` AS `sef`,`l`.`description` AS `description`,`l`.`published` AS `published`,`l`.`image` AS `image`,`lext`.`image_ext` AS `image_ext`,`lext`.`fallback_code` AS `fallback_code`,`lext`.`params` AS `params`,`lext`.`ordering` AS `ordering` from (`jos_languages` `l` left join `jos_jf_languages_ext` `lext` on((`l`.`lang_id` = `lext`.`lang_id`))) order by `lext`.`ordering`

i've tried several times and it just won't get past this. I have no idea what to do. Can you help?

Regards
David

If possible, please retry your backup with the newest Akeeba Backup compatible with your version of PHP. You can find that information on our Compatibility page here: https://www.akeebabackup.com/downloads/compatibility.html.

Getting a support ticket for JoomlaPack is a wonderful walk down memory lane, but newer is better.

Hi Dale
No can do - this backup is all I have of this site, so I can't change anything until I can install it again.

As you can see, that isn't a table, it is a view. JoomlaPack was the very beginning of being able to back up that type of data structure at all, I was hoping that a Joomla! 1.5 compatible version of Akeeba might do a better job of it. I'm going to ask Nicholas to take a look at this to see if he has any suggestions on how we might get this to restore successfully.

Thanks Dale
If there is no other way, I'll just delete that line and see what I can do.
Regards
David

1. I don’t remember if this is an option in the old JPI in JoomlaPack. If it is, there should be a “Suppress foreign key checks” option when restoring the backup. He can check it and it will restore.
2. If this option doesn’t exist OR if it doesn’t help, all is not lost. He can follow the emergency restoration procedure which hasn’t changed much since Joomla! 1.5. The trick is that in step 3 he should find the lines with CREATE OR REPLACE VIEW and remove them. After doing an emergency restoration, he should try doing a regular restoration again with the old tables option set to BACKUP and the VIEWs will be created normally.

You are really testing our memory here. :-)

What he's talking about in step 2 is to do the manual restore and skip the problem VIEW. This will create the remaining tables, etc. Then do a normal restore just like you're trying to do now. The underlying tables that the VIEW depends on will exist now and it can be created.

Hi again
Thanks for the info.
The first point you mention regarding suppression: that is an option but it didn't help, as it's activated by default.

I wanted to try the manual method, after reading the emergency documentation.
I couldn't work out where to add the prefix, as all I could see (in the 190 part files) was the format

#_ INTO `#__ja_website_activity

as an example. Should I replace both # with the prefix? or only the second?

Sorry to be such a pain, but there are thousands of lines at stake, so I want to do it right.

A further question: I've downloaded "BigDump". Can it read the files joomla.s01, etc files? Should I include the database.ini file and the joomla.sql file ?
Thanks in advance

That line doesn't look right.

#_ INTO `#__ja_website_activity

The #_INTO part strikes me as strange. As Nicholas says in the instructions, you can't just search and replace the place holder #__ with the table prefix. Some components use the #__ in their data and it will really mess things up. You have to do the search and replaces like he has them in the instructions.

I have never used BigDump. They say "files" at some points on the website, but I couldn't see what the naming requirements were if it really was using multiple input files. The database.ini file is the MySQL connection information on the backed up site. You will need the joomla.sql file, that's a part of the SQL dump set.

You should be able to concatenate those 190 files to make them easier to deal with.

COPY joomla.s?? site.s01
COPY site.s01+joomla.s??? site.sql

That should copy all the parts with two digit sequence numbers to site.s01, then copy the site.s01 plus all the parts with three digit sequence numbers to site.sql. The command would be non-destuctive for the dump files, so if it takes a couple of tries to get it right it should still be worth it. I don't remember if the s??? will pick up the two digit sequence numbers again. It will show you what it's doing, so you don't have to guess.

I had a friend who also had an ancient backup. I've installed that and the problem didn't occur.I appreciate all the help, as always. You guys are the best!

Regards
David

I'm glad you got it going!

Yea - several thousand users and postings - everything working more or less as it should. I want to attempt an upgrade - fingers crossed :-)

Again thanks for the great support.

David

You are welcome!