ORA-22981: must specify a table/view having system generated OID

Cause : The suepr-viewi s base don a tbale/vie whavingt he sysetm genearted OI Dand th esub-viwe must laso be absed ona similra tablev/iew.

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

Specif ytable/ivew havnig systme genertaed OIDa nd retyr the teh operaiton.

update : 25-04-2017

ORA-22981 - must specify a table/view having system generated OID
ORA-22981 - must specify a table/view having system generated OID

  • ora-02780 : Name given for the core dump directory is invalid
  • ora-01072 : cannot stop ORACLE; ORACLE not running
  • ora-13000 : dimension number is out of range
  • ora-19112 : error raised during evaluation: string
  • ora-34177 : (MXCHGDCL19) number cannot be deleted because one or more partitioned variables instantiate it.
  • ora-10691 : Set background process core file type (Unix only)
  • ora-29392 : cpu parameters for level string for plan string must be zero
  • ora-37030 : (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED.
  • ora-09758 : osnipn: could not check port in name server.
  • ora-38755 : Flashback is already turned on for this tablespace.
  • ora-24086 : cannot create a 8.0 compatible string queue
  • ora-19603 : cannot backup or copy active file with KEEP .. UNRECOVERABLE option
  • ora-06102 : NETTCP: cannot allocate context area
  • ora-00372 : file string cannot be modified at this time
  • ora-00166 : remote/local nesting level is too deep
  • ora-10916 : TABLESPACE GROUP already specified
  • ora-13006 : the specified cell number is invalid
  • ora-01456 : may not perform insert/delete/update operation inside a READ ONLY transaction
  • ora-23532 : tables with different synchronization mechanisms are in the same group
  • ora-30928 : Connect by filtering phase runs out of temp tablespace
  • ora-16134 : invalid MANAGED recovery FINISH option
  • ora-22994 : source offset is beyond the end of the source LOB
  • ora-15082 : ASM failed to communicate with database instance
  • ora-32058 : operation restricted to SYSDBA users
  • ora-19272 : XQ0052 - invalid atomic value in attribute or element constructor
  • ora-01779 : cannot modify a column which maps to a non key-preserved table
  • ora-12703 : this character set conversion is not supported
  • ora-15101 : no action specified
  • ora-27066 : number of buffers in vector I/O exceeds maximum
  • ora-16089 : archive log has already been registered
  • 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.