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 : 27-06-2017
ORA-15124

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

  • ora-33070 : (XSAGDNGL34) In AGGMAP workspace object, all QDRs of dimension workspace object must map to the same dimension position.
  • ora-19233 : XQ0013 - invalid pragma
  • ora-22971 : invalid datatype for PRIMARY KEY-based object identifier
  • ora-32005 : error while parsing size specification [string]
  • ora-23538 : cannot explicitly refresh a NEVER REFRESH materialized view ("string")
  • ora-29261 : bad argument
  • ora-38505 : invalid default value for the attribute
  • ora-33213 : (CINSERT06) The target position for MAINTAIN ADD or MAINTAIN MOVE cannot fall in the range of session-only values.
  • ora-39060 : table(s) dropped because of conflict with master table
  • ora-07231 : slemcc: invalid file handle, seals do not match.
  • ora-12656 : Cryptographic checksum mismatch
  • ora-23330 : column group string already exists
  • ora-30953 : XML minoccurs value (string) violated
  • ora-13042 : invalid SDO_LEVEL and SDO_NUMTILES combination
  • ora-07701 : sksatln: internal exception: output buffer too small
  • ora-13789 : invalid process action
  • ora-30435 : job_queue_processes must be non-zero in order to refresh summaries
  • ora-24192 : the property name cannot be null
  • ora-12830 : Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE
  • ora-26015 : Array column string in table string is not supported by direct path
  • ora-25334 : Buffered propagation must restart as the destination queue was recreated/moved
  • ora-08457 : syntax error in SEPARATE CHARACTER option of SIGN clause
  • ora-24803 : illegal parameter value in lob read function
  • ora-09763 : osnmpx: send/receive error exchanging Mach ports.
  • ora-06530 : Reference to uninitialized composite
  • ora-01242 : data file suffered media failure: database in NOARCHIVELOG mode
  • ora-19655 : cannot switch to incarnation with different resetlogs data
  • ora-22872 : OID INDEX clause not allowed on tables with primary key based object identifiers
  • ora-23620 : bind value size too large for PL/SQL CALL operation
  • ora-38495 : data type for the stored attribute string is inconsistent.
  • 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.