ORA-02270: no matching unique or primary key for this
column-list
Answers were Sorted based on User's Feedback
Answer / sangam
ORA-02270: no matching unique or primary key for this
column-list
This error also occurs when we try to add a foreign key
constraint to a table and there does not exist primary key
in the referenced table or the column being referenced is
not a promary key.
http://dotnetspidor.blogspot.com
| Is This Answer Correct ? | 12 Yes | 3 No |
Answer / guest
Cause: A REFERENCES clause in a CREATE/ALTER TABLE statement
gives a column-list for which there is no matching unique or
primary key constraint in the referenced table.
Action: Find the correct column names using the
ALL_CONS_COLUMNS catalog view
Please add more information about this Error
| Is This Answer Correct ? | 8 Yes | 3 No |
Answer / pauline wan
You tried to reference a table using a unique key, but the
column that you listed only have unique index instead of
unique constraint. For example, referenced table called A
has PK column a1, another column a2, a2 has unique index
but not unique constraint, child table B has PK column b1
and another column b2. Now if you want to add FK on
table B column b2 which references table A column a2, you
will get ORA-02270.
To solve the problem, you need to drop unique index on
table A column a2 and create unique constraint on table A
column a2, then add FK on table B column b2.
The tricky is unique index has same functionality as unique
constraint which uniquely identify the data on the column,
but it doesn't have information in user_constraints,
all_constraints,dba_constraints.
| Is This Answer Correct ? | 8 Yes | 3 No |
Answer / jay
please u can check your primary key field
after set unique yes
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / chetan
CAUSE:You tried to reference a table using a unique or
primary key, but the columns that you listed did not match
the primary key, or a primary key does not exist for this
table.
SOL:
This error commonly occurs when you try to create a foreign
key that references a table that doesn't have a primary
key. To resolve this problem, create a primary key on the
referenced table. Then re-execute your command to create
the foreign key.
| Is This Answer Correct ? | 1 Yes | 3 No |
TNS-00303: Connection Manager: Reread parameter data
ORA-31444: parameter error while acquiring lock on string
ORA-36952: (XSFCAST23) You cannot specify a cycle number when querying the string forecasting option.
QSM-02138: agg(expr) requires correspondng agg(expr*expr) function
SQL*Loader-00262: PIECED keyword (on column string) allowed only when path is direct
SQL*Loader-00306: Token longer than max allowable length of number chars
LPX-00107: element "~S" has multiple declarations
SQL-01075: you are currently logged on
ORA-09797: Failed to get O/S MAC privileges.
NZE-29236: the random number generator will not accept seed
PLS-00614: creating a FINAL NOT INSTANTIABLE type
NNO-00607: server will forward to default forwarders only