ORA-13331: invalid LRS segment

Cause : The given LRS segment was not a valid line string.

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

A valid LRS geometric segment is a line string geometry in Oracle Spatial. It could be a simple or compound line string (made of lines or arcs, or both). The dimension information must include the measure dimension as the last element in the Oracle Spatial metadata. Currently, the number of dimensions for an LRS segment must be greater than 2 (x/y or longitude/latitude, plus measure)

update : 23-06-2017

ORA-13331 - invalid LRS segment
ORA-13331 - invalid LRS segment

  • ora-07608 : szprv: $GETUAI failure
  • ora-02227 : invalid cluster name
  • ora-30573 : AUTO segment space management not valid for this type of tablespace
  • ora-15091 : operation incompatible with open handle in this session
  • ora-26062 : Can not continue from previous errors.
  • ora-31497 : invalid value specified for first_scn
  • ora-25409 : failover happened during the network operation,cannot continue
  • ora-01106 : database must be closed before dismounting
  • ora-00128 : this command requires a dispatcher name
  • ora-09702 : sem_acquire: cannot acquire latch semaphore
  • ora-37116 : OLAP API table function error: (string)
  • ora-06602 : LU6.2 Driver: Error allocating context area
  • ora-23416 : table "string"."string" does not contain a primary key constraint
  • ora-31632 : master table "string.string" not found, invalid, or inaccessible
  • ora-21611 : key length [string] is invalid
  • ora-16582 : could not edit instance specific property
  • ora-25257 : consumer must be specified with a multi-consumer queue
  • ora-32057 : invalid lock mode
  • ora-07514 : scgcan: $deq unexpected return while canceling lock
  • ora-16210 : Logical standby coordinator process terminated with error
  • ora-36188 : (XSAGGR16) AGGREGATE read a value less than 1 out of COUNTVAR variable workspace object. Either the values of the COUNTVAR variable are stored improperly, or there is problem in AGGREGATE. If no one has modified the values in this COUNTVAR, contact Oracle customer support.
  • ora-36764 : (XSAGGCNTMOVE02) AGGCOUNT variable workspace object must be of type INTEGER, not string.
  • ora-12013 : updatable materialized views must be simple enough to do fast refresh
  • ora-02141 : invalid OFFLINE option
  • ora-28344 : fails to decrypt data
  • ora-36978 : (XSRELGID01) workspace object must be a self-relation.
  • ora-01226 : file header of log member is inconsistent with other members
  • ora-36405 : (XSSPROP05) Property ignored for object workspace object:
  • ora-23367 : table string is missing the primary key
  • ora-32121 : Source FILE is 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.