# Toad fails to execute query using SQL\*Plus

**URL:** <https://forums.toadworld.com/t/toad-fails-to-execute-query-using-sql-plus/39864>\
**Category:** Toad for Oracle - Beta\
**Created:** [August 17, 2017, 6:22am UTC](https://forums.toadworld.com/t/toad-fails-to-execute-query-using-sql-plus/39864 "2017-08-17T06:22:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kornelis.abe](https://avatars.discourse-cdn.com/v4/letter/k/59ef9b/32.png) [@kornelis.abe](https://forums.toadworld.com/u/kornelis.abe)\
**Post date:** [August 17, 2017, 6:22am UTC](https://forums.toadworld.com/t/toad-fails-to-execute-query-using-sql-plus/39864/1 "2017-08-17T06:22:58Z")

</div>

All,

This relates to Toad for Oracle, Beta 12.12.0.12

When I have Toad execute a query using the “editor” --\> “Execute query via SQL\*Plus” that normally works flawlessly.

Unfortunately, for one specific schema it fails to do so; it does bring up a DOS-box for SQL\*Plus, but then it fails:  
 ![20170817 sqlplus failure.png](https://global.discourse-cdn.com/quest/original/2X/f/f05ebd485dac9f3655fd1227d97d0af45a2dcdff.png)

So I tried to connect manually. Same result.  
Realizing the password contains an @-sign, I then retried with the password enclosed in “double quotation marks”.

That worked!

So, could it be Toad is supplying the password to SQL\*Plus without enclosing quotation marks?

If so, could it be fixed, please?

# Kind regards, Abe Kornelis

---

<div class="post-metadata">

**Author:** ![mstaszew](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/mstaszew/32/23_2.png) [@mstaszew](https://forums.toadworld.com/u/mstaszew)\
**Post date:** [August 17, 2017, 7:06am UTC](https://forums.toadworld.com/t/toad-fails-to-execute-query-using-sql-plus/39864/2 "2017-08-17T07:06:25Z")

</div>

Abe, It’s like you’re sitting behind me watching me work. 🙂 I just ran into this yesterday in some things I’m doing.

Oracle has a doc on passwords… [http://docs.oracle.com/database/121/DBSEG/guidelines.htm#DBSEG10005](http://docs.oracle.com/database/121/DBSEG/guidelines.htm#DBSEG10005)

…and Ask Tom has a post on the same… [https://asktom.oracle.com/pls/apex/f?p=100:11:::NO:RP:P11\_QUESTION\_ID:9533940800346284735](https://asktom.oracle.com/pls/apex/f?p=100:11:::NO:RP:P11_QUESTION_ID:9533940800346284735)

It seems like Toad should be wrapping any password that doesn’t fit this… "_can contain only alphanumeric characters from your database character set and the underscore (\_), dollar sign ($), and pound sign (#)."_

I’ll take a look.

Thanks,

Michael

---

<div class="post-metadata">

**Author:** ![kornelis.abe](https://avatars.discourse-cdn.com/v4/letter/k/59ef9b/32.png) [@kornelis.abe](https://forums.toadworld.com/u/kornelis.abe)\
**Post date:** [August 17, 2017, 11:38pm UTC](https://forums.toadworld.com/t/toad-fails-to-execute-query-using-sql-plus/39864/3 "2017-08-17T23:38:57Z")

</div>

Michael,

I’m sorry - I cannot read thoughts. (My wife regrets this, but to most this is a great relief 😉

Anyway, for ease of coding you might opt to enclose any pwd in “” marks…

# Kind regards, Abe

---

<div class="post-metadata">

**Author:** ![mstaszew](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/mstaszew/32/23_2.png) [@mstaszew](https://forums.toadworld.com/u/mstaszew)\
**Post date:** [August 18, 2017, 11:04am UTC](https://forums.toadworld.com/t/toad-fails-to-execute-query-using-sql-plus/39864/4 "2017-08-18T11:04:28Z")

</div>

This is fixed for next beta. I had considered just wrapping all passwords, but the routine used for generating the connect string is used elsewhere and produces strings that are user facing. Some may not take kindly to seeing unnecessary double quotes.

Michael

---

<div class="post-metadata">

**Author:** ![kornelis.abe](https://avatars.discourse-cdn.com/v4/letter/k/59ef9b/32.png) [@kornelis.abe](https://forums.toadworld.com/u/kornelis.abe)\
**Post date:** [August 20, 2017, 10:39pm UTC](https://forums.toadworld.com/t/toad-fails-to-execute-query-using-sql-plus/39864/5 "2017-08-20T22:39:41Z")

</div>

Agreed. Thanks for the fix.

# Abe