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 : 25-04-2017

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

  • ora-28169 : unsupported certificate type
  • ora-32009 : cannot reset the memory value for instance string from instance string
  • ora-13373 : invalid line segment in geodetic data
  • ora-33046 : (XSAGDNGL22) In AGGMAP workspace object, you can specify only one SCREENBY clause.
  • ora-06430 : ssaio: Seals do not match
  • ora-00333 : redo log read error block string count string
  • ora-12208 : TNS:could not find the TNSNAV.ORA file
  • ora-16103 : Logical Standby apply must be stopped to allow this operation
  • ora-09987 : unable to attach to SGA in READ-ONLY mode
  • ora-01328 : only one build operation may occur at one time
  • ora-08468 : mask option string is not supported
  • ora-01933 : cannot create a stored object using privileges from a role
  • ora-32163 : Method called on Invalid Environment type
  • ora-19041 : Comment data cannot contain two consecutive '-'s
  • ora-26076 : cannot set or reset value after direct path structure is allocated
  • ora-36862 : (XSTFRC02) Column number for this SQL Cache must be between 1 and number. Specified column number number is invalid.
  • ora-32128 : setDataBuffer called after fetch has started
  • ora-26022 : index string.string was made unusable due to:
  • ora-22852 : invalid PCTVERSION LOB storage option value
  • ora-38719 : Invalid DUMP FLASHBACK object.
  • ora-39157 : error appending extension to file "string"
  • ora-38797 : Full database recovery required after a database has been flashed back
  • ora-12081 : update operation not allowed on table "string"."string"
  • ora-13273 : dimension metadata table string does not exist
  • ora-39753 : unsupported use of subquery in PARTITIONED OUTER JOIN condition
  • ora-12168 : TNS:Unable to contact LDAP Directory Server
  • ora-00127 : dispatcher string does not exist
  • ora-32307 : must use FROM ONLY clause when referencing an object table
  • ora-32024 : invalid directory specified for audit_file_dest parameter
  • ora-16079 : standby archival not enabled
  • 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.