Hello,
I've finally found some time to upgrade my VaultWiki 3.0.20 PL1 to VaultWiki 4.0.4. I've followed all the steps mentioned in the
blog. Thank you very much for this great guide! However, I finally ran out of luck...
When I clicked on "Import/Export" and picked "Vault Wiki 3" I got an error at step 13 ("Importing wiki pages").
This is the SQL-Error message I got:
Code:
[...]
Invalid SQL:
SELECT `t`.`threadid` AS `threadid`,`t`.`title` AS `title`,`t`.`forumid` AS `forumid`,`t`.`visible` AS `visible`,`t`.`dateline` AS `dateline`,`p`.`postid` AS `postid`,`p`.`pagetext` AS `post_pagetext`,`p`.`userid` AS `userid`,`p`.`username` AS `username`,`p`.`attach` AS `attach`,`p`.`ipaddress` AS `ipaddress`,`p2`.`options` AS `protect`,`t`.`prefixid` AS `prefixid`,`a`.`groupid` AS `groupid`,`a`.`languageid` AS `languageid` FROM `vb_thread` `t` LEFT JOIN `vb_vault_article` `a` ON (`t`.`threadid` = `a`.`threadid`)
LEFT JOIN `vb_post` `p` ON (`t`.`threadid` = `p`.`threadid` AND `p`.`parentid` = 0)
LEFT JOIN `vb_vault_protect` `p2` ON (`t`.`threadid` = `p2`.`targetid`) WHERE `t`.`forumid` IN (818,819,820,822,823,827) ORDER BY `t`.`threadid` ASC LIMIT 0,100;
MySQL-Fehler : The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay
Fehler-Nr. : 1104
Fehler-Zeit : Friday, 05.06.2015 @ 13:01:27
Datum : Friday, 05.06.2015 @ 13:01:27
Skript : xxx/backup/admin_cp/wiki_cp.php?panel=impex&do=import&step=13&nostyle=1
Referrer : xxx/backup/admin_cp/wiki_cp.php?panel=impex&do=import&step=12&nostyle=1
IP-Adresse : xxx
Benutzername : xxxxx
Klassenname : vB_Database
MySQL-Version : 5.5.42-37.1-log
Now that "Max-Join-Size" issue strikes me as oddly familiar... I recall having similiar issue, when I updated from vBulletin 4.2.0 to 4.2.2 about 2 years ago. Back then, the support told me that I should increase the value of the MAX_JOIN_SIZE and so I called my hoster and asked them about it. They told me that the value already is around 200 millions, so that wasn't causing the problems. The support over at vBulletin couldn't help me either and so I tried to find a work around on my own. I finally found out that my styles were causing the errors. Once I had reduced the number of styles, the upgrade completed successfully.
But now it has happend again during the import script for VaultWiki and I wonder if there's anything I can do about it. I don't think it is related to the number of styles this time, but I'm afraid that the number of forums and threads is causing this. Could that be the case? I have 3 Wikis in three forums on my board, but they don't have that many threads. And of course there's the images-forum, the categories and the books..., but that's pretty much about it. What I do have are several other forums, threads and posts apart from the wiki, because my site is quite old.
Could you please help me to find a solution for this issue, because I really want to update my version of VW3, since some users are not able to view the wiki properly. (There's an "infinite loop error" when viewing a wiki page for one user, but it works fine for all the others..). Finally, the time has come to try out something new now and I'd be glad to hear from you, Pegasus.
Thanks!
~Kirauni
PS: Maybe there's a work around if I added
Code:
$vbulletin->db->query_write("
SET SQL_BIG_SELECTS=1"
);
somwhere? But I don't know where to put it. Any ideas?
June 5, 2015 7:26 AM
Junior Member
Please Wait