Multiple Sessions and the DBMS
The DBMS treats each session in a multiple-session application as an individual application. When you are creating multiple-session applications, keep the following points in mind:
• Be sure that the server parameter connect_limit is large enough to accommodate the number of sessions required by the application. For details, see the System Administrator Guide.
• In a multiple-session application, the application can encounter deadlock against itself. For example, one session can attempt to update a table that was locked by another session.
• An application can also lock itself out in an undetectable manner. For example, if a table is updated in a transaction in one session and then selected from in another transaction in a second session, the second session waits indefinitely.
Last modified date: 08/28/2024