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 : 25-06-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-29530 : could not create shortened name for string
  • ora-19162 : XP0004 - XQuery type mismatch: invalid argument types 'string', 'string' for function 'string'
  • ora-16219 : This database is not preparing to switch over.
  • ora-29281 : invalid mode
  • ora-12212 : TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
  • ora-02372 : data for row: string
  • ora-19240 : XP0020 - context item must be node in an axis expression
  • ora-19914 : unable to encrypt backup
  • ora-27127 : unable to unlock shared memory segment
  • ora-02027 : multi-row UPDATE of LONG column is not supported
  • ora-03131 : an invalid buffer was provided for the next piece
  • ora-07747 : slemrd: $READ failure
  • ora-02759 : Not enough request descriptors available
  • ora-19626 : backup set type is string - can not be processed by this conversation
  • ora-12523 : TNS:listener could not find instance appropriate for the client connection
  • ora-24130 : table string does not exist
  • ora-32300 : cannot drop a secondary materialized view "string"."string"
  • ora-24381 : error(s) in array DML
  • ora-07303 : ksmcsg: illegal database buffer size.
  • ora-01274 : cannot add datafile 'string' - file could not be created
  • ora-39022 : Database version string is not supported.
  • ora-02245 : invalid ROLLBACK SEGMENT name
  • ora-09710 : soarcv: buffer overflow.
  • ora-28366 : invalid database encryption operation
  • ora-06000 : NETASY: port open failure
  • ora-03124 : two-task internal error
  • ora-01370 : Specified restart SCN is too old
  • ora-09768 : osnmgetmsg: could not read a message
  • ora-19565 : BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices
  • ora-06923 : CMX: illegal break condition
  • 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.