Executing A Migration Plan Through REST API Returns "intBranchName can't be empty, Please provide valid Integration branch name" (Doc ID 2971370.1)

Last updated on OCTOBER 04, 2023

Applies to:

Symptoms

After updating Siebel Application to 23.7 release or later, when attempting to execute a migration plan via REST API call the following response is returned:

The following REST CALL was used as per Siebel Bookshelf instructions:

https://docs.oracle.com/cd/F26413_44/books/UPG/c-REST-Executing-Migration-Plan.html#u30227942

{
"schemaPassword":"<Encrypted_Password>",
"pwdPreEncrypted":"true",
"watermarkFilename":"",
"irrEndVersion":"",
"packageFilename":"",
}

STEPS
1. Update Siebel application to 23.7 or above.
2. Log in to Siebel Migration Application
3. Create a connection towards any available DR environment
4. Create a migration plan for a Full Runtime Repository migration
Process of setting up Siebel Migration Application is described in the Siebel Bookshelf:
https://docs.oracle.com/cd/F26413_44/books/UPG/c-Process-of-Using-Siebel-Migration-to-Migrate-Data-di1009976.html#u30228261
5. Attempt to run the migration plan via REST API call
https://docs.oracle.com/cd/F26413_44/books/UPG/c-REST-Executing-Migration-Plan.html#u30227942

Changes

 Siebel application was updated to 23.7 or later

Cause

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