Siebel Migration Application FilePrepareAndDeploy Throws "HTTP 401" Error When Deploying Across Multiple Application Interface Nodes
(Doc ID 3005064.1)
Last updated on APRIL 03, 2024
Applies to:
Siebel CRM - Version 23.12 and laterInformation in this document applies to any platform.
Symptoms
Executing a Migration import using the "FilePrepareAndDeploy" step does not propagate the changes to all the existing AI nodes in the target Siebel environment.
AI_HOME/applicationcontainer_external/logs/migration.log does not log any particular message to assist in debugging:
[ERROR] 2024-02-07 20:00:41.219 [pool-7-thread-1] Migration - com.siebel.migration.server.Transaction:invokeRestCall
[ERROR] 2024-02-07 20:00:56.250 [pool-7-thread-1] Migration - com.siebel.migration.server.Transaction:invokeRestCall REST Service returned error response
[ERROR] 2024-02-07 20:00:56.250 [pool-7-thread-1] Migration - com.siebel.migration.server.Transaction:invokeRestCall
[ERROR] 2024-02-07 20:00:56.250 [pool-7-thread-1] Migration - com.siebel.migration.server.Transaction:checkStatus Archive Id [1-244VD75X] CheckStatus REST Resource execution failed
[ERROR] 2024-02-07 20:00:56.264 [pool-7-thread-1] Migration - com.siebel.migration.server.ProcessFlow:getResources Archive Id [1-244VD75X] Resource [MigrationFilePrepareAndDeploy] Operation [Import] encountered an error. Aborting the Execution
[ERROR] 2024-02-07 20:00:56.265 [Thread-10] Migration - com.siebel.migration.server.Transaction:callExecutor Archive Id [1-244VD75X] Unable to Import the resources
The only relevant information is captured in the target environment under AI_HOME/applicationcontainer_external/logs/localhost_access_logs
Localhost_access log in working node:
[06/Feb/2024:15:02:18 +0100] "POST /siebel/v1.0/service/Application Migration Utility Service/GetFileSystemPath HTTP/1.1" 200 70 15
[06/Feb/2024:15:02:18 +0100] "POST /siebel/v1.0/MigrationFilePrepareAndDeploy/getstatus HTTP/1.1" 200 92 31
[06/Feb/2024:15:02:18 +0100] "POST /siebel/v1.0/service/Authentication Service For Migration/AuthenticateUser HTTP/1.1" 200 115 0
[06/Feb/2024:15:02:18 +0100] "POST /siebel/v1.0/service/Application Migration Utility Service/GetFileSystemPath HTTP/1.1" 200 70 0
[06/Feb/2024:15:02:18 +0100] "POST /siebel/v1.0/service/Authentication Service For Migration/AuthenticateUser HTTP/1.1" 200 115 0
[06/Feb/2024:15:02:18 +0100] "POST /siebel/v1.0/MigrationFilePrepareAndDeploy/Import HTTP/1.1" <LOCAL_PHONE_NUMBER>
[06/Feb/2024:15:02:18 +0100] "POST /siebel/v1.0/MigrationFilePrepareAndDeploy/importFiles HTTP/1.1" 200 20 250
Localhost_access log in the affected node:
STEPS
1. Set up a Siebel environment with at least 2 AI nodes (must be on different hosts). This will act as the target
2. Log in to SMC on the primary node and create a new AI profile.
3. Deployed the new AI profile on the AI installation from the secondary node.
4. Created a new Migration profile and deployed it using the Primary AI as host.
5.Logged in to Migration Application and created a new connection.
6.Created a new Migration Plan having only FilePrepareAndDeploy box checked.
7.Start the import process using the Migration Plan created previously.
8. Notice the changes are not propagated across all AI nodes.
Changes
Siebel has been updated from 23.5 to 23.9 release.
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 |