| Author |
WCS 5.1 to WC 5.6 Migration Issue
|
|
| Niranjan Soni 2004-11-18, 5:54 pm |
| Hi
I am currently working on migrating WCS 5.1 websites to WC 5.6 and facing a
some problem at the time of database migration. I am migrating unencrypted
data using the migratedb script as described in the migration guides. Now
during this migration, the script is deleting existing data from certain
tables but is not populating them. One example being that script is deleting
records from WCS 5.1 ATTRTYPE table and then later on its creating Foreign
Keys relationship using ATTRTYPE_ID field of this table without
re-populating the records it removed. This is causing the Foreign Key create
sql to fail and this is not the only table in question. There are many such
tables some coming from original WCS 5.1 schema and some new tables
introduced in WC 5.6 (with respect to WCS 5.1).
What i am not able to understand is why the script is doing this? Are we
supposed to resolve these errors manually if yes then why none of the
migration guides talk about this point.
Thanks in advance for any help or insight.
Niranjan Soni
| |
| tapan1 2004-11-29, 1:17 pm |
| quote:
Originally posted by Niranjan Soni
Hi
I am currently working on migrating WCS 5.1 websites to WC 5.6 and facing a
some problem at the time of database migration. I am migrating unencrypted
data using the migratedb script as described in the migration guides. Now
during this migration, the script is deleting existing data from certain
tables but is not populating them. One example being that script is deleting
records from WCS 5.1 ATTRTYPE table and then later on its creating Foreign
Keys relationship using ATTRTYPE_ID field of this table without
re-populating the records it removed. This is causing the Foreign Key create
sql to fail and this is not the only table in question. There are many such
tables some coming from original WCS 5.1 schema and some new tables
introduced in WC 5.6 (with respect to WCS 5.1).
What i am not able to understand is why the script is doing this? Are we
supposed to resolve these errors manually if yes then why none of the
migration guides talk about this point.
Thanks in advance for any help or insight.
Niranjan Soni
| |
| tapan1 2004-11-29, 1:25 pm |
| Hi ,
We are also facing the same problem. Trying to migrate database from 5.1 to 5.5.
In the migratedb log there are bunch of SQLSTATE=23520 errors.
The migratedb script deleted entries even from the language table but failed to load the data back into language table.
Did you get any solution for that. |
|
|
|