ORA-15124: ASM file name 'string' contains an invalid alias name

Cause : A file name was specified which did not contain a valid ASM alias name. The ASM alias name, if present, follows immediately after the diskgroup name, in place of the ASM file number. It must be preceeded by a slash, start with an alphabetic character, and consist of up to 48 characters which are alphabetic, numeric, or the characters '$', '_', '-', or '#". A space can separate two parts of an alias name.

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

Correct the file name specification.

update : 26-04-2017

ORA-15124 - ASM file name 'string' contains an invalid alias name
ORA-15124 - ASM file name 'string' contains an invalid alias name

  • ora-16146 : standby destination control file enqueue unavailable
  • ora-07268 : szguns: getpwuid error.
  • ora-19503 : cannot obtain information on device, name="string", type="string", parms="string"
  • ora-02069 : global_names parameter must be set to TRUE for this operation
  • ora-09209 : sftget: error reading from file
  • ora-32301 : object-relational materialized views must be primary key based
  • ora-28108 : circular security policies detected
  • ora-00356 : inconsistent lengths in change description
  • ora-09749 : pws_look_up: port lookup failure
  • ora-22165 : given index [string] must be in the range of [string] to [string]
  • ora-38794 : Flashback target time not in current incarnation
  • ora-12802 : parallel query server lost contact with coordinator
  • ora-15158 : rolling upgrade prevented by string
  • ora-07460 : cannot set the RESOURCE_MANAGER_PLAN parameter
  • ora-06519 : active autonomous transaction detected and rolled back
  • ora-01213 : MAXINSTANCES may not exceed string
  • ora-32815 : message system link string is referenced by a foreign queue
  • ora-28338 : cannot encrypt indexed column(s) with salt
  • ora-38604 : FI including & excluding cursor item-id type must match input cursor item-id type
  • ora-02778 : Name given for the log directory is invalid
  • ora-13024 : polygon has less than three segments
  • ora-10658 : Lob column to be shrunk is marked unused
  • ora-39070 : Unable to open the log file.
  • ora-14064 : Index with Unusable partition exists on unique/primary constraint key
  • ora-12414 : internal LBAC error: string Error: string
  • ora-07231 : slemcc: invalid file handle, seals do not match.
  • ora-10362 : simulate a write error to take a file offline
  • ora-24184 : transformation string.string already exists
  • ora-12007 : materialized view reuse parameters are inconsistent
  • ora-26678 : Streams capture process must be created first
  • 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.