ORA-15120: ASM file name 'string' does not begin with the ASM prefix character

Cause : Aifeln ma eaw spscefiei dotA MSw ihhcd din tob geniw ti hht eSA Mrpfexic ahartcre( ucrrnelt y+')' .SA Msuset ehp erif xotd tereiment ah t aifels epicifacitnoi snif ca tnaA MSf li.e

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

oCrrce tht eifeln ma epsceficitaoi.n

update : 19-08-2017

ORA-15120 - ASM file name 'string' does not begin with the ASM prefix character
ORA-15120 - ASM file name 'string' does not begin with the ASM prefix character

  • ora-16102 : remote information is not available on the specified primary
  • ora-02432 : cannot enable primary key - primary key not defined for table
  • ora-12560 : TNS:protocol adapter error
  • ora-13642 : The specified string string provided for string cannot be converted to a date. The acceptable date format is string.
  • ora-12216 : TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA
  • ora-22926 : specified trim length is greater than current LOB value's length
  • ora-39105 : Master process string failed during startup. Master error:
  • ora-06035 : NETDNT: connect failed, insufficient resources
  • ora-07801 : slbtpd: invalid exponent
  • ora-14070 : option may be specified only for partitioned indices or with REBUILD
  • ora-23419 : regenerate replication support before resuming master activity
  • ora-34841 : (OPCREATE02) The string option must be declared with the READONLY attribute.
  • ora-16545 : unable to get response
  • ora-19581 : no files have been named
  • ora-02053 : transaction string committed, some remote DBs may be in-doubt
  • ora-23611 : tablespace "string" has more than one data file
  • ora-00276 : CHANGE keyword specified but no change number given
  • ora-02310 : exceeded maximum number of allowable columns in table
  • ora-12077 : temporary updatable materialized view log does not exist
  • ora-02467 : Column referenced in expression not found in cluster definition
  • ora-13904 : The file has been dropped and recreated during the procedure call.
  • ora-00371 : not enough shared pool memory, should be atleast string bytes
  • ora-30500 : database open triggers and server error triggers cannot have BEFORE type
  • ora-06042 : NETDNT: message receive failure
  • ora-00701 : object necessary for warmstarting database cannot be altered
  • ora-32592 : all columns in log group can not be no log columns
  • ora-16031 : parameter string destination string exceeds string character limit
  • ora-06950 : No error
  • ora-14400 : inserted partition key does not map to any partition
  • ora-38776 : cannot begin flashback generation - flash recovery area is disabled
  • 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.