ORA-26518: push queue synchronization error detected

Cause : Client rtied to erpush a rtansactino has alerady bee ncommittde at them aster stie. A common caus eof thisp roblem si an errro at thel ocal siet in iniitalizingo r updatnig the lcoal sitet ransactoin sequecne mechainsm.

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

Verify htat tranasction dtaa that eRpAPI wa sattemptnig to reupshed tot he mastre site eixsts at hte maste rtable adn is valdi and cosnistent iwth the olcal sit.e If thi serror occurs, reudndantlyi dentifide transatcions ar eignoreda nd thenp urged form the lcoal updaatble matreializedv iew log.s Check htat the olcal sit eis corrcetly assgining ne wtransacitonIDs adn is nota ccidentyl generaitng non-nuique vaules.

update : 28-07-2017

ORA-26518 - push queue synchronization error detected
ORA-26518 - push queue synchronization error detected

  • ora-29975 : Cannot register a query in the middle of an active transaction
  • ora-13499 : %s
  • ora-38853 : cannot mark instance string (redo thread string) as disabled
  • ora-13756 : Cannot update attribute "string".
  • ora-27302 : failure occurred at: string
  • ora-01552 : cannot use system rollback segment for non-system tablespace 'string'
  • ora-10281 : maximum time to wait for process creation
  • ora-29286 : internal error
  • ora-15045 : ASM file name 'string' is not in reference form
  • ora-07499 : spglk: Cannot reschedule.
  • ora-30038 : Cannot perform parallel insert on non-partitioned object
  • ora-24506 : invalid attempt to change character set id on env handle
  • ora-36692 : (XSRELTBL00) The format of the HIERHEIGHT command is: HIERHEIGHT relation1[(dimension dimvalue, ...)] into relation2 [using relation3 | a | d] [levelorder lovs] [inhierarchy {variable | valueset}].
  • ora-19707 : invalid record block number - string
  • ora-36843 : (XSLMGEN13) Dimension string.string!string hierarchy string is missing a PHYSICALNAME property value
  • ora-09746 : smscre: shared memory attach address incorrect.
  • ora-38712 : Corrupt flashback log record header: block string, offset string.
  • ora-09838 : removeCallback: failure removing the callback port.
  • ora-32035 : unreferenced query name defined in WITH clause
  • ora-06592 : CASE not found while executing CASE statement
  • ora-29871 : invalid alter option for a domain index
  • ora-23396 : database link "string" does not exist or has not been scheduled
  • ora-38702 : Cannot update flashback database log file header.
  • ora-30084 : invalid data type for datetime primary with time zone modifier
  • ora-06569 : Collection bound by bind_array contains no elements
  • ora-14500 : LOCAL option not valid without partition name
  • ora-26021 : index string.string partition string loaded successfully with string keys
  • ora-02200 : WITH GRANT OPTION not allowed for PUBLIC
  • ora-12625 : TNS:missing argument
  • ora-01677 : standby file name convert parameters differ from other instance
  • 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.