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 : 26-07-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-25102 : PARALLEL option can only be used with ALTER INDEX REBUILD
  • ora-30744 : "string" is not an object table
  • ora-00607 : Internal error occurred while making a change to a data block
  • ora-36212 : (XSAGOP06) In AGGMAP workspace object, you can only specify the MIN, MAX, FLOOR, and CEILING arguments while using the PROPORTIONAL operator, not string.
  • ora-30461 : 'string.string' cannot be refreshed because it is marked DISABLED
  • ora-37011 : (XSACQUIRE_LOCKED) Object workspace object is locked by another user.
  • ora-39020 : invalid mode type string
  • ora-28003 : password verification for the specified password failed
  • ora-01478 : array bind may not include any LONG columns
  • ora-13380 : network not found
  • ora-24238 : object settings argument passed to DBMS_UTILITY.INVALIDATE is not legal
  • ora-13826 : empty SQL profile not allowed for create or update SQL profile
  • ora-12042 : cannot alter job_queue_processes in single process mode
  • ora-37142 : (XSSQLMDQ02) Invalid host variable data type for MDQUERY procedure: string expected.
  • ora-16148 : user requested expiration of managed recovery operation
  • ora-02053 : transaction string committed, some remote DBs may be in-doubt
  • ora-31686 : error creating worker processes
  • ora-19706 : invalid SCN
  • ora-22975 : cannot create a PRIMARY KEY-based REF to this object view
  • ora-06593 : %s is not supported with natively compiled PL/SQL modules
  • ora-32017 : failure in updating SPFILE
  • ora-29706 : incorrect value string for parameter ACTIVE_INSTANCE_COUNT
  • ora-16178 : Cannot specify remote destinations in archivelog manual mode
  • ora-16059 : Log file is empty or invalid next available block
  • ora-01679 : database must be mounted EXCLUSIVE and not open to activate
  • ora-28103 : adding a policy to an object owned by SYS is not allowed
  • ora-16729 : validation of value for property string found string error
  • ora-12155 : TNS:received bad datatype in NSWMARKER packet
  • ora-13214 : failed to compute supercell for window object
  • ora-38857 : cannot mark redo thread string as enabled
  • 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.