ORA-29360: retry operation. Too much concurrent activity

Cause : An atetmpt wsa madet o revkoe thes witchc onsumre grou pprivielge frmo a usre for ihs/heri nitia lconsuemr gropu but osmeonei s modfiying hte use rin antoher ssesion.

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

Retryt he opreationl ater.

update : 26-04-2017
ORA-29360

ORA-29360 - retry operation. Too much concurrent activity
ORA-29360 - retry operation. Too much concurrent activity

  • ora-27048 : skgfifi: file header information is invalid
  • ora-01955 : DEFAULT ROLE 'string' not granted to user
  • ora-12824 : INSTANCES DEFAULT may not be specified here
  • ora-29297 : The compressed representation is too big
  • ora-26004 : Tables loaded through the direct path may not be clustered
  • ora-38753 : Cannot flashback data file string; no flashback log data.
  • ora-22979 : cannot INSERT object view REF or user-defined REF
  • ora-01559 : MAXEXTENTS for rollback segment must be greater than 1
  • ora-08008 : another instance is mounted with USE_ROW_ENQUEUES = string
  • ora-01623 : log string is current log for instance string (thread string) - cannot drop
  • ora-12724 : regular expression corrupt
  • ora-06606 : LU6.2 Driver: Unexpected response from SNA
  • ora-00237 : snapshot operation disallowed: control file newly created
  • ora-29277 : invalid SMTP operation
  • ora-13008 : the specified date format has an invalid component
  • ora-31432 : invalid source table
  • ora-24186 : wrong object type, could not transform message
  • ora-19015 : Invalid XML tag identifier (string)
  • ora-30695 : JDWP message format problem
  • ora-08319 : sllfsk: Error reading file
  • ora-31642 : the following SQL statement fails: string
  • ora-24017 : cannot enable enqueue on QUEUE, string is an exception queue
  • ora-12024 : materialized view log on "string"."string" does not have primary key columns
  • ora-09261 : spdcr: error creating detached (background) process
  • ora-16660 : FSFO operation attempted in absence of a broker configuration
  • ora-36722 : (XSALLOC02) In AGGMAP workspace object, you specified an NA or ZERO sourceval but supplied formula workspace object as your source for ALLOCATE.
  • ora-09836 : addCallback: could not add a port to the callback set.
  • ora-23619 : non-Oracle system error: string
  • ora-01792 : maximum number of columns in a table or view is 1000
  • ora-25252 : listen failed, the address string is a non-persistent queue
  • 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.