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 : 29-04-2017

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-30752 : column or table string is not substitutable
  • ora-02265 : cannot derive the datatype of the referencing column
  • ora-39144 : file name parameter must be specified and non-null
  • ora-26736 : Data Pump error
  • ora-04089 : cannot create triggers on objects owned by SYS
  • ora-26089 : LONG column "string" must be specified last
  • ora-22332 : a dependent object in schema "string" has errors. string
  • ora-06700 : TLI Driver: incorrect message type from host
  • ora-33018 : (XSAGDNGL08) In AGGMAP workspace object, the data type of workspace object must be TEXT, not string.
  • ora-32589 : unable to drop minimal supplemental logging
  • ora-31642 : the following SQL statement fails: string
  • ora-29918 : cannot create domain indexes on temporary tables
  • ora-28302 : User does not exist in the LDAP directory service.
  • ora-19648 : datafile string: incremental-start SCN equals checkpoint SCN
  • ora-36883 : (XSSRF02) The first parameter of an AW single row function cannot be NULL.
  • ora-09213 : slgfn: error fabricating file name
  • ora-38498 : invalid stored attribute for the index object : string
  • ora-08108 : may not build or rebuild this type of index online
  • ora-07214 : slgunm: uname error, unable to get system information.
  • ora-16167 : LGWR network server could not switch to non-blocking mode
  • ora-28113 : policy predicate has error
  • ora-30944 : Error during rollback for XML schema 'string' table string column 'string'
  • ora-12922 : concurrent ALTER DATABASE [NO] FORCE LOGGING command is running
  • ora-01217 : logfile member belongs to a different logfile group
  • ora-38713 : Flashback Database logging is already turned on.
  • ora-38853 : cannot mark instance string (redo thread string) as disabled
  • ora-31074 : XML comment length string exceeds maximum string
  • ora-01640 : cannot make tablespace read only with active transactions
  • ora-36685 : (XSDPART23) Only CONCAT partition templates can be subpartitioned.
  • ora-16530 : invalid buffer or length
  • 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.