ORA-17612: Failed to discover Oracle Disk Manager library, return value string

Cause : Discovery of the odm library by calling odm_discover() failed

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

Contact your storage vendor who has provided the ODM library or call Oracle Support

update : 19-08-2017
ORA-17612

ORA-17612 - Failed to discover Oracle Disk Manager library, return value string
ORA-17612 - Failed to discover Oracle Disk Manager library, return value string

  • ora-29548 : Java system class reported: string
  • ora-01614 : instance string (thread string) is busy - cannot enable
  • ora-14036 : partition bound value too large for column
  • ora-31035 : Could not bind locked resource to path string/string
  • ora-22275 : invalid LOB locator specified
  • ora-31423 : change table string does not contain column string
  • ora-32518 : cannot wait for ORADEBUG command completion (waited number ms for process string); total wait time exceeds number ms
  • ora-13408 : invalid blockSize storage parameter
  • ora-30047 : Internal event for kti tracing
  • ora-26671 : maximum number of STREAMS processes exceeded
  • ora-28529 : invalid or missing parameter in Net8 service name definition
  • ora-01215 : enabled thread string is missing after CREATE CONTROLFILE
  • ora-12546 : TNS:permission denied
  • ora-01939 : only the ADMIN OPTION can be specified
  • ora-13600 : error encountered in Advisor string
  • ora-02331 : cannot create constraint on column of datatype string
  • ora-19607 : %s is an active control file
  • ora-30488 : argument should be a function of expressions in PARTITION BY
  • ora-27002 : function called with invalid device structure
  • ora-13703 : The snapshot pair [string, string] for database_id string and instance_id string are not found in the current repository.
  • ora-14038 : GLOBAL partitioned index must be prefixed
  • ora-39169 : Local version of string cannot work with remote version of string.
  • ora-02484 : Invalid _trace_buffers parameter specification (string)
  • ora-13158 : Oracle object string does not exist
  • ora-02428 : could not add foreign key reference
  • ora-31217 : DBMS_LDAP: PL/SQL - Invalid LDAP newparent.
  • ora-37185 : length of string (string) exceeds maximum (string)
  • ora-30959 : The indexed column is not stored in CLOB.
  • ora-00119 : invalid specification for system parameter string
  • ora-01121 : cannot rename database file string - file is in use or recovery
  • 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.