ORA-28595: Extproc agent : Invalid DLL Path

Cause : The path of DLL supplied for the extproc execution is invalid.

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

Check if the DLL path is set properly using the EXTPROC_DLLS environment variable. errors 28600 - 28620 are reserved for bitmap indexes

update : 29-06-2017
ORA-28595

ORA-28595 - Extproc agent : Invalid DLL Path
ORA-28595 - Extproc agent : Invalid DLL Path

  • ora-07486 : scg_get_inst: cannot convert(get) instance number lock.
  • ora-32151 : Environment not specified
  • ora-19503 : cannot obtain information on device, name="string", type="string", parms="string"
  • ora-10902 : disable seghdr conversion for ro operation
  • ora-01235 : END BACKUP failed for string file(s) and succeeded for string
  • ora-07487 : scg_init_lm: cannot create lock manager instance.
  • ora-07514 : scgcan: $deq unexpected return while canceling lock
  • ora-01144 : File size (string blocks) exceeds maximum of string blocks
  • ora-00126 : connection refused; invalid duplicity
  • ora-29954 : domain index partition is marked LOADING/FAILED/UNUSABLE
  • ora-13628 : Insufficient privileges to access the task belonging to the specified user
  • ora-38479 : creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed
  • ora-31415 : change set string does not exist
  • ora-12415 : A column of another datatype exists on the specified table
  • ora-29972 : user does not have privilege to change/ create registration
  • ora-30055 : NULL snapshot expression not allowed here
  • ora-32828 : Messaging Gateway agent must be running
  • ora-12520 : TNS:listener could not find available handler for requested type of server
  • ora-29930 : COMPUTE ANCILLARY DATA specified without the INDEX CONTEXT clause
  • ora-22331 : cannot alter an incomplete type
  • ora-24816 : Expanded non LONG bind data supplied after actual LONG or LOB column
  • ora-38492 : invalid ALTER INDEX parameters clause "string"
  • ora-02156 : invalid TEMPORARY tablespace identifier
  • ora-07451 : slskstat: unable to obtain load information.
  • ora-24375 : Cannot use V6 syntax when talking to a V8 server
  • ora-14512 : cannot perform operation on a clustered object
  • ora-12067 : empty refresh groups are not allowed
  • ora-22958 : This operation is not allowed in check constraints or triggers
  • ora-07488 : scgrcl: lock manager not initialized.
  • ora-25467 : table alias not specified
  • 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.