ORA-10373: parallel query server kill event

Cause : internla use olny

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

this eevnt sholud neve rbe sete xternally

update : 25-06-2017

ORA-10373 - parallel query server kill event
ORA-10373 - parallel query server kill event

  • ora-00702 : bootstrap verison 'string' inconsistent with version 'string'
  • ora-12419 : null binary label value
  • ora-14325 : only LOCAL indexes may be specified in this clause
  • ora-19661 : datafile string could not be verified
  • ora-32143 : Environment not specified
  • ora-01202 : wrong incarnation of this file - wrong creation time
  • ora-04063 : %s has errors
  • ora-19911 : datafile string contains future changes at the incarnation boundary
  • ora-06806 : TLI Driver: could not complete protocol initialization for SPX
  • ora-32019 : The parameter SPFILE cannot be updated in the server parameter file.
  • ora-38504 : this operator not allowed with the configured attribute set
  • ora-12625 : TNS:missing argument
  • ora-14292 : Partitioning type of table must match subpartitioning type of composite partition
  • ora-31419 : source table string does not exist
  • ora-09814 : Unable to expand file name
  • ora-26045 : REF column string expects string arguments; found string.
  • ora-13334 : LRS segments not connected
  • ora-30732 : table contains no user-visible columns
  • ora-24911 : Cannot start listener thread at specified port
  • ora-16518 : unable to allocate virtual instance id
  • ora-16639 : specified instance inactive or currently unavailable
  • ora-06011 : NETASY: dialogue too long
  • ora-16775 : target standby database in broker operation has potential data loss
  • ora-29261 : bad argument
  • ora-29544 : invalid type
  • ora-38787 : Creating the first guaranteed restore point requires mount mode when flashback database is off.
  • ora-15079 : ASM file is closed
  • ora-25952 : join index must only contain inner equi-joins
  • ora-31420 : unable to submit the purge job
  • ora-27210 : syntax error in device PARMS
  • 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.