ORA-13049: unable to determine tolerance value from table _SDODIM

Cause : An SD_OGEOM ufnctio nwas uanble t odeterimne th etolernace vaule fort he SD Olayer< layer.>

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

Verif ythat hte _SDDOIM talbe hasa vali dvaluef or th ecolum nSDO_TLOERANC.E

update : 28-07-2017
ORA-13049

ORA-13049 - unable to determine tolerance value from table _SDODIM
ORA-13049 - unable to determine tolerance value from table _SDODIM

  • ora-09881 : sstasfre/sstasdel: shmdt error, unable to detach tas read page
  • ora-07324 : smpall: malloc error while allocating pga.
  • ora-30736 : objects in a table or view hierarchy have to be in the same schema
  • ora-27142 : could not create new process
  • ora-33922 : (MAKEDCL35) You cannot define a surrogate of dimension workspace object because it is a time dimension.
  • ora-12805 : parallel query server died unexpectedly
  • ora-27065 : cannot perform async vector I/O to file
  • ora-26666 : cannot alter STREAMS process string
  • ora-02434 : cannot enable unique(string) - unique key not defined for table
  • ora-29374 : resource plan string in top-plan string has no plan directives
  • ora-01757 : Must specify an object number
  • ora-23407 : object name string must be shaped like "schema"."object" or "object"
  • ora-07202 : sltln: invalid parameter to sltln.
  • ora-33458 : (ESDREAD09) Discarding compiled code for workspace object because number is now type string, whereas it was type string when the code was compiled.
  • ora-39305 : schema "string" does not exist
  • ora-27475 : "string.string" must be a string
  • ora-02292 : integrity constraint (string.string) violated - child record found
  • ora-19500 : device block size string is invalid
  • ora-01247 : database recovery through TSPITR of tablespace string
  • ora-30459 : 'string.string' cannot be refreshed because the refresh method is NONE
  • ora-36280 : (XSCGMDLAGG08) Valueset workspace object does not contain values of any dimension of the current model.
  • ora-25225 : invalid value string, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED
  • ora-31055 : A null XMLType element cannot be inserted into RESOURCE_VIEW
  • ora-25003 : cannot change NEW values for this column type in trigger
  • ora-15194 : Internal ASM-DB interaction testing event number 15194
  • ora-09276 : All bequeath database links must be loopback database links
  • ora-02377 : invalid resource limit
  • ora-29760 : instance_number parameter not specified
  • ora-10645 : Recursive Extension in SYSTEM tablespace during migration
  • ora-14193 : invalid ALTER INDEX MODIFY SUBPARTITION option
  • 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.