describe_table does not work

[stringkm]

My describe_table command returns "Table not found." in des-sci on easyaccess 1.4.3. find_tables and SQL select statements work for a given table. I have also tried refreshing the metadata and putting in the table owner like this describe_table owner.table_name. Unfortunately, none of these seems to do the trick. Thank you in advance for checking into this!

[kadrlica]

Which table are you trying to describe?

[stringkm]

It hasn't been working for pretty much any table. But here's a few I've tried:

It may be an issue related to my account. I'm not sure.

[kadrlica]

Hmmm, I just tried the first one Y3A2_MOF and got the full table information. What version of easyaccess are you using?

[stringkm]

I'm using version 1.4.3 on Ubuntu 14.04.

[kadrlica]

I just tried with 1.4.3 on SL6. Any ideas @mgckind?

[mgckind]

Is not the first time I've heard about this weird issue, but I haven't been able to reproduce it on any of my machines unfortunately. My guess is that there is an error throwing which make it look like there is no description. is not on easyaccess side, not Oracle. I'll take a look

[mgckind]

@stringkm what version of cx_Oracle are you using?
python -c "import cx_Oracle; print(cx_Oracle.__version__)"

[stringkm]

Hi Matias! I have version 5.3.

[mgckind]

@stringkm Can you try these commands please? (I'm trying to at least find the error)

import easyaccess as ea
con=ea.connect()
qcom = "select comments from all_tab_comments atc where atc.table_name = 'Y3_GOLD_2_2'"
comment_table = con.query_results(qcom)[0][0]

[stringkm]

Here's what I got.

[mgckind]

Thanks, so that's the issue. Now, it's a weird error. I'll dig up bit more.

[stringkm]

Thanks Matias!

[mgckind]

Maybe @madamow can help?

[madamow]

@stringkm could you check if this issue is gone after change in prefetch? Just to be sure.

[stringkm]

Describe_table runs without error. So glad it is working again! Thank you!

[mgckind]

are you kidding me? I completely ruled out that option since the describe table isn't returning large number of rows.... I usually recommend changing this parameter for getting a good number of rows in a normal query... still is a mistery the memory leak, but this is good for me