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 : 26-06-2017
ORA-31659

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

  • ora-07447 : ssarena: usinit failed.
  • ora-36278 : (XSCGMDLAGG07) workspace object does not exist or is not valueset.
  • ora-01784 : RECOVERABLE cannot be specified with database media recovery disabled
  • ora-27480 : window "string" is currently open
  • ora-13484 : the file format and/or compression type is not supported
  • ora-29386 : plan or consumer group string is mandatory and cannot be deleted or modified
  • ora-07241 : slemrd: read error.
  • ora-38855 : cannot mark instance string (redo thread string) as enabled
  • ora-19320 : Host name not specified in HTTP URL
  • ora-36198 : (XSAGGR33) The AGGREGATE operator string does not require a weight, but ARGS variable workspace object specified workspace object as a weight.
  • ora-30680 : debugger connection handshake failed
  • ora-33918 : (MAKEDCL33) You cannot define a surrogate of dimension workspace object because it is a string.
  • ora-24409 : client cannot understand the object
  • ora-06978 : X.25 Driver: Too many callback tries
  • ora-16160 : Cannot change protected standby database configuration
  • ora-22326 : cannot change a type to FINAL if it has subtypes
  • ora-35280 : (SNSYN165) The format of the AGGREGATE command is: AGGREGATE varname1 [varname2 varname3 ...] USING aggmap-name [COUNTVAR intvar-name1 [intvar-name2 intvar-name3 ...]] [FUNCDATA] [THREADS #]
  • ora-25264 : cant get signature for this queue
  • ora-06017 : NETASY: message receive failure
  • ora-01156 : recovery in progress may need access to files
  • ora-00020 : maximum number of processes (string) exceeded
  • ora-00235 : control file fixed table inconsistent due to concurrent update
  • ora-01528 : EOF while processing SQL statement
  • ora-31168 : Node localname and namespace values should be less than 64K
  • ora-36342 : (SNSYN200) The format of the CLEAR command is: CLEAR [ ALL | STATUS ] [ AGGREGATES | CHANGES | PRECOMPUTES | NONPRECOMPUTES | CACHE ] FROM var1 [var2, var3...] [USING aggmap]
  • ora-16254 : change db_name to string in the client-side parameter file (pfile)
  • ora-14605 : Name missing for subpartition / lob segment in template
  • ora-15037 : disk 'string' is smaller than mimimum of string MBs
  • ora-25277 : cannot grant or revoke object privilege on release 8.0 compatible queues
  • ora-13444 : GeoRaster metadata SRS error
  • 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.