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-07-2017

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

  • ora-06518 : PL/SQL: Probe version string incompatible with version string
  • ora-00102 : network protocol string cannot be used by dispatchers
  • ora-40108 : input data contains too few distinct target (string) values
  • ora-08330 : Printing not supported
  • ora-29317 : datafile string does not exist
  • ora-26664 : cannot create STREAMS process string
  • ora-31067 : XML nodes must be updated with valid nodes and of the same type
  • ora-27141 : invalid process ID
  • ora-28538 : result set not found
  • ora-01177 : data file does not match dictionary - probably old incarnation
  • ora-16067 : activation identifier mismatch in archive log string
  • ora-31059 : Cannot insert root XML document node if it already exists
  • ora-24067 : exceeded maximum number of subscribers for queue string
  • ora-01641 : tablespace 'string' is not online - cannot add data file
  • ora-29336 : Internal error [string] [string] from DBMS_PLUGTS
  • ora-08119 : The new initrans will make the index too big
  • ora-25103 : NOPARALLEL option can only be used with ALTER INDEX REBUILD
  • ora-16524 : unsupported operation
  • ora-08276 : No room in nameserver for pid
  • ora-30366 : child JOIN KEY columns not in same relation as child level
  • ora-01143 : cannot disable media recovery - file string needs media recovery
  • ora-23415 : materialized view log for "string"."string" does not record the primary key
  • ora-01155 : the database is being opened, closed, mounted or dismounted
  • ora-01558 : out of transaction ID's in rollback segment string
  • ora-08344 : srapp: failed to send redo data to the redo server
  • ora-06755 : TLI Driver: cannot close transport endpoint
  • ora-36638 : (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-17509 : Attempt to do i/o beyond block1 offset
  • ora-19860 : piece validation cannot be performed more than once
  • ora-37102 : (XSVPART02) Invalid partition name string.
  • 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.