Insufficient memory to parse request during Optimizer phase.

Visit Teradata.com

Home

Guidelines

Member List

Welcome Guest ( Login | Register )

This online forum is for user-to-user discussions of Teradata products, and is not an official customer support channel for Teradata. If you require direct assistance, please contact Teradata support.

Insufficient memory to parse request during...

Rate Topic

Display Mode

Topic Options

Author

Message

Toshu

Posted 6/8/2009 2:06:24 AM

Forum Newbie

Group: Forum Members
Last Login: 10/27/2009 6:55:52 AM
Posts: 4, Visits: 7

Hello,

i'm running BTEQ via MVS Batch (BTQMAIN program).
From yesterday, i'm getting below error for my SQL:

Failure 3710 Insufficient memory to parse this request, during Optimizer phase.
Statement# 1, Info =0

I figured out that it has something to do with MaxParseTreeSegs. But don't know how to use it in my case. I don't have much access to teradata which is behind the seen.

Is there any way to tackle this issue. May be by including some statement at the top of my SQL query?

Please suggest!

Thanks,
Tushar Saxena

Post #15697

teradata_dba

Posted 6/11/2009 4:10:18 AM

Forum Member

Group: Forum Members
Last Login: Yesterday @ 11:57:16 PM
Posts: 35, Visits: 58

ifact one of our developr faced the same error.
it has got something to do with maxparsetreeseg. what is the current value that is set in your system? i suggest you ask ur dba to increase it to 4000 and then give it a shot.
if u still find the error then u may have to revisit your SQL statement.
IMP: when ever you are trying to use a join avoid using sel * from.... . i mean it is better to restrict the col's.

cheers
TD_DBA

Post #15749

Toshu

Posted 6/12/2009 11:35:48 AM

Forum Newbie

Group: Forum Members
Last Login: 10/27/2009 6:55:52 AM
Posts: 4, Visits: 7

Hello TD_DBA,

is there anyway to add some statement at top of my sql to revise maxparesetreeseg for particular case? is thr any way to avoid invlovement of DBA?

Thanks,
Tushar Saxena

Post #15775

cezargoncalves

Posted 10/22/2009 9:25:45 AM

Forum Newbie

Group: Forum Members
Last Login: 10/22/2009 9:20:19 AM
Posts: 1, Visits: 1

Hi..

You can try to use the following DIAGNOSTIC command before your query:

DIAGNOSTIC NOSATTC ON FOR SESSION;

Best regards,
Cezar
Teradata Brazil

Cezar Eduardo Goncalves
Teradata Brazil
Advanced Teradata Certified
Teradata Administrator
cezar.goncalves@teradata.com

Post #17138

Toshu

Posted 10/22/2009 10:11:17 AM

Forum Newbie

Group: Forum Members
Last Login: 10/27/2009 6:55:52 AM
Posts: 4, Visits: 7

Hello Cezar

Thanks for replying, but it didn't work :(
I wish there is some magical statement that can solve the purpose.

Thanks and Regards,
Tushar Saxena

Post #17139

« Prev Topic | Next Topic »

Reading This Topic

Active Users: 0 ( 0 guests, 0 members, 0 anonymous members )

No members currently viewing this topic.

All times are GMT -5:00, Time now is 5:59am