LiveCache migration FAQs

 What happens if the /sapapo/om_order_lc_to_dbstart, /sapapo/om_upgrade_converter, /sapapo/om_upgrade_lc_anchors, and /sapapo/om_order_db_to_lcstart jobs are running?

The /sapapo/om_order_lc_to_dbstart program (report /sapapo/om_order_lc_to_db) starts jobs that save the liveCache transaction data to the APO database.
The /sapapo/om_order_db_to_lcstart program (report /sapapo/om_order_db_to_lc) starts jobs that transfer the transaction data from the database back to the liveCache.
The /sapapo/om_upgrade_converter program converts the internal data structure of the /sapapo/upgrade cluster table, where the (compressed) transaction data is saved. This is necessary because the internal organization of the table was changed.
The /sapapo/upgrade_lc_anchors program transfers the master data saved in the APO database back to the liveCache. In contrast to /sapapo/delete_lc_anchors, activity texts in the APO database are not deleted.

When and how are the time series and allocations backed-up?
See the relevant APO documentation.

Why is the migration executed via SAP reports and not via SAP migration tools (as it is done when migrating Oracle from NT to Unix)?
There are no relevant tools.

When can I deactivate the old liveCache?
Once all jobs that save the transaction data from the liveCache to the database (that is, all jobs with a 'LC_SAVE' name) are terminated.

For RFC connections: all clients or production clients only?
You only need to connect production clients. However, if you want, you can also connect other clients.

Should the new liveCache have the same name as the previous liveCache?
This is not necessary. It is only important that you maintain the LCA/LDA connection correctly.