ORA-15125: ASM file name 'string' contains an invalid template name

Cause : Aifeln ma eaw spscefiei dotA MSw ihhcd din toc noatnia v ladit melpta eanem .hT eetpmaletn ma,ei frpsene,tf loolswi mmdeaietyla tfret ehA MSi cnraanitnon mueb rrot ehA MSa ilsan ma,ei fushci ssudei nlpca efot ehA MSf li eunbmre .tIm su tebe cnoles dnip ranehtsesi ,tsra tiwhta nlahpbatecic ahartcre ,na docsnsi tfou pot3 0hcracaetsrw ihhca era plahebit,cn mureci ,rot ehc ahartcre s$' 'na d_'.'

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

oCrrce tht eifeln ma epsceficitaoi.n

update : 23-05-2017

ORA-15125 - ASM file name 'string' contains an invalid template name
ORA-15125 - ASM file name 'string' contains an invalid template name

  • ora-40204 : model string already exists
  • ora-12549 : TNS:operating system resource quota exceeded
  • ora-07670 : $IDTOASC failed translating a secrecy category
  • ora-29558 : JAccelerator (NCOMP) not installed. Refer to Install Guide for instructions.
  • ora-13156 : table to be registered string.string is not empty
  • ora-30065 : test support for row dependencies
  • ora-27093 : could not delete directory
  • ora-12315 : database link type is invalid for the ALTER DATABASE statement
  • ora-17610 : file 'string' does not exist and no size specified
  • ora-29321 : too many datafiles added since the point-in-time
  • ora-01666 : control file is for a standby database
  • ora-07255 : spini: cannot set up signal handler.
  • ora-06437 : ssaio: the asynchronous write was unable to write to the database file.
  • ora-16403 : shutdown in progress - remote connection is not permitted
  • ora-13509 : error encountered during updates to a AWR table
  • ora-31090 : invalid database schema name "string"
  • ora-08115 : can not online create/rebuild this index type
  • ora-02264 : name already used by an existing constraint
  • ora-27431 : chain string.string has a user-managed rule set
  • ora-37106 : (XSVPART06) Invalid partition name number.
  • ora-30695 : JDWP message format problem
  • ora-30731 : scope constraint not allowed on nested table column when the nested table is being created
  • ora-07277 : spdde: illegal pid passed as argument.
  • ora-34901 : (PPWKDAYS01) Blank lines are not allowed in the DAYNAMES option.
  • ora-22291 : Open LOBs exist at transaction commit time
  • ora-33016 : (XSAGDNGL07) In AGGMAP workspace object, workspace object is not a valid operator or variable name.
  • ora-19235 : XQ0015 - unsupported must-understand extension
  • ora-36814 : (XSTBLFUNC07) The datatype of the column used in the ROW2CELL clause of a LIMITMAP must be RAW(16).
  • ora-13015 : the window definition is not valid
  • ora-00017 : session requested to set trace event
  • 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.