This site has been specifically designed to troubleshoot all Siebel related issues. When any exception or error occurs in Siebel, the cause is given by a specific error code. Whenever we face an issue, we try to Google or search for a resolution mostly from Oracle Support, IT Toolbox, Siebel Unleashed etc. I have tried to search for all the solutions for a particular error code in all the mentioned sites and put all the solutions in this site.
Search This Blog
SBL-DAT-60228: Cannot persist session %1. Possible errors include: Model pooling not enabled; No valid session ID; The current session
Error Message Area:Data Manager - DAT
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-60228: Cannot persist session %1.
This document is informational and intended for any user.
The error message is intended for internal software integrity checking only and should not occur under normal operating conditions. Possible causes of the internal error include: Model pooling not enabled; No valid session ID; The current session is dedic
The system administrator should collect assert, prefer, and .fdr log files from the Siebel Server /bin directory, collect all component log files, and tar all files together. Submit this data to Siebel Technical Support in a service request, with a descri