ORA-37039: (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.

Cause : One cannot use TRIGGER command on objects in an analytic workspace attached in MULTI mode.

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

Do all persistent object maintenance in read-write mode.

update : 24-07-2017
ORA-37039

ORA-37039 - (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.
ORA-37039 - (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.

  • ora-01883 : overlap was disabled during a region transition
  • ora-21779 : duration not active
  • ora-09213 : slgfn: error fabricating file name
  • ora-01725 : USERENV('COMMITSCN') not allowed here
  • ora-28605 : bitmap indexes cannot be reversed
  • ora-09989 : attempt to use invalid skgmsdef struct pointer
  • ora-14116 : partition bound of partition "string" is too long
  • ora-08430 : raw data missing leading sign
  • ora-29400 : data cartridge error string
  • ora-09936 : Open of ORACLE password file for write failed.
  • ora-01113 : file string needs media recovery
  • ora-06253 : NETNTT: cannot read arguments from address file
  • ora-36642 : (XSDUNION06) Concat dimension list contains duplicate leaf dimension workspace object.
  • ora-38719 : Invalid DUMP FLASHBACK object.
  • ora-17503 : ksfdopn:string Failed to open file string
  • ora-07490 : scgrcl: cannot convert lock.
  • ora-29508 : query derived from USING clause did not select a value of type string
  • ora-02446 : CREATE TABLE ... AS SELECT failed - check constraint violated
  • ora-37015 : (XSACQUIRE_YNRESYNC) Object workspace object is ambiguously listed to be acquired both with and without RESYNC.
  • ora-25956 : join index cannot be created on tables owned by SYS
  • ora-28534 : Heterogeneous Services preprocessing error
  • ora-12028 : materialized view type is not supported by master site string
  • ora-25182 : feature not currently available for index-organized tables
  • ora-19634 : filename required for this function
  • ora-19901 : database needs more recovery to create new incarnation
  • ora-10645 : Recursive Extension in SYSTEM tablespace during migration
  • ora-24758 : not attached to the requested transaction
  • ora-06529 : Version mismatch - PL/SQL profiler
  • ora-01262 : Stat failed on a file destination directory
  • ora-12618 : TNS:versions are incompatible
  • 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.