ORA-02260: table can have only one primary key

Cause : Selfe-videtn.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Remoev thee xtrap rimayr key.

update : 24-09-2017
ORA-02260

ORA-02260 - table can have only one primary key
ORA-02260 - table can have only one primary key

  • ora-14125 : REVERSE/NOREVERSE may not be specified in this context
  • ora-28277 : LDAP search, while authenticating global user with passwords, failed.
  • ora-02239 : there are objects which reference this sequence
  • ora-09951 : Unable to create file
  • ora-07570 : szrfc: $IDTOASC failure
  • ora-25124 : Database link name not allowed.
  • ora-00443 : background process "string" did not start
  • ora-06504 : PL/SQL: Return types of Result Set variables or query do not match
  • ora-04072 : invalid trigger type
  • ora-03236 : max # extents (string) reached in index string.string subpartition string
  • ora-00439 : feature not enabled: string
  • ora-07493 : scgrcl: lock manager error.
  • ora-12476 : least upper bound resulted in an invalid OS label
  • ora-39037 : Object type path not supported for string metadata filter.
  • ora-01060 : array binds or executes not allowed
  • ora-00438 : %s Option not installed
  • ora-38796 : Not enough flashback database log data to undo FLASHBACK.
  • ora-01283 : Options specified is invalid
  • ora-25531 : MTTR specified is too small: string
  • ora-15104 : conflicting CONTENTS options
  • ora-37070 : You may not execute OLAP DML programs in a parallel query session.
  • ora-06510 : PL/SQL: unhandled user-defined exception
  • ora-09363 : Windows 3.1 Two-Task driver invalid context area
  • ora-07565 : sldext: $SEARCH failure
  • ora-38954 : Cross platform transport is not supported between source platform identifier string and target platform identifier string
  • ora-12031 : cannot use primary key columns from materialized view log on "string"."string"
  • ora-13043 : failed to read metadata from the _SDOLAYER table
  • ora-16216 : Log stream sequence error
  • ora-12354 : secondary object being dropped
  • ora-12711 : this CREATE CONTROLFILE character set is not allowed
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.