In some cases the migration of historical data may fail or get stuck. If users are on old and/or out of support version, then in rare cases history data may not fully migrate.
Release : 12.2, 12.3
Component : Workload Automation DE
The history data migration takes place after the artifacts. Large amount of data or row counts can sometimes result in DB timeouts.
The DBA can manually move the data from old database to new schema used by R12.x version.
Data from following tables:
esp_sap_job
esp_as400_job
esp_bdc_job
esp_bwip_job
esp_bwpc_job
esp_peoplesoft_job
esp_sppm_job
esp_spda_job
esp_virtual_job
esp_filemontr_job
esp_application
esp_generic_job
will move to these in R12.x:
h_sap_job
h_as400_job
h_bdc_job
h_bwip_job
h_bwpc_job
h_peoplesoft_job
h_sppm_job
h_spda_job
h_virtual_job
h_filemontr_job
h_application
h_generic_job
-----------------
Do not move the data from 11.3 ESP_ to R12 ESP_.
Note: If data moves result in primary key or sql constraints issue, then older database may have been modified. See this link fix the db constraints issue.