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

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

  • ora-31624 : A job cannot be modified after it has started.
  • ora-08114 : can not alter a fake index
  • ora-16089 : archive log has already been registered
  • ora-13043 : failed to read metadata from the _SDOLAYER table
  • ora-06037 : NETDNT: connect failed, node unreachable
  • ora-12217 : TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA
  • ora-09214 : sfdone: I/O error detected
  • ora-13408 : invalid blockSize storage parameter
  • ora-13711 : Some snapshots in the range [string, string] are missing key statistics.
  • ora-02152 : Invalid ALTER TABLESPACE ... RENAME option
  • ora-28350 : cannot encrypt the specified column recorded in CDC synchronized change table
  • ora-14641 : STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition
  • ora-29517 : recursive resolution failed for a referenced class
  • ora-38743 : Time/SCN is in the future of the database.
  • ora-23431 : wrong state: string
  • ora-25010 : Invalid nested table column name in nested table clause
  • ora-31403 : change table string already contains a column string
  • ora-38765 : Flashed back database cannot be opened read-only.
  • ora-24341 : bad mode specified
  • ora-01678 : parameter string must be pairs of pattern and replacement strings
  • ora-37027 : (XSMLTRESYNC02) Object workspace object cannot be resynced without modified object workspace object because they share a modified composite dimension.
  • ora-27365 : job has been notified to stop, but failed to do so immediately
  • ora-32731 : Another Parallel Oradebug session is in progress
  • ora-14606 : Tablespace was specified for previous subpartitions in template but is not specified for string
  • ora-12731 : invalid collation class in regular expression
  • ora-07402 : sprst: cannot restore user signal handler.
  • ora-24367 : user handle has not been set in service handle
  • ora-39099 : cannot create index for "string" on master table string
  • ora-01233 : file string is read only - cannot recover using backup control file
  • ora-37100 : (XSUNCOMMITTED) You have one or more updated but uncommitted analytic workspaces.
  • 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.