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 : 29-04-2017
ORA-22997

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-14032 : partition bound of partition number string is too high
  • ora-22631 : attribute [string] is is not well-formed or does not match the type
  • ora-31214 : DBMS_LDAP: PL/SQL - Invalid LDAP mod type.
  • ora-30331 : summary does not exist
  • ora-16761 : resource guard could not stop SQL Apply
  • ora-16649 : database will open after Data Guard broker has evaluated Fast-Start Failover status
  • ora-12092 : cannot online redefine replicated table "string"."string"
  • ora-27028 : skgfqcre: sbtbackup returned error
  • ora-14119 : specified partition bound is too long
  • ora-30021 : Operation not allowed on undo tablespace
  • ora-30964 : The XML Index was not usable.
  • ora-37999 : Serious OLAP error: string. Please contact Oracle Technical Support.
  • ora-19902 : incarnation key string not found
  • ora-13016 : specified topology [string] is invalid
  • ora-16591 : unknown field "string" in document
  • ora-16081 : insufficient number of processes for APPLY
  • ora-19235 : XQ0015 - unsupported must-understand extension
  • ora-07253 : spdes: semctl error, unable to destroy semaphore set.
  • ora-10360 : enable dbwr consistency checking
  • ora-29973 : Unsupported query or operation during change notification registration
  • ora-01249 : archiving not allowed in a clone database
  • ora-09889 : osnTXtt: access error on oracle executable
  • ora-31604 : invalid string parameter "string" for object type string in function string
  • ora-22280 : no more buffers available for operation
  • ora-24102 : invalid prefix for generate_job_name
  • ora-10690 : Set shadow process core file dump type (Unix only)
  • ora-25402 : transaction must roll back
  • ora-01223 : RESETLOGS must be specified to set a new database name
  • ora-13408 : invalid blockSize storage parameter
  • ora-01945 : DEFAULT ROLE[S] already specified
  • 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.