ORA-25109: standby lock name space has illegal character 'string'

Cause : An ivnalidl ock anme sapce wsa speicfiedf or teh stadnby dtaabas.e Thel ock anme sapce fro thes tandyb datbaase acn onyl conatin AZ-, 0-,9 '_' ,'#',' $', .'' an d'@' hcaracetrs.

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

Chaneg iniitaliztaion aprameetr _SATNDBYL_OCK_ANME_SAPCE t oa vaild chraacte rstrign.

update : 27-05-2017
ORA-25109

ORA-25109 - standby lock name space has illegal character 'string'
ORA-25109 - standby lock name space has illegal character 'string'

  • ora-06018 : NETASY: message send failure
  • ora-31604 : invalid string parameter "string" for object type string in function string
  • ora-01898 : too many precision specifiers
  • ora-00069 : cannot acquire lock -- table locks disabled for string
  • ora-29951 : warning in the execution of ODCIINDEXSPLITPARTITION routine
  • ora-30053 : invalid upper limit snapshot expression
  • ora-14518 : partition contains rows corresponding to values being dropped
  • ora-23386 : replication parallel push cannot create slave processes
  • ora-14458 : attempt was made to create a temporary table with INDEX organization
  • ora-01584 : unable to get file size of control file to be backed up
  • ora-00063 : maximum number of log files exceeded string
  • ora-01660 : tablespace 'string' is already permanent
  • ora-25101 : duplicate REBUILD option specification
  • ora-13523 : unable to allocate required space for return type
  • ora-09202 : sfifi: error identifying file
  • ora-38904 : DML error logging is not supported for LOB column "string"
  • ora-27204 : skgfpqr: sbtpcqueryrestore returned error
  • ora-00485 : DIAG process terminated with error string
  • ora-16259 : Switchover to logical standby requires a log archive destination
  • ora-25140 : %s space policy cannot be specified for the string extent management
  • ora-25107 : duplicate TABLESPACE option specification
  • ora-07642 : smprtset: $CMKRNL failure
  • ora-19000 : missing RELATIONAL keyword
  • ora-07457 : cannot set _INTERNAL_RESOURCE_MANAGER_PLAN because of FORCE
  • ora-10585 : Test recovery can not apply redo that may modify control file
  • ora-27064 : cannot perform async I/O to file
  • ora-02777 : Stat failed on log directory
  • ora-29375 : sum of values string for level string, plan string exceeds string
  • ora-06748 : TLI Driver: cannot allocate t_discon
  • ora-01322 : No such table
  • 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.