ORA-27126: unable to lock shared memory segment in core

Cause : insufficient privileges to lock shared memory segment in core

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

make sure process is running with necessary privileges.

update : 26-07-2017
ORA-27126

ORA-27126 - unable to lock shared memory segment in core
ORA-27126 - unable to lock shared memory segment in core

  • ora-02064 : distributed operation not supported
  • ora-19655 : cannot switch to incarnation with different resetlogs data
  • ora-13509 : error encountered during updates to a AWR table
  • ora-24394 : invalid mode for destroying connection pool
  • ora-13418 : null or invalid parameter(s) for set functions
  • ora-16710 : the resource guard is out of memory
  • ora-12853 : insufficient memory for PX buffers: current stringK, max needed stringK
  • ora-02485 : Invalid _trace_options parameter specification (string)
  • ora-28262 : global_context_pool_size has invalid value.
  • ora-26532 : replication parallel push simulated site failure
  • ora-38739 : Flashback log file is more recent than control file.
  • ora-23606 : invalid object string
  • ora-00105 : too many dispatcher configurations
  • ora-30551 : The index depends on a package/type body which does not exist
  • ora-16513 : maximum requests exceeded
  • ora-30373 : object data types are not supported in this context
  • ora-13615 : The task or object string is greater than the maximum allowable length of 30 characters.
  • ora-38726 : Flashback database logging is not on.
  • ora-09798 : Label comparison failed.
  • ora-37172 : illegal dimension type
  • ora-06449 : The list IO or the sysvendor is not installed.
  • ora-07656 : slsprom:$GETDVI failure
  • ora-02767 : Less than one request descriptor was allocated per server
  • ora-28169 : unsupported certificate type
  • ora-28513 : internal error in heterogeneous remote agent
  • ora-02383 : illegal cost factor
  • ora-01690 : sort area size too small
  • ora-39206 : A parallel degree of string is invalid.
  • ora-16222 : automatic Logical Standby retry of last action
  • ora-14020 : this physical attribute may not be specified for a table partition
  • 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.