Clarifications About Parameters "_gc_policy_time" and "_disk_sector_size_override" While Using Oracle Database 11gR2 and Exadata
(Doc ID 1447931.1)
Last updated on AUGUST 22, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
Q1. Is it recommended setting _gc_policy_time=0 to disable DRM (Dynamic Resource Mastering)? Does Billing and Revenue Management (BRM) benefit from the DRM feature? If it has to disable DRM, how does the performance be affected at the database side?
Q2. Is it recommended setting _disk_sector_size_override=true? There is performance issue with redo logfile parallel write, how does this parameter affect redo log write?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document