eConfigurator File Cache Errors With Long Attribute, Class Or Product Names
(Doc ID 2034850.1)
Last updated on FEBRUARY 03, 2019
Applies to:Siebel CRM - Version 22.214.171.124  and later
Information in this document applies to any platform.
In a Windows environment the whole path (path + filename) is not allowed to be longer than 260 chars. This can lead to file cache issues on eConfigurator.
Siebel eConfigurator will create a binary file from database objects Attributes, Classes and Products to speed up access of these objects. These objects will create files in the Siebel eConfigurator filesystem (<filesystem directory>/ISS_OBrkCache/CfgObjBroker/<object type>/<Language>/<name of object>). The object name is constructed by using product ID, product last update time, class ID, class last update time, product version, and version update time.
- product name = Free Voice Mail 2 Min Greeting / 10 Msgs / 28 Day Storage w/DISH Bundle
- filesystem name = 71_as_Free_sp_Voice_sp_Mail_sp_2_sp_Min_sp_Greeting_sp__sl__sp_10_sp_Msgs_sp__sl__sp_28_sp_Day_sp_Storage_sp_w_sl_DISH_sp_Bundle7_as_1-95ZD01_as_17_as_1-9HIM319_as_12_sl_04_sl_2011_sp_14_sc_05_sc_18.obj
If the resulting filename is too long, Windows cannot create the file and you will see an error in the Siebel logfile. Unfortunately this will break eConfigurator filesystem cache and will lead to poor performance in all accesses of this object. Example of poor performance is described under My Oracle Support entry "Loading a Customizable Product Needs a Lot of Time When Running a Bulk Request (Doc ID 2021535.1)"
How can this be resolved?
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