database question

[Sufian]

I have version 2.2.9 on one server and 2.3.0 on a new server. I wanted to transfer the data from the 2.2.9 database to the 2.3.0 and when I try I keep getting errors about the columns not matching the rows.

What's the best way I can transfer the data from 2.2.9 to 2.3.0? I was thinking of going back to 2.2.9 on the second server, transfer data, then upgrade to 2.3.0 but I don't have the 2.2.9 files anymore.

[Cary]

If you're getting an unmatched column message it means you didn't upload all of the files for the new version.

Move the 2.2.9 database to your new server, upload then 2.3.0 files, then run admin/upgrade23.php

[Sufian]

What I did was I've already installed 2.3.0 on the new server. I guess I'll have to go back to 2.2.9 on it. Is there a copy of 2.2.9 in the members area?

Oh, I forgot to metion. The old server has some problems in its database so the only tables out of it that I wanted to transfer were the user, forum, and thread; basically so I don't loose the threads or the users. I don't want the entire database transfered.

[Steve Machol]

2.2.9 is not available. As Cary said you need to run upgrade23.php.

As for transferring only those three tables, that's not easy to do because of the interdependency among all the tables.

[Sufian]

Ok, I found 2.2.9 files in one of my hd's so I put 2.2.9 on the new server and I transfered most of the tables that I wanted over. The user table is still giving me problems, which I don't understand as it's 2.2.9 -> 2.2.9.

Here's one of the queries I entered (from the dump file created on the old server):

INSERT INTO user VALUES (2525, 2, 'etherscape', '804ecc3f1cb809d390233c24998787a1', '[email protected]', 1, '', 0, '', '172602472', 'AnimePrnstr', 'nexusceo', '', 1, 1, 0, 'Junior Member', 0, 1039503157, 1, -1, 1039552237, 1039767309, 1039503225, 1, '-5', 1, '', '', '', 1, 1, 1, 7, 15, '1983-12-05', -1, 1, '68.13.203.130', 0, 1, 0, 0, 0, 1, 0, '');

and this is what I get back:

Column count doesn't match value count at row 1

What am I doing wrong? How can I get this data to import properly into the user table on the new server?

[Steve Machol]

You said you have installed 2.3.0. If that's true then you need to do what both Cary and I have said - run upgrade23.php.

Also you cannot just transfer those three tables and expect it to work. You really should backup and reastore the entire database. At the very least you will need the user and userfield tables for the members info.

[Sufian]

Yes, Cory said to move the 2.2.9 database then run upgrade23.php. I've moved over most of the database. Doing one large dump would take me forever and has already crashed the old server once when tried. All the tables I've moved over have had no problems. The user table is the one that is giving me the error I mentioned above. I think it means mysql is not liking the # of values I have in my backup for the userid row?

Should I run upgrade23.php and then try importing the user table? I don't see how that would work, but I'm running out of ways to get this table to import. Again, all other tables have been moved without problems.

[Steve Machol]

You need to run upgrade23.php *after* transferring the database. You also need to transfer the userfield table since the user table is dependent on it.

[Sufian]

The userfield table is transfered. The user table is the only table I have left to transfer, and I keep getting "Column count doesn't match value count at row 1."

I've got about 5862 lines of insert statements in the user table dump file I have. When I try to transfer the entire table via phpmyadmin (telnet/ssh login on the server is a little problematic atm so I can't do it through there) the loading times out so I tried inputting manually a few insert statements at a time and I get that error for each insert statement I try.

[Hardwaregeeks]

I got it to work. when phpmyadmin created the backup of the tables it not only backed up the data but also the format of the table.

So what I have done is I droped the table on the new server and re created it with the backup.

It works not

only problem is that some of the tables are 50 to 700 MB in size and I have to do the comands 3000 at a time.