ORA-22875: cannot drop primary key of an object table whose object identifier is primary key based

Cause : Ana ttmeptt o rdopt hep riamryk eyo f na ojbec ttalbe hwic hha sa rpimray eky abse dobejcti detnifeir

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

Reomvet hed ro pprmiar yke ycluase

update : 23-04-2017

ORA-22875 - cannot drop primary key of an object table whose object identifier is primary key based
ORA-22875 - cannot drop primary key of an object table whose object identifier is primary key based

  • ora-30040 : Undo tablespace is offline
  • ora-13342 : an arc geometry has fewer than three coordinates
  • ora-24272 : initialization value must be either F or T
  • ora-12701 : CREATE DATABASE character set is not known
  • ora-14641 : STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition
  • ora-31037 : Invalid XML attribute name string
  • ora-29958 : fatal error occurred in the execution of ODCIINDEXCREATE routine
  • ora-01122 : database file string failed verification check
  • ora-01299 : dictionary string corresponds to a different database incarnation
  • ora-07484 : snlkput: cannot convert(put) lock.
  • ora-25116 : invalid block number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-15059 : invalid device type for ASM disk
  • ora-29839 : failed to validate implementation type
  • ora-36960 : (XSFCAST27) The value of the string expression must be an odd number. You specified number.
  • ora-13052 : unsupported geometric type for geometry string.string
  • ora-24353 : user buffer too small to accommodate COBOL display type
  • ora-28184 : global user cannot have proxy permissions managed in the directory
  • ora-26698 : %s did not have a string rule set
  • ora-39143 : dump file "string" may be an original export dump file
  • ora-36165 : (XSAGGCNTPROP) Variable workspace object cannot have both an AGGCOUNT and the $COUNTVAR property.
  • ora-19643 : datafile string: incremental-start SCN is too recent
  • ora-27143 : OS system call failure
  • ora-01313 : LogMiner dictionary column type different from specified type
  • ora-15021 : parameter "string" is not valid in string instance
  • ora-13613 : The requested operation is not supported for this advisor object.
  • ora-13181 : unable to determine length of column string_SDOINDEX.SDO_CODE
  • ora-09710 : soarcv: buffer overflow.
  • ora-12522 : TNS:listener could not find available instance with given INSTANCE_ROLE
  • ora-29894 : base or varray datatype does not exist
  • ora-33288 : (DBERR15) Another user has incompatible access to analytic workspace string, and the wait timeout has expired.
  • 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.