How To Perform Siebel Upgrade and Migration Installation Scenarios When Using Different OS Platforms Between Source (AIX) and Target (RHEL) Siebel Versions?
(Doc ID 2585900.1)
Last updated on JANUARY 21, 2020
Applies to:Siebel CRM - Version 17.0 [IP2017] and later
Information in this document applies to any platform.
Customer had current Siebel installation for IP2016.19 on AIX 7.2. Their target installation is to IP2019 on RHEL7. Customer had to do migration installation from IP2016 to IP2019. Customer had below questions:
1. How can we do a migration installation as they are from AIX to RHEL7. Normally, they would just run the migration installation in place on AIX and it would use the existing server configuration, siebns.dat, etc and would remain in place after the installation. With moving from AIX to RHEL7, how do they preserve those server configurations? Can we somehow copy the siebns.dat from the old to new and refer to it during the installation?
2. Can we replatform our AIX Siebel enterprises, 14 of them SDLC+Prod+DR, to RHEL7 and upgrade at the same time? How to achieve this?
3. Can you confirm: In order to get an upgraded DB from IP2016 to IP2019 is to run the upgrade from an existing ip2016 that was upgraded install to IP2019, then run db upgrade from there?
4. I can't run the IP2017/19 db upgrade from a newly installed IP2017/19 env, because I can't config the new env without a db and the only db I can get is the vanilla OOB database from a new install. I don't yet have an IP2017/19 database instance unless I've run the upgrade from an upgraded IP2016 env. What can be done?
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