# Toad Data Point Pro Edition 6.x - crash, close -out and slow performance issues

**URL:** <https://forums.toadworld.com/t/toad-data-point-pro-edition-6-x-crash-close-out-and-slow-performance-issues/58370>\
**Category:** Toad Data Point & Toad Intelligence Central\
**Created:** [October 24, 2023, 10:41pm UTC](https://forums.toadworld.com/t/toad-data-point-pro-edition-6-x-crash-close-out-and-slow-performance-issues/58370 "2023-10-24T22:41:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![joe.zhou](https://avatars.discourse-cdn.com/v4/letter/j/eb8c5e/32.png) [@joe.zhou](https://forums.toadworld.com/u/joe.zhou)\
**Post date:** [October 24, 2023, 10:41pm UTC](https://forums.toadworld.com/t/toad-data-point-pro-edition-6-x-crash-close-out-and-slow-performance-issues/58370/1 "2023-10-24T22:41:44Z")

</div>

I have searched the forum but could not find definitive answers.

My Toad Data Point 5.4 Base Edition worked fine with Cloudera Impala connection without many issues.

Two weeks ago, I upgraded to TDP Pro Edition 6.0.5 and run into crash issues with common table expression queries. After hours of investigations and discussions with colleague who had same issues. We managed to replicate crashes 100% time under two scenarios for Cloudera ODBC driver.

1. CTE with 'limit' clause. Crash 100% time

sample code:

with cte\_test as ( select \* from impala.test\_tbl)  
select \* from cte\_test limit 10;

Removing limit clause works fine.

1. CTE with 'order by' clause with numeric values (order by 1, 2) instead of columns names (order by col1, col2) after 'group by'. Crash 100%.

with cte\_test as ( select \* from impala.test\_tbl)  
select column1, count(\*) from cte\_test  
group by 1  
order by 1;

removing 'order by' statement runs fine.

rearranging code below runs fine.

select \* from (  
with cte\_test as ( select \* from impala.test\_tbl)  
select column1, count(\*) from cte\_test  
group by 1  
) order by 1;

Replacing order by numeric values with column names runs fine too.

with cte\_test as ( select \* from impala.test\_tbl)  
select column1, count(\*) from cte\_test  
group by column1  
order by column1;

I run CTE with limit clause and order by numeric values clauses all the time in TDP 5.4. Never experienced crashed as much as in 6.0.5.

Before I figured what caused crashes in 6.05, I tried 6.1.0 but ran into extremely slow performance. Simple 'show tables' in db took 3-4 mins as opposed to just one sec in 6.0.5 or 5.4. The results were returned a few rows per second. I found another post on the forum and replied with my experience. So far, no clear solution.

---

<div class="post-metadata">

**Author:** ![Gary.Jerep](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/gary.jerep/32/205_2.png) [@Gary.Jerep](https://forums.toadworld.com/u/Gary.Jerep)\
**Post date:** [October 24, 2023, 11:05pm UTC](https://forums.toadworld.com/t/toad-data-point-pro-edition-6-x-crash-close-out-and-slow-performance-issues/58370/2 "2023-10-24T23:05:37Z")

</div>

Raising awareness with Quest Dev... stay tuned...

---

<div class="post-metadata">

**Author:** ![joe.zhou](https://avatars.discourse-cdn.com/v4/letter/j/eb8c5e/32.png) [@joe.zhou](https://forums.toadworld.com/u/joe.zhou)\
**Post date:** [October 25, 2023, 7:35pm UTC](https://forums.toadworld.com/t/toad-data-point-pro-edition-6-x-crash-close-out-and-slow-performance-issues/58370/3 "2023-10-25T19:35:57Z")

</div>

Thanks. Forgot to mention. Just confirmed by my colleagues that CTE query crashes happen for TDP 5.6 as well. Teammates with older versions (5.3 and 5.4) are not experiencing crashes.