My Oracle Support Banner

Siebel Application shows incorrect Language for all MLOV/Pick List Display Values (Doc ID 1314591.1)

Last updated on JULY 16, 2021

Applies to:

Siebel Clinical Manager - Version 8.1.1.3 SIA[21219] and later
Information in this document applies to any platform.
Siebel thin Client.



Symptoms

Symptoms in Siebel version prior to IP17

Siebel Life Science Application(ENU). When they tried to launch the thin clkient URL, they got server busy message., log file:

ObjMgrLog Error 1 0000000a4d9523ea:0 2011-04-01 08:18:27 Your current application is running in ENU language and the seed data LOV of type ACCESS_RESOURCE_TYPE name BUS_SVC cannot be found in the database for that language. This is most likely that the current database was not created with ENU seed data. Please make sure the database contains seed data for the language in which your application is running. 

The issue is --> From the thin client all the Out of the box pick lists/drop downs are referring to FRA lovs. Please note that this issue is only occuring when using thin client
With Dedicated client every thing is working fine. [pointing to same database as server and same SRF as server]
Even with the vanilla srf, issue has been reproduced.

Also checked and made sure the following parameters are set to ENU, yet it was looking for FRA
Application Language Code=ENU
OM - Resource Language Code= ENU
Language Code= ENU
OM - Resource Language Code= ENU

-----------------------------------------------------------

Symptoms in Siebel version > IP 17

Customer has ENU and FRA enabled, after create a new RR env they noticed that all MLOV were showing as FRA in the ENU application.

Changes

Changes in Siebel version prior to IP17

They had incorrectly changed S_CONTACT record for the Siebel Administrator by setting PREF_LANG_ID to FRA.

-----------------------------------------------------------

Changes in Siebel version > IP17

The AI Profile have the parameter "Anonymous User Name" set to a Siebel User and the corresponding S_CONTACT record had the PREF_LANG column explicitly set to FRA.

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
Changes
Cause
Solution


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