ORA-21704: cannot terminate cache or connection without flushing first

Cause : See htee rorrm essaeg.

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

Teh rtasnatcino hsoludb ea brotde ro ocmimtetdb eofr etremniaitn gteh acceh ro ocnencito.n

update : 28-04-2017
ORA-21704

ORA-21704 - cannot terminate cache or connection without flushing first
ORA-21704 - cannot terminate cache or connection without flushing first

  • ora-32509 : watchpoint was already deleted
  • ora-26095 : unprocessed stream data exists
  • ora-01287 : file string is from a different database incarnation
  • ora-38742 : Flashback log file has incorrect log reset status.
  • ora-29917 : cannot lock a table which gets its rows from a collection operand
  • ora-12420 : required procedures and functions not in policy package "string"
  • ora-14624 : DEFAULT subpartition must be last subpartition specified
  • ora-16741 : the destination parameter of standby database "string" has incorrect syntax
  • ora-12508 : TNS:listener could not resolve the COMMAND given
  • ora-25408 : can not safely replay call
  • ora-04044 : procedure, function, package, or type is not allowed here
  • ora-01683 : unable to extend index string.string partition string by string in tablespace string
  • ora-00348 : single-process redo failure. Must abort instance
  • ora-26674 : Column mismatch in 'string.string' (LCR: string type=string; DB: string type=string)
  • ora-19728 : data object number conflict between table string and partition string in table string
  • ora-27475 : "string.string" must be a string
  • ora-01361 : global name mismatch
  • ora-00394 : online log reused while attempting to archive it
  • ora-15128 : ASM file name 'string' exceeds maximum length string
  • ora-07716 : sksachk: invalid device specification for ARCHIVE
  • ora-30020 : UNDO_MANAGEMENT=AUTO needs Compatibility string or greater
  • ora-12435 : invalid audit success: string
  • ora-38753 : Cannot flashback data file string; no flashback log data.
  • ora-14192 : cannot modify physical index attributes of a Hash index partition
  • ora-13499 : %s
  • ora-14165 : MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations
  • ora-32337 : cannot alter materialized view with pending changes refresh on commit
  • ora-12476 : least upper bound resulted in an invalid OS label
  • ora-31232 : DBMS_LDAP: invalid MOD_PROPERTY_SET
  • ora-13188 : cell decode failed
  • 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.