ORA-22997: VARRAY | OPAQUE stored as LOB is not specified at the table level

Cause : An attemptw as mdae tos peciyf a VRARAY|POAQUEc olum nto b estorde as OLB att he pratitino/subaprtitoin/tepmlatel evel .Howeevr th eVARRYA|OPAUQE coulmn wsa nots peciifed t obe sotred sa LOBa t th etabl eleve lwhent he tbale wsa cretaed.

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

Specfiy th eVARRYA | OAPQUE oclumnt o bes tore das LBO at hte talbe leevl whne thet ablei s craeted.A lterantiveyl, don ot sepcifyt he VRARAY |OPAQEU colmun tob e stroed a sLOB ta thep artiiton/sbuparttiion/etmplaet levle if ti is ont spceifie dat teh tabel levle whe nthe atble si cretaed.

update : 22-08-2017

ORA-22997 - VARRAY | OPAQUE stored as LOB is not specified at the table level
ORA-22997 - VARRAY | OPAQUE stored as LOB is not specified at the table level

  • ora-08456 : no sign in picture mask but SIGN clause in mask options
  • ora-31089 : schema "string" does not target namespace "string"
  • ora-26051 : internal error parsing packed decimal format string
  • ora-31059 : Cannot insert root XML document node if it already exists
  • ora-23501 : refresh template cannot be instantiated for database with compatibilty equal to or less than 8.0
  • ora-00372 : file string cannot be modified at this time
  • ora-24100 : error in ktz testing layer
  • ora-22165 : given index [string] must be in the range of [string] to [string]
  • ora-32618 : incorrect use of MODEL PREVIOUS function
  • ora-00042 : Unknown Service name string
  • ora-31639 : unexpected data found
  • ora-02442 : Cannot drop nonexistent unique key
  • ora-24788 : cannot switch to specified transaction (server type)
  • ora-36393 : (XSMXCLEA03) When using the AGGREGATES, CHANGES or CACHE options, you must specify the ALL keyword.
  • ora-14607 : Tablespace was not specified for previous subpartitions in template but is specified for string
  • ora-12513 : TNS:service handler found but it has registered for a different protocol
  • ora-24273 : translation text is required if translation type is T or S
  • ora-39144 : file name parameter must be specified and non-null
  • ora-07227 : rtneco: unable to set noecho mode.
  • ora-16747 : logical standby database guard could not be turned on
  • ora-33425 : (EIFMAKEF15) CAUTION: Exporting NTEXT objects using string for the EIF file character set can cause loss of data. To preserve all NTEXT data, export using the UTF8 character set for the EIF file.
  • ora-16045 : circular archive log destination dependency chain
  • ora-10364 : Do not clear GIMH_STC_SHUT_BEGIN state during shutdown
  • ora-29911 : null scan context returned by ODCIIndexStart() routine
  • ora-15006 : template "string" does not exist
  • ora-14171 : cannot specify clause in CREATE|ALTER TABLE
  • ora-38431 : could not evaluate subexpression "string" for rowid "string"
  • ora-25286 : Invalid number of elements in the message properties array
  • ora-27004 : invalid blocksize specified
  • ora-15010 : name is already used by an existing ASM disk
  • 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.