In addition, the primary key/unique constraints have to be created on referenced tables/columns. It makes no sense (except 1:1 table relationship, but it does not substitute that need anyway) to do it on the opposite (foreign key) side.
Even the error description is clear: http://ora-02270.ora-code.com/
ORA-02270: no matching unique or primary key for this column-list 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