Discussion
Tech Mahindra
CA
Last activity: 13 Jul 2020 3:50 EDT
Bulk Data Migration approach in Pega 6.2 SP2 using Oracle 11g for Custom Archival Solution
Hi ,
Please suggest best approach for bulk data migration when planning for a custom Archival solution.
Pega Version : 6.2 SP2
Database: Oracle 11g
We are designing a custom Pega archival solution. Need your valuable inputs on the initial bulk data migration approach between different schemas. (Eg: Active Schema --> Archive Schema)
Suggested approaches:
1. Calling Stored Procedures to move bulk data
2. Using Pega activity rule inside Agent rule to move data between different schemas.
Let me know for any further questions to clarify more.
Updated: 11 Jul 2020 22:12 EDT
Agriculture Victoria
AU
I think there are more than few archival strategies that can be considered depending upon how frequently the archived data will be used in future and what techniques are acceptable for data access.
Not going into much detail in absence of the landscape, few simple approaches that you can consider as below.
- If archived data will not be accessed by a Pega application and is required for regulatory or audit purpose only, then the best approach would be to use Pega BIX to extract the data in flat/relational structure so that data can be queried easily when required.
- If the data will be accessed by a Pega application then you may want to take a cold backup of the data and enable incremental backups to refresh the archive on a suitable frequency. Use Pega activities to purge inactive data from online application. In this approach, there will not be a clean separation in online and archived data, as archive copy will have additional data unless you purge data from archive as well.
- Another approach would be to consider Pega Purge/Archive wizard. However I have not used it for Pega 6.x. Have a look at this link - https://community.pega.com/sites/default/files/help_v62/tools/purgearchive/aboutpurgearchivewizard.htm
Tech Mahindra
CA
Hi Praveen,
Thanks for your reply.
Below are the use cases related to Archived case data:
1. Business users don't have any requirement to reopen the cases once it is archived.
2. Business users wants to have an archived case search functionality wherein only application related information should be presented other than audit, history table info.
3. Main agenda behind this Archival thought process is that they want to free up the space inside active database which will also drastically reduce periodic database backup time.
4. Long term purging of Archived data is required after 10 years for which DBA team agreed to move the data to Tape using stored procedures.
For the suggestion on using Pega BIX, we are already using this to export data on a daily basis in multiple target files for downstream systems.