Constraints on a Partition Table

Question

Hi There,
I have a question reg. PK constraint on a partition table please.
We have a partition table with a primary key and a PK local defined index, as well as other local indexes defined on the table. My question is, how come we don't see a PK constraint in DBA_CONSTRAINTS for the table, yet the PK index is there:
SQL> select owner, CONSTRAINT_NAME, CONSTRAINT_TYPE, status, DEFERRABLE, INDEX_NAME from dba_constraints where table_name='STR_ORDER_MM';
OWNER                CONSTRAINT_NAME                C STATUS   DEFERRABLE     INDEX_NAME               
AADV                 SYS_C003510                    C ENABLED  NOT DEFERRABLE
AADV                 SYS_C003511                    C ENABLED  NOT DEFERRABLE
AADV                 SYS_C003512                    C ENABLED  NOT DEFERRABLE
AADV                 SYS_C003513                    C ENABLED  NOT DEFERRABLE
AADV                 SYS_C003514                    C ENABLED  NOT DEFERRABLE
AADV                 SYS_C003515                    C ENABLED  NOT DEFERRABLE
AADV                 SYS_C003516                    C ENABLED  NOT DEFERRABLE
AADV                 SYS_C003517                    C ENABLED  NOT DEFERRABLE
AADV                 SYS_C003518                    C ENABLED  NOT DEFERRABLE
9 rows selected.
SQL> select OWNER,INDEX_NAME,INDEX_TYPE,TABLE_NAME,UNIQUENESS,INCLUDE_COLUMN,STATUS from dba_indexes where table_name='STR_ORDER_MM';
OWNER         INDEX_NAME                     INDEX_TYPE                  TABLE_NAME                     UNIQUENES INCLUDE_COLUMN STATUS
AADV          PK_STR_ORDER_MM                NORMAL                      STR_ORDER_MM                   UNIQUE                   N/A
AADV          IX_STR_ORDER_MM_01             BITMAP                      STR_ORDER_MM                   NONUNIQUE                N/A
AADV          IX_STR_ORDER_MM_02             BITMAP                      STR_ORDER_MM                   NONUNIQUE                N/A
AADV          IX_STR_ORDER_MM_03             BITMAP                      STR_ORDER_MM                   NONUNIQUE                N/A
AADV          IX_STR_ORDER_MM_04             BITMAP                      STR_ORDER_MM                   NONUNIQUE                N/A
AADV          IX_STR_ORDER_MM_05             BITMAP                      STR_ORDER_MM                   NONUNIQUE                N/A
AADV          IX_STR_ORDER_MM_06             BITMAP                      STR_ORDER_MM                   NONUNIQUE                N/A
AADV          IX_STR_ORDER_MM_07             NORMAL                      STR_ORDER_MM                   NONUNIQUE                N/A
8 rows selected.
SQL> select OWNER,TABLE_NAME,INDEX_NAME,LOCALITY,PARTITION_COUNT from DBA_PART_INDEXES where table_name='STR_ORDER_MM' order by 3;
OWNER         TABLE_NAME                     INDEX_NAME                     LOCALI PARTITION_COUNT
AADV          STR_ORDER_MM                   IX_STR_ORDER_MM_01             LOCAL              840
AADV          STR_ORDER_MM                   IX_STR_ORDER_MM_02             LOCAL              840
AADV          STR_ORDER_MM                   IX_STR_ORDER_MM_03             LOCAL              840
AADV          STR_ORDER_MM                   IX_STR_ORDER_MM_04             LOCAL              840
AADV          STR_ORDER_MM                   IX_STR_ORDER_MM_05             LOCAL              840
AADV          STR_ORDER_MM                   IX_STR_ORDER_MM_06             LOCAL              840
AADV          STR_ORDER_MM                   IX_STR_ORDER_MM_07             LOCAL              840
AADV          STR_ORDER_MM                   PK_STR_ORDER_MM                LOCAL              840
8 rows selected.
Shouldn't there be a PK constraint (constraint type "P") defined under DBA_CONSTRAINTS with an INDEX_NAME of "PK_STR_ORDER_MM"? or is that not the case for partitioned tables?
Thanks for your help

Answer 1

Maybe whoever created the table didn't actually create a constraint but simply created a unique index that started with the letters "PK".