Inconsistent SRF Compile Behavior for the Same Repository in different Siebel Environments, Dev, Test.
(Doc ID 1327725.1)
Last updated on NOVEMBER 22, 2019
Applies to:Siebel Tools - Version 220.127.116.11 SIA  and later
Information in this document applies to any platform.
Reviewed for relevance "6-APR-2016".
On : 18.104.22.168 SIA  version, Configuration - Dev Env
Customer has found that in one environment, the SRF full compile generates a SRF file that works as expected in their environment.
If they migrate the repository to another test environment and do a full compile, the same repository produces a SRF that has a configuration error that stops the users from logging in to the Siebel Application.
Why does the same repository compile a good srf in one environment and a bad srf in another environment?
The SRF from the second environment produces this error when the users try to log in.
The issue can be reproduced at will with the following steps:
1. In the first Siebel environment, compile a new SRF for all projects. Note, that the SRF works fine in this environment.
2. Migrate the repository to a test environment and then compile a new srf with all projects. Note that the new srf does not work in the new environment.
The new custom srf gives a configuration error at login.
Since the repositories are the same, the full compile srf file should behave the same.
Note that the first environment srf is good and can be used in any environment. The second environment srf gives this configuration error in any environment. The srfs compiled from the same repository are different.
The srf compile should be the same in both environments since it is the same configuration, the same repository.
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