ORA-14552: cannot perform a DDL, commit or rollback inside a query or DML

Cause : DDL operations like creation tables, views etc. and transaction control statements such as commit/rollback cannot be performed inside a query or a DML statement.

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

Ensure that the offending operation is not performed or use autonomous transactions to perform the operation within the query/DML operation.

update : 28-04-2017
ORA-14552

ORA-14552 - cannot perform a DDL, commit or rollback inside a query or DML
ORA-14552 - cannot perform a DDL, commit or rollback inside a query or DML

  • ora-13484 : the file format and/or compression type is not supported
  • ora-31053 : The value of the depth argument in the operator cannot be negative
  • ora-29390 : some resource plans are not part of any top-plan
  • ora-36163 : (XSMXAGGR06) The AGGREGATE function cannot be run on more than one variable at a time.
  • ora-04071 : missing BEFORE, AFTER or INSTEAD OF keyword
  • ora-30353 : expression not supported for query rewrite
  • ora-12469 : no user levels found for user string and policy string
  • ora-24238 : object settings argument passed to DBMS_UTILITY.INVALIDATE is not legal
  • ora-40302 : invalid classname string in cost matrix specification
  • ora-14626 : values being added already exist in DEFAULT subpartition
  • ora-06005 : NETASY: dialogue file read failure
  • ora-12618 : TNS:versions are incompatible
  • ora-26082 : load of overlapping segments on table string.string is not allowed
  • ora-30398 : illegal JOIN KEY clause
  • ora-23350 : maximum number of recursive calls exceeded
  • ora-13267 : error reading data from layer table string
  • ora-00021 : session attached to some other process; cannot switch session
  • ora-16082 : logical standby is not initialized correctly
  • ora-38422 : invalid datatype for the attribute: string
  • ora-39705 : component 'string' not found in registry
  • ora-29317 : datafile string does not exist
  • ora-08440 : raw buffer is too short to hold converted data
  • ora-01589 : must use RESETLOGS or NORESETLOGS option for database open
  • ora-06431 : ssaio: Invalid Block number
  • ora-13529 : Error occurred when flushing AWR table group
  • ora-06751 : TLI Driver: bound addresses unequal
  • ora-01930 : auditing the object is not supported
  • ora-14107 : partition specification is required for a partitioned object
  • ora-38768 : resizing datafile string failed
  • ora-19705 : tag value exceeds maximum length of string characters
  • 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.