Known Issues in Classic Migration
These known issues have been identified in Classic Migration Service.
Migration fails for Oracle Java Cloud Service applications that have long names
- Details
- Classic Migration Service does not support the migration of Oracle Java Cloud Service applications that have names greater than 28 characters.
- Workaround
- Before you start migrating an Oracle Java Cloud Service application, rename the application so that the name has less than 28 characters.
Unsupported attributes for Oracle Analytics Cloud - Classic application
- Details
- When you create a migration for the Oracle Analytics Cloud - Classic application using the API or CLI, it is mandatory to provide values for the
serviceInstanceUser
andserviceInstancePassword
attributes. However, Classic Migration Service ignores these values. - Workaround
- You can enter any value for these attributes, such as "unused."
Unsupported query parameters in the listSourceApplications command
- Details
- The
listSourceApplications
command does not support the following query parameters:limit
,page
,sortOrder
, andsortBy
. - Workaround
- Do not use these query parameters to filter your search results.
Unsupported query parameter in the listMigrations command
- Details
- The
listMigrations
command does not support thelifecycleState
query parameter. - Workaround
- Do not use this query parameter to filter your search results.