In the good old days of 8.0, this was a problem for advanced replication : the table you wanted to replicate had to have a PK and it had to be enforced by a unique index (the error message we got when this was not the case was "table or view does not exist" : very helpful in tracking down the problem :). If you are planning to use replication, you might want to check the current requirements for the PK index. mvg/regards Jo Sai Selvaganesan <ssaisundar@xxxxxxxxxxxxx> Sent by: oracle-l-bounce@xxxxxxxxxxxxx 03/31/2004 00:50 Please respond to oracle-l To: oracle-l@xxxxxxxxxxxxx cc: Subject: pros and cons hi i read the follwing line in oracle 9i documentation, Unique and primary keys can use non-unique as well as unique indexes. They can even use just the first few columns of non-unique indexes. i am planning to use a primary key constraint enforced by the first few columns of a non-unique index.any feedback or advice or gotchas in having such a setup. thanks sai ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------