ORA-24336: invalid result set descriptor

Cause : The result set descriptor should have valid data fetched into it before it can be converted to a statement handle

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

Fetch valid data into the descriptor before attempting to convert it into a statement handle

update : 22-07-2017

ORA-24336 - invalid result set descriptor
ORA-24336 - invalid result set descriptor

  • ora-02377 : invalid resource limit
  • ora-14459 : missing GLOBAL keyword
  • ora-02396 : exceeded maximum idle time, please connect again
  • ora-27458 : A program of type PLSQL_BLOCK cannot have any arguments.
  • ora-14642 : Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
  • ora-23514 : invalid or incorrect number of arguments
  • ora-12982 : cannot drop column from a nested table
  • ora-32001 : write to SPFILE requested but no SPFILE specified at startup
  • ora-13525 : error with computing space usage for sysaux occupant
  • ora-02404 : specified plan table not found
  • ora-26040 : Data block was loaded using the NOLOGGING option
  • ora-31482 : invalid option for non-distributed Hotlog change source
  • ora-06001 : NETASY: port set-up failure
  • ora-27205 : skgfpcn: sbtpccancel returned error
  • ora-02176 : invalid option for CREATE ROLLBACK SEGMENT
  • ora-12732 : invalid interval value in regular expression
  • ora-23497 : repgroup name cannot be null
  • ora-28051 : the account is locked
  • ora-31162 : element or attribute "string" has no SQLType specified
  • ora-15124 : ASM file name 'string' contains an invalid alias name
  • ora-12003 : materialized view "string"."string" does not exist
  • ora-19562 : file string is empty
  • ora-07487 : scg_init_lm: cannot create lock manager instance.
  • ora-01229 : data file string is inconsistent with logs
  • ora-16138 : end of log stream not received from primary
  • ora-01082 : 'row_locking = always' requires the transaction processing option
  • ora-00448 : normal completion of background process
  • ora-01158 : database string already mounted
  • ora-25461 : rule set not specified
  • ora-03239 : maxextents (string) reached in LOB segment string.string subpartition string
  • 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.