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 : 24-07-2017
ORA-31659

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

  • ora-32550 : Replacement occured despite hint to the contrary
  • ora-19740 : text is longer than string
  • ora-34179 : (MXCHGDCL20) workspace object is not a PARTITION TEMPLATE.
  • ora-01469 : PRIOR can only be followed by a column name
  • ora-39139 : Data Pump does not support XMLSchema objects. string will be skipped.
  • ora-39136 : cannot specify an SCN on a transportable job
  • ora-26748 : The one-to-one transformation function string encountered the following error: string
  • ora-00339 : archived log does not contain any redo
  • ora-30069 : Auto Undo-Management Error simulation - test site = string
  • ora-32837 : invalid configuration state string
  • ora-35071 : (QFHEAD06) EIF file string cannot be imported because analytic workspace string has not been upgraded to version string.
  • ora-28117 : integrity constraint violated - parent record not found
  • ora-16584 : illegal operation on a standby site
  • ora-09340 : Specified ORACLE_SID is either invalid or too long
  • ora-12900 : must specify a default temporary tablespace for a locally managed database
  • ora-24354 : number fetched too large to fit in COBOL display type buffer.
  • ora-22916 : cannot do an exact FETCH on a query with Nested cursors
  • ora-40287 : invalid data for model - cosine distance out of bounds
  • ora-01296 : character set mismatch between dictionary string and logfiles
  • ora-12197 : TNS:keyword-value resolution error
  • ora-08456 : no sign in picture mask but SIGN clause in mask options
  • ora-13117 : [string]_RELATION$ table does not exist
  • ora-13525 : error with computing space usage for sysaux occupant
  • ora-10589 : Test recovery had to corrupt string data blocks in order to proceed
  • ora-09880 : sstasfre/sstasdel: shmdt error, unable to detach tas write page
  • ora-14106 : LOGGING/NOLOGGING may not be specified for a clustered table
  • ora-28353 : failed to open wallet
  • ora-14461 : cannot REUSE STORAGE on a temporary table TRUNCATE
  • ora-01080 : error in shutting down ORACLE
  • ora-30339 : illegal dimension attribute name
  • 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.