ORA-12839: cannot modify an object in parallel after modifying it

Cause : Within the same transaction, an attempt was made to perform parallel modification operations on a table after it had been modified. This is not permitted.

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

Rewrite the transaction or break it up into two transactions: one containing the parallel modification and the second containing the initial modification operation.

update : 24-04-2017

ORA-12839 - cannot modify an object in parallel after modifying it
ORA-12839 - cannot modify an object in parallel after modifying it

  • ora-07600 : slkmnm: $GETSYIW failure
  • ora-12034 : materialized view log on "string"."string" younger than last refresh
  • ora-23368 : name string cannot be null or the empty string
  • ora-28105 : cannot create security relevant column policy in an object view
  • ora-37180 : expected exactly one column for dimension string, got string
  • ora-02171 : invalid value for MAXLOGHISTORY
  • ora-32804 : invalid value string, string should have form string
  • ora-31437 : duplicate change set string
  • ora-00316 : log string of thread string, type string in header is not log file
  • ora-07657 : slsprom:$ASSIGN failure
  • ora-30978 : The XML Index is not locally partitioned.
  • ora-08193 : Flashback Table operation is not allowed on temporary tables
  • ora-00053 : maximum number of enqueues exceeded
  • ora-19738 : cannot find language information for character set: 'string'
  • ora-15123 : ASM file name 'string' contains an invalid incarnation number
  • ora-02096 : specified initialization parameter is not modifiable with this option
  • ora-24307 : invalid length for piece
  • ora-27012 : skgfrd: read from file failed
  • ora-15104 : conflicting CONTENTS options
  • ora-30161 : A system error occurred during the OCIFile function call
  • ora-12437 : invalid policy option: string
  • ora-06532 : Subscript outside of limit
  • ora-19209 : invalid or unsupported formatting argument
  • ora-30475 : feature not enabled: string
  • ora-03219 : Tablespace 'string' is dictionary-managed, offline or temporary
  • ora-27373 : unknown or illegal event source queue
  • ora-26027 : unique index string.string partition string initially in unusable state
  • ora-24338 : statement handle not executed
  • ora-07702 : unrecognized device type in archive text
  • ora-14177 : STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash 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.