ORA-19038: Invalid opertions on query context

Cause : SetMaxRows, SetSkipRows, SetRowTagName opertions are applied to a query context created from newContextFromHierarchy().

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

SetMaxRows, SetSkipRows, SetRowTagName opertions can not be applied to a query context created from newContextFromHierarchy().

update : 26-04-2017
ORA-19038

ORA-19038 - Invalid opertions on query context
ORA-19038 - Invalid opertions on query context

  • ora-02231 : missing or invalid option to ALTER DATABASE
  • ora-19911 : datafile string contains future changes at the incarnation boundary
  • ora-26717 : SCN limit reached
  • ora-37041 : (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out.
  • ora-12462 : undefined compartment string for policy string
  • ora-07431 : fork failed
  • ora-10644 : SYSTEM tablespace cannot be default temporary tablespace
  • ora-24386 : statement/server handle is in use when being freed
  • ora-01504 : database name 'string' does not match parameter db_name 'string'
  • ora-06604 : LU6.2 Driver: Unable to allocate session with remote LU
  • ora-38728 : Cannot FLASHBACK DATABASE to the future.
  • ora-01022 : database operation not supported in this configuration
  • ora-03263 : cannot drop the first file of tablespace string
  • ora-03240 : User's temporary tablespace same as tablespace being migrated
  • ora-27208 : syntax error in device PARMS - environment variable value missing
  • ora-09812 : Unable to get user clearance from connection
  • ora-07241 : slemrd: read error.
  • ora-25301 : Cannot enqueue or dequeue user buffered messages to a database with version lower than 10.2
  • ora-12442 : policy column "string" already used by an existing policy
  • ora-30990 : insufficient privileges to change owner of resource string
  • ora-12547 : TNS:lost contact
  • ora-32005 : error while parsing size specification [string]
  • ora-03280 : invalid DATAFILE filename specified
  • ora-16649 : database will open after Data Guard broker has evaluated Fast-Start Failover status
  • ora-04090 : 'string' specifies same table, event and trigger time as 'string'
  • ora-32009 : cannot reset the memory value for instance string from instance string
  • ora-32343 : let MVIEW engine know that it is IMPORT from 9i or earlier
  • ora-36832 : (XSLMGEN02) View token cannot be greater than 4000 bytes
  • ora-14505 : LOCAL option valid only for partitioned indexes
  • ora-23416 : table "string"."string" does not contain a primary key constraint
  • 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.