Any side effects of storage parameter buffer_pool KEEP instead of DEFAULT if database has no KEEP po
We have 12.1.0.2 database with SGA_TARGET 180G. Several application objects (tables, indexes, table_partitions, index_partitions) are defined with buffer_pool KEEP by former developers (more randomly, not following recommendations, not reasonable).
Database parameter DB_KEEP_CACHE_SIZE and DB_RECYCLE_CACHE_SIZE are both zero, DEFAULT buffer pool used only.
Does buffer_pool KEEP parameter on database objects cause any side effects in a database which does not use KEEP buffer pool? Maybe does optimizer internally use KEEP storage flag? Or does buffer in default cache stay longer in buffer than objects with buffer_pool DEFAULT, maybe other internal differences in LRU management?