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 : 17-08-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-25001 : cannot create this trigger type on views
  • ora-12737 : Instant Client Light: unsupported server character set string
  • ora-19361 : ONLINE option not allowed with this type of index
  • ora-07390 : sftopn: translate error, unable to translate file name.
  • ora-23322 : Privilege error accessing pipe
  • ora-26534 : collision: tranID number ignored and purged
  • ora-07803 : slpdtb: invalid packed decimal nibble
  • ora-39098 : Worker process received data objects while loading metadata. Invalid process order range is string..string
  • ora-27151 : buffer not large enough to hold process ID string
  • ora-00102 : network protocol string cannot be used by dispatchers
  • ora-12418 : user string not found
  • ora-24403 : error occured while trying to destroy the connection pool
  • ora-29660 : Unable to find the class defined in the EXTERNAL NAME clause
  • ora-04010 : the number of values to CACHE must be greater than 1
  • ora-09915 : Password encryption failed.
  • ora-12708 : error while loading create database NLS parameter string
  • ora-36977 : (XSRELGID17) The GROUPINGID command does not support hierarchies with more than 126 levels.
  • ora-00445 : background process "string" did not start after string seconds
  • ora-31671 : Worker process string had an unhandled exception.
  • ora-28137 : Invalid FGA audit Handler
  • ora-38702 : Cannot update flashback database log file header.
  • ora-27417 : BYWEEKNO clause is only supported when FREQ=YEARLY
  • ora-29307 : datafile string error, string
  • ora-32131 : bind data type cannot be changed
  • ora-32144 : Cannot perform operation on a null interval
  • ora-01929 : no privileges to GRANT
  • ora-31649 : Master process string violated startup protocol.
  • ora-31219 : DBMS_LDAP: PL/SQL - Invalid LDAP notypes.
  • ora-00236 : snapshot operation disallowed: mounted control file is a backup
  • ora-27088 : unable to get file status
  • 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.