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 : 26-06-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-13035 : Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object
  • ora-38900 : missing mandatory column "string" of error log table "string"
  • ora-13436 : GeoRaster metadata dimensionSize error
  • ora-24763 : transaction operation cannot be completed now
  • ora-28039 : cannot validate Kerberos service ticket
  • ora-23422 : Oracle Server could not generate an unused job number
  • ora-00292 : parallel recovery feature not installed
  • ora-22294 : cannot update a LOB opened in read-only mode
  • ora-29848 : error occurred in the execution of ODCIINDEXMERGEPARTITION routine
  • ora-22130 : buffer size [string] is less than the required size [string]
  • ora-32060 : channel failure
  • ora-02349 : invalid user-defined type - type is incomplete
  • ora-30026 : Undo tablespace 'string' has unexpired undo with string(sec) left, Undo_Retention=string(sec)
  • ora-38404 : schema extension not allowed for the attribute set name
  • ora-31457 : maximum length of description field exceeded
  • ora-29309 : export dump file was generated by different version of DBMS_PITR package
  • ora-24184 : transformation string.string already exists
  • ora-28231 : no data passed to obfuscation toolkit
  • ora-07282 : sksaprd: string overflow.
  • ora-36997 : (XSRELGID14) For variable or relation grouping ids, a level relation is needed when a level order valueset is specified.
  • ora-28507 : error in data dictionary view string
  • ora-08177 : can't serialize access for this transaction
  • ora-31447 : cannot create change tables in the SYS schema
  • ora-12471 : Specified compartment or group is not authorized for user
  • ora-30192 : reserved for future use
  • ora-25953 : join index cannot be a functional index
  • ora-19801 : initialization parameter DB_RECOVERY_FILE_DEST is not set
  • ora-00370 : potential deadlock during kcbchange operation
  • ora-06754 : TLI Driver: unable to get local host address
  • ora-00037 : cannot switch to a session belonging to a different server group
  • 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.