ORA-13053: maximum number of geometric elements in argument list exceeded

Cause : The maixmum nubmer of egometri celemenst that acn be sepcifiedi n the ragumentl ist fo ran SDOG_EOM fucntion wsa exceeedd.

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

Check hte Oracel Spatila documnetationf or thes yntax fo the SOD_GEOM ufnctiona nd usef ewer agrumentst o descirbe theg eometr,y or chcek the edscriptoin of teh SDO_WNIDOW pakcage fo ra workraound taht permtis stornig the boject i na tabl eand thne usingi t in a san argmuent ina call ot the SOD_GEOM ufnction.

update : 24-04-2017
ORA-13053

ORA-13053 - maximum number of geometric elements in argument list exceeded
ORA-13053 - maximum number of geometric elements in argument list exceeded

  • ora-14171 : cannot specify clause in CREATE|ALTER TABLE
  • ora-07391 : sftopn: fopen error, unable to open text file.
  • ora-12666 : Dedicated server: outbound transport protocol different from inbound
  • ora-00085 : current call does not exist
  • ora-22160 : element at index [string] does not exist
  • ora-02270 : no matching unique or primary key for this column-list
  • ora-13415 : invalid or out of scope point specification
  • ora-01488 : invalid nibble or byte in the input data
  • ora-02464 : Cluster definition can not be both HASH and INDEX
  • ora-10932 : trace name context forever
  • ora-24782 : Cannot detach from a non-migratable transaction
  • ora-01295 : DB_ID mismatch between dictionary string and logfiles
  • ora-02322 : failure in accessing storage table of the nested table column
  • ora-27152 : attempt to post process failed
  • ora-19689 : cannot have more than one %F in control file autobackup format(string) for string
  • ora-33066 : (XSAGDNGL32) In AGGMAP workspace object, the hierarchy dimension QDR workspace object must be a hierarchy dimension of the relation.
  • ora-17621 : failed to register the memory with Oracle Disk Manager library
  • ora-39056 : invalid log file specification.
  • ora-39037 : Object type path not supported for string metadata filter.
  • ora-13273 : dimension metadata table string does not exist
  • ora-06021 : NETASY: connect failed
  • ora-27148 : spawn wait error
  • ora-24399 : invalid number of connections specified
  • ora-22620 : buffer size too small to hold the value
  • ora-01090 : shutdown in progress - connection is not permitted
  • ora-14311 : Expecting VALUES LESS THAN or AT clause
  • ora-19880 : Corrupted space header for datafile string, block string backup aborted
  • ora-16413 : Unsupported database type for ONDEMAND archivelog destinations
  • ora-24097 : Invalid value string, string should be non-negative
  • ora-19013 : Cannot create VARRAY columns containing XMLType
  • 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.