Siebel Full RR Migration Process Stops After Export and Fails On Creating .zip File And Migration Plan Shows Error
(Doc ID 2569365.1)
Last updated on MARCH 05, 2024
Applies to:
Siebel CRM - Version 17.0 [IP2017] and laterInformation in this document applies to any platform.
Symptoms
Customer upgraded their Siebel application to IP2017 and later. When running the Full RR (Runtime Repository) migration the process stops right after all exports are completed in the Source. There is no error during the export, however the migration plan execution status is "Error" and below error was seen in migration.log.
[DEBUG] 2019-07-11 17:58:08.944 [Thread-13] Migration - com.siebel.migration.server.Transaction:invokeRestCall HTTP Operation: POST
[DEBUG] 2019-07-11 17:58:09.194 [Thread-13] Migration - com.siebel.migration.server.Transaction:invokeRestCall Connecting to the server : *****/siebel/v1.0/MigrationFilePrepareAndDeploy/preparePackage
[DEBUG] 2019-07-11 17:58:09.194 [Thread-13] Migration - com.siebel.migration.server.Transaction:invokeRestCall Http response : {"status":"Error","error":""}
[ERROR] 2019-07-11 17:58:09.194 [Thread-13] Migration - com.siebel.migration.server.Transaction:callExecutor Packaging Failed
STEPS TO REPRO
-----------------------
The issue can be reproduced at will with the following steps:
1. Perform Full RR Migration from Source to Target.
2. Make sure that the RR migration is completed with all steps.
3. Check to see if the Migration Plan shows as Complete and without errors.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |