Network Outages May Cause Runtime Repository Migration To Fail With Error "504 Gateway Time-out" (Doc ID 2939217.1)

Last updated on APRIL 12, 2023

Applies to:

Symptoms

 During the execution of a Runtime Repository Migration, the status of the execution goes to "Error" during the step Schema Service - Import even though the utility finished without any errors:

SIEBEL_FILESYSTEM/migration/<migration id>/log/ddlimport_*.log


This type of behavior is not specific to Schema Service - Import and can happen for any other step of the Runtime Repository Migration process including export steps.
NOTE: For Siebel releases prior to 21.2, migration.log file will be located under AI_HOME\applicationcontainer\logs

The issue can be reproduced using the following steps:
1. Set up a Siebel environment with additional web layers in front of the AI (ex:proxies, load balancers etc)
2. Configure Siebel Migration Application (SMA) REST Endpoint to be one of the extra web layers
3. Access Siebel Migration Application
Following URL is valid for a standard setup: https://AI_HOST:AI_HTTPS_PORT/siebel/migration
If additional layers are configured in front of the AI, please check with internal teams For the appropriate URL
4. Log in to the Siebel Migration Application
5. Execute a Runtime Repository Migration as per instructions in Siebel Bookshelf:
https://docs.oracle.com/cd/F26413_39/books/UPG/c-Process-of-Using-Siebel-Migration-to-Migrate-Data-di1009976.html#u30228261
6. During execution of Runtime Repository Migration, shut down the web layer configured as the REST Endpoint host.
7. Notice the Runtime Repository Migration fails without any errors recorded.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.