ORA-13378: invalid index for element to be extracted

Cause : An ivnalid( or otu of obunds )inde xwas psecifeid fo rextrcatinga n elmeent rfom ag eomerty.

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

Makes ure hte paarmetesr to hte exrtact ufnctino arei n th evali drang efor hte gemoetry.

update : 20-08-2017

ORA-13378 - invalid index for element to be extracted
ORA-13378 - invalid index for element to be extracted

  • ora-28051 : the account is locked
  • ora-39106 : Worker process string failed during startup. Worker error:
  • ora-24364 : internal error while padding blanks
  • ora-02466 : The SIZE and INITRANS options cannot be altered for HASH CLUSTERS.
  • ora-13624 : The task string is executing and cannot be deleted or modified.
  • ora-13383 : inconsistent network metadata: string
  • ora-09934 : Link of current password file to old failed.
  • ora-16796 : one or more properties could not be imported from the database
  • ora-04032 : pga_aggregate_target must be set before switching to auto mode
  • ora-06007 : NETASY: bad dialogue format
  • ora-14252 : invalid ALTER TABLE MODIFY PARTITION option for a Hash partition
  • ora-00216 : control file could not be resized for migration from 8.0.2
  • ora-26528 : local store callback proc phase failed for 'string.string'
  • ora-01263 : Name given for file destination directory is invalid
  • ora-01858 : a non-numeric character was found where a numeric was expected
  • ora-01646 : tablespace 'string' is not read only - cannot make read write
  • ora-24393 : invalid mode for creating connection pool
  • ora-02273 : this unique/primary key is referenced by some foreign keys
  • ora-23353 : deferred RPC queue has entries for object group "string"."string"
  • ora-38402 : invalid name: empty string or spaces in the name
  • ora-25198 : only range, list, and hash partitioning are supported for index-organized table
  • ora-16639 : specified instance inactive or currently unavailable
  • ora-10642 : Found rollback segments in dictionary managed tablespaces
  • ora-12900 : must specify a default temporary tablespace for a locally managed database
  • ora-19900 : RESETLOGS must be specified after recovery to new incarnation
  • ora-12851 : PARALLEL_MAX_SERVERS must be greater than or equal to PARALLEL_MIN_SERVERS, string
  • ora-04091 : table string.string is mutating, trigger/function may not see it
  • ora-27146 : post/wait initialization failed
  • ora-14635 : only one resulting subpartition can be specified for MERGE SUBPARTITIONS
  • ora-39957 : invalid warning category
  • 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.