Taod Data Point Connection error

Toad Data Point & Toad Intelligence Central
1

hello I am trying to connect to an Oracle database using Toad Data Point v 6.3. It works for my production connection but when trying to connect to lower environments i am getting the below error:

System.ArithmeticException
Invalid bytes count
Stack Trace:
at Devart.Data.Oracle.by.a(List`1 A_0, SshOptions A_1, SslOptions A_2, Boolean A_3)
at Devart.Data.Oracle.cz.a(ea A_0, Boolean A_1)
at Devart.Data.Oracle.cz.a(ea A_0, b1 A_1)
at Devart.Data.Oracle.OracleInternalConnection..ctor(ea connectionOptions, OracleInternalConnection proxyConnection)
at Devart.Data.Oracle.ei.a(z A_0, Object A_1, DbConnectionBase A_2)
at Devart.Common.DbConnectionFactory.a(DbConnectionBase A_0, z A_1)
at Devart.Common.DbConnectionFactory.b(DbConnectionBase A_0)
at Devart.Common.DbConnectionClosed.Open(DbConnectionBase outerConnection)
at Devart.Common.DbConnectionBase.Open()
at Devart.Data.Oracle.OracleConnection.Open()
at Quest.Toad.Db.Connection.OpenConnection(IDbConnection connection)
at Quest.Toad.Oracle.OracleToadConnection.OpenConnection(IDbConnection connection)
at Quest.Toad.Db.Connection.AllocConnection()
at Quest.Toad.Db.Connection.Connect(Boolean notify)
at Quest.Toad.Db.Provider.BackgroundConnector.CreateBackgroundConnection()

I am using a direct connection (not oracle client). This connection has also previously worked but recently started throwing this error and i cannot figure out why.

Any suggestions?

2

I am a Toad for Oracle developer, but I happened to see this post. This is the same as a bug we had in Toad for Oracle.

See here for cause and workarounds.

That's a long thread so I'll summarize:

  • Oracle was updated (or you are connecting to a new version)
  • You have one of the following in server-side sqlnet.ora
SQLNET.CRYPTO_CHECKSUM_CLIENT=REQUIRED
SQLNET.CRYPTO_CHECKSUM_SERVER=REQUIRED
SQLNET.ENCRYPTION_SERVER=REQUIRED
  • You are connecting without an Oracle client.

Change any of these, and it will work.

I'm sure the TDP folks will have it fixed soon. Note to TDP folks: Update your Devart components. :slight_smile:

1 Like
3

@JohnDorlon -
Has this been ever fixed on TDP? I am also facing same error for one of database I am trying to connect. Here is full stack of error -

We don't have liberty to change the parameter on server end as mentioned earlier on this forum, wondering if Quest/Toad Datapoint has fixed this error or can give urgent Beta with fix so my work doesnt get hampered.

I am using Toad Datapoint 6.3.0.28375
Oracle Client 19.20.0
Oracle Instant Client - 23_5

System.ArithmeticException
Invalid bytes count
Stack Trace:
at Devart.Data.Oracle.by.a(List`1 A_0, SshOptions A_1, SslOptions A_2, Boolean A_3)
at Devart.Data.Oracle.cz.a(ea A_0, Boolean A_1)
at Devart.Data.Oracle.cz.a(ea A_0, b1 A_1)
at Devart.Data.Oracle.OracleInternalConnection..ctor(ea connectionOptions, OracleInternalConnection proxyConnection)
at Devart.Data.Oracle.ei.a(z A_0, Object A_1, DbConnectionBase A_2)
at Devart.Common.DbConnectionFactory.a(DbConnectionBase A_0, z A_1)
at Devart.Common.DbConnectionFactory.b(DbConnectionBase A_0)
at Devart.Common.DbConnectionClosed.Open(DbConnectionBase outerConnection)
at Devart.Common.DbConnectionBase.Open()
at Devart.Data.Oracle.OracleConnection.Open()
at Quest.Toad.Db.Connection.OpenConnection(IDbConnection connection)
at Quest.Toad.Oracle.OracleToadConnection.OpenConnection(IDbConnection connection)
at Quest.Toad.Db.Connection.AllocConnection()
at Quest.Toad.Db.Connection.Connect(Boolean notify)
at Quest.Toad.Db.Provider.BackgroundConnector.CreateBackgroundConnection()

Tried setting following on my laptop (client) with and without it both gives same error.
SQLNET.CRYPTO_CHECKSUM_TYPES_CLIENT = (SHA256,SHA1)
SQLNET.ENCRYPTION_CLIENT = required
SQLNET.CRYPTO_CHECKSUM_CLIENT = required
SQLNET.ENCRYPTION_TYPES_CLIENT = (AES256,AES192,AES128)

4

Did you ever got fix for you?

5

No it never was resolved

6

yeah it's 3 month and for premium license products, I hope support should be quick, especially it looks the bug has been figured out and fixed in Toad for Oracle.

Curious - any workaround? or are you using all together different tool to connect to DB now?

7

Yes I am using SQL Developer tool for now as Could not connect using Toad.

8

@nnkalathia I am an Toad for Oracle developer, not a Toad Data Point developer. I know nothing about their bug fix schedule. I only wanted to share with them that we experienced the same bug in Toad for Oracle, and tell them how we fixed it.

If you can use an Oracle client with TDP, the problem will not occur. It only happens when you connect without an Oracle client.

9

@JohnDorlon - Thanks it worked finally with tnsnames.ora.
@william.lillicrapp - you might want to try that, only direct connection is causing that bug hit. with tnsentry it is working fine.

Thanks both of you for helping out.