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-06-2017
ORA-25109

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

  • ora-39064 : unable to write to the log file
  • ora-13951 : MMON sub-action time limit exceeded
  • ora-12432 : LBAC error: string
  • ora-10661 : Invalid option specified
  • ora-24170 : %s.string is created by AQ, cannot be dropped directly
  • ora-40289 : duplicate attributes provided for data mining function
  • ora-13234 : failed to access R-tree-index table [string]
  • ora-07849 : sllfsk: $GET failure
  • ora-32828 : Messaging Gateway agent must be running
  • ora-37108 : (XSVPART08) workspace object has an AGGCOUNT, but workspace object does not.
  • ora-02434 : cannot enable unique(string) - unique key not defined for table
  • ora-13138 : could not determine name of object string
  • ora-13011 : value is out of range
  • ora-28181 : proxy 'string' failed to enable one or more of the specified initial roles for client 'string'
  • ora-01917 : user or role 'string' does not exist
  • ora-22885 : cannot get REF to a non-persistent object
  • ora-13605 : The specified task or object string does not exist for the current user.
  • ora-02062 : distributed recovery received DBID string, expected string
  • ora-36767 : (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it.
  • ora-12210 : TNS:error in finding Navigator data
  • ora-38502 : invalid XML tag: string
  • ora-38460 : filtering based on datatype "string" not supported for XML Tags
  • ora-31076 : required attribute "string" not specified
  • ora-23601 : PROPAGATION_NAME string does not exist
  • ora-12077 : temporary updatable materialized view log does not exist
  • ora-23501 : refresh template cannot be instantiated for database with compatibilty equal to or less than 8.0
  • ora-32731 : Another Parallel Oradebug session is in progress
  • ora-33918 : (MAKEDCL33) You cannot define a surrogate of dimension workspace object because it is a string.
  • ora-39753 : unsupported use of subquery in PARTITIONED OUTER JOIN condition
  • ora-02722 : osnpui: cannot send break message to orapop
  • 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.