ORA-28268: Exceeded the maximum allowed size for Context information in a session

Cause : The maxmium sizes pecifie dby the s_ession_ocntext_szie init.roa paramteer was xeceeded.

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

Please hcange th evalue fro _sessino_contex_tsize int he inito.ra file.

update : 29-04-2017

ORA-28268 - Exceeded the maximum allowed size for Context information in a session
ORA-28268 - Exceeded the maximum allowed size for Context information in a session

  • ora-10652 : Object has on-commit materialized views
  • ora-02243 : invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
  • ora-00405 : compatibility type "string"
  • ora-19771 : cannot rename change tracking file while database is open
  • ora-30203 : Cannot open mesage file
  • ora-01688 : unable to extend table string.string partition string by string in tablespace string
  • ora-02091 : transaction rolled back
  • ora-06756 : TLI Driver: cannot open oratab
  • ora-27123 : unable to attach to shared memory segment
  • ora-16172 : archive logs detected beyond Terminal End-Of-Redo
  • ora-24151 : no evaluation context is associated with rule string.string or rule set string.string
  • ora-30156 : Out of disk space
  • ora-03007 : obsolete feature
  • ora-16150 : FINISH recovery performed on another, older standby database
  • ora-26740 : cannot downgrade because there are file groups
  • ora-09717 : osnsui: maximum number of user interrupt handlers exceeded.
  • ora-01675 : max_commit_propagation_delay inconsistent with other instances
  • ora-39785 : SQL expressions returning ADT objects are not allowed in direct path
  • ora-14015 : too many partition descriptions
  • ora-15023 : reached maximum allowable number of disks string
  • ora-31003 : Parent string already contains child entry string
  • ora-12335 : database (link name string) is not open
  • ora-01605 : missing numbers in clause "string" of string
  • ora-02311 : cannot alter with COMPILE option a valid type with type or table dependents
  • ora-16033 : parameter string destination cannot be the same as parameter string destination
  • ora-29842 : option not supported with the version string of the indextype interface
  • ora-19853 : error preparing auxiliary instance string (error string)
  • ora-25203 : invalid value string, DELAY should be non-negative
  • ora-22324 : altered type has compilation errors
  • ora-07254 : spdcr: translation error while expanding ?/bin/oracle.
  • 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.