My Oracle Support Banner

Siebel Not Using Bind Variable For WS_ID (Doc ID 2684966.1)

Last updated on APRIL 05, 2021

Applies to:

Siebel CRM - Version 20.3 and later
Information in this document applies to any platform.

Goal

Everytime  during full repository migration WS_ID changes. In turn it changes the queries Siebel uses as in the FROM condition  ,  a hard coded WS_ID = '1-N4U4-8SFY'

Why Siebel is using hardcoded values instead of bind variables for WS_ID ?
 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.