ORA-10389: parallel query server interrupt (cleanup)

Cause : internal use only

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

this event should never be set externally

update : 27-06-2017

ORA-10389 - parallel query server interrupt (cleanup)
ORA-10389 - parallel query server interrupt (cleanup)

  • ora-37157 : MDX syntax error was found in MDX query string but error text was missing
  • ora-13497 : %s
  • ora-02072 : distributed database network protocol mismatch
  • ora-31021 : Element definition not found
  • ora-07255 : spini: cannot set up signal handler.
  • ora-04096 : trigger 'string' has a WHEN clause which is too large, limit 2K
  • ora-09960 : Unable to establish signal handler for termination signal
  • ora-29351 : can not transport system, sysaux, or temporary tablespace 'string'
  • ora-31688 : Worker process string failed during startup.
  • ora-19599 : block number string is corrupt in string string
  • ora-01258 : unable to delete temporary file string
  • ora-39179 : unable to load table "string"."string" because of OID transform
  • ora-19616 : output filename must be specified if database not mounted
  • ora-23459 : flavor string must contain "string"
  • ora-16012 : Archive log standby database identifier mismatch
  • ora-16606 : unable to find property "string"
  • ora-31100 : XDB Locking Internal Error
  • ora-12831 : Must COMMIT or ROLLBACK after executing INSERT with APPEND hint
  • ora-01622 : thread number must be specified - default not specific
  • ora-02053 : transaction string committed, some remote DBs may be in-doubt
  • ora-24086 : cannot create a 8.0 compatible string queue
  • ora-25296 : Queue Table string has a buffered queue string
  • ora-16756 : resource guard could not open standby database read-only
  • ora-32132 : maximum iterations cannot be changed
  • ora-23472 : materialized view "string"."string" must be atomically refreshed
  • ora-02776 : Value for request done signal exceeds maximum
  • ora-25220 : enqueue failed, signature not specified for a non-repudiable queue
  • ora-28300 : No permission to read user entry in LDAP directory service.
  • ora-06816 : TLI Driver: could not set the SPX SAP address
  • ora-09293 : sksasmo: unable to send message to console
  • 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.