SERVICE_NAME not generated in the connect string when using the Direct Connect method (4226934)

When a user uses the direct method to connect to a database, the connection string generated always defaults to SID and never creates the Service Name parameter.

Steps to recreate the issue:

1. Launch Toad and open a new connection window.
2. Click on the Direct Tab and enter in Host | Port number | Service Name information of a database and select the SERVICE NAME radio button.
3. Fill in just the UserSchema name in and leave the password field blank.
4. Click on Connect and the Oracle Logon window appears.
5. In the Database field, the connection string is created on the fly; go to the end of the string and look for "(CONNECT_DATA=(SID=xxxxxxxx)))"
Notice that even though you have selected the Service_Name parameter that the connection screen always defaults to SID.
6. Try connecting and notice the user will receive the error: "ORA-12505: TNS:listener could not resolve SID given in connect descriptor".

Note: If you have filled in the password along with everything else in Direct tab you automatically get the ORA-12505 error.

WORKAROUND 1:
(Note: This workaround is only good for Toad versions 9.1 and 9.5, please use workaround 2 or upgrade Toad)

1. Fill in all the UserSchema name, Host, Port number, and Service Name information of a database, but leave the password field blank.
2. Click on Connect and the Oracle Logon screen appears.
3. In the Database field, go to the end of the connection string and locate the "(CONNECT_DATA=(SID=xxxxxxxx)))" at the end.
Note: (xxxxx is the service name you have filled in the previous screen).
4. Replace the SID parameter with the word "SERVICE_NAME" so it looks like this "(CONNECT_DATA=(SERVICE_NAME=xxxxxxxx)))"
5. Type in your password and click OK.

WORKAROUND 2:

1. Add a connection entry to the TNSnames.ora file or use the TNS Editor to add the connection entry for your Service Name.

STATUS:

Waiting for fix to be released in a future version of Toad for Oracle.