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 : 26-05-2017

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-29953 : cannot issue DDL on a domain index partition marked as FAILED
  • ora-06526 : Unable to load PL/SQL library
  • ora-06123 : NETTCP: cannot set KEEPALIVE
  • ora-03236 : max # extents (string) reached in index string.string subpartition string
  • ora-09977 : skxfqhini: Error Connecting
  • ora-00319 : log string of thread string has incorrect log reset status
  • ora-12658 : ANO service required but TNS version is incompatible
  • ora-19380 : invalid plan filter
  • ora-00077 : dump string is not valid
  • ora-10852 : Enable tracing for Enqueue Dequeue Operations
  • ora-08269 : destroy_ora_addr: cannot destroy name
  • ora-27075 : SSTMOFRC constant too large
  • ora-23322 : Privilege error accessing pipe
  • ora-28026 : user with same external name already exists
  • ora-02875 : smpini: Unable to get shared memory for PGA
  • ora-06909 : CMX: error during acknowledge of ORACLE_SID
  • ora-38505 : invalid default value for the attribute
  • ora-13157 : Oracle error ORAstring encountered while string
  • ora-14321 : cannot add/drop values to DEFAULT partition
  • ora-16637 : an instance failed to access the Data Guard broker configuration
  • ora-16206 : database already configured as Logical Standby database
  • ora-14512 : cannot perform operation on a clustered object
  • ora-00025 : failed to allocate string
  • ora-39140 : dump file "string" belongs to job string
  • ora-23313 : object group "string"."string" is not mastered at string
  • ora-13330 : invalid MASK
  • ora-09265 : spwat: error temporarily suspending process
  • ora-01112 : media recovery not started
  • ora-14601 : Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template
  • ora-16075 : standby database destination mismatch
  • 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.