Memo migration in TIBCO iProcess Engine 11.5 - Should a customer who is upgrading to 11.5 migrate their memo data?
Article ID: KB0093546
Updated On:
| Products | Versions |
|---|---|
| TIBCO iProcess Engine (Oracle) | - |
| Not Applicable | - |
Description
Resolution:
From TIBCO iProcess Engine 11.5, memos are stored in BLOB (Oracle) or VARBINARY (SQL Server) data types in the database. All new cases' memos are stored this way. Customers upgrading from older versions need to look carefully at how much memo data they have and to decide whether to migrate or not.
1). For customers with large amounts of memo data we recommend choosing not to migrate during the upgrade and also not to migrate with the swutil option. In this situation, as old cases are purged through maintenance of the system, the number of memos in the old format will gradually clear. The reason this option is best is that migrating memos can be a very time consuming process. For example, in tests run in TIBCO QA with the Oracle version, 10,000 cases with 8 lots of 140Kb memo data took approx 1.5 hours to migrate. Customers with large amounts of data choosing to migrate upon upgrading could potentially be waiting days for the process to complete. This option is the one we suspect most customers who have memo data will need to use. Customers also have the option of running the migrate utility once the number of memos remaining in the old format is very small.
2). For customers with some memo data but not very large amounts, there is the option to not migrate during the upgrade to 11.5 but to use the swutil option to migrate the cases gradually. If you use this option you can do so with iProcess running but be aware it will lock each case as it is moved in which case you may only want to migrate closed cases. You can also run with iProcess down. For this option you should benchmark the impact first on an environment with the same data load as production so you can see what the impact will be before doing this in production. Note: The is no rollback option on the utility.
3). If a customer has virtually no memo data then you do have the option to migrate during the upgrade. Only choose this option if you have checked and tested the impact first outside of production and are satisfied that it will be a quick process within the downtime window you have for your iProcess upgrade.
From TIBCO iProcess Engine 11.5, memos are stored in BLOB (Oracle) or VARBINARY (SQL Server) data types in the database. All new cases' memos are stored this way. Customers upgrading from older versions need to look carefully at how much memo data they have and to decide whether to migrate or not.
1). For customers with large amounts of memo data we recommend choosing not to migrate during the upgrade and also not to migrate with the swutil option. In this situation, as old cases are purged through maintenance of the system, the number of memos in the old format will gradually clear. The reason this option is best is that migrating memos can be a very time consuming process. For example, in tests run in TIBCO QA with the Oracle version, 10,000 cases with 8 lots of 140Kb memo data took approx 1.5 hours to migrate. Customers with large amounts of data choosing to migrate upon upgrading could potentially be waiting days for the process to complete. This option is the one we suspect most customers who have memo data will need to use. Customers also have the option of running the migrate utility once the number of memos remaining in the old format is very small.
2). For customers with some memo data but not very large amounts, there is the option to not migrate during the upgrade to 11.5 but to use the swutil option to migrate the cases gradually. If you use this option you can do so with iProcess running but be aware it will lock each case as it is moved in which case you may only want to migrate closed cases. You can also run with iProcess down. For this option you should benchmark the impact first on an environment with the same data load as production so you can see what the impact will be before doing this in production. Note: The is no rollback option on the utility.
3). If a customer has virtually no memo data then you do have the option to migrate during the upgrade. Only choose this option if you have checked and tested the impact first outside of production and are satisfied that it will be a quick process within the downtime window you have for your iProcess upgrade.
Issue/Introduction
Memo migration in TIBCO iProcess Engine 11.5 - Should a customer who is upgrading to 11.5 migrate their memo data?
Additional Information
Read the details on this subject in the Installation document for iProcess and the iProcess swutil and swbatch Reference Guide.
Feedback
Yes
No
Powered by
