![]() ![]() ![]() Summaryĭon’t try inserting NULLs as a partitioning key if that partition key uses interval partitioning. Today I learned that database links don’t have object_ids. I hadn’t thought about NULL values in dba_objects.object_id, but apparently there are: SQL> select object_id, object_name, object_type from dba_objects where object_id is null NEARBY: not having a not-null constraint on a partition key might be an indication of a sub-optimal design choice.Ī quick search revealed an article on AskTom mentioning NULLs. There shouldn’t be more than 16 partitions … I knew about the limit of 1048575 partitions, but that shouldn’t be the case here: SQL> select max(object_id), max(object_id) / 5000 from dba_objects *Action Ensure that the partitioning key falls within 1048575 partitions or subpartitions. *Cause: The row inserted had a partitioning key that maps to a partition number greater than 1048575 ![]() ORA-14300: partitioning key maps to a partition outside maximum permittedġ4300, 00000, "partitioning key maps to a partition outside maximum permitted number of partitions" Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - ProductionĢ partition by range (id) interval (5000)Ħ select object_id, object_name, created from dba_objects Last Successful login time: Fri 09:07:55 +02:00 As always, if you are following along, make sure you are appropriately licensed for this feature The SituationĬonsider the following example: SQL*Plus: Release 19.0.0.0.0 - Production on Fri Aug 16 09:32:17 2019Ĭopyright (c) 1982, 2019, Oracle. This time I decided to write about it so I don’t have to spend 5 minutes rediscovering the wheel. While researching interval partitioning in Oracle 19c I came across a phenomenon I had already solved a long time ago but then forgot about. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |