ORA-13344: an arcpolygon geometry has fewer than five coordinates

Cause : A geometry, specified as being an arcpolygon, has fewer than five coordinates in its definition.

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

An arcpolygon must consist of at least five coordinates. An arcpolygon consists of an ordered sequence of arcs, each of which must be described using three coordinates. Since arcs are connected the end-point of the first is the start of the second and does not have to be repeated. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.

update : 26-09-2017
ORA-13344

ORA-13344 - an arcpolygon geometry has fewer than five coordinates
ORA-13344 - an arcpolygon geometry has fewer than five coordinates

  • ora-30741 : WITH HIERARCHY OPTION can be specified only for SELECT privilege
  • ora-39149 : cannot link privileged user to non-privileged user
  • ora-30738 : object "string" does not exist in schema "string"
  • ora-22630 : attribute [string] is null or it is not well-formed
  • ora-06744 : TLI Driver: listener cannot bind
  • ora-26041 : DATETIME/INTERVAL datatype conversion error
  • ora-33454 : (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.
  • ora-29894 : base or varray datatype does not exist
  • ora-12554 : TNS:current operation is still in progress
  • ora-36974 : (XSRELTBL14) workspace object is not a BOOLEAN variable dimensioned by all the dimensions of the hierarchy.
  • ora-01238 : cannot shrink datafile string
  • ora-04042 : procedure, function, package, or package body does not exist
  • ora-16078 : media recovery disabled
  • ora-36392 : (XSMXCLEA02) When using CLEAR with the PRECOMPUTES or NONPRECOMPUTES options, you must supply an AGGMAP.
  • ora-13600 : error encountered in Advisor string
  • ora-13048 : recursive SQL fetch error
  • ora-25526 : bad format of _DB_MTTR_SIM_TARGET: string
  • ora-22901 : cannot compare nested table or VARRAY or LOB attributes of an object type
  • ora-24127 : TABLESPACE parameter specified with an ACTION other than CREATE_ACTION
  • ora-38722 : ON or OFF expected.
  • ora-12236 : TNS:protocol support not loaded
  • ora-29386 : plan or consumer group string is mandatory and cannot be deleted or modified
  • ora-24015 : cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE string.string does not exist
  • ora-01146 : cannot start online backup - file string is already in backup
  • ora-30131 : number of keys being set exceeds allocation
  • ora-14084 : you may specify TABLESPACE DEFAULT only for a LOCAL index
  • ora-28183 : proper authentication not provided by proxy
  • ora-02252 : check constraint condition not properly ended
  • ora-09836 : addCallback: could not add a port to the callback set.
  • ora-27454 : argument name and position cannot be NULL
  • 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.