Insufficient memory for this plastic step

Database
Enthusiast

Insufficient memory for this plastic step

I am getting an error Insufficient memory for this plastic step. I just want to know what does this error tries to tell us.

5 REPLIES
Junior Contributor

Re: Insufficient memory for this plastic step

Check the Messages manual

3712 Insufficient memory for Plastic Steps for

this request.

Explanation: The request was more complex than the

Teradata SQL Parser could process. The parser stopped

during generation of ’Plastic Steps’ which must fit

within two segments of memory. A single ’Plastic Step’

must fit within one segment.

Generated By: GEN modules.

For Whom: End User.

Remedy: Increase the DBS Control Record field Steps-

SegmentSize. See Teradata Utilities Manual for information

on DBS Control fields. Otherwise, simplify the

request and resubmit it. If the request appears to be simple

and there is some question as to whether it should

fail for lack of memory, submit script to your support

representative.

Dieter

Enthusiast

Re: Insufficient memory for this plastic step

Thanks for your information. Can you please tell me what is mean by DBS Control Record field and also how can we edit from the query man.

Enthusiast

Re: Insufficient memory for this plastic step

Wat i meant in the previous post was how to edit the DBS Control Record fields from the query man if at all its possible.

Enthusiast

Re: Insufficient memory for this plastic step

Hi Barani,

Start Teradata Manager

<Administer><Database Console>

<Utilities><DBS Control>

Display Performance;<enter>

Modify Performance 6 =1024<enter> ( modifies the StepsSegmentSize ( field 6 ) of the performance group )

WRITE<enter>

QUIT<enter>

Unfortunately mine was already set to this maximum so it doesn't solve my problem.

Tony.

Enthusiast

Re: Insufficient memory for this plastic step

My code was too complex so I did the following:

1. Add an alias name only to the columns that you are going to reference. 

(e.g. INSERT INTO TAB_1 ... Col_1 * Col_2      as A_Col_1_Col_2,)

2. Move some of the code to a subsequent update statement. 

I realise that this isn't alway possible but it was the best solution for my problem.