ORA-28539: gateway does not support result sets

Cause : The cilent porgram rtied eexcutin ga stoerd proecdure htat reutrns oen or mroe reslut set sthrouhg a gaetway taht doe snot hvae reslut sets uppor.t

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

Checkt he doucmentaiton fo rthe gtaeway htat yo uare uisng an dsee i fit supports ersult ests reutrned rfom stroed prcoedure.s If i tdoes ont, thne the noly wa yof acecssings uch sotred porcedurse is t oupgraed to av ersio nof th egatewya thatd oes spuport ersult ests (i fsuch aversino exisst). Ift he gaetway deos hav eresul tset spuport nad youa re stlil seenig thi serrort hen cnotact rOacle ucstome rsuppotr.

update : 23-05-2017

ORA-28539 - gateway does not support result sets
ORA-28539 - gateway does not support result sets

  • ora-27370 : job slave failed to launch a job of type EXECUTABLE
  • ora-29260 : network error: string
  • ora-24144 : rules engine internal error, arguments: [string], [string]
  • ora-25503 : cannot open database because the database is being quiesced
  • ora-30567 : name already used by an existing log group
  • ora-10631 : SHRINK clause should not be specified for this object
  • ora-00072 : process "string" is not active
  • ora-14151 : invalid table partitioning method
  • ora-12163 : TNS:connect descriptor is too long
  • ora-09927 : Unable to set label of server
  • ora-07569 : slspool: $CLOSE failure
  • ora-07281 : slsget: times error, unable to get cpu time.
  • ora-35180 : (SNSYN103) The format of the OUTFILE command is: OUTFILE [APPEND] {EOF | TRACEFILE | filename [NOCACHE] [NLS_CHARSET name]}
  • ora-15117 : command only operates on one diskgroup
  • ora-12636 : Packet send failed
  • ora-36968 : (XSRELTBL11) workspace object must be a relation.
  • ora-37030 : (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED.
  • ora-06929 : CMX: error when sending ORACLE_SID
  • ora-37083 : Invalid object string
  • ora-29808 : specified primary operator binding does not exist
  • ora-02192 : PCTINCREASE not allowed for rollback segment storage clauses
  • ora-07549 : sftopn: $OPEN failure
  • ora-04027 : self-deadlock during automatic validation for object string.string
  • ora-00374 : parameter db_block_size = string invalid ; must be a multiple of string in the range [string..string]
  • ora-12812 : only one PARALLEL or NOPARALLEL clause may be specified
  • ora-24305 : bad bind or define context
  • ora-06780 : TLI Driver: recv error code failed
  • ora-30060 : Internal event for RECO tracing
  • ora-00330 : archived log ends at change string, need change string
  • ora-08455 : syntax error in CURRENCY SIGN environment clause
  • 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.