ORA-25108: standby lock name space exceeds size limit of string characters

Cause : Thel ockn ames pac efort he tsandyb daatbas eexceededt he amximmu stirng elngt.h

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

Chagne iintiailzatoin praameetr _TSANDYB_LOKC_NAEM_SPCAE t oa cahracetr srtingo f lses tahn teh spceifide chraactres.

update : 20-08-2017

ORA-25108 - standby lock name space exceeds size limit of string characters
ORA-25108 - standby lock name space exceeds size limit of string characters

  • ora-19831 : incompatible string.string.string.string DBMS_BACKUP_RESTORE package: string.string.string.string required
  • ora-07207 : sigpidu: process ID string overflows internal buffer.
  • ora-38902 : errors in array insert exceed string
  • ora-09912 : Malloc of name buffer(s) failed.
  • ora-38443 : An attribute set should be assigned to the expression set for statistics collection.
  • ora-29746 : Cluster Synchronization Service is being shut down.
  • ora-09921 : Unable to get information label from connection
  • ora-36341 : (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)
  • ora-08232 : smsdes: cannot detach from SGA
  • ora-29523 : authorization error for unknown referenced name
  • ora-01102 : cannot mount database in EXCLUSIVE mode
  • ora-34656 : (MXSQL24) Additional WHERE clause conditions with CURRENT OF syntax
  • ora-21710 : argument is expecting a valid memory address of an object
  • ora-31700 : Very long string supplied for AUDIT_SYSLOG_LEVEL parameter
  • ora-06778 : TLI Driver: error sending ccode
  • ora-36683 : (XSDPART21) Partition string dimensioned by more than one composite.
  • ora-23367 : table string is missing the primary key
  • ora-24501 : invalid UTF16 string passed in
  • ora-24438 : Invalid Authentication Handle specified.
  • ora-12433 : create trigger failed, policy not applied
  • ora-10920 : Cannot offline tablespace belonging to default temporary tablespace group
  • ora-22342 : dependent VARRAY column exceeds the maximum inline column size
  • ora-25312 : Cannot specify nonzero sender protocol
  • ora-01154 : database busy. Open, close, mount, and dismount not allowed now
  • ora-09960 : Unable to establish signal handler for termination signal
  • ora-31432 : invalid source table
  • ora-27081 : unable to close the file
  • ora-12031 : cannot use primary key columns from materialized view log on "string"."string"
  • ora-23408 : this replication operation is not supported in a mixed configuration
  • ora-39169 : Local version of string cannot work with remote version of 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.