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 : 26-05-2017
ORA-27127

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

  • ora-28106 : input value for argument #string is not valid
  • ora-32517 : cannot issue ORADEBUG command (waited number ms for process string); total wait time exceeds number ms
  • ora-02144 : no option specified for ALTER CLUSTER
  • ora-37011 : (XSACQUIRE_LOCKED) Object workspace object is locked by another user.
  • ora-16238 : attempt to use version 9 log
  • ora-01583 : unable to get block size of control file to be backed up
  • ora-19250 : XQ0030 - too many values to validate expression
  • ora-22952 : Nested Table equality requires a map method on the element ADT
  • ora-22615 : attribute is not a collection
  • ora-12462 : undefined compartment string for policy string
  • ora-10642 : Found rollback segments in dictionary managed tablespaces
  • ora-16556 : error message is in XML already
  • ora-24792 : cannot mix services in a single global transaction
  • ora-23326 : object group "string"."string" is quiesced
  • ora-13612 : The recommendation action string,string is not valid for task string.
  • ora-07203 : sltln: attempt to translate a long environment variable.
  • ora-25004 : WHEN clause is not allowed in INSTEAD OF triggers
  • ora-14261 : partition bound may not be specified when adding this Hash partition
  • ora-02454 : Number of hash keys per block (string) exceeds maximum of string
  • ora-31207 : DBMS_LDAP: PL/SQL - Invalid LDAP search time value.
  • ora-26682 : invalid value for publication_on
  • ora-30360 : REF not supported with query rewrite
  • ora-25437 : duplicate table value for table alias: string
  • ora-12053 : this is not a valid nested materialized view
  • ora-16627 : operation disallowed since no standby databases would remain to support protection mode
  • ora-31605 : the following was returned from string in routine string: LPX-number: string
  • ora-29277 : invalid SMTP operation
  • ora-06814 : TLI Driver: the SPX device file could not be opened
  • ora-16093 : dependent archive log destination is not LGWR-enabled
  • ora-07584 : spdcr: invalid value for ORA_sid_(proc_)PQL$_item
  • 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.