ORA-22974: missing WITH OBJECT OID clause

Cause : WITH OBJECT OID clause is not specified when creating an object view.

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

Specify the WITH OBJECT OID clause.

update : 25-06-2017

ORA-22974 - missing WITH OBJECT OID clause
ORA-22974 - missing WITH OBJECT OID clause

  • ora-21700 : object does not exist or is marked for delete
  • ora-03210 : DBMS_ADMIN_PACKAGE invalid option specification
  • ora-16170 : Terminal recovery may have left the database in an inconsistent state
  • ora-24379 : invalid user callback type
  • ora-01253 : cannot start online backup - file string in recovery manager backup
  • ora-35952 : (XSSPFC01) The string dimension workspace object and the string dimension workspace object must have the same number of values in status for SPFCEXEC method number.
  • ora-39098 : Worker process received data objects while loading metadata. Invalid process order range is string..string
  • ora-28534 : Heterogeneous Services preprocessing error
  • ora-31399 : Cannot contact LDAP server string at port number
  • ora-01517 : log member: 'string'
  • ora-22897 : no scope clause specified for user-defined REF column "string"
  • ora-22606 : pickler image handle [string] is not well-formed
  • ora-32845 : Messaging Gateway agent is already running
  • ora-13124 : unable to determine column id for column string
  • ora-02720 : osnfop: shmat failed
  • ora-30204 : buffer is not large enougth
  • ora-30649 : missing DIRECTORY keyword
  • ora-01511 : error in renaming log/data files
  • ora-22905 : cannot access rows from a non-nested table item
  • ora-00567 : Requested processor group string is too large (maximum string)
  • ora-25951 : join index where clause cannot contain OR condition
  • ora-26011 : Cannot load type string into column string in table string
  • ora-36174 : (XSMXAGGR23) workspace object must be either a VARIABLE, a RELATION or a FORMULA.
  • ora-06515 : PL/SQL: unhandled exception string
  • ora-34000 : (MODCOMP13) You cannot use both workspace object and workspace object as model dimensions, because they are both surrogates of dimension workspace object.
  • ora-07756 : slemcf: fread failure
  • ora-31001 : Invalid resource handle or path name "string"
  • ora-13065 : cannot delete a child layer with a parent layer
  • ora-12154 : TNS:could not resolve the connect identifier specified
  • ora-25964 : column type incompatible with join column type
  • 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.