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 : 30-05-2017

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

  • ora-28581 : protocol error while executing recursive external procedure
  • ora-32639 : Aggregate functions on reference MODELs are not allowed
  • ora-29367 : object string does not exist
  • ora-26082 : load of overlapping segments on table string.string is not allowed
  • ora-00108 : failed to set up dispatcher to accept connection asynchronously
  • ora-09301 : osncon: local kernel only supported in standard mode
  • ora-12014 : table 'string' does not contain a primary key constraint
  • ora-23448 : duplicate user parameter value
  • ora-14311 : Expecting VALUES LESS THAN or AT clause
  • ora-39143 : dump file "string" may be an original export dump file
  • ora-10931 : trace name context forever
  • ora-19812 : cannot use string without DB_RECOVERY_FILE_DEST
  • ora-39954 : DEFERRED is required for this system parameter
  • ora-26507 : null master connection
  • ora-19932 : control file is not clone or standby
  • ora-29329 : Table not of type XMLType
  • ora-29975 : Cannot register a query in the middle of an active transaction
  • ora-16181 : SGA specified for Logical Standby is too large
  • ora-09817 : Write to audit file failed.
  • ora-29852 : keyword IS is missing
  • ora-01201 : file string header failed to write correctly
  • ora-38783 : Instance recovery required.
  • ora-13152 : invalid HHCODE type
  • ora-16774 : error stopping Redo Apply
  • ora-12453 : label string already exists
  • ora-27162 : thread creation failed
  • ora-09880 : sstasfre/sstasdel: shmdt error, unable to detach tas write page
  • ora-13869 : Instance-wide SQL tracing on instance string is already enabled
  • ora-30188 : reserved for future use
  • ora-19263 : XQ0043 - duplicate namespace prefix 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.