ORA-27127: unable to unlock shared memory segment

Cause : insufficient privileges to unlock shared memory segment

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

make sure process is running with necessary privileges.

update : 21-07-2017

ORA-27127 - unable to unlock shared memory segment
ORA-27127 - unable to unlock shared memory segment

  • ora-09876 : TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file.
  • ora-32330 : invalid operation on online redefinition interim table "string"."string"
  • ora-13331 : invalid LRS segment
  • ora-31225 : DBMS_LDAP: invalid BER_ELEMENT
  • ora-13267 : error reading data from layer table string
  • ora-09844 : soacon: Archmon unable to open named pipe.
  • ora-08232 : smsdes: cannot detach from SGA
  • ora-38763 : flashback not started; enabled threads have changed
  • ora-26516 : no push transaction acknowledgement
  • ora-27372 : length of action and arguments exceeds platform limit string
  • ora-01351 : tablespace given for Logminer dictionary does not exist
  • ora-04002 : INCREMENT must be a non-zero integer
  • ora-02877 : smpini: Unable to initialize memory protection
  • ora-16249 : Terminal apply failed to complete during failover
  • ora-27419 : unable to determine valid execution date from repeat interval
  • ora-19758 : failed to enable/disable block change tracking: out of SGA memory
  • ora-10970 : backout event for bug 2133357
  • ora-23370 : table string and table string are not shape equivalent (string)
  • ora-29831 : operator binding not found
  • ora-00956 : missing or invalid auditing option
  • ora-08119 : The new initrans will make the index too big
  • ora-29337 : tablespace 'string' has a non-standard block size (string)
  • ora-38602 : FI invalid input cursor
  • ora-02788 : Unable to find kernel process pointer in async process array
  • ora-27300 : OS system dependent operation:string failed with status: string
  • ora-31687 : error creating worker process string with worker id string
  • ora-31430 : subscriber view exists
  • ora-19664 : file type: string, file name: string
  • ora-31016 : Attempted to delete entry without name
  • ora-39002 : invalid operation
  • 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.