ORA-24384: Application context size is not initialized

Cause : The size of the application context must be initialized before populating each context element.

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

Issue OCIAttrSet with OCI_ATTR_CTX_SIZE to initialize context size

update : 29-05-2017
ORA-24384

ORA-24384 - Application context size is not initialized
ORA-24384 - Application context size is not initialized

  • ora-03207 : subpartitioned type must be specified for composite object
  • ora-00370 : potential deadlock during kcbchange operation
  • ora-19767 : missing TRACKING keyword
  • ora-01610 : recovery using the BACKUP CONTROLFILE option must be done
  • ora-19591 : backup aborted because job time exceeded duration time
  • ora-24776 : cannot start a new transaction
  • ora-12420 : required procedures and functions not in policy package "string"
  • ora-25142 : default storage clause specified twice
  • ora-30740 : cannot grant UNDER privilege on this object
  • ora-15067 : command or option incompatible with diskgroup redundancy
  • ora-22911 : duplicate storage specification for the nested table item
  • ora-25127 : RELY not allowed in NOT NULL constraint
  • ora-04067 : not executed, string does not exist
  • ora-36394 : (XSMXCLEA04) When using CLEAR on the AGGMAP workspace object, CACHE is the only valid directive.
  • ora-01453 : SET TRANSACTION must be first statement of transaction
  • ora-16105 : Logical Standby is already running in background
  • ora-19651 : cannot apply offline-range record to datafile string: SCN mismatch
  • ora-01347 : Supplemental log data no longer found
  • ora-26018 : Column string in table string does not exist
  • ora-13861 : Statistics aggregation for client identifier string is already enabled
  • ora-24783 : Cannot switch non-migratable transactions
  • ora-32405 : cannot alter tablespace for existing materialized view log
  • ora-19114 : error during parsing the XQuery expression: string
  • ora-24197 : JAVA stored procedure throws JAVA exceptions
  • ora-00488 : RBAL process terminated with error
  • ora-13644 : The user "string" is invalid.
  • ora-14026 : PARTITION and CLUSTER clauses are mutually exclusive
  • ora-03237 : Initial Extent of specified size cannot be allocated in tablespace (string)
  • ora-31004 : Length string of the BLOB in XDB$H_INDEX is below the minimum string
  • ora-23389 : obsolete procedure; drop objects and recreate using new master
  • 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.