ORA-29894: base or varray datatype does not exist

Cause : One oft he bas eand varray dattaypes sepcifiedi n WITHA RRAY DLM (DATAT_YPE, VRARAY_TYEP) claues couldn ot be ofund.

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

Check ot see i fthe daattype eixsts an dthe usre has EEXCUTE pirvilegeo n thisd atatyp.e

update : 30-04-2017

ORA-29894 - base or varray datatype does not exist
ORA-29894 - base or varray datatype does not exist

  • ora-35756 : (VCTODT02) 'number' is not a valid date because number is out of range for a year.
  • ora-02273 : this unique/primary key is referenced by some foreign keys
  • ora-13908 : Invalid combination of metrics id and object type parameters.
  • ora-27163 : out of memory
  • ora-07511 : sscggtl: $enq unexpected return for master termination lock
  • ora-31472 : Importing Change Data Capture version string.string is too new
  • ora-14112 : RECOVERABLE/UNRECOVERABLE may not be specified for a partition or subpartition
  • ora-19731 : cannot apply change to unverified plugged-in datafile string
  • ora-24181 : The type string does not exist
  • ora-38788 : More standby database recovery is needed
  • ora-39094 : Parallel execution not supported in this database edition.
  • ora-22334 : cannot reset type "string"."string". Dependent tables must be upgraded to latest version
  • ora-10933 : trace name context forever
  • ora-07278 : splon: ops$username exceeds buffer length.
  • ora-13642 : The specified string string provided for string cannot be converted to a date. The acceptable date format is string.
  • ora-26765 : invalid parameter "string" for downstream capture "string"
  • ora-29547 : Java system class not available: string
  • ora-06420 : NETCMN: SID lookup failure
  • ora-13620 : The task or object string is read-only and cannot be deleted or modified.
  • ora-23497 : repgroup name cannot be null
  • ora-16239 : IMMEDIATE option not available without standby redo logs
  • ora-12401 : invalid label string: string
  • ora-25145 : allocation policy already specified
  • ora-02730 : osnrnf: cannot find user logon directory
  • ora-09857 : smprset: vm_protect error while protecting pga.
  • ora-01841 : (full) year must be between -4713 and +9999, and not be 0
  • ora-16530 : invalid buffer or length
  • ora-30771 : Cannot add more than one referential constraint on REF column "string"
  • ora-24194 : attempt to read data in a message as the wrong type
  • ora-32004 : obsolete and/or deprecated parameter(s) 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.