ORA-25400: must replay fetch

Cause : A failure occured since the last fetch on this statement. Failover was able to bring the statement to its original state to allow continued fetches.

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

This is an internally used error message and should not be seen by the user.

update : 25-04-2017
ORA-25400

ORA-25400 - must replay fetch
ORA-25400 - must replay fetch

  • ora-07233 : slemcw: invalid file handle, seals do not match.
  • ora-13153 : invalid high water mark specified
  • ora-16110 : user procedure processing of logical standby apply DDL
  • ora-39312 : call to DBMS_SCHEMA_COPY.CLEAN_TARGET is not legal
  • ora-02805 : Unable to set handler for SIGTPA
  • ora-33072 : (XSAGDNGL35) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must be specified for every relation dimensioned by that hierarchy dimension.
  • ora-16134 : invalid MANAGED recovery FINISH option
  • ora-15041 : diskgroup space exhausted
  • ora-00382 : %s not a valid block size, valid range [string..string]
  • ora-28109 : the number of related policies has exceeded the limit of 16
  • ora-32303 : mviews with user-defined types cannot reference multiple master sites
  • ora-14081 : new partition name must differ from the old partition name
  • ora-27050 : function called with invalid FIB/IOV structure
  • ora-31649 : Master process string violated startup protocol.
  • ora-23316 : the masterdef is string
  • ora-16233 : The table string.string is unsupported now
  • ora-25007 : functions or methods not allowed in WHEN clause
  • ora-17621 : failed to register the memory with Oracle Disk Manager library
  • ora-36168 : (XSMXAGGR10) COUNTVAR variable workspace object must have the same dimensionality as workspace object
  • ora-19699 : cannot make copies with compression enabled
  • ora-37112 : OLAP API requires Oracle 9.2 or later
  • ora-31516 : CDC change set string already exists
  • ora-08316 : sllfsk: Error seeking in file.
  • ora-16817 : unsynchronized Fast-Start Failover configuration
  • ora-02184 : resource quotas are not allowed in REVOKE
  • ora-19667 : cannot do incremental restore of datafile string
  • ora-06767 : TLI Driver: alloc failed during release
  • ora-31087 : insufficient privileges to delete schema "string"
  • ora-40253 : no target counter examples were found
  • ora-00060 : deadlock detected while waiting for resource
  • 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.