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 : 24-07-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-01121 : cannot rename database file string - file is in use or recovery
  • ora-01506 : missing or illegal database name
  • ora-00052 : maximum number of enqueue resources (string) exceeded
  • ora-02245 : invalid ROLLBACK SEGMENT name
  • ora-30119 : unable to obtain a valid value for 'string'
  • ora-01980 : error during OS ROLE initialization
  • ora-08005 : specified row does not exist
  • ora-14157 : invalid subpartition name
  • ora-39501 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-01190 : control file or data file string is from before the last RESETLOGS
  • ora-24435 : Invalid Service Context specified.
  • ora-03283 : specified datafile string does not exist
  • ora-40217 : priors table mismatched with training data
  • ora-16028 : new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires
  • ora-00294 : invalid archivelog format specifier 'string'
  • ora-01466 : unable to read data - table definition has changed
  • ora-37151 : MDX parser initialization error
  • ora-38469 : invalid privilege for an expression set: string
  • ora-28342 : integrity check fails on column key
  • ora-40104 : invalid training data for model build
  • ora-22925 : operation would exceed maximum size allowed for a LOB value
  • ora-00470 : LGWR process terminated with error
  • ora-09749 : pws_look_up: port lookup failure
  • ora-30691 : failed to allocate system resources while registering a TCP/IP connection for data traffic detection
  • ora-12030 : cannot create a fast refresh materialized view
  • ora-30749 : column string not enabled to store objects of type string.string
  • ora-24320 : unable to initialize a mutex
  • ora-29327 : unsupported client compatibility mode used when talking to the server
  • ora-06778 : TLI Driver: error sending ccode
  • ora-12843 : pdml lock not held properly on the table
  • 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.