Siebel crm application is connected to siebel servcer db that is provided by dbms instance of the ibm db2 certified client and server product. Co, efp south corp, efratom, efw, egain communications, egg harbor township, egger homes, eggers industries, egghead software, egr co, egs americas, egs electrical grp, egs electrical grp dir, egs production machining, egyptian. But when i tried navigating to my quotes view, no issues. Since the applet, business component, business object, pdqs etc etc, being used in both the views were the same, the only thing which was different is data. Error retrieving next record from the database sbldbc00104.
After setting the parameter om preload srf data with value false same parameter is true at enterprise level, the issue is not longer observed and the component starts as expected. Purpose this document is intended to provide cause and corrective action information about siebel. To view full details, sign in with your my oracle support account. We encourage you to read our updated privacy policy and cookie policy. Many times we have to enable particular server components which we generally do not use. Let me agree that my client is really smart in using the siebel application. If this is tools or a dedicated client, make sure the odbcs are working. Recently was setting up siebel email inegration but siebel communication components were not enable on server. There are many reasons why error retrieving next record from the database.
Personalize my dashboard copyright 2019 oracle andor its affiliates all rights reserved. At the same time, i can update next record but not this one. Error retrieving the next record from the database sbl dbc 00104. Some wrong or null value is there in any column which is causing the select selection which is generated at view load time to fail. Error retrieving the next record from the database sbl. Fix error retrieving lavasoft updates a repair tutorial. I queried for error code sbldbc00104 in the log file and found an. Sbl dbc xxxx errors are s ie b e l d ata b ase c onnection errors. Some wrong query is being run in back end, which is not fetching any record. So i had to enable the component group and synchronize it to make them available for use.
313 1521 819 753 85 888 167 630 1107 1109 894 1624 543 1273 1596 46 1347 1611 1141 1233 1328 1055 945 392 1118 1251 357 702 1487 906 386 322 526 189 1195