ORA-12802: parallel query server lost contact with coordinator

Cause : A parallel query server lost contact with the foreground (coordinator) process/thread.

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

Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services.

update : 23-04-2017

ORA-12802 - parallel query server lost contact with coordinator
ORA-12802 - parallel query server lost contact with coordinator

  • ora-14626 : values being added already exist in DEFAULT subpartition
  • ora-26013 : List allocated may not be big enough
  • ora-38492 : invalid ALTER INDEX parameters clause "string"
  • ora-12157 : TNS:internal network communication error
  • ora-13272 : geometric object string in table string is invalid
  • ora-13917 : Posting system alert with reason_id string failed with code [string] [string]
  • ora-36690 : (NTEXTCNV01) Error during conversion from NTEXT to TEXT.
  • ora-23501 : refresh template cannot be instantiated for database with compatibilty equal to or less than 8.0
  • ora-14407 : partitioned table contains subpartitions in a different tablespace
  • ora-07643 : smsalo: SMSVAR is invalid
  • ora-10615 : Invalid tablespace type for temporary tablespace
  • ora-33427 : (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.
  • ora-09941 : Version of orapasswd or installer is older than file.
  • ora-14302 : only one list of added-LOB-storage-clauses can be specified in a statement
  • ora-30066 : test support - drop rollback segment wait
  • ora-31668 : Timeout before worker process string finished initialization.
  • ora-07217 : sltln: environment variable cannot be evaluated.
  • ora-16536 : unknown object type
  • ora-09870 : spini: failure initializing maximum number of open files.
  • ora-39141 : dump file "string" is a duplicate of dump file "string"
  • ora-14511 : cannot perform operation on a partitioned object
  • ora-00272 : error writing archive log string
  • ora-31158 : schema "string" currently being referenced
  • ora-38852 : cannot mark the current instance (redo thread) as disabled
  • ora-12668 : Dedicated server: outbound protocol does not support proxies
  • ora-24016 : cannot create QUEUE_TABLE, user string does not have execute privileges on QUEUE_PAYLOAD_TYPE string.string
  • ora-13915 : Critical byte based free space threshold value is greater than warning threshold value.
  • ora-39059 : dump file set is incomplete
  • ora-27546 : Oracle compiled against IPC interface version string.string found version string.string
  • ora-29883 : cannot create a domain index on column expressions
  • 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.