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 : 20-09-2017
ORA-27126

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

  • ora-30005 : missing or invalid WAIT interval
  • ora-39962 : invalid parameter for PLSQL_CCFLAGS
  • ora-08467 : error converting Oracle number to string
  • ora-12910 : cannot specify temporary tablespace as default tablespace
  • ora-00482 : LMD* process terminated with error
  • ora-06541 : PL/SQL: compilation error - compilation aborted
  • ora-35095 : (QFSVNS01) One or more imported values of fixed-width dimension workspace object have been truncated.
  • ora-24787 : remote cursors must be closed before a call completes
  • ora-14012 : resulting partition name conflicts with that of an existing partition
  • ora-29846 : cannot create a local domain index on a string partitioned table
  • ora-27209 : syntax error in device PARMS - unknown keyword or missing =
  • ora-16133 : Datafile string has incorrect terminal recovery stamp.
  • ora-38854 : cannot mark instance string (redo thread string) as disabled
  • ora-15095 : reached maximum ASM file size (string GB)
  • ora-36686 : (XSDPART24) Value number is not in partition number.
  • ora-21560 : argument string is null, invalid, or out of range
  • ora-30104 : 'string' is not a legal integer for 'string'
  • ora-00077 : dump string is not valid
  • ora-26708 : remote DDL not supported by STREAMS : dblink string
  • ora-16958 : DML statements running parallel are not supported for test execute.
  • ora-14177 : STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table
  • ora-07224 : sfnfy: failed to obtain file size limit; errno = string.
  • ora-26046 : REF column string expects scoped table name string; user passed in string.
  • ora-02274 : duplicate referential constraint specifications
  • ora-09834 : snyGetPortSet: failed to collect info on a port.
  • ora-10943 : trace name context forever
  • ora-04063 : %s has errors
  • ora-16516 : the current state is invalid for the attempted operation
  • ora-16519 : the resource handle is invalid
  • ora-00071 : process number must be between 1 and string
  • 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.