How can I Migrate the entire PEGA data schema from DB2zOS to ORACLE 12c Database?
Hello Mesh I am tasked with the migration of all the data from the data schema in PRPC 7.1.7 from DB2zOS down to Oracle 12c database. I would like to find the best solution for this task that works. I am able to move the entire RULES schema and its contents from the mainframe to Oracle using the PEGA Migrate script utilizing the bulk mover process and that works fine. The problem is the Migrate script does not move the data schema.
Things I have tried.
Using DB2 utility to do a unload of the data from the tables the problem is the LOB the Unload utility places the LOBS in PDS as members and because of this we cannot create one file to FTP down.
Oracle is not recommending the use of Golden Gate for the initial move they are recommending to create a flat file send it from the mainframe first as the initial load and use SQLLOADER to populate the oracle database.
Idea I have.
If there was some way to be able to make a clone like how the migrate process does it for the RULES table and then unload the data the same way would be the ultimate solution.
Can the forum provide any way that they have done this migration process before that works so I may leverage it going forward?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
I have looked at the article in the link you sent me but that will not work for my situation. The problems are as follows.
This system has evolved over several upgrades on the mainframe and the column and structure are not the same in oracle.
The PRPC application does not have DBA authority on either system to make the necessary alteration to the database so it is a painful task to start and stop import because of column length and triggers.
Ideally if there was a way to take a list of the tables in DB2 data schema and clone it like how PEGA does for rules would resolve this matter. This would be a Perfect opportunity for PEGA to modify the Migrate script to be able to take input from a file defining the different organization data schema tables like how he does it for rules and be able to unload and load the new database with the data.
The reason I say that is the rules process of the clone and moving of rules works fine. The reason is there is a MASTER list of all the rules tables that he references when doing this migration.
So the solution you pointed me to do not work for me. I need to move all the content of the data schema including the lob in one file.
The moderators of the community could you please create an enhancement request for a way to migrate the data schema in a similar way that the migrate script does for the rules schema. It should ideally take a text file input like how the rules schema does and create the individual data schema clone. Then the bulk mover process should be able to unload the database on the zOS and load the data into any other database.
I checked for this item on our internal portal and see that there has been no progress. However, your Pega Account Executive might get you more details on the reasons behind this lack of progress and such.