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 : 23-06-2017
ORA-12839

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

  • ora-13860 : Invalid service name
  • ora-38785 : Media recovery must be enabled for guaranteed restore point.
  • ora-25953 : join index cannot be a functional index
  • ora-34840 : (OPCREATE01) The string option must be declared with datatype string.
  • ora-15133 : instance recovery required for diskgroup string
  • ora-39106 : Worker process string failed during startup. Worker error:
  • ora-30083 : syntax error was found in interval value expression
  • ora-14004 : missing PARTITION keyword
  • ora-39206 : A parallel degree of string is invalid.
  • ora-13241 : specified dimensionality does not match that of the data
  • ora-26714 : User error encountered while applying
  • ora-12840 : cannot access a remote table after parallel/insert direct load txn
  • ora-26020 : index string.string loaded successfully with string keys
  • ora-00363 : log is not the archived version
  • ora-19690 : backup piece release string incompatible with Oracle release string
  • ora-24098 : invalid value string for string
  • ora-01086 : savepoint 'string' never established
  • ora-13466 : format not appropriate for specified compression method
  • ora-13210 : error inserting data into the index table
  • ora-14176 : this attribute may not be specified for a hash partition
  • ora-04017 : invalid value string (length = string) for parameter max_dump_file_size
  • ora-16056 : backup control file archival requires proper syntax
  • ora-12629 : TNS:no event test
  • ora-01084 : invalid argument in OCI call
  • ora-39026 : master table is inconsistent on validation string
  • ora-30132 : invalid key index supplied
  • ora-22871 : ALTER TYPE with REPLACE is not allowed for pure incomplete types
  • ora-16080 : invalid LogMiner session string for APPLY
  • ora-00485 : DIAG process terminated with error string
  • ora-30757 : cannot access type information
  • 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.