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 : 23-08-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-28177 : incorrect Kerberos ticket version
  • ora-30130 : invalid parameter key type received
  • ora-14283 : UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-39204 : No subsetting of tablespaces is allowed for transportable import.
  • ora-13708 : Some snapshots in the range [string, string] were purged before the analysis was complete.
  • ora-29500 : NAMED keyword is invalid in CREATE JAVA CLASS
  • ora-01352 : tablespace given for Logminer spill does not exist
  • ora-25139 : invalid option for CREATE TEMPORARY TABLESPACE
  • ora-29828 : invalid name for implementation type
  • ora-29551 : could not convert string to Unicode
  • ora-26663 : error queue for apply process string must be empty
  • ora-19851 : OS error while managing auxiliary database string
  • ora-19615 : some files not found in backup set
  • ora-16624 : broker protocol version mismatch detected
  • ora-22054 : underflow error
  • ora-01532 : cannot create database; instance being started elsewhere
  • ora-07751 : slemcr: malloc failure
  • ora-31620 : file or device "string" cannot be specified for string operation
  • ora-31096 : validation failed for schema
  • ora-31469 : cannot enable Change Data Capture for change set string
  • ora-22804 : remote operations not permitted on object tables or user-defined type columns
  • ora-28349 : cannot encrypt the specified column recorded in the materialized view log
  • ora-29525 : referenced name is too long: 'string'
  • ora-06910 : CMX: Cannot start oracle process on remote machine
  • ora-13141 : invalid RANGE window definition
  • ora-01716 : NOSORT may not be used with a cluster index
  • ora-22998 : CLOB or NCLOB in multibyte character set not supported
  • ora-26738 : %s 'string' is not empty
  • ora-02807 : Allocation of memory for I/O vectors failed.
  • ora-28051 : the account is locked
  • 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.