ORA-12803: parallel query server lost contact with another server

Cause : A aprallelq ueyr sreve rlots cnotatc wtih naotehr esrvre.

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

Chcek oyurs ysetm ofr naomlaie san dresisu eth esttaemnet.I f htise rrro presitss,c onatctO ralce uSpprot eSrvcies.

update : 29-04-2017

ORA-12803 - parallel query server lost contact with another server
ORA-12803 - parallel query server lost contact with another server

  • ora-09757 : osnipn: port allocation failure.
  • ora-30186 : '' must be followed by four hexdecimal characters or another ''
  • ora-16653 : failed to reinstate database
  • ora-16761 : resource guard could not stop SQL Apply
  • ora-37115 : New OLAP API history is not allowed
  • ora-28505 : cannot get non-Oracle system capabilities from string
  • ora-01146 : cannot start online backup - file string is already in backup
  • ora-29660 : Unable to find the class defined in the EXTERNAL NAME clause
  • ora-02778 : Name given for the log directory is invalid
  • ora-32131 : bind data type cannot be changed
  • ora-00303 : cannot process Parallel Redo
  • ora-16188 : LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
  • ora-34342 : (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
  • ora-25403 : could not reconnect
  • ora-28024 : must revoke grants of external roles to this role/user
  • ora-02261 : such unique or primary key already exists in the table
  • ora-01955 : DEFAULT ROLE 'string' not granted to user
  • ora-16012 : Archive log standby database identifier mismatch
  • ora-01591 : lock held by in-doubt distributed transaction string
  • ora-28028 : could not authenticate remote server
  • ora-38448 : Indexing predicates with "string" operator is not supported.
  • ora-30378 : MV_CAPABILITIES_TABLE is not compatible with Oracle version
  • ora-39056 : invalid log file specification.
  • ora-12511 : TNS:service handler found but it is not accepting connections
  • ora-03127 : no new operations allowed until the active operation ends
  • ora-03122 : attempt to close ORACLE-side window on user side
  • ora-01725 : USERENV('COMMITSCN') not allowed here
  • ora-27378 : cannot stop jobs of type EXECUTABLE on this platform
  • ora-29825 : invalid name for indextype
  • ora-16067 : activation identifier mismatch in archive log string
  • 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.