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 : 28-05-2017

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

  • ora-03286 : ALLOCATE EXTENT not valid for HASH CLUSTERS
  • ora-09931 : Unable to open ORACLE password file for reading
  • ora-04000 : the sum of PCTUSED and PCTFREE cannot exceed 100
  • ora-10940 : trace name context forever
  • ora-23324 : error string, while creating deferror entry at "string" with error string
  • ora-09216 : sdnfy: bad value 'string' for parameter string
  • ora-01096 : program version (string) incompatible with instance (string)
  • ora-13268 : error obtaining dimension from USER_SDO_GEOM_METADATA
  • ora-02831 : Segment deallocation failed - empty segment list
  • ora-13868 : Instance-wide SQL tracing on instance string is not enabled
  • ora-31434 : purge is currently running
  • ora-39703 : server version and script version do not match
  • ora-30972 : invalid ALTER INDEX option for XML Index
  • ora-12053 : this is not a valid nested materialized view
  • ora-25181 : missing ON keyword for NESTED INDEX
  • ora-25236 : buffer too small for user data
  • ora-22140 : given size [string] must be in the range of 0 to [string]
  • ora-01989 : role 'string' not authorized by operating system
  • ora-19616 : output filename must be specified if database not mounted
  • ora-12640 : Authentication adapter initialization failed
  • ora-32003 : error occured processing parameter 'string'
  • ora-13766 : A ranking measure is required.
  • ora-30957 : cannot downgrade because there are XML indexes
  • ora-38740 : Usable blocks value string is not valid.
  • ora-00480 : LCK* process terminated with error
  • ora-22994 : source offset is beyond the end of the source LOB
  • ora-01222 : MAXINSTANCES of string requires MAXLOGFILES be at least string, not string
  • ora-06402 : NETCMN: error receiving break message
  • ora-30442 : can not find the definition for filter string
  • ora-02421 : missing or invalid schema authorization identifier
  • 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.