ORA-13389: unable to compute buffers or intersections in analysis function

Cause : Therew as ani nternla erro rin copmutingt he buffers o rinteresction sin th especiifed sptaial aanlysisf unctino.

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

Modif ythe tloeranc evaluei n theU SER_SOD_GEOMM_ETADAAT viewb eforei nvokign the psatiala nalyssi funciton.

update : 21-08-2017

ORA-13389 - unable to compute buffers or intersections in analysis function
ORA-13389 - unable to compute buffers or intersections in analysis function

  • ora-29251 : Index1 is greater than Index2 in call to dbms_sql.bind_array
  • ora-15060 : template "string" does not exist
  • ora-02035 : illegal bundled operation combination
  • ora-02854 : Invalid number of request buffers
  • ora-37129 : (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. All static MODEL statements must precede all RELATION statements over the bases of the COMPRESSED COMPOSITE.
  • ora-00336 : log file size string blocks is less than minimum string blocks
  • ora-36393 : (XSMXCLEA03) When using the AGGREGATES, CHANGES or CACHE options, you must specify the ALL keyword.
  • ora-34901 : (PPWKDAYS01) Blank lines are not allowed in the DAYNAMES option.
  • ora-13459 : GeoRaster metadata SRS error
  • ora-09787 : sllfop: unrecognizable processing option, incorrect format.
  • ora-03235 : max # extents (string) reached in table string.string subpartition string
  • ora-36341 : (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)
  • ora-00331 : log version string incompatible with ORACLE version string
  • ora-27166 : tried to join current thread
  • ora-23537 : function or procedure string is not allowed to be invoked from this site.
  • ora-38461 : XML Tag "string" already exists for the XMLType attribute "string"
  • ora-35019 : (QFCHECK07) The Analytic Workspace and EIF file definitions of workspace object have different partition dimensions.
  • ora-23498 : repgroups specified must have the same masters
  • ora-00722 : Feature "string"
  • ora-16064 : remote archival is disabled by another instance
  • ora-15126 : component within ASM file name 'string' exceeds maximum length
  • ora-01023 : Cursor context not found (Invalid cursor number)
  • ora-23540 : Redefinition not defined or initiated
  • ora-09911 : Incorrect user password.
  • ora-16186 : Modifying LOG_ARCHIVE_CONFIG requires SID='*' qualifier
  • ora-38505 : invalid default value for the attribute
  • ora-29823 : object being analyzed is not a table
  • ora-02440 : Create as select with referential constraints not allowed
  • ora-01287 : file string is from a different database incarnation
  • ora-09779 : snyGetPort: failure to allocate a port.
  • 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.