Oracle Magazine, September/October 2017
DBA PERFORMANCE ORACLE MAGAZINE SEPTEMBER OCTOBER 2017 83 PARTITION_ NAME HIGH_ VALUE P1 VG SYS_ P1095 SG Note how Oracle Database created a new partition SYS_ P1095 for the SG value However you might wonder did the new row actually go into that partition Lets check select from accounts partition SYS_ P1095 ACC_ NO ACC_ TYPE STATUS_ CODE ACC_ BALANCE 2 S SG 3000 Yes the partition was created at runtime to accommodate a new row for which no partition existed and the row was inserted into that partition With automatic list partitioning in Oracle Database 12c Release 2 you dont have to know all the possible values of the partitioning key to create the list partitioned table Oracle Database handles that for you automatically because of the AUTOMATIC keyword in the PARTITION BY LIST clause Oracle Database creates this partition automatically via an autonomous transaction separate from the INSERT transaction So the partition stays even if you roll back the operation The automatic list partitioning strategy is only for partitions it cannot be used for a subpartitioning clause If you use list subpartitioning you should use the DEFAULT
You must have JavaScript enabled to view digital editions.
