SBL-DAT-00500 error when retrieving definition of complex Integration Object from a run-time table (S_INT_OBJ_DATA)
Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 8.0  and later
Information in this document applies to any platform.
Design and Validation of the EAI Declarative Data Maps of Integration Objects, using Siebel Client View (Site Map >Administration - Integration >Data Map Editor)
Error occurs during design time when one clicks "Validate" button for purpose to validate definition of the selected Integration Objects map.
Same Error occurs during run-time when the "Execute" method of the data mapper Business Service (BS) - the "EAI Data Transformation Engine" BS is invoked
to perform the data mapping of accordant Integration Object instance (SiebelMessage). Same error can be expected from any Business Service that has to use the Int. Obejcts.
SBL-DAT-00500: There were more rows than could be returned. Please refine your query to bring back fewer rows
In noted that the error occurs every time, when over 10.000 records (e.g. 16307) were fetching from the "S_INT_OBJ_DATA" table of Siebel DB
No error occurs and data mapping can take place.
NOTE: It is known that error addresses a known limitation for "ForwardBackward" mode used by EAI Data mapper to execute query of system Business Component that provides the data from the data map table.
So setting the DSMaxArrayFetchSize = -1 enterprise level component parameter that performs data map did indeed help, however it is apparently not acceptable setting as it introduced well known impact on all BC query operations
for all Siebel Object Manager components on the Enterprise.
One need to know how better to address this issue and suggest an option which allows to handle large Int. Objects without changing the DSMaxArrayFetchSize parameter.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms