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 : 28-05-2017

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

  • ora-28362 : master key not found
  • ora-35276 : (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [ USING aggmap ]
  • ora-24195 : attemp to retrieve the name list of a map message with size exceeding 1024
  • ora-25118 : invalid DUMP DATAFILE/TEMPFILE option
  • ora-31060 : Resource at path string could not be deleted
  • ora-29283 : invalid file operation
  • ora-06007 : NETASY: bad dialogue format
  • ora-22304 : input type is not an object type
  • ora-06757 : TLI Driver: server got bad command
  • ora-12481 : effective label not within program unit clearance range
  • ora-02751 : osnfsmmap: cannot map shared memory file
  • ora-19551 : device is busy, device type: string, device name: string
  • ora-40272 : apply rules prohibited for this model mode
  • ora-00101 : invalid specification for system parameter DISPATCHERS
  • ora-24053 : PRIMARY_INSTANCE and SECONDARY_INSTANCE must be non-negative
  • ora-12681 : Login failed: the SecurID card does not have a pincode yet
  • ora-00114 : missing value for system parameter SERVICE_NAMES
  • ora-29289 : directory access denied
  • ora-25187 : specified exceptions table form incorrect
  • ora-01351 : tablespace given for Logminer dictionary does not exist
  • ora-32838 : exceeded maximum number of properties
  • ora-29868 : cannot issue DDL on a domain index marked as LOADING
  • ora-00370 : potential deadlock during kcbchange operation
  • ora-31671 : Worker process string had an unhandled exception.
  • ora-22917 : use VARRAY to define the storage clause for this column or attribute
  • ora-30107 : parameter name abbreviation 'string' is not unique
  • ora-07216 : slghst: gethostname error, unable to get name of current host.
  • ora-12234 : TNS:Redirect to destination
  • ora-38424 : no attribute set currently assigned to the expression set
  • ora-18015 : invalid source outline signature
  • 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.