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 : 25-06-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-01612 : instance string (thread string) is already enabled
  • ora-36740 : A CHILDLOCK was detected in your valueset
  • ora-19282 : XQ0068 - It is a static error if a Prolog contains more than one xmlspace declaration
  • ora-19638 : file string is not current enough to apply this incremental backup
  • ora-13043 : failed to read metadata from the _SDOLAYER table
  • ora-26094 : stream format error: input column overflow
  • ora-02302 : invalid or missing type name
  • ora-02760 : Client close of file failed.
  • ora-09200 : sfccf: error creating file
  • ora-22865 : more than one column specified
  • ora-25200 : invalid value string, QUEUE_NAME should be [SCHEMA.]NAME
  • ora-28578 : protocol error during callback from an external procedure
  • ora-03213 : Invalid Lob Segment Name for DBMS_SPACE package
  • ora-29509 : incorrectly formed Java binary class definition
  • ora-12653 : Authentication control function failed
  • ora-39157 : error appending extension to file "string"
  • ora-33920 : (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, or INTEGER.
  • ora-40285 : label not in the model
  • ora-02468 : Constant or system variable wrongly specified in expression
  • ora-01197 : thread string only contains one log
  • ora-39762 : streams must be loaded in conversion order
  • ora-15007 : name is already used by an existing template
  • ora-28584 : heterogeneous apply internal error
  • ora-14121 : MODIFY DEFAULT ATTRIBUTES may not be combined with other operations
  • ora-04068 : existing state of packagesstringstringstring has been discarded
  • ora-15102 : invalid POWER expression
  • ora-29295 : invalid mime header tag
  • ora-31181 : PL/SQL DOM handle accesses node that is no longer available
  • ora-30134 : reserved for future use
  • ora-16652 : Fast-Start Failover target standby database is disabled
  • 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.