This issues was faced by a developer, who asked for the solution, so here is something can be done at database level -
[a]
Create an Oracle profile and limit the number of sessions per database user, for example:
sql> CREATE PROFILE <profilename> limit SESSIONS_PER_USER 1;
sql> ALTER USER <username> <profilename>;
sql> ALTER SYSTEM SET RESOURCE_LIMIT=TRUE;
Using this approach, please be aware that dead connections will not always be detected by the database immediately, so users might occasionally not be able to login even a single time until a database administrator has killed their session. Also, …

During Siebel development, we have many development environments like DEV, QA, BUILD, and PRODUCTION. And we may get mails or end-users may get mails from Siebel, but we don’t know which the originating environment is. Hence, it takes time to debug and find the source of emails.
Solution:
The emails are sent by the server component – Outbound Communication Manager. Outbound Communication Manager Business service inserts records with parameters in two tables – S_SRM_ACTION and S_SRM_DATA. The action name is stored in S_SRM_ACTION. S_SRM_DATA stores the various parts of the mail like …