What could be a reason for this recommendation?

A senior DBA asked you to execute the following command to improve performance:
SQL> ALTER TABLE subscribe log STORAGE (BUFFER_POOL recycle);
You checked the data in the SUBSCRIBE_LOG table and found that it is a large table containing
one million rows.
What could be a reason for this recommendation?

A senior DBA asked you to execute the following command to improve performance:
SQL> ALTER TABLE subscribe log STORAGE (BUFFER_POOL recycle);
You checked the data in the SUBSCRIBE_LOG table and found that it is a large table containing
one million rows.
What could be a reason for this recommendation?

A.
The keep pool is not configured.

B.
Automatic Workarea Management is not configured.

C.
Automatic Shared Memory Management is not enabled.

D.
The data blocks in the SUBSCRIBE_LOG table are rarely accessed.

E.
All the queries on the SUBSCRIBE_LOG table are rewritten to a materialized view.

Explanation:
The most of the rows in SUBSCRIBE_LOG table are accessed once a week.



Leave a Reply 7

Your email address will not be published. Required fields are marked *


Umaruddin Ansari

Umaruddin Ansari

D is correct

Alexis

Alexis

It is assumed that this utility is no longer to 12c

legos21

legos21

D
https://www.toadworld.com/platforms/oracle/w/wiki/1347.using-the-keep-and-recycle-pool
Any segments whose blocks to be accessed with less frequency should be assigned to the recycle pool so that it does not flush the other segments, either in the default cache or the keep pool. Segments that contain frequently accessed blocks should be assigned to the keep buffer pool so that the blocks of those segments will not be inadvertently removed, thus impacting performance.