ORA-15002: parameter LOCK_NAME_SPACE exceeds limit of string characters

Cause : The LOCK_NAME_SPACE initialization parameter contained a value that is too long.

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

Correct the LOCK_NAME_SPACE initialization parameter.

update : 23-07-2017
ORA-15002

ORA-15002 - parameter LOCK_NAME_SPACE exceeds limit of string characters
ORA-15002 - parameter LOCK_NAME_SPACE exceeds limit of string characters

  • ora-32623 : incorrect use of MODEL PRESENT* functions
  • ora-06605 : LU6.2 Driver: Unexpected line turnaround
  • ora-24905 : invalid recepient protocol attribute passed into OCI call
  • ora-01616 : instance string (thread string) is open - cannot disable
  • ora-29814 : expecting USING or DEFAULT keyword
  • ora-16955 : Unknown error during SQL analyze.
  • ora-16084 : an apply engine is already running
  • ora-36341 : (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)
  • ora-09839 : removeCallback: callback port is not in the callback set.
  • ora-03216 : Tablespace/Segment Verification cannot proceed
  • ora-27054 : NFS file system where the file is created or resides is not mounted with correct options
  • ora-24431 : Statement does not exist in the cache
  • ora-12068 : updatable mview log for mview "string"."string" does not exist
  • ora-27467 : invalid datatype for string value
  • ora-09764 : osnmop: access error on oracle executable
  • ora-02452 : invalid HASHKEYS option value
  • ora-16409 : Archive log switchover reference number mismatch
  • ora-36964 : (XSRELTBL09) workspace object is not a valid level relation.
  • ora-02841 : Server died on start up
  • ora-22600 : encountered 8.0.2 (Beta) VARRAY data that cannot be processed
  • ora-19577 : file string is MISSING
  • ora-04069 : cannot drop or replace a library with table dependents
  • ora-02042 : too many distributed transactions
  • ora-16406 : Primary and standby database software version mismatch
  • ora-06951 : Operating system call error
  • ora-31087 : insufficient privileges to delete schema "string"
  • ora-09791 : slembdf: translation error, unable to translate error file name.
  • ora-38906 : insert into DML Error Logging table "string" failed
  • ora-24902 : invalid subscription name or name-length in subscription handle
  • ora-16086 : standby database does not contain available standby log files
  • 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.