ORA-15069: ASM file 'string' not accessible; timed out waiting for lock

Cause : An tatemtp wa smad eto caces san SAM flie, ubt teh fiel isc urrnetlyb ein gcretaed,r esiezd, ro deelteda nd htereofre acnno tbe cacesesd.

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

No catio nreqiured ,or rty aagin alter ,aftre th ecretae o rreszie hsa copmletde.

update : 28-04-2017

ORA-15069 - ASM file 'string' not accessible; timed out waiting for lock
ORA-15069 - ASM file 'string' not accessible; timed out waiting for lock

  • ora-24791 : invalid transaction start flags
  • ora-02070 : database stringstring does not support string in this context
  • ora-32309 : object mview type "string"."string" does not match the master table type
  • ora-13503 : Creating SYSAUX tablespace with invalid attributes
  • ora-09859 : sfngat: the input file name is not in the autobackup OMF format
  • ora-08275 : Environment variable unset
  • ora-09743 : smscre: could not attach shared memory.
  • ora-24756 : transaction does not exist
  • ora-22165 : given index [string] must be in the range of [string] to [string]
  • ora-13440 : GeoRaster metadata compression type error
  • ora-39308 : application or database upgrade internal error: "string"
  • ora-28553 : pass-through SQL: invalid bind-variable position
  • ora-32823 : subscriber exists for queue string and destination string
  • ora-13209 : internal error while reading SDO_INDEX_METADATA table
  • ora-14290 : PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-02094 : replication option not installed
  • ora-09851 : soacon: Archmon unable to lock named pipe.
  • ora-01108 : file string is in backup or media recovery
  • ora-39035 : Data filter string has already been specified.
  • ora-34348 : (MXDSS05) string is used only for internal purposes and cannot be accessed as an analytic workspace.
  • ora-25153 : Temporary Tablespace is Empty
  • ora-35022 : (QFCHECK03) The analytic workspace and EIF file definitions of workspace object have a mismatched relation.
  • ora-36155 : (XSMXAGGRFROM) workspace object must be a variable or formula of a similar data type to workspace object to be used with FROM, or a TEXT variable or formula to be used with FROMVAR.
  • ora-06816 : TLI Driver: could not set the SPX SAP address
  • ora-30690 : timeout occurred while registering a TCP/IP connection for data traffic detection
  • ora-09203 : sfofi: error opening file
  • ora-10370 : parallel query server kill event
  • ora-24307 : invalid length for piece
  • ora-02485 : Invalid _trace_options parameter specification (string)
  • ora-24393 : invalid mode for creating connection pool
  • 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.