Siebel Async Migration Import Package Fails 'Could Not Unpackage The Zip File Due To File System Path' Error
(Doc ID 2745892.1)
Last updated on OCTOBER 10, 2023
Applies to:
Siebel eService - Version 18.8 and laterInformation in this document applies to any platform.
Symptoms
When attempting to run Asynchronous migration between source and target, the migration fails and the following error occurs in both the UI and migration.log.
[DEBUG] 2021-01-08 13:44:22.433 [https-openssl-nio-9443-exec-5] Migration - com.siebel.migration.server.MigrationUtility:InvokeRestCall Response from Server: {"SiebelMessage":{"IntObjectFormat":"Siebel Hierarchical","MessageId":"","IntObjectName":"Transaction","MessageType":"Integration Object","Transaction":{"status":"Running","Id":"xxxx","mgPlanName":"ImportFullRR","mgPlanId":"xxxx","TransactionResource":{"seq_num":"7","Id":"1-ZKQIVS","resName":"Migration Application Workspace Data Service","status":"Not Started","endTime":"","loglocation":"https:/\xxxx/siebel\/v1.0","txnId":"xxxxx","stDate":"","operationName":"FullSeedImport","resType":"DB Util","trackingId":"","resId":"xxxx"}}}}
[TRACE] 2021-01-08 13:44:22.433 [https-openssl-nio-9443-exec-5] Migration - com.siebel.migration.server.MigrationServer:doPost Output message: {"status":"error","msg":"Could not unpackage the zip file due to File System Path \\\\******\\xxx\\xxx does not exist. "}
The issue can be reproduced at will with the following steps:
1. Setup 18.8 or later on source and target
2. Make sure migration profile is setup and migration application is working
3. Check to see if Async migration with export is working
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 |
| References |