11/02/17 10:32:39.347 CET] Processing table -{ OA_NODE->OA_NODE }-I was able to solve this error by just adding the missing table in the target database (DB2) with the following command:
11/02/17 10:32:39.347 CET] SELECT * FROM "ACTIVITIES"."OA_NODE"
[11/02/17 10:32:39.722 CET] Transferring table --{ ACTIVITIES.OA_NODE} -- to table --{ACTIVITIES.OA_NODE }--
[11/02/17 10:32:39.957 CET] ERROR: Error validating data. The number of values is not equal to the number of columns in the destination table OA_NODE
[11/02/17 10:32:39.957 CET] ERROR: The number of values is 38 while the number of columns is 37
[11/02/17 10:32:39.957 CET] error.executing.transfer com.ibm.wps.config.DatabaseTransferException: Column number mismatch
ALTER TABLE ACTIVITIES.OA_NODE ADD COLUMN OWNERMEMBERUUID CHAR(36) NULL;I opened a PMR for this because I wanted to know what was causing this issue:
ALTER TABLE ACTIVITIES.OA_NODE ALTER COLUMN OWNERMEMBERUUID DROP DEFAULT;
ALTER TABLE ACTIVITIES.OA_NODE ALTER COLUMN OWNERMEMBERUUID DROP NOT NULL;
ALTER TABLE ACTIVITIES.OA_NODE ALTER COLUMN OWNERMEMBERUUID SET DATA TYPE CHAR(36);
CALL SYSPROC.ADMIN_CMD( 'REORG TABLE ACTIVITIES.OA_NODE' );
The table itself was no longer used in 5.5 which is why it was removed from the 5.5 createDB.sql and the upgrade-50CR1-55.sql script at some point.
But all "old" 5.0 envoirnments that were migrated to 5.5 still have this obsolete table.
To solve this problem you may also just delete the column and its index from the OA_node table in the source db. Thanks to David McCarthy from ICS Support IRL for this hint.
Regards,
Jan
Keine Kommentare:
Kommentar veröffentlichen
Sometimes there is no next time, no second chance, no time out. Sometimes it is now or never.
- Alan Bennett