ORA-12838: cannot read/modify an object after modifying it in parallel

Cause : Within the same transaction, an attempt was made to add read or modification statements on a table after it had been modified in parallel or with direct load. 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 initial modification and the second containing the parallel modification operation.

update : 28-04-2017

ORA-12838 - cannot read/modify an object after modifying it in parallel
ORA-12838 - cannot read/modify an object after modifying it in parallel

  • ora-00490 : PSP process terminated with error
  • ora-02058 : no prepared transaction found with ID string
  • ora-07478 : scgcmn: cannot get lock status.
  • ora-32622 : illegal multi-cell reference
  • ora-22329 : cannot alter a non-object type
  • ora-06432 : ssaio: Buffer Not Aligned
  • ora-13919 : Cannot specify values for parameter "string" and for parameter "string"
  • ora-01479 : last character in the buffer is not Null
  • ora-12026 : invalid filter column detected
  • ora-32836 : database user string must be granted role string
  • ora-10387 : parallel query server interrupt (normal)
  • ora-01562 : failed to extend rollback segment number string
  • ora-29529 : invalid function or method call string in trigger string
  • ora-13420 : the SRID of the geometry parameter was not null
  • ora-02270 : no matching unique or primary key for this column-list
  • ora-29869 : cannot issue ALTER without REBUILD on a domain index marked FAILED
  • ora-30731 : scope constraint not allowed on nested table column when the nested table is being created
  • ora-13304 : failure to insert a transformed geometry object in a table
  • ora-14108 : illegal partition-extended table name syntax
  • ora-16632 : instance being added to database profile
  • ora-12322 : unable to mount database (link name string)
  • ora-06811 : TLI Driver: could not set the IPX network number at init
  • ora-01606 : gc_files_to_locks not identical to that of another mounted instance
  • ora-39129 : Object type string not imported. Name conflicts with the master table
  • ora-10919 : Default temporary tablespace group must have at least one tablespace
  • ora-38620 : DT expressions in input cursor do not have an alias name
  • ora-12467 : minimum label can contain a level only
  • ora-12718 : operation requires connection as SYS
  • ora-31205 : DBMS_LDAP: PL/SQL - Invalid LDAP Auth method.
  • ora-25253 : listen failed, queue string.string is not enabled for dequeue
  • 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.