Generating scripts with cfgmerge

(Doc ID 486874.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel System Software - Version 7.5.3.11 SIA [16199] and later
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)

Symptoms

Hello,

We are upgrading from Siebel 7.5 to Siebel 7.8. We have followed the steps listed in our SR 38-3293905321:

1. Backup our siebns.dat file from 7.5 environment.
2. Uninstall Siebel 7.5.
3. Install Siebel 7.8 and get the siebns.dat file from 7.8 environment.
4. Run cfgmerge utility using both siebns.dat files (the siebns.dat of 7.5 and the siebns.dat of 7.8).
5. Run the "parameter migration script".

We have done the steps 1, 2 and 3 sucessfully, and then we have run the cfgmerge utility in Enterprise mode and Siebel Server mode. In the .cmd file generated in Enterprise mode, there isn't any information about our customized workflow monitor / action Siebel 7.5 components.

We are sure all the components were active in our Siebel 7.5 enviroment and they appear in the siebns.dat file of this enviroment. We attach both siebns.dat file and the .cmd file generated in Enterprise mode with the cfgmerge utility.

Is it necessary to add manually these components in the Siebel 7.8 enviroment before running the cfgmerge utility?

Thanks and regards.

Cause

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