My Oracle Support Banner

Changing Buffer_pool for a Partitioned Table Requires Database to be Bounced (Doc ID 1077819.1)

Last updated on MARCH 28, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.4 to 11.2.0.1 [Release 10.2 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Problem Description:
The following changes for a non-partitioned table produces the expected result:
. Create a table with STORAGE (BUFFER_POOL KEEP)
. Blocks are going into the KEEP buffer.
. Alter the table with STORAGE (BUFFER_POOL DEFAULT)
. Flush buffer cache
. As expected blocks are now stored in the DEFAULT buffer.

The following actions for a partitioned table produce a different result:
. Create a table with two partitions, one of them with STORAGE (BUFFER_POOL KEEP)
Ex: PARTITION ONE VALUES LESS THAN (10),
PARTITION TWO VALUES LESS THAN (20) STORAGE (BUFFER_POOL KEEP))
. Blocks are going into the KEEP buffer.
. Alter the table with modify PARTITION TWO STORAGE (BUFFER_POOL DEFAULT)
. Flush buffer cache
. Blocks are still stored in the KEEP buffer.
. After rebouncing the instance, blocks are stored in the DEFAULT as expected.

This behaviour was reproduced in 10.2.0.4 and 11.2.0.1.

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.