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 : 25-06-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-14644 : table is not subpartitioned by Hash method
  • ora-28026 : user with same external name already exists
  • ora-02196 : PERMANENT/TEMPORARY option already specified
  • ora-09718 : osnsui: cannot set up user interrupt handler.
  • ora-12651 : Encryption or data integrity algorithm unacceptable
  • ora-19566 : exceeded limit of string corrupt blocks for file string
  • ora-30439 : refresh of 'string.string' failed because of string
  • ora-00053 : maximum number of enqueues exceeded
  • ora-07454 : queue timeout, string second(s), exceeded
  • ora-13627 : Setting of parameter string is disallowed until the task is reset.
  • ora-02485 : Invalid _trace_options parameter specification (string)
  • ora-13061 : topology with the name string does not exist
  • ora-27145 : insufficient resources for requested number of processes
  • ora-19611 : backup piece out of order. Expected string but found string
  • ora-08175 : discrete transaction restriction violated (string)
  • ora-12197 : TNS:keyword-value resolution error
  • ora-19621 : archivelog range has already been specified
  • ora-16000 : database open for read-only access
  • ora-12064 : invalid refresh sequence number: string
  • ora-06010 : NETASY: dialogue file too long
  • ora-27088 : unable to get file status
  • ora-13703 : The snapshot pair [string, string] for database_id string and instance_id string are not found in the current repository.
  • ora-00166 : remote/local nesting level is too deep
  • ora-36735 : A value exceeded the MAX specification
  • ora-23332 : group string is in use; cannot drop
  • ora-24080 : unschedule_propagation pending for QUEUE string and DESTINATION string
  • ora-25122 : Only LOCAL bitmap indexes are permitted on partitioned tables
  • ora-01627 : rollback segment number 'string' is not online
  • ora-14122 : only one REVERSE or NOREVERSE clause may be specified
  • ora-13135 : failed to alter spatial table
  • 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.