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 : 28-05-2017

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

  • ora-13335 : LRS measure information not defined
  • ora-12166 : TNS:Client can not connect to HO agent.
  • ora-29258 : buffer too small
  • ora-25136 : this cluster can contain only one table
  • ora-12350 : database link being dropped is still mounted
  • ora-27061 : waiting for async I/Os failed
  • ora-37112 : OLAP API requires Oracle 9.2 or later
  • ora-33022 : (XSAGDNGL10) The measure dimension workspace object must be a TEXT or ID base dimension that does not dimension AGGMAP workspace object, but is in the same analytic workspace.
  • ora-07631 : smcacx: $EXPREG failure
  • ora-26511 : master table 'string.string' not found
  • ora-39039 : Schema expression "string" contains no valid schemas.
  • ora-01982 : invalid auditing option for tables
  • ora-01488 : invalid nibble or byte in the input data
  • ora-13799 : threshold not found
  • ora-37128 : (XSCCOMP03) It is not possible to PARTITION over a base of a COMPRESSED COMPOSITE.
  • ora-16187 : LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
  • ora-39304 : conflicting changes to object "string" : string
  • ora-06307 : IPA: Cannot reset connection
  • ora-00341 : log string of thread string, wrong log # string in header
  • ora-06135 : NETTCP: connection rejected; server is stopping
  • ora-12094 : error during online redefinition
  • ora-32305 : RepAPI materialized views with user-defined types are not supported
  • ora-00824 : cannot set sga_target due to existing internal settings, see alert log for more information
  • ora-01681 : max # extents (string) reached in LOB segment in tablespace string
  • ora-24785 : Cannot resume a non-migratable transaction
  • ora-29800 : invalid name for operator
  • ora-31659 : status message was invalid type - detaching job
  • ora-21560 : argument string is null, invalid, or out of range
  • ora-01620 : no public threads are available for mounting
  • ora-03204 : the segment type specification should indicate partitioning
  • 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.