ORA-15126: component within ASM file name 'string' exceeds maximum length

Cause : Teh amxmiu miednitfeirl egnt ho f3 0cahrcatresw a secxedee dfro hted iksgoru pnmae ,tmepalt enmae ,o raila snmaef iledw ihti nteh SAMf iel anm.e

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

Crorcett h eflien aem pseicfciaito.n

update : 26-09-2017

ORA-15126 - component within ASM file name 'string' exceeds maximum length
ORA-15126 - component within ASM file name 'string' exceeds maximum length

  • ora-15205 : requested mirror side unavailable
  • ora-36923 : (XSVPMVTOPART04) workspace object is not a LIST or RANGE PARTITION TEMPLATE.
  • ora-30680 : debugger connection handshake failed
  • ora-25237 : navigation option used out of sequence
  • ora-09858 : sfngat: the input file name is not in the OMF format
  • ora-30654 : missing DEFAULT keyword
  • ora-07621 : smscre: illegal redo block size
  • ora-01022 : database operation not supported in this configuration
  • ora-19861 : additional backup pieces cannot be validated in this conversation
  • ora-25132 : UNIQUE constraint (string.string) disabled and validated in ALTER TABLE EXCHANGE PARTITION
  • ora-24167 : incompatible rule engine objects, cannot downgrade
  • ora-39054 : missing or invalid definition of the SQL output file.
  • ora-29887 : cannot support row movement if domain index defined on table
  • ora-38452 : Expression Filter index name may not be longer than 25 characters
  • ora-09270 : szalloc: error allocating memory for security
  • ora-24805 : LOB type mismatch
  • ora-02039 : bind by value is not allowed for array type
  • ora-19670 : file string already being restored
  • ora-14067 : duplicate TABLESPACE_NUMBER specification
  • ora-31654 : unable to convert file or volume size as specified to a number
  • ora-06778 : TLI Driver: error sending ccode
  • ora-23344 : constraint (string.string) does not exist
  • ora-16643 : unable to determine location of broker configuration files
  • ora-06140 : NETTCP: no such user
  • ora-12805 : parallel query server died unexpectedly
  • ora-34279 : (MXDCL37) CONCAT can only be used when defining a DIMENSION.
  • ora-16194 : Modifying DB_UNIQUE_NAME requires SID='*' qualifier
  • ora-28293 : No matched Kerberos Principal found in any user entry
  • ora-24146 : rule string.string already exists
  • ora-37105 : (XSVPART05) Only variables dimensioned by a CONCAT PARTITION TEMPLATE can have string partitions.
  • 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.