ORA-36988: (XSRELGID06) The related dimension of relation workspace object must be of type NUMBER.

Cause : The related dimension of the destination relation has the wrong data type.

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

Redefine the destination relation or choose another relation whose related dimension is of type NUMBER.

update : 19-08-2017
ORA-36988

ORA-36988 - (XSRELGID06) The related dimension of relation workspace object must be of type NUMBER.
ORA-36988 - (XSRELGID06) The related dimension of relation workspace object must be of type NUMBER.

  • ora-06446 : ssvpstevrg: Failed with unexpected error number.
  • ora-19815 : WARNING: string of string bytes is string%% used, and has string remaining bytes available.
  • ora-01858 : a non-numeric character was found where a numeric was expected
  • ora-12596 : TNS:internal inconsistency
  • ora-37182 : you may only specify one dimension to partition
  • ora-01907 : TABLESPACE keyword expected
  • ora-13431 : GeoRaster metadata rasterType error
  • ora-04099 : trigger 'string' is valid but not stored in compiled form
  • ora-38461 : XML Tag "string" already exists for the XMLType attribute "string"
  • ora-28584 : heterogeneous apply internal error
  • ora-02075 : another instance changed state of transaction string
  • ora-16207 : Logical standby dictionary build not permitted.
  • ora-39953 : the range value specified is beyond allowed range
  • ora-15116 : invalid combination of ALTER DISKGROUP options
  • ora-16574 : switchover disallowed when required databases are offline
  • ora-22991 : insufficient space allocated for argument string
  • ora-31062 : Cannot delete an unsaved resource
  • ora-06781 : TLI Driver: error reading negotation string
  • ora-14262 : new subpartition name must differ from the old subpartition name
  • ora-08462 : raw buffer contains invalid decimal data
  • ora-40225 : model is currently in use by another process
  • ora-02090 : network error: attempted callback+passthru
  • ora-28345 : cannot downgrade because there exists encrypted column
  • ora-16953 : Type of SQL statement not supported.
  • ora-31531 : could not find column string in CDC subscriber view string.string
  • ora-13838 : invalid ADDRESS value
  • ora-16713 : the resource guard timed out while servicing the request
  • ora-12418 : user string not found
  • ora-24775 : cannot prepare or commit transaction with non-zero lock value
  • ora-19380 : invalid plan filter
  • 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.