Custom Script Stops Working After Migrating To Other Environment
(Doc ID 2230903.1)
Last updated on NOVEMBER 18, 2019
Applies to:
Siebel CRM - Version 8.1.1.11.17 [IP2013] and laterInformation in this document applies to any platform.
Symptoms
There are two Siebel environments (Env1 and Env2). Whole repository data was exported from Env1 and imported to Env2. No change was made. After full compilation on both environments, a custom script works fine on Env1 but does not work on Env2.
Cause
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
Symptoms |
Cause |
Solution |