Re: latches and alter table freelist

>The init.ora parameters probably are not going to help much in looking
>at a latching problem. Latches are not my strong suit, but there are
>some posters on these boards that are very good with them. Still I
>have seen a couple of problems so which latches are you seeing waits
>on? Do they have latch children?
 

>For only 40 users your buffer pool and distributed transactions seem
>high. Maybe a better number would be how many concurrent sessions
>does your db have to support?
>And what kind of db is it: OLTP vs
>Warehouse? What is the total size of the db?
3-tier app., Oracle/Tomcat/Java (fat) client, and as intranet/internet app.
Application is document warehousing & workflow management (for lawyers), so answer is Warehouse type.
40 users connect to db and after getting data, connection ended. (I'm not satisfied, because I think that we can use connection pooling. If I use cursor names declared in packages and if I do NOT close connection, can I get any benefit vs. cursor memory allocation problem? Named cursors can be shared/reallocated, don't they?). You ask for sessions and answer is only few or better say 40 maximum. Total size is 10 Gb reallocated, and real size is 7Gb. We are now in optimizing state, so our app. must get better performance as much as possible.
We also handle lot of files, but saving files are not through Oracle or MSSQL (compatibility db problems) , just on server side file system, in db we store only descriptors and path.

>Just taking a shot in the dark I would think that perhaps your finder
>table, if multiple users are accessing rows in the same block
>concurrently, needs to have more than the default transaction work
Yes, I know, just testing another possibilities. Any suggestions are really helpfull.
>areas preallocated. Multiple free lists might be in order, but I find
>Oracle does a pretty good job with them so just a couple should be
>enough.
 You mean 4 freelist is enough?
>Your compatiable is set to 8.1.6 so hopefully your db is 8.1.6. If it
>is higher I would set it to match the db.
Yes, version is 8.1.6!

--
Posted via http://dbforums.com