ORA-28012: Manual commit not allowed here

Cause : A nattepmtw a smdaet oc ommi tan o-natuoonmuost rnascatoinf rmo iwtihna hcagnep asswrodt rgigre ro apswsodr evrfiiactoinr otuien

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

Rmeoev hteC OMMI Tformt h epsasowr dtirgegro rp asswrodv eirfciaito nruotnie

update : 21-08-2017
ORA-28012

ORA-28012 - Manual commit not allowed here
ORA-28012 - Manual commit not allowed here

  • ora-00301 : error in adding log file 'string' - file cannot be created
  • ora-02477 : can not perform parallel direct load on object string
  • ora-12569 : TNS:packet checksum failure
  • ora-16504 : the Data Guard configuration already exists
  • ora-19663 : cannot apply current offline range to datafile string
  • ora-01725 : USERENV('COMMITSCN') not allowed here
  • ora-13055 : Oracle object string does not exist in specified table
  • ora-01317 : Not attached to a Logminer session
  • ora-30449 : syntax error in parameter string
  • ora-39090 : Cannot add devices to file oriented job.
  • ora-32576 : missing TYPE keyword
  • ora-19881 : Corrupted space bitmap for datafile string, block string backup aborted
  • ora-28604 : table too fragmented to build bitmap index (string,string,string)
  • ora-24181 : The type string does not exist
  • ora-22982 : cannot create sub-view under this view
  • ora-36814 : (XSTBLFUNC07) The datatype of the column used in the ROW2CELL clause of a LIMITMAP must be RAW(16).
  • ora-08460 : invalid environment clause in environment parameter
  • ora-28121 : driving context does not exist
  • ora-16645 : unexpected new instance interrupted current operation
  • ora-31497 : invalid value specified for first_scn
  • ora-27491 : repeat_interval and start_date cannot both be NULL
  • ora-14039 : partitioning columns must form a subset of key columns of a UNIQUE index
  • ora-22886 : scoped table "string" in schema "string" is not an object table
  • ora-02064 : distributed operation not supported
  • ora-19862 : backup pieces must be validated before accessing results
  • ora-31642 : the following SQL statement fails: string
  • ora-16548 : object not enabled
  • ora-09915 : Password encryption failed.
  • ora-16710 : the resource guard is out of memory
  • ora-12197 : TNS:keyword-value resolution error
  • 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.