Question
msg systems
DE
Last activity: 2 Aug 2016 7:56 EDT
Migration from Pega6.3 to Pega7.1.7 - DataMigration
Data Migration from Pega6.3 sp1 to Pega7.1.7.
We make not the in place migration, because we migrate from an Pega6 environment to the already existing Pega7 environment. On this Pega7 environment there are some products on the platform that work till more then 1 year.
Our application consist of a FW and 6 Layer. We have bulk Data (Workitems, assignments , attachment, ...).
We use following tool to import the data.
https://community.pega.com/marketplace/components/data-migration-helper
We first create for the FW the select statements. Then change them so we can insert the selected data from Pega6 to Pega7.
Then we simulate an run of this script. In the logfile we find ORA-00947 error.
We have some shared tables which have new columns. We dont now what to write into this colums.
Data Migration from Pega6.3 sp1 to Pega7.1.7.
We make not the in place migration, because we migrate from an Pega6 environment to the already existing Pega7 environment. On this Pega7 environment there are some products on the platform that work till more then 1 year.
Our application consist of a FW and 6 Layer. We have bulk Data (Workitems, assignments , attachment, ...).
We use following tool to import the data.
https://community.pega.com/marketplace/components/data-migration-helper
We first create for the FW the select statements. Then change them so we can insert the selected data from Pega6 to Pega7.
Then we simulate an run of this script. In the logfile we find ORA-00947 error.
We have some shared tables which have new columns. We dont now what to write into this colums.
Has someone an overview/idea about new colums (Datatype, length, ...) in Pega7.1.7 and what we need to write into.
The tables we identifyed: PC_ASSIGN_WORKBASKET; PC_ASSIGN_WORKLIST; PC_DATA_WORKATTACH; PC_HISTORY_WORK; PC_INDEX_WORKPARTY; PC_LINK_ATTACHMENT; PC_LINK_FOLDER; PR_ASSIGN; PR_DATA; PR_HISTORY; PR_INDEX_ASSIGNMENTDEPS; PR_INDEX_ASSIGNMENTSKILLS; PR_SYS_QUEUES; PR_SYS_QUEUE_SLA (see attached File)
Are there more tables we need to take under consideration?
may this issue also occur for values within blobs?
Kind regards
Annemarie
Accepted Solution
msg systems
DE
We have an answer from PEGA, that in our application we can leave the new columns empty.
This resolve our problem.
Regards
Annemarie
Virtusa IT Consulting
AE
As you described that you are not going for in place upgrade, I presume you have used out of place upgrade in that case have you tried using migrate scripts from 717 media file?
Regarding ORA-00947 error can you please share the complete stack trace of the error?