ORA-31659: status message was invalid type - detaching job

Cause : Message from the master process on the status queue had an invalid message type, indicating a failure in the protocol.

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

Reattach and retry the operation. Contact Oracle Customer Support if the problem persists.

update : 29-04-2017
ORA-31659

ORA-31659 - status message was invalid type - detaching job
ORA-31659 - status message was invalid type - detaching job

  • ora-16194 : Modifying DB_UNIQUE_NAME requires SID='*' qualifier
  • ora-27413 : repeat interval is too long
  • ora-28331 : encrypted column size too long for its data type
  • ora-10662 : Segment has long columns
  • ora-24029 : operation not allowed on a single-consumer queue
  • ora-01509 : specified name 'string' does not match actual 'string'
  • ora-27143 : OS system call failure
  • ora-08278 : Cannot get CPU statistics
  • ora-36882 : (XSSRF01) The second parameter of an AW single row function cannot be NULL.
  • ora-32016 : parameter "string" cannot be updated in SPFILE
  • ora-36992 : (XSRELGID09) A level relation is needed to produce a surrogate dimension gid.
  • ora-36176 : (XSMXAGGR25) Relation workspace object must be a one-dimensional self-relation to be used as a weight for AGGREGATE.
  • ora-12066 : invalid CREATE MATERIALIZED VIEW command
  • ora-13789 : invalid process action
  • ora-09942 : Write of ORACLE password file header failed.
  • ora-30121 : 'string' is not an allowable value for 'string'
  • ora-06804 : TLI Driver: could not bind an IPX address at initialization
  • ora-01652 : unable to extend temp segment by string in tablespace string
  • ora-13443 : GeoRaster metadata SRS error
  • ora-25245 : agent name cannot be specified if address is a single-consumer queue or an exception queue
  • ora-02467 : Column referenced in expression not found in cluster definition
  • ora-25473 : cannot store string in rule action context
  • ora-24772 : Cannot mix tightly-coupled and loosely-coupled branches
  • ora-16061 : Log file status has changed
  • ora-38786 : Flash recovery area is not enabled.
  • ora-09321 : slzdtb: unable to convert zoned decimal to binary
  • ora-29975 : Cannot register a query in the middle of an active transaction
  • ora-31638 : cannot attach to job string for user string
  • ora-22872 : OID INDEX clause not allowed on tables with primary key based object identifiers
  • ora-27543 : Failed to cancel outstanding IPC request
  • 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.