Product Release: V7 (Professional)
Version: 7.8.2.5 [19227] NLD
Database: Oracle 10.2.0.2
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: Red Hat Linux 4.0
This document was previously published as Siebel SR 38-3360396501.
Symptoms
Hi,
We're migrating our product definitions through exporting and importing the full structure through a workspace. However, we have created a new group theme that we are using in the product definition HI User Interface. Now, when we are importing this workspace xml into the target environment we get the following error(s):
SBL-EAI-04186: Picklist validation of field 'UI Style Name' in integration component 'Object UI Group ImpExp BC' did not find any matches satisfying the query '[Name] = "KZM Summary Group Theme JS" AND [Type] = "Group Style"; and an attempt to create a new record through the picklist failed.
Picklist validation of field 'UI Style Name' in integration component 'Object UI Group ImpExp BC' did not find any matches satisfying the query '[Name] = "KZM Summary Group Theme JS" AND [Type] = "Group Style"', and an attempt to create a new record through the picklist failed. (SBL-EAI-04186) (IDS_EAI_ERR_SA_PICK_NEW_FAILED).
Currently, this product definition cannot be imported like this. As a workaround we now have to create the product definition manually and create this UI information ourselves. After that, we can import the product definition through the workspace.
Why would this not be created through the process itself?
Thanks,
Stefan
Solution
Message 1
For the benefit of others,
The customer encountered the following error when trying to import a product which had a new group theme added to the product definition HI User Interface along with a matching custom web template.
When importing the workspace xml into the target environment the customer received following error:
SBL-EAI-04186: Picklist validation of field 'UI Style Name' in integration component 'Object UI Group ImpExp BC' did not find any matches satisfying the query '[Name] = "KZM Summary Group Theme JS" AND [Type] = "Group Style"; and an attempt to create a new record through the picklist failed.
The same behavior was reproducible in the sample db using the standard srf.
New webtemplates are not moved via the Import/Export mechanism. It is necessary to move the file and then create a new record for this file to access it.
Change Request 12-1JOEKRJ has been logged as a Product Enhancement to have this functionality in future versions of the product.
However, even for an enhancement there would be an issue.
The group definition is a name and a swt file name. If you want to create the record you would need both bits of information in the xml file.
Continued in next activity...........
Message 2
Continued from previous activity..........
Also you may encounter new conflicts like what if this name already exists with a different swt file and what is if the web template file is not on the target system.
Setting up this information is an administration task and is not a frequent task and in most cases only once. So this should not impact highly on the migration of products.
Thank you,
Oracle | Siebel Product Support.
Applies to:
Siebel System Software - Version: 7.8.2.3 SIA [19221] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221] Com/Med
Database: Oracle 9.2.0.6
Application Server OS: Sun Solaris 9
Database Server OS: HP-UX 11i
This document was previously published as Siebel SR 38-3150460375.
Symptoms
SBL-DAT-00225
Here is the problem encountered :-
Assume a workflow process that does and EAI Siebel Adpater, method Upsert. The process is executed in the WfProcMgr component. Just after the start up of the component, while the LOV have not been yet loaded, several tasks are started simultaneously. If there are concurrent accesses to the same pick list, one is failing with the error below.
SBL-EAI-04186: Picklist validation of field '%1' in integration component '%2' did not find any matches satisfying the query '%3', and an attempt to create a new record through the picklist failed.
SBL-DAT-00225: The value entered in field %2 of buscomp %3 does not match any value in the bounded pick list %1.
However, the value does exist in the database and is successfully used in other case without any changes.
Cause
The behaviour was re-produced, and change request Bug 10513363 was created to have this problem addressed in future versions.
Solution
There is no straightforward workaround to this. However, it seems that the context is very specific.
- The time frame is really thin for concurrent accesses, which makes the matter very intermittent.
- Once the LOV is in cache and the cache is not clear, for all MT Servers, the problem should not happen. In case where MaxMTServer and MinMTServer are different, the problem may occur for a new MTServer spawned when the load requires it. Also, having MaxMTServer=MinMTServer could be an approach to limit the occurrence for this case.
It may not be limited to pick list used or references with EAI but static pick list in general.
The change request 10513363 is listed as fixed in :-
Siebel version 7.7.10 and above maintenance releases
Siebel version 7.8.2.7 and above maintenance releases
This particular defect has not been reported in Siebel version 8.x.
Applies to:
Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 7.5.3
Purpose
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04186: Picklist validation of field '%1' in integration component '%2' didn't find any matches satisfying the query '%3', and an attempt to create a new record through the picklist failed.
Scope
This document is informational and intended for any user.
SBL-EAI-04186: Picklist validation of field '%1' in integration component '%2' didn't find any matches satisfying the query '%3', and an attempt to create a new record through the picklist failed.
Explanation
EAI Siebel Adapter tried to resolve a foreign key using dynamic PickList, but a matching record could not be found. Since PickList allowed inserting a new record, it tried to do so, but that failed (most likely because some required fields were missing).
Corrective Action
If the intention was indeed to insert a new record through the picklist, check the process log file for information that will indicate the exact error why the insert failed. Otherwise, check to see whether the record was in the database but could not be found. If this is the case, then check for the search specification on the buscomp used by the PickList in question, and consider explicitly specifying 'PicklistUserKeys' Int. Comp. Field User Property to enable EAI SA to find the match. In the case where the record did not exist in the database, and it is not possible to insert through picklist, consider using another Integration Object to insert records before picking through the PickList.
אין תגובות:
הוסף רשומת תגובה