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

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

  • ora-22315 : type "string" does not contain a map or order function
  • ora-07472 : snclrd: open error when opening sgadef.dbf file.
  • ora-12714 : invalid national character set specified
  • ora-08314 : sllfcf: Error closing file
  • ora-19620 : %s is not of string type
  • ora-29896 : Length of PARAMETER string longer than string characters
  • ora-30772 : opaque types do not have default constructors
  • ora-38787 : Creating the first guaranteed restore point requires mount mode when flashback database is off.
  • ora-00481 : LMON process terminated with error
  • ora-19556 : required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred
  • ora-25218 : enqueue failed, delay must be zero for queue string.string
  • ora-24312 : illegal parameters specified for allocating user memory
  • ora-28106 : input value for argument #string is not valid
  • ora-30188 : reserved for future use
  • ora-17619 : max number of processes using I/O slaves in a instance reached
  • ora-07717 : sksaalo: error allocating memory
  • ora-01968 : Only specify RESETLOGS or NORESETLOGS once
  • ora-34021 : (MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE workspace object.
  • ora-01589 : must use RESETLOGS or NORESETLOGS option for database open
  • ora-22931 : MOVE of nested table to a different tablespace not supported
  • ora-02178 : correct syntax is: SET TRANSACTION READ { ONLY | WRITE }
  • ora-06917 : CMX: error in data read (too many bytes read)
  • ora-10854 : Sets poll count used for AQ listen code under RAC
  • ora-09817 : Write to audit file failed.
  • ora-12227 : TNS:syntax error
  • ora-27365 : job has been notified to stop, but failed to do so immediately
  • ora-32813 : propagation schedule string already exists
  • ora-25243 : CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string
  • ora-14196 : Specified index cannot be used to enforce the constraint.
  • ora-32638 : Non unique addressing in MODEL dimensions
  • 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.