HomeНаука и техникаRelated VideosMore From: Ramkumar Swaminathan

Connection Pool with an Oracle Database - DBArch Video 19

39 ratings | 4075 views
In this video you will learn the concept of a Connection pool an application uses with a Database. You will learn the need for connection pool and how it helps in optimizing resource utilzation on the Database Server. You will learn that Logon and Logoff are the most resource intensive tasks in a database, and hence both tasks should be avoided during normal operations of the application and database.
Html code for embedding videos on your blog
Text Comments (13)
m .v kishore (1 month ago)
Hi Sir, I have a doubt We need pfile/spfile to start db. We need control file as well to start db. Pfile has all the parameters mentioned while control file has db physical details. So what is the difference between both? Y can't we maintain a single file.? This question arises as pfile has db name and unique name. Whereas control file also has db name.
m .v kishore (1 month ago)
Ramkumar Swaminathan thank you so much for the wonderful explanation 😊
Ramkumar Swaminathan (1 month ago)
Control file is a binary file whereas pfile is a text file. you can create a pfile even if you lose one, but control file is maintained by the server. Pfile is for instance to start and come to nomount state... after that the control file is read and instance gets to mount state and then the data files and redo log files are opened by the instance and the instance is open for users to work with their data.
Sourabh Verma (2 months ago)
great video , Thanks a lot
Padala Sundeep (5 months ago)
How do the application verify the users? Even for verification it needs to check the credentials in DB I hope. Or else does it verify users by using these 10connection pools? Confused..!!
Ramkumar Swaminathan (5 months ago)
Most Welcome... Enjoy Learning...
Padala Sundeep (5 months ago)
Ramkumar Swaminathan Perfect Explanation..!! Thanks for your time.
Ramkumar Swaminathan (5 months ago)
Hi Padala, very good question. When all application users connect to the application and get authenticated as application users maintained by the application( for which the application will have its own authentication mechanism), the DB User for all application users happens to be the same. Thus the database is unaware of who is the real user. Thats the problem with Connection pool... To overcome this.. you have solutions like maintaining a CLIENT_ID or APPLICATION_CONTEXT which are attributes of a database connection. Thus when an application uses one of the connections in the pool to perform an operation for an Application user say USER1, The application should append this information to the DB Connection attribute... thereby the database can be aware of the real application user. Which can be used to audit or other operations in the database where the real users should be known to the Database. Another way to identify the application user in the Database is by using Proxy connections... Hope this helps..
Nazir Hussain (8 months ago)
Sir, very nice explanation, do you have any training lessons on JBOSS SERVER.
Ramkumar Swaminathan (8 months ago)
+Nazir Hussain not from me... Boy shall keep you posted if I find any good channel on jboss
Sain Singh (8 months ago)
nicely explained , like the way it is explained!!!
Ramkumar Swaminathan (8 months ago)
+Sain Singh thanks
tirupati Y (10 months ago)
Thanks you Sir..Nice

Would you like to comment?

Join YouTube for a free account, or sign in if you are already a member.