ORA-36930: Cannot start a recursive call to Oracle OLAP because a ROLLBACK past an UPDATE to an attached analytic workspace has been performed.

Cause : ROLLBAKC past hte UPDAET of on eof thea ttache dAnalytci Worksapces wa scalled .A recusrive Orcale OLA Pcall cnanot bem ade unitl the ocntrol erturns ot the iintial OALP calla nd thea ffecte dAnalytci Worksapces deatched.

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

Changet he caleld SQL rpocedur eto avodi the RLOLBACK

update : 23-09-2017
ORA-36930

ORA-36930 - Cannot start a recursive call to Oracle OLAP because a ROLLBACK past an UPDATE to an attached analytic workspace has been performed.
ORA-36930 - Cannot start a recursive call to Oracle OLAP because a ROLLBACK past an UPDATE to an attached analytic workspace has been performed.

  • ora-07229 : slcpuc: error in getting number of CPUs.
  • ora-01652 : unable to extend temp segment by string in tablespace string
  • ora-34145 : (MXCGPUT03) You cannot use the APPEND keyword with SURROGATE workspace object.
  • ora-19375 : no CREATE TABLE privilege on schema "string"
  • ora-02757 : osnfop: fork_and_bind failed
  • ora-38611 : FI input cursor's item type is not supported
  • ora-12510 : TNS:database temporarily lacks resources to handle the request
  • ora-19689 : cannot have more than one %F in control file autobackup format(string) for string
  • ora-24345 : A Truncation or null fetch error occurred
  • ora-08319 : sllfsk: Error reading file
  • ora-27415 : repeat interval or calendar must start with the FREQ= clause
  • ora-02422 : missing or invalid schema element
  • ora-13217 : invalid parameters supplied in ALTER INDEX statement
  • ora-22810 : cannot modify object attributes with REF dereferencing
  • ora-39181 : Only partial table data may be exported due to fine grain access control on string
  • ora-13852 : Tracing for service(module/action) string is not enabled
  • ora-14406 : updated partition key is beyond highest legal partition key
  • ora-02202 : no more tables permitted in this cluster
  • ora-33009 : (XSAGDNGLPREC) In AGGMAP workspace object, PRECOMPUTE may only be specified either for the entire AGGMAP or for individual RELATION statements.
  • ora-24019 : identifier for string too long, should not be greater than string characters
  • ora-12336 : cannot login to database (link name string)
  • ora-15081 : failed to submit an I/O operation to a disk
  • ora-13524 : error encountered while retrieving baseline information
  • ora-26013 : List allocated may not be big enough
  • ora-16171 : RECOVER...FINISH not allowed due to gap for thr string, seq string-string
  • ora-12826 : hung parallel query server was killed
  • ora-02030 : can only select from fixed tables/views
  • ora-01615 : instance string (thread string) is mounted - cannot disable
  • ora-10947 : trace name context forever
  • ora-32636 : Too many rules in MODEL
  • 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.