So i had to enable the component group and synchronize it to make them available for use. 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. Error retrieving next record from the database sbldbc00104. V7 to v8 information in this document applies to any platform. Sbl dbc xxxx errors are s ie b e l d ata b ase c onnection errors. Many times we have to enable particular server components which we generally do not use. Recently was setting up siebel email inegration but siebel communication components were not enable on server. If this is tools or a dedicated client, make sure the odbcs are working. We encourage you to read our updated privacy policy and cookie policy. 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. Siebel crm application is connected to siebel servcer db that is provided by dbms instance of the ibm db2 certified client and server product. 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. Let me agree that my client is really smart in using the siebel application.
Error retrieving the record often followed by a crash can be a tricky issue to debug in siebel. There are many reasons why error retrieving next record from the database. Error retrieving the next record from the database sbl. Some wrong query is being run in back end, which is not fetching any record. To view full details, sign in with your my oracle support account.
1010 813 523 482 555 1429 1218 979 1219 1078 785 1538 1449 1107 656 222 1401 387 27 868 789 984 1432 1373 1549 1434 870 1438 644 249 1135 343 1451 288 203 915 473 1543 1618 1278 851 640 1060 27 1311 366 548 1465 727 1161 329