Toad Adds extract character (non-ASCII) when loading


I just upgraded my Toad for Oracle version. Everything seems fine EXCEPT

When I load a schema from the dialog box, it will add an extra character to the schema name. The character is an extended ASCII character whose source I cannot ascertain. I deleted the schema from the list and tried to add it anew and it did add it, again with extra characters.

Loading a schema from the pull-down once I am in works as expected. I am not sure what is causing this and it is getting in the way.

Can anyone assist?

Thank you.

Are you using Oracle client version

We have a known issue with it. Please use Oracle client version,, or 18.anything. I do not recommend any 19c client, as they have a memory leak with LOBs.

To be clear - Toad has no problems with Oracle server version or 19c. Only client version or 19c.

Thank you for the prompt reponse.

Yes. That is the version that I am using.

However, if the choice is between disrupting the organization by requiring an update to the Oracle client or not dealing with a minor version upgrade in TOAD, we cannot upgrade TOAD until or if this issue is addressed. I am sure you understand.

Is there any effort to resolve this issue?

Your help is appreciated.

Yes, we hope to have it resolved by the next version.

Unfortunately, it is a bug in the current version of our data access component. I've reported it to them here . They have confirmed the issue and will hopefully they will have it fixed soon so we can have it fixed in the next Toad version. You are welcome to comment on that thread so that maybe they will give it a higher priority.

The prior version of our data access component had a problem with CLOBs that was impossible to work around, so I felt like it was necessary for us to switch to this new version despite the problem (which has a workaround).

However, if the choice is between disrupting the organization by requiring an update to the Oracle client...

I'm not trying to be a smart-alec, but how is updating an Oracle client any more disruptive than updating Toad?

Fair Question. Not everyone needs the features that are being rolled out in 14.2 or have come across any of the issues that necessitated the update from 14.1 to 14.2. However, minor as it is, the regression work that is part and parcel of upgrading to a new Oracle client would not be warranted just to satisfy the use of 14.2.

I upgrade to be aware of what is new, useful or exciting and am old school. Others don't see the necessity.


TOAD is up to version 15.x (2021R3).

But the issue in connecting with my instance using Oracle client is still around. I still cannot upgrade my Oracle client.

Any progress on this issue?

Thank you.



It is fixed in the 15.1 beta which you can get here

Thank you very much.

As to your question, TOAD is only one tool that is at our disposal. For everything else, including custom applications, we are bound to use the same Oracle client version that is in place at the client we support. They are still using the version that is only my machine and I cannot change that as it would bring "uncertainty" into the equation. We have suggested upgrading but priorities and/or inertia get in the way.

And, of course, when I mention this issue, they have no problem recommending that I just stay with the TOAD version that works. Not an all too uncommon response, I'm afraid.

Thank you for your help.

Yeah, sorry I asked again. I realized it was already asked and answered so I edited my reply, but you already saw the question, I guess.

I hope you can use the beta. If you have any problems with it, please let me know. We'll do our best to resolve them quickly.

No problem. I do appreciate your assistance.

The beta works fine. A special thanks for that. Hopefully it will be released out of beta before the expiration runs out.


A new beta is released (almost) every Monday. We don't let it expire before another one, or the official release, is available.