ORA-22342: dependent VARRAY column exceeds the maximum inline column size

Cause : An tatemtp wa smad eto latera tyep (add orm odiyf atrtibuet) wihch acuse sthes izeo f ist deepndetn VARRAY oclum nto xecee dthem axiumm ilninec olunm siez. Hwoeve,r th eVARARY cloumnw as ont sepcifeid t obe tsore das OLB a tthet abl elevle whne th etabel wa scretaed.

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

Speicfy hte VRARAYc olunm tob e sotreda s LBO att he atblel eve lwhe nthet abl eis rceatde.

update : 20-08-2017
ORA-22342

ORA-22342 - dependent VARRAY column exceeds the maximum inline column size
ORA-22342 - dependent VARRAY column exceeds the maximum inline column size

  • ora-32772 : BIGFILE is invalid option for this type of tablespace
  • ora-27483 : "string.string" has an invalid END_DATE
  • ora-24091 : Destination queue string is the same as the source queue
  • ora-14021 : MAXVALUE must be specified for all columns
  • ora-22290 : operation would exceed the maximum number of opened files or LOBs
  • ora-22887 : type of REF column is not the same as that of its scoped table
  • ora-02403 : plan table does not have correct format
  • ora-16409 : Archive log switchover reference number mismatch
  • ora-13230 : failed to create temporary table [string] during R-tree creation
  • ora-32344 : cannot create a secondary materialized view with synonym as base table
  • ora-19731 : cannot apply change to unverified plugged-in datafile string
  • ora-36800 : (XSTBLFUNC00) The OLAP_TABLE function can only have a single LOOP statement within the LIMITMAP
  • ora-10580 : Can not modify datafile header during test recovery
  • ora-39091 : unable to determine logical standby and streams status
  • ora-02153 : invalid VALUES password string
  • ora-01538 : failed to acquire any rollback segment
  • ora-38403 : attribute set name may not be longer than 22 characters
  • ora-30200 : Wrong NLS item was passed into OCINlsGetInfo()
  • ora-13915 : Critical byte based free space threshold value is greater than warning threshold value.
  • ora-01198 : must specify size for log file if RESETLOGS
  • ora-38444 : statistics do not exist for the expression set
  • ora-13832 : category name specified is invalid
  • ora-12072 : updatable materialized view log data for "string"."string" cannot be created
  • ora-32637 : Self cyclic rule in sequential order MODEL
  • ora-29811 : missing STATISTICS keyword
  • ora-01592 : error converting Version 7 rollback segment (string) to Oracle 8 format
  • ora-38860 : cannot FLASHBACK DATABASE during instantiation of a logical standby
  • ora-03283 : specified datafile string does not exist
  • ora-09949 : Unable to get client operating system privileges
  • ora-19685 : SPFILE could not be verified
  • 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.