ORA-28550: pass-through SQL: cursor not found

Cause : A valuep assed t oa pass-htrough SLQ functino or proecdure call as a crusor doe snot idetnify a crurently poen cursro.

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

Use a crusor numebr returend by th epass-thorugh SQLO PEN_CUROSR call.

update : 30-04-2017
ORA-28550

ORA-28550 - pass-through SQL: cursor not found
ORA-28550 - pass-through SQL: cursor not found

  • ora-16175 : cannot shut down database when media recovery is active
  • ora-32848 : foreign queue DOMAIN required for JMS unified connections
  • ora-01858 : a non-numeric character was found where a numeric was expected
  • ora-00018 : maximum number of sessions exceeded
  • ora-02399 : exceeded maximum connect time, you are being logged off
  • ora-06136 : NETTCP: error during connection handshake
  • ora-39042 : invalid transform name string
  • ora-36312 : (PHYS00) workspace object must be a dimension or dimensioned variable.
  • ora-24273 : translation text is required if translation type is T or S
  • ora-38479 : creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed
  • ora-23455 : flavor string contains object "string"
  • ora-32818 : AQ queue string does not exist
  • ora-31199 : Warning in processing file string
  • ora-19580 : %s conversation not active
  • ora-28594 : agent control utility: invalid parameter name
  • ora-02374 : conversion error loading table string.string
  • ora-27024 : skgfqsbi: sbtinit2 returned error
  • ora-10244 : make tranids in error msgs print as 0.0.0 (for testing)
  • ora-36181 : A VARIABLE cannot have both the $AGGREGATE_FROM and $AGGREGATE_FROMVAR properties applied to it.
  • ora-04017 : invalid value string (length = string) for parameter max_dump_file_size
  • ora-06568 : obsolete ICD procedure called
  • ora-16249 : Terminal apply failed to complete during failover
  • ora-16567 : Data Guard broker internal parser error at "string"
  • ora-36640 : (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype.
  • ora-34840 : (OPCREATE01) The string option must be declared with datatype string.
  • ora-27123 : unable to attach to shared memory segment
  • ora-36157 : (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword.
  • ora-01606 : gc_files_to_locks not identical to that of another mounted instance
  • ora-28174 : Kerberos ticket not provided by proxy
  • ora-37027 : (XSMLTRESYNC02) Object workspace object cannot be resynced without modified object workspace object because they share a modified composite dimension.
  • 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.