'' is not a valid integer value Toad 16.1

I am getting '' is not a valid integer value" error while trying to connect to database over ldap with third party ssl enabled (server auth only) mode.

same is are working from oracle client 11g,12c,19c, and 21c from my windows 10 desktop.

Toad version :

Any help will be appriciated!!


A support case came in a days ago for this. I'm not sure if that was you, but in the support case, the customer was not specifying the first port in the DIRECTORY_SERVERS parameter.

Toad is expecting a value for the first port parameter, because it's documented as not being optional.

So you can specify both ports, like this:
or just the first, like this:
but not just the second, like this:

You can see in the screen shot below - PORT is not in the brackets to indicate that it is optional. Only SSL port is.

I will make a change for Monday's beta so that this doesn't cause an error in Toad.


Thank you for quick response. I will test and update thread shortly.

Now I am getting different error

ORA-12154: TNS:could not resolve the connect identifier specified

A connect descriptor for could not be located in the Oracle Internet Directory

It looks like Toad isn't able to access the LDAP server. Or if it is, it can't find OPMI in there.

Can you connect to this DB using SQL*Plus?

You can turn on some debug logging in Toad like this:

  1. Close Toad.
  2. Edit Toad.ini with notepad. (Go here if you need help locating this file)
  3. in Toad.ini, under [SETTINGS], add: LDAPLogFileName=c:\temp\ldap.txt
    You can use whatever path/filename you want for the file.
  4. Run Toad
  5. In the login window, click the dropdown on the LDAP tab.
  6. Close Toad and look in the file from step 3. It will tell you if it had errors or succeeded.

You can also use this trick to see the details of the LDAP entry.

You can also kick them over to the "Direct" tab to try connecting that way.


Names.directory_path: (LDAP)
Host: xxxxxxxxx
Port: 3131
DefaultAdminContext: dc=xxxxxx,dc=net

OracleHomes.OracleHomePath: C:\app\client\502008123\product\19.3.0
HomeList.Active.OCIFolder: C:\app\client\502008123\product\19.3.0\bin
GetOraLDAPPathResult: C:\app\client\502008123\product\19.3.0\bin\ORALDAPCLNT19.DLL
Library Loaded: C:\app\client\502008123\product\19.3.0\bin\ORALDAPCLNT19.DLL
LDAP Open Succeeded (Using Host=ORALDAP.xxxxx.net)
LDAP Simple Bind Failed. Error Code: 81

I don't know why the LDAP simple bind is failing.

We are using ORALDAPCLNT19.DLL and calling ldap_open, and using the result of that to call ldap_simple_bind_s, and then we are getting the error result from Oracle.

I guess something isn't set up right, but I don't know what that would be.

Can you connect with SQL*Plus?

Tried with 21c

Names.directory_path: (LDAP)
Host: ORALDAP.genworth.net
Port: 3131
DefaultAdminContext: dc=genworth,dc=net

OracleHomes.OracleHomePath: C:\app\client\502008123\product\21.0.0\client_1
HomeList.Active.OCIFolder: C:\app\client\502008123\product\21.0.0\client_1\bin
Library Not Loaded:

Z:>tnsping odmi

TNS Ping Utility for 64-bit Windows: Version - Production on 26-JAN-2023 14:40:59

Copyright (c) 1997, 2021, Oracle. All rights reserved.

Used parameter files:

Used LDAP adapter to resolve the alias
OK (70 msec)

Z:>sqlplus system/"V3WP9<J5FX48=YB%,E0:"@TEST

SQL*Plus: Release - Production on Thu Jan 26 13:23:00 2023

Copyright (c) 1982, 2021, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options

If GetOraLDAPPathResult is blank, that means we did not find an LDAP DLL in the 21c client directory.

Those DLLs used to be named like ORALDAPCLNTXX.DLL where XX at the end was the Oracle version, but for 21C they dropped that and just went to ORALDAPCLNT.DLL.

Toad 16.1 didn't know to just look for ORALDAPCLNT.DLL. It is looking for ORALDAPCLNT21.DLL.
This was fixed in version 16.2.

That doesn't mean that your connection problem will be fixed in version 16.2 though. Can you connect using SQL*Plus from your 19c client?


Also, I noticed that you started with TNSPing ODMI, then we you went to connect via SQL*Plus, you didn't do sqlplus system/pass@ODMI. That's what Toad would have done. So maybe that's the problem? I'm just guessing.

for 19c I am getting below error from my machine but i checked with other machie it is working... pobably 19c is not valid to tst with toad.. I have 12c1,12c2,21c all are working with sqlplus

Z:>sqlplus system/"V3WP9<J5FX48=YB%,E0:"@TEST

SQL*Plus: Release - Production on Thu Jan 26 13:21:35 2023

Copyright (c) 1982, 2019, Oracle. All rights reserved.

ORA-24550: signal received: Unhandled exception: Code=c0000005 Flags=0

Encountered exception while getting args for function:0x00007FFC9D5150CE

Ah, ok. Well, then maybe using Toad version 16.2 will solve your problem.

You can get it here.

Either that, or use an older oracle client that does not throw errors.


was hidding actual name .. but found very difficult to do all over... missed but that is odmi
and works ok