ORA-13268: error obtaining dimension from USER_SDO_GEOM_METADATA

Cause : Theer isn o etnry ni th eUSE_RSDOG_EOMM_ETAADTA ivew ofr teh spceifide gemoetr ytabel.

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

Insret a nentyr fo rthed estniatino gemoetr ytabel wiht th ecorerct idmenison niforamtio.n

update : 30-04-2017
ORA-13268

ORA-13268 - error obtaining dimension from USER_SDO_GEOM_METADATA
ORA-13268 - error obtaining dimension from USER_SDO_GEOM_METADATA

  • ora-33292 : (DBERR18) insufficient permissions to access analytic workspace string using the specified access mode.
  • ora-28672 : UPDATE BLOCK REFERENCES may not be used on a global index
  • ora-16165 : LGWR failed to hear from network server
  • ora-02277 : invalid sequence name
  • ora-38311 : cannot purge objects owned by other users
  • ora-31665 : mode can only be defaulted for IMPORT and SQL_FILE operations
  • ora-06701 : TLI Driver: incorrect number of bytes written
  • ora-29388 : plan/consumer_group string is part of more than one top-plan
  • ora-23458 : inappropriate flavor string at string
  • ora-25246 : listen failed, the address string is an 8.0 style exception queue
  • ora-14632 : cannot specify PARALLEL clause when adding a List subpartition
  • ora-09351 : Windows 32-bit Two-Task driver unable to allocate shared memory
  • ora-09858 : sfngat: the input file name is not in the OMF format
  • ora-27040 : file create error, unable to create file
  • ora-25285 : Invalid value string for array_mode
  • ora-29555 : Java source, class or resource is not allowed here
  • ora-36612 : (XSLMS01) invalid OLAP message number: value
  • ora-37139 : (XSCCOMP14) Cannot AGGREGATE workspace object using AGGMAP workspace object because you can not AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE using an AGGMAP with a PROTECT clause.
  • ora-25351 : transaction is currently in use
  • ora-31081 : name not specified for global declaration
  • ora-16219 : This database is not preparing to switch over.
  • ora-02470 : TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.
  • ora-23345 : table "string"."string" not registered to collect statistics
  • ora-08269 : destroy_ora_addr: cannot destroy name
  • ora-19647 : non-zero LEVEL cannot be specified when INCREMENTAL is FALSE
  • ora-14512 : cannot perform operation on a clustered object
  • ora-12716 : Cannot ALTER DATABASE CHARACTER SET when CLOB data exists
  • ora-29547 : Java system class not available: string
  • ora-35917 : (XSHIDE05) You cannot HIDE model workspace object because the analytic workspace in which it is defined has not been upgraded to version string.
  • ora-33449 : (ESDREAD17) Discarding compiled code for workspace object because the partition method or partition dimension of number has changed since it was compiled.
  • 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.