Copy of Oracle FAQ ORACLE RECOVERY without DUL
ORAFAQ HOME | ORAFAQ ASK QUESTION | ORAFAQ ADD INFO | ORAFAQ SEARCH | ORAFAQ E-MAIL
 

Index > ORACLE Server Parameters > _db_block_max_dirty_target

_db_block_max_dirty_target


NOTE: This is an internal Oracle parameter. Do NOT use it unless instructed to do so by Oracle Support. Playing with this parameter may be harmful.

Oracle 10.0.1:

No such parmeter in Oracle 10.0.1.

Oracle 9.2.0:

Paramter Name:_db_block_max_dirty_target
Description:Upper bound on modified buffers/recovery reads
Type:NUMBER Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:IMMEDIATE

Oracle 8.1.7:

Paramter Name:db_block_max_dirty_target
Description:Upper bound on modified buffers/recovery reads
Type:NUMBER Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:IMMEDIATE

Oracle 8.0.6:

Paramter Name:db_block_max_dirty_target
Description:Target upper bound on number of buffers that can be dirty
Type:NUMBER Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:IMMEDIATE

Oracle 7.3.4:

No such parmeter in Oracle 7.3.4.

This parameter is not documented and should not be used. Search for more info about [ _db_block_max_dirty_target ] on the Oracle FAQ.

ORAFAQ HOME | ORAFAQ ASK QUESTION | ORAFAQ ADD FAQ | ORAFAQ SEARCH | ORAFAQ E-MAIL
All content of this page is copy from www.orafaq.com