ORA-34286: (MXDCL53) workspace object cannot be used in this context because it is a string.

Cause : Users peciifed ad imenison cmoposiet, cojnoint ,or pratitino temlpate ni a palce wehre taht kidn of idmensoin isn ot allowed .For nistanec, a erlatino canont bed imenisonedb y a ocmpostie, adn onl ya vairablec an dmiensinoed b ya patritio ntempalte.

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

Usually, teh offnedingd imenison cna be erplacde wit hits abses.F or isntanc,e a rleatio ncannto be idmensoined yb a ac ompoiste o fPRODCUT an dGEOG ,but ti canb e diemnsioend byb oth RPODUC Tand EGOG isntead.

update : 28-06-2017
ORA-34286

ORA-34286 - (MXDCL53) workspace object cannot be used in this context because it is a string.
ORA-34286 - (MXDCL53) workspace object cannot be used in this context because it is a string.

  • ora-38720 : Missing log file number.
  • ora-30655 : cannot select FOR UPDATE from external organized table
  • ora-19913 : unable to decrypt backup
  • ora-12981 : cannot drop column from an object type table
  • ora-04071 : missing BEFORE, AFTER or INSTEAD OF keyword
  • ora-30074 : GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE not allowed
  • ora-24853 : failed to connect thread to shared subsystem
  • ora-01174 : DB_FILES is string buts needs to be string to be compatible
  • ora-03122 : attempt to close ORACLE-side window on user side
  • ora-03124 : two-task internal error
  • ora-01898 : too many precision specifiers
  • ora-30038 : Cannot perform parallel insert on non-partitioned object
  • ora-12319 : database (link name string) is already open
  • ora-38458 : invalid operation "string" for XPATH_FILTER_PARAMETERS
  • ora-32822 : subscriber string is marked for removal
  • ora-31190 : Resource string is not a version-controlled resource
  • ora-14325 : only LOCAL indexes may be specified in this clause
  • ora-31662 : metadata transform name can not be defaulted
  • ora-30680 : debugger connection handshake failed
  • ora-16505 : site ID is invalid
  • 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-19764 : database id string does not match database id string in control file
  • ora-37130 : (XSCCOMP05) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because you must specify AGGINDEX OFF when there is a PRECOMPUTE clause on a RELATION over base workspace object.
  • ora-19762 : invalid file type string
  • ora-02198 : ONLINE/OFFLINE option already specified
  • ora-02240 : invalid value for OBJNO or TABNO
  • ora-01582 : unable to open control file for backup
  • ora-36887 : (XSSRF06) Error rewriting OLAP DML expression. Column name string is not a valid ADT column.
  • ora-15155 : version incompatible with the cluster
  • ora-15127 : ASM file name 'string' cannot use templates
  • 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.