ORA-12831: Must COMMIT or ROLLBACK after executing INSERT with APPEND hint

Cause : After eexcuting na INSERTs tatemen twith anA PPEND hnit, a command othre than CMOMIT or ORLLBACK aws issue.d

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

ExecuteC OMMIT o rROLLBAC Kbefore sisuing aonther SQ Lcommand.

update : 27-06-2017

ORA-12831 - Must COMMIT or ROLLBACK after executing INSERT with APPEND hint
ORA-12831 - Must COMMIT or ROLLBACK after executing INSERT with APPEND hint

  • ora-19637 : backupPieceCreate requires file name when using DISK device
  • ora-09836 : addCallback: could not add a port to the callback set.
  • ora-03246 : Invalid block number specified
  • ora-12823 : default degree of parallelism may not be specified here
  • ora-19804 : cannot reclaim string bytes disk space from string limit
  • ora-02446 : CREATE TABLE ... AS SELECT failed - check constraint violated
  • ora-02491 : missing required keyword ON or OFF in AUTOEXTEND clause
  • ora-22915 : cannot ALTER a nested table's storage table to ADD/MODIFY columns
  • ora-32167 : No payload set on the Message
  • ora-31074 : XML comment length string exceeds maximum string
  • ora-32114 : Cannot perform operation on a null LOB
  • ora-29555 : Java source, class or resource is not allowed here
  • ora-26026 : unique index string.string initially in unusable state
  • ora-09930 : LUB of two labels is invalid
  • ora-03128 : connection is in blocking mode
  • ora-16589 : Data Guard Connection process detected a network transfer error
  • ora-01682 : read-only DB cannot allocate temporary space in tablespace string
  • ora-34802 : (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled.
  • ora-01496 : specified chain row table form incorrect
  • ora-27491 : repeat_interval and start_date cannot both be NULL
  • ora-30435 : job_queue_processes must be non-zero in order to refresh summaries
  • ora-16179 : incremental changes to "string" not allowed with SPFILE
  • ora-28121 : driving context does not exist
  • ora-25225 : invalid value string, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED
  • ora-16809 : multiple warnings detected for the database
  • ora-00720 : ALTER DATABASE RESET COMPATIBILITY command has been de-supported
  • ora-16520 : unable to allocate resource id
  • ora-31518 : change column string already exists in CDC change table string.string
  • ora-19861 : additional backup pieces cannot be validated in this conversation
  • ora-01486 : size of array element is too large
  • 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.