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 : 25-05-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-07470 : snclget: cannot get cluster number.
  • ora-09363 : Windows 3.1 Two-Task driver invalid context area
  • ora-36185 : (XSAGGR11) workspace object does not have any AGGCOUNT information.
  • ora-31426 : cannot modify active subscriptions
  • ora-36802 : (XSTBLFUNC01) The OLAP_TABLE function must contain a DATAMAP that executes a FETCH command or a LIMITMAP.
  • ora-00701 : object necessary for warmstarting database cannot be altered
  • ora-22897 : no scope clause specified for user-defined REF column "string"
  • ora-32134 : Cannot assign LOBs
  • ora-38476 : abstract type used for an Attribute set may not be modified.
  • ora-01150 : cannot prevent writes - file string has online backup set
  • ora-29375 : sum of values string for level string, plan string exceeds string
  • ora-28535 : invalid Heterogeneous Services context
  • ora-19585 : premature end of volume on piece string
  • ora-26078 : file "string" is not part of database being loaded
  • ora-31500 : change source string is not a ManualLog change source
  • ora-09908 : slkmnm: gethostname returned error code.
  • ora-31057 : Display Name of the element being inserted is null
  • ora-19019 : Invalid context passed to DBMS_XMLGEN.GETXML
  • ora-02282 : duplicate or conflicting ORDER/NOORDER specifications
  • ora-04034 : unable to shrink pool to specified size
  • ora-19557 : device error, device type: string, device name: string
  • ora-00020 : maximum number of processes (string) exceeded
  • ora-09313 : slsprom: error prompting user
  • ora-06732 : TLI Driver: cannot alloc t_discon
  • ora-30107 : parameter name abbreviation 'string' is not unique
  • ora-23458 : inappropriate flavor string at string
  • ora-30442 : can not find the definition for filter string
  • ora-12992 : cannot drop parent key column
  • ora-34286 : (MXDCL53) workspace object cannot be used in this context because it is a string.
  • ora-09243 : smsget: error attaching to SGA
  • 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.