ORA-22872: OID INDEX clause not allowed on tables with primary key based object identifiers

Cause : A nattepmtt oc raet ea nODI NIDXE no atbal ewtihp rmiayr ekyb aesdo bejc tiednitfeir.s

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

Rmeoev hteO I DIDNE Xcalues

update : 22-07-2017

ORA-22872 - OID INDEX clause not allowed on tables with primary key based object identifiers
ORA-22872 - OID INDEX clause not allowed on tables with primary key based object identifiers

  • ora-22293 : LOB already opened in the same transaction
  • ora-27150 : attempt to notify process of pending oradebug call failed
  • ora-32642 : non-unique cell values from the ORDER BY clause
  • ora-22336 : table contained 8.0 image format, must specify INCLUDING DATA
  • ora-28106 : input value for argument #string is not valid
  • ora-13386 : commit/rollback operation error: [string]
  • ora-07303 : ksmcsg: illegal database buffer size.
  • ora-13378 : invalid index for element to be extracted
  • ora-06121 : NETTCP: access failure
  • ora-31414 : error(s) occurred during change table advance
  • ora-13850 : Tracing for client identifier string is not enabled
  • ora-29394 : session id string and serial# string do not exist
  • ora-14286 : cannot COALESCE the only subpartition of this table partition
  • ora-01124 : cannot recover data file string - file is in use or recovery
  • ora-00201 : control file version string incompatible with ORACLE version string
  • ora-24156 : duplicate table alias string
  • ora-16137 : No terminal recovery is required
  • ora-19123 : fn:zero-or-one() called with a sequence containing more than one item
  • ora-22918 : specified column or attribute is not a VARRAY type
  • ora-25185 : index column other than last can not be specified for INCLUDE clause
  • ora-07599 : spwat: $SCHDWK failure
  • ora-24142 : invalid ruleset name
  • ora-09363 : Windows 3.1 Two-Task driver invalid context area
  • ora-06511 : PL/SQL: cursor already open
  • ora-13265 : geometry identifier column string in table string is not of type NUMBER
  • ora-38499 : expression set already configured for stored/indexed attributes
  • ora-17501 : logical block size string is invalid
  • ora-13619 : The procedure argument string is greater than the maximum allowable length of string characters.
  • ora-28175 : incorrect certificate type
  • ora-10566 : Test recovery has used all the memory it can use
  • 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.