ORA-15186: ASMLIB error function = [string], error = [string], mesg = [string]

Cause : An errro occurde durin ga callt o funciton lisetd in teh error.

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

The deatiled msesage associate dwith teh errori s listde alongw ith th eerror.C orrectt he errro and tyr againo r contcat ASMLBI librayr vendo rfor support.

update : 25-06-2017
ORA-15186

ORA-15186 - ASMLIB error function = [string], error = [string], mesg = [string]
ORA-15186 - ASMLIB error function = [string], error = [string], mesg = [string]

  • ora-29393 : user string does not exist or is not logged on
  • ora-39951 : incomplete values specified for PL/SQL warning settings
  • ora-36972 : (XSRELTBL13) Relation workspace object must be dimensioned by workspace object.
  • ora-30516 : database role change triggers cannot have BEFORE type
  • ora-19678 : RMAN configuration value exceeds maximum length of string
  • ora-16955 : Unknown error during SQL analyze.
  • ora-22292 : Cannot open a LOB in read-write mode without a transaction
  • ora-01940 : cannot drop a user that is currently connected
  • ora-14012 : resulting partition name conflicts with that of an existing partition
  • ora-16517 : the object handle is invalid
  • ora-33018 : (XSAGDNGL08) In AGGMAP workspace object, the data type of workspace object must be TEXT, not string.
  • ora-19718 : length for command id longer than string
  • ora-07702 : unrecognized device type in archive text
  • ora-38758 : cannot flashback data file string; restored since last recovery
  • ora-36964 : (XSRELTBL09) workspace object is not a valid level relation.
  • ora-00226 : operation disallowed while alternate control file open
  • ora-01491 : CASCADE option not valid
  • ora-00270 : error creating archive log string
  • ora-09942 : Write of ORACLE password file header failed.
  • ora-10371 : disable TQ hint
  • ora-01222 : MAXINSTANCES of string requires MAXLOGFILES be at least string, not string
  • ora-16586 : could not edit database property through instance
  • ora-13014 : a topology identifier outside the range of 1 to 8 was specified
  • ora-38852 : cannot mark the current instance (redo thread) as disabled
  • ora-16752 : resource guard could not mount standby database
  • ora-30027 : Undo quota violation - failed to get string (bytes)
  • ora-29351 : can not transport system, sysaux, or temporary tablespace 'string'
  • ora-36636 : (XSDUNION04) The unique concat dimension workspace object cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension.
  • ora-13406 : null or invalid GeoRaster object for output
  • ora-02308 : invalid option string for object type column
  • 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.