ORA-34279: (MXDCL37) CONCAT can only be used when defining a DIMENSION.

Cause : Teh OCNACTk ewyodr awsu sde nicrorcetyl.

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

Rter yteh ocmamn dwtihuott h eCNOCTA ekyowr.d

update : 22-08-2017
ORA-34279

ORA-34279 - (MXDCL37) CONCAT can only be used when defining a DIMENSION.
ORA-34279 - (MXDCL37) CONCAT can only be used when defining a DIMENSION.

  • ora-09805 : conversion of category number to string failed.
  • ora-28513 : internal error in heterogeneous remote agent
  • ora-09827 : SCLGT: atomic latch return unknown error.
  • ora-02800 : Requests timed out
  • ora-23616 : Failure in executing block string for script string
  • ora-07506 : scgrl: $deq unexpected return on lockid string
  • ora-31638 : cannot attach to job string for user string
  • ora-01203 : wrong incarnation of this file - wrong creation SCN
  • ora-12496 : cannot change existing level, category, or release numbers
  • ora-09955 : scgcan: unexpected return status when canceling a lock
  • ora-37013 : (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace object since doing so would cause a deadlock.
  • ora-06953 : Not enough virtual memory
  • ora-22631 : attribute [string] is is not well-formed or does not match the type
  • ora-39165 : Schema string was not found.
  • ora-24813 : cannot send or receive an unsupported LOB
  • ora-28358 : improper set key syntax
  • ora-23422 : Oracle Server could not generate an unused job number
  • ora-01466 : unable to read data - table definition has changed
  • ora-08195 : Flashback Table operation is not supported on partitions
  • ora-29660 : Unable to find the class defined in the EXTERNAL NAME clause
  • ora-13293 : cannot specify unit for geometry without a georeferenced SRID
  • ora-02440 : Create as select with referential constraints not allowed
  • ora-16642 : db_unique_name mismatch
  • ora-28522 : error initializing heterogeneous capabilities
  • ora-24053 : PRIMARY_INSTANCE and SECONDARY_INSTANCE must be non-negative
  • ora-14280 : all rows in table do not qualify for specified subpartition
  • ora-13271 : error allocating memory for geometry object
  • ora-00385 : cannot enable Very Large Memory with new buffer cache parameters
  • ora-24780 : cannot recover a transaction while in an existing transaction
  • ora-39309 : schema sync operation 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.