ORA-36994: (XSRELGID11) The SURROGATE DIMENSION workspace object must be numeric.

Cause : The surrogate dimension is not numeric

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

Change the surrogate dimension as numeric

update : 24-08-2017

ORA-36994 - (XSRELGID11) The SURROGATE DIMENSION workspace object must be numeric.
ORA-36994 - (XSRELGID11) The SURROGATE DIMENSION workspace object must be numeric.

  • ora-29261 : bad argument
  • ora-19910 : can not change recovery target incarnation in control file
  • ora-01160 : file is not a string
  • ora-13125 : partition key is already set
  • ora-06513 : PL/SQL: index for PL/SQL table out of range for host language array
  • ora-22923 : amount of data specified in streaming LOB write is 0
  • ora-25105 : RECOVERABLE option can only be used with ALTER INDEX REBUILD
  • ora-30135 : OCI Thread operation fails
  • ora-00334 : archived log: 'string'
  • ora-13153 : invalid high water mark specified
  • ora-29760 : instance_number parameter not specified
  • ora-34358 : (MXDSS14) number other users reading
  • ora-15044 : ASM disk 'string' is incorrectly named
  • ora-01219 : database not open: queries allowed on fixed tables/views only
  • ora-00329 : archived log begins at change string, need change string
  • ora-07579 : spini: $DCLEXH failure
  • ora-15205 : requested mirror side unavailable
  • ora-30431 : refresh method must be ANY or INCREMENTAL or FORCE_FULL, not string
  • ora-30501 : instance shutdown triggers cannot have AFTER type
  • ora-13912 : Critical threshold value is less than warning threshold value.
  • ora-01677 : standby file name convert parameters differ from other instance
  • ora-36168 : (XSMXAGGR10) COUNTVAR variable workspace object must have the same dimensionality as workspace object
  • ora-23425 : invalid materialized view identifier string
  • ora-22312 : must specify either CASCADE or INVALIDATE option
  • ora-06439 : ssaio: the asynchronous write returned incorrect number of bytes
  • ora-16105 : Logical Standby is already running in background
  • ora-16003 : standby database is restricted to read-only access
  • ora-31000 : Resource 'string' is not an XDB schema document
  • ora-32836 : database user string must be granted role string
  • ora-12598 : TNS:banner registration failed
  • 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.