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 : 24-08-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-12635 : No authentication adapters available
  • ora-13752 : User "string" must be SYS or must have the "ADMINISTER ANY SQL TUNING SET" privilege.
  • ora-37177 : column string does not have any leaf values
  • ora-23438 : missing refresh group template
  • ora-00282 : UPI string call not supported, use ALTER DATABASE RECOVER
  • ora-36765 : (XSAGGCNTMOVE03) A string aggregation variable cannot have a string AGGCOUNT.
  • ora-12544 : TNS:contexts have different wait/test functions
  • ora-08265 : create_ora_addr: cannot open nameserver
  • ora-31091 : empty string specified as a SQL name
  • ora-01719 : outer join operator (+) not allowed in operand of OR or IN
  • ora-02201 : sequence not allowed here
  • ora-13195 : failed to generate maximum tile value
  • ora-02778 : Name given for the log directory is invalid
  • ora-10574 : Test recovery did not corrupt any data block
  • ora-06533 : Subscript beyond count
  • ora-03200 : the segment type specification is invalid
  • ora-01626 : rollback segment number 'string' cannot handle more transactions
  • ora-06126 : NETTCP: ORASRV unable to open network connection
  • ora-27019 : tape filename length exceeds limit (SBTOPMXF)
  • ora-12597 : TNS:connect descriptor already in use
  • ora-16782 : instance not open for read and write access
  • ora-08121 : Number of indexes need to be maintained offline exceeds limit for DML
  • ora-38708 : not enough space for first flashback database log file
  • ora-01623 : log string is current log for instance string (thread string) - cannot drop
  • ora-08457 : syntax error in SEPARATE CHARACTER option of SIGN clause
  • ora-40215 : model string is incompatible with current operation
  • ora-38445 : TOP clause not allowed with no statistics
  • ora-22911 : duplicate storage specification for the nested table item
  • ora-25290 : Cannot complete operation on queue string with existing messages
  • ora-19717 : for non-OMF search the pattern must be specified
  • 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.