ORA-19036: Invalid query result set in newContextFromHierarchy()

Cause : The result set of the query used in the newContextFromHierarchy() does not have the same property as the result set generated by a CONNECT BY query.

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

Make sure the query used in newContextFromHierarchy() is a CONNECT BY query or the query returns the result set have the same property as the result set generated by a CONNECT BY query.

update : 24-08-2017
ORA-19036

ORA-19036 - Invalid query result set in newContextFromHierarchy()
ORA-19036 - Invalid query result set in newContextFromHierarchy()

  • ora-02059 : ORA-2PC-CRASH-TEST-string in commit comment
  • ora-39056 : invalid log file specification.
  • ora-00346 : log member marked as STALE
  • ora-29913 : error in executing string callout
  • ora-28175 : incorrect certificate type
  • ora-15037 : disk 'string' is smaller than mimimum of string MBs
  • ora-00094 : %s requires an integer value
  • ora-32315 : REFRESH FAST of "string"."string" unsupported after mixed DML and Direct Load
  • ora-27205 : skgfpcn: sbtpccancel returned error
  • ora-16120 : dependencies being computed for transaction at SCN string
  • ora-19271 : XP0051 - invalid atomic type definition
  • ora-26035 : Error attempting to encrypt or decrypt column
  • ora-10634 : Segment is already being shrunk
  • ora-08266 : create_ora_addr: cannot register name in nameserver
  • ora-24129 : table name string does not start with string prefix
  • ora-28173 : certificate not provided by proxy
  • ora-30085 : syntax error was found in overlaps predicate
  • ora-31523 : could not find change source string for CDC change set string
  • ora-26511 : master table 'string.string' not found
  • ora-26512 : error pushing transaction to def$error
  • ora-32016 : parameter "string" cannot be updated in SPFILE
  • ora-02342 : replacement type has compilation errors
  • ora-25221 : enqueue failed, signature specified queue not supporting non-repudiation
  • ora-16242 : Processing logfile (thread# string, sequence# string)
  • ora-26510 : materialized view name: 'string' is greater than max. allowed length of string bytes
  • ora-22618 : attribute is a BAD NULL in the image handle
  • ora-37131 : (XSCCOMP06) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because the OPERATOR string is not supported for bases of a COMPRESSED COMPOSITE.
  • ora-13751 : "SQL Tuning Set" "string" does not exist for owner "string" or user "string" does not have permission to access the "SQL Tuning Set".
  • ora-09360 : Windows 3.1 Two-Task driver unable to allocate context area
  • ora-15176 : file 'string' already has an alias associated with it
  • 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.