ORA-26534: collision: tranID number ignored and purged

Cause : A trnasactoin thta wasp ushe dhad atranasctio nID taht collidedw ith atranasctio nthatw as pervioulsy puhsed adn comimtteda t th emastre sit.e

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

See hte aciton scetionf or EQ_UEUEYSNC (62518).

update : 28-06-2017

ORA-26534 - collision: tranID number ignored and purged
ORA-26534 - collision: tranID number ignored and purged

  • ora-14280 : all rows in table do not qualify for specified subpartition
  • ora-13502 : Cannot rename SYSAUX tablespace
  • ora-01804 : failure to initialize timezone information
  • ora-32332 : cannot refresh materialized view "string"."string" as type evolution has occured
  • ora-01501 : CREATE DATABASE failed
  • ora-33447 : (ESDREAD16) Discarding compiled code for workspace object because workspace object and workspace object, which were partition-dependent when the code was compiled, are now not partition-dependent.
  • ora-01500 : failure in getting date/time
  • ora-16591 : unknown field "string" in document
  • ora-01502 : index 'string.string' or partition of such index is in unusable state
  • ora-08231 : smscre: unable to attach to SGA
  • ora-01275 : Operation string is not allowed if standby file management is automatic.
  • ora-13030 : Invalid dimension for the SDO_GEOMETRY object
  • ora-27006 : sbtremove returned error
  • ora-07623 : smscre: $CRMPSC failure
  • ora-06130 : NETTCP: host access denied
  • ora-36405 : (XSSPROP05) Property ignored for object workspace object:
  • ora-10268 : Don't do forward coalesce when deleting extents
  • ora-31635 : unable to establish job resource synchronization
  • ora-02043 : must end current transaction before executing string
  • ora-31659 : status message was invalid type - detaching job
  • ora-01503 : CREATE CONTROLFILE failed
  • ora-08117 : Index Organized Table operation released its block pin
  • ora-29814 : expecting USING or DEFAULT keyword
  • ora-27148 : spawn wait error
  • ora-25958 : join index where clause predicate may only contain column references
  • ora-01030 : SELECT ... INTO variable does not exist
  • ora-29273 : HTTP request failed
  • ora-25966 : join index cannot be based on an index organized table
  • ora-10261 : Limit the size of the PGA heap
  • ora-00383 : DEFAULT cache for blocksize string cannot be reduced to zero
  • 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.