OJS OCS OMP OHS

You are viewing the PKP Support Forum | PKP Home Wiki



Migration enquiry 1.1.8 to 2.0.2

Are you responsible for making OJS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.

Moderators: jmacgreg, btbell, michael, bdgregg, barbarah, asmecher

Forum rules
What to do if you have a technical problem with OJS:

1. Search the forum. You can do this from the Advanced Search Page or from our Google Custom Search, which will search the entire PKP site. If you are encountering an error, we especially recommend searching the forum for said error.

2. Check the FAQ to see if your question or error has already been resolved.

3. Post a question, but please, only after trying the above two solutions. If it's a workflow or usability question you should probably post to the OJS Editorial Support and Discussion subforum; if you have a development question, try the OJS Development subforum.

Migration enquiry 1.1.8 to 2.0.2

Postby enri » Fri Jan 20, 2006 11:03 am

I am now managing a journal running OJS 1.1.8 with some modifications on the code and database.

When I try to use the import tools in OJS 2.0.2 to import the data in 1.1.8 to 2.0.2, I receive an error:

    DB Error: Duplicate entry 'g' for key 2
After that, I can see the OJS 2.0.2 have a journal entry with no issue & article in the database.
Interestingly, I can see 171 users in the database of the ojs2.
I tried to delete the 172th user in the ojs1 database but the same error occur.

My system is working with the following environment:
    OS platform WINNT
    PHP version 4.4.1
    Apache version Apache/2.0.55 (Win32) PHP/4.4.1
    Database driver mysql
    Database server version 4.1.10

Is there any way I can do to know what is going wrong?

Is there any advice for my upgrade?

Thanks a lot.
enri
 
Posts: 12
Joined: Fri Jan 20, 2006 11:00 am

Postby asmecher » Fri Jan 20, 2006 12:17 pm

Hi enri,

It sounds like you've got multiple users sharing the same username in your OJS 1 database, which shouldn't be possible with a stock installation as OJS 1.x creates a unique index on the username column. Check for this situation using the following query on your OJS 1 database:
Code: Select all
SELECT chUsername, COUNT(nUserId) AS count FROM tblusers GROUP BY chUsername HAVING count > 1
You'll have to resolve any entries that you find before the migration will complete successfully.

Regards,
Alec Smecher
Open Journal Systems Team
asmecher
 
Posts: 8315
Joined: Wed Aug 10, 2005 12:56 pm

Postby enri » Mon Feb 06, 2006 5:59 am

Thank you for your support reply.

I rename all European character in the user database and it works. (For 2.0.2.1)

However, the Author name (appeared in issue page) would be cut starting from the European character.

I try to upgrade from 2.0.2.1 to 2.1, it works (with the author name issue)

1.1.8 directly upgrade to 2.1 would be failed (possibly because of the Author name)

What would be the best way to handle this? Do not use the European characters, or any other tricks?

Please advise.
enri
 
Posts: 12
Joined: Fri Jan 20, 2006 11:00 am

Postby asmecher » Mon Feb 06, 2006 12:18 pm

Hi Enri,

OJS 2.1 supports character set transcoding in the 1.x => 2.x migration process; have you tried using that option? I'd also suggest, if you've got a fairly recent DBMS, using the database charset and connection charset options. (These are chosen during the install process.)

Regards,
Alec Smecher
Open Journal Systems Team
asmecher
 
Posts: 8315
Joined: Wed Aug 10, 2005 12:56 pm


Return to OJS Technical Support

Who is online

Users browsing this forum: Bing [Bot] and 8 guests