ORA-22918: specified column or attribute is not a VARRAY type

Cause : Attemp to define a VARRAY storage clause for a column or attribute which is not VARRAY type.

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

Specify VARRAY storage clause for a VARRAY column or attribute.

update : 27-05-2017
ORA-22918

ORA-22918 - specified column or attribute is not a VARRAY type
ORA-22918 - specified column or attribute is not a VARRAY type

  • ora-07482 : snlmini: cannot create lock manager instance.
  • ora-09320 : szrfc: unable to obtain the list of valid OS roles
  • ora-00081 : address range [string, string) is not readable
  • ora-16000 : database open for read-only access
  • ora-19637 : backupPieceCreate requires file name when using DISK device
  • ora-27198 : skgfpvl: sbtpcvalidate returned error
  • ora-02025 : all tables in the SQL statement must be at the remote database
  • ora-01259 : unable to delete datafile string
  • ora-27102 : out of memory
  • ora-25229 : error on transformation of message string string
  • ora-28668 : cannot reference mapping table of an index-organized table
  • ora-19759 : block change tracking is not enabled
  • ora-31487 : cannot support begin dates or end dates in this configuration
  • ora-28121 : driving context does not exist
  • ora-13285 : Geometry coordinate transformation error
  • ora-02727 : osnpop: access error on orapop executable
  • ora-24775 : cannot prepare or commit transaction with non-zero lock value
  • ora-31467 : no column found in the source table
  • ora-06323 : IPA: Cause event error
  • ora-02832 : Segment deallocation failed - segment not on list
  • ora-16179 : incremental changes to "string" not allowed with SPFILE
  • ora-36706 : (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension.
  • ora-32102 : invalid OCI handle
  • ora-06916 : CMX: error in data read (t_datain)
  • ora-33076 : (XSAGDNGL37) In AGGMAP workspace object, the value 'number' is not a valid value of dimension workspace object.
  • ora-27505 : IPC error destroying a port
  • ora-10638 : Index status is invalid
  • ora-25959 : join index must be of the bitmap type
  • ora-14295 : column type or size mismatch between partitioning columns and subpartitioning columns
  • ora-24168 : rule string.string cannot have default evaluation context
  • 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.