-
Hi,
Is anybody using multiple buffer pools (KEEP,RECYCLE,DEFAULT)?
Is there any practical benefit seen by anybody after using this?
How to check whether there is any real advatage of these pools?
Pl. throw some light on this.
TIA
Sam
------------------------
To handle yourself, use your head. To handle others, use your heart
-
Hi ,
You can gather information about these multiple buffer pools from:
V$BUFFER_POOL
V$BUFFER_POOL_STATISTICS.
Vijay.
Say No To Plastics
-
Thanks Vijay,
I also wanted to know...
Is there any practical benefit seen by anybody after using this?
How to check whether there is any real advatage of these pools?
Thanks,
Sam
------------------------
To handle yourself, use your head. To handle others, use your heart
-
BUFFER_POOL KEEP is a very good option introduced in 8/8i.
If the appln system has 100s of look up tables, then use KEEP option while creating the tables. The data cached on KEEP buffer will not be flushed out due to aging mechanism.
-
U can use different parts of db cache, if u know characteristics of ur applications.
DEFAULT pool (~ 50% of all of cache) for "usuall" transaction process
KEEP pool (~20% of of size of cache) for lookup operation on small tables
RECYCLE for full scan table operations
But how u going to divide db cache, depend from application.
This is only example.
-
[QUOTE]Originally posted by Shestakov
RECYCLE for full scan table operations
Is there any table, which gives list of tables which perform full table scans?
I read somewhere that RECYCLE buffer pool is for large frequently used tables.
Can I only use KEEP and DEFAULT buffer pool to begin with?
Pl. advise.
Thanks,
Sam
------------------------
To handle yourself, use your head. To handle others, use your heart
-
Yes u can.
"I read somewhere that RECYCLE buffer pool is for large frequently used"
RECYCLE pool --> for rarely segments of blocks or for large segments of blocks.
(usually it happend when we have full scan table operations)
-
Sizing the recycle pool is not easy: personal experience. Even after using TKPROF and SQL Trace one might end with poorly sized R-pool. Especially, if the application is "rich" in SQL-statements: then you'll do better without the R-pool.
Oracle Certified Master
Oracle Certified Professional 6i,8i,9i,10g,11g,12c
email: ocp_9i@yahoo.com
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|