ORA-22899: cannot specify both scope and rowid constraint on ref column

Cause : An atetmpt wsa madet o speicfy boht a scpoe anda rowi dconstarint o na REFc olumn.

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

Remov eeithe rthe rwoid ors cope ocnstranit andt hen rtery th eoperaiton.

update : 23-06-2017
ORA-22899

ORA-22899 - cannot specify both scope and rowid constraint on ref column
ORA-22899 - cannot specify both scope and rowid constraint on ref column

  • ora-01690 : sort area size too small
  • ora-16064 : remote archival is disabled by another instance
  • ora-03244 : No free space found to place the control information
  • ora-14626 : values being added already exist in DEFAULT subpartition
  • ora-25206 : enqueue failed, enqueue to exception queue string.string not permitted
  • ora-38442 : The ADT "string" is not in a valid state.
  • ora-14120 : incompletely specified partition bound for a DATE column
  • ora-27545 : Fail to prepare buffer for remote update
  • ora-16128 : User initiated stop apply successfully completed
  • ora-32772 : BIGFILE is invalid option for this type of tablespace
  • ora-02450 : Invalid hash option - missing keyword IS
  • ora-16055 : FAL request rejected
  • ora-32025 : %s.string is not a table or view object.
  • ora-31445 : invalid lock handle while acquiring lock on string
  • ora-00318 : log string of thread string, expected file size string doesn't match string
  • ora-32103 : error from OCI call
  • ora-15180 : Could not open dynamic library string, error [string]
  • ora-01941 : SEQUENCE keyword expected
  • ora-02765 : Invalid maximum number of servers
  • ora-40225 : model is currently in use by another process
  • ora-14268 : subpartition 'string' of the partition resides in offlined tablespace
  • ora-30960 : The entity is neither an XPATH nor a NAMESPACE.
  • ora-00381 : cannot use both new and old parameters for buffer cache size specification
  • ora-07238 : slemcl: close error.
  • ora-19277 : XP0005 - XPath step specifies an item type matching no node: (string)
  • ora-35076 : (QFHEAD04) CAUTION: The textual data in EIF file string is encoded in a character set that is not recognized by this version of string.
  • ora-00339 : archived log does not contain any redo
  • ora-02254 : DEFAULT not allowed here
  • ora-32811 : subscriber string already exists
  • ora-09949 : Unable to get client operating system privileges
  • 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.