After upgrade from 11g to 12c/18c/19c,Alter Table Exchange Partition ddl Populates V$Im_Column_Level Even Though Table Is Not Using Inmemory
(Doc ID 2747737.1)
Last updated on FEBRUARY 02, 2021
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
In this case, Database was upgraded from 220.127.116.11 to 18.6. After the upgrade, noticed the issue related to InMemory. The issue is, alter table exchange partition operation caused populate rows under v$im_column_level even though The table is is not using InMemory.
Below is a small test case explaining the issue.
In this case Database was upgraded from 11.2 to 18c.
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