What value Oracle uses for db_cache_size when making decision on direct path reads if db_cache_size isn't set?
From: vsevolod afanassiev <vsevolod.afanassiev_at_gmail.com>
Date: Thu, 14 Aug 2014 04:37:08 -0700 (PDT)
Message-ID: <d1816bdd-2915-4daa-94af-fc4ae57b2189_at_googlegroups.com>
It is known that from 11.2.02 Oracle would use direct path reads when doing full table scan if table size exceeds certain percentage of the db_cache_size.
Date: Thu, 14 Aug 2014 04:37:08 -0700 (PDT)
Message-ID: <d1816bdd-2915-4daa-94af-fc4ae57b2189_at_googlegroups.com>
It is known that from 11.2.02 Oracle would use direct path reads when doing full table scan if table size exceeds certain percentage of the db_cache_size.
Question: if we are using AMM and set memory_target and memory_max_target but don't set db_cache_size - what value Oracle would use for db_cache_size when deciding whether to use direct path reads of buffered reads for a particular table? Received on Thu Aug 14 2014 - 13:37:08 CEST