SQL> create table part_table_large (id_column number(6), data_col_1 varchar2(100), data_col_2 varchar2(100)) partition by range (id_column) (partition p_100 values less than (101), partition p_200 values less than (201), partition p_300 values less than (301), partition p_400 values less than (401),
After the curious finding in my previous blog post, where a Partition's HighWaterMark was noticeably higher than that for a non-Partitioned Table but then shrunk on a MOVE operation, retrying the same rows with a different pattern of INSERT statements.
Early last year I put the call out to #orclapex developers, asking them to fill out some questions in survey (using a packaged APEX application, of course).
The results helped contribute to a presentation I did Kscope15. Thank you to all those who responded. I thought I'd finally post some results, see if it can elicit further discussion, even of a casual nature.