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 : 23-06-2017

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

  • ora-19960 : Internal use only
  • ora-12528 : TNS:listener: all appropriate instances are blocking new connections
  • ora-27120 : unable to removed shared memory segment
  • ora-06305 : IPA: Illegal message type
  • ora-00824 : cannot set sga_target due to existing internal settings, see alert log for more information
  • ora-38439 : invalid operation "string"
  • ora-30438 : unable to access named pipe 'string'
  • ora-07222 : slspool: line printer spooler command exited with an error.
  • ora-38901 : column "string" of table "string" must be one of the first "number" columns
  • ora-12423 : invalid position specified
  • ora-14283 : UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-13109 : spatial table string exists
  • ora-23313 : object group "string"."string" is not mastered at string
  • ora-13440 : GeoRaster metadata compression type error
  • ora-24165 : invalid rule engine object privilege: string
  • ora-02068 : following severe error from stringstring
  • ora-01479 : last character in the buffer is not Null
  • ora-31606 : XML context number does not match any previously allocated context
  • ora-12990 : duplicate option specified
  • ora-13339 : LRS polygon clipping across multiple rings
  • ora-26093 : input data column size (number) exceeds the maximum input size (number)
  • ora-01250 : Error string occurred during termination of file header access
  • ora-32501 : Writing SGA to file failed
  • ora-32143 : Environment not specified
  • ora-01259 : unable to delete datafile string
  • ora-13025 : polygon does not close
  • ora-38860 : cannot FLASHBACK DATABASE during instantiation of a logical standby
  • ora-25400 : must replay fetch
  • ora-16767 : SQL Apply unexpectedly online
  • ora-24171 : creation properties are only for internal use
  • 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.