IP 17 Migration Application Failure when username is not SADMIN
Last updated on JUNE 14, 2018
Applies to:Siebel CRM - Version 17.2 [IP2017] and later
Information in this document applies to any platform.
When executing a migration application between 2 environments, where the passwords for SADMIN user are not the same in source and target, export will get completed, but the import does not start.
Since the SADMIN password is different in source and target environments, a new user (SIEBMIG) is created with the same password. This is done as a workaround for the Bug 26823978. But still the migration fails.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms