priv_check tablespace error

[Arantor]

Argh, I see the problem you're having.

The real question is if you have access to the underlying files on the server or not. If you do, it'll be a case of going spelunking to the database directory, if not your host will have to get involved.

I'm a bit surprised it got exported as part of a dump in the first place though.


Ultimately: a table is made up of several files. You seem to have the file that indicates where the data would go if there were a table, but not the file that contains the table structure.

[willerby]

Back to the host. I've outlined the issue as best I can in an email to them.

It would be nice to complete this upgrade and start rebuilding my forum.

[willerby]

Bluehost support very quickly moved the priv_check file - it appeared to be an orphaned ibd file (?) - so I cracked on with the upgrade routine.

Initially looked good... then bad... then good. On running upgrade.php, no longer had any tablespace error messages and could log-in to start the process.

However, the first options screen had red warnings re script.js being missing or out of date and after checking repair_settings.php I took a look again. It was all there and was the file downloaded from the upgrade zip folder (?) I decided to proceed anyway. I'm good at ignoring stuff I don't understand. 

After successful backup the database changes started but highlighted an 'Unknown Error' - see screenshot - and then appeared to stop on 5 of 71 - legacy attachments. However, even though it says 'Database Updates complete, tick continue to proceed' - the button was greyed out and I noticed that the % progresses referred to were still going up but hidden under there respective text heading - see image top left (Overall and Step Progress). This is probably just a browser (Firefox) widescreen issue.

The database changes apparently completed successfully and I was rewarded with a functioning SMF 2.0.3 forum - complete with its 280,000 posts.

I have no idea whether the errors highlighted will come back to haunt me so if anyone can suggest any checks to do - beyond the usual forum is working one - could you let me know?

Many thanks for the great support, particularly Arantor - again. Hoepfully I am away now to get back some mods and redevelop my theme.

Peter

[Arantor]

Yeah, the orphan ibd is what I alluded to earlier - every table in a database (normally) is made up of several files. There's a .frm file for its structure, .myd or .ibd for its data, .myi for indexes and so on.

Since the name of this file is the table's name (so, smf_priv_check.ibd or whatever), it can see if there is an ibd file without a matching frm, which is what it was complaining about.

script.js being out of date on upgrade is not usually a deal breaker as long as the upgrade's files were applied over the top of the regular files completely (so, everything in Sources and everything in Themes/default and all the subfolders)

As far as attachments are concerned, go find a topic with attachments, are they visible? My best guess without further digging is that the rename step wasn't carried out, assuming the attachments folder was correct in the settings (all attachments in 2.1 have a .dat extension now to avoid FileZilla messing with them)

[willerby]

Yep, you were right.

Now I could ask what to do about that but I thought I'd do a quick search and I found that my attachments settings had mysteriously been set to Array. Now I know that was not the case before I upgraded as I did a conscientious repair_settings.php and it was correctly set to /attachments. Oh well.

Anyway, I ran repair_settings.php again and reset it to the correct folder then ran upgrade.php again, checking the attachments upgrade in options (again).

And all good!

Topic finally solved.