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 : 28-05-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-31479 : could not create LogMiner session
  • ora-34481 : (MXMAINT07) You cannot string values of PARTITION TEMPLATE workspace object.
  • ora-02355 : error opening file: string
  • ora-16770 : physical standby database not in read-only state
  • ora-24502 : codepoint length overflows
  • ora-30343 : level name is not unique within this dimension
  • ora-28658 : This operation is supported only for Index-Organized tables
  • ora-01890 : NLS error detected
  • ora-24364 : internal error while padding blanks
  • ora-25463 : table alias not specified
  • ora-25407 : connection terminated
  • ora-01125 : cannot disable media recovery - file string has online backup set
  • ora-24048 : cannot create QUEUE_TABLE, user does not have access to AQ object types
  • ora-04043 : object string does not exist
  • ora-27158 : process control failure
  • ora-01287 : file string is from a different database incarnation
  • ora-01243 : system tablespace file suffered media failure
  • ora-22931 : MOVE of nested table to a different tablespace not supported
  • ora-30201 : Unable to load NLS data object
  • ora-13869 : Instance-wide SQL tracing on instance string is already enabled
  • ora-01023 : Cursor context not found (Invalid cursor number)
  • ora-09791 : slembdf: translation error, unable to translate error file name.
  • ora-31614 : routine string received this error from string: string
  • ora-28555 : pass-through SQL: required parameter missing or NULL
  • ora-15038 : disk 'string' size mismatch with diskgroup [string] [string] [string]
  • ora-31675 : worker process interrupt for unexpected death of master process
  • ora-36714 : (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.
  • ora-22855 : optional name for LOB storage segment incorrectly specified
  • ora-19284 : Encoding specification in version declaration not supported
  • ora-13112 : cannot delete topo_geometry layer [string] from topology
  • 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.