3610: internal error: please do not resubmit the last request

[natncm70]

Hello,
I am geting error in the case when select statement.The error message is " 3610: internal error: please do not resubmit the last request"
what should I do for that
Please help me.
This is the query.
SELECT
a.DOMICILE_CHANNEL_ID AS IDD
, COALESCE(SUM(
CASE
WHEN A.ACCOUNT_NBR IN (
SELECT D_S.ACCOUNT_NBR
FROM
DD_TEDW.T0305_ACCOUNT_SUMMARY_DERIVE D_S
WHERE D_S.ACCOUNT_NBR IN (973400,888700,971120,971300,973800,970900,970912,970910, 971100,970301,970302,970303,970300,973000,900071,900072,971000)
AND D_S.ACCOUNT_SUMMARY_DATE = '2002-10-31' )
THEN ENDING_LEDGER_BALANCE_AMT
END ),0) AS TODAY_ADV
FROM
dd_tedw.t0300_account a
Inner Join dd_tedw.t0303_account_status_history c
On a.account_nbr = c.account_nbr
Inner Join dd_tedw.t0305_account_summary_derive d
On a.account_nbr = d.account_nbr
Inner Join DD_TEDW.B0800_CHANNEL_MAP E
On E.mapped_id = a.domicile_channel_id
WHERE c.acct_status_type_code = 1
GROUP BY 1

 

[tdatgod]

Hi,
Please report this to the Teradata Customer Support organization since this error means your Query Hit a BUG within the Teradata Software.

If you don't have a NCR customer support ID because you are using the Teradata Demo software, which by the way is the real product ( V2r4.1 with a size limitation ) so it shouldn't crash either, please let me know and we can work something off line to collect the information necessary to submit a test case to engineering and fix the problem in the real product.

The reason we tell you not to resubmit it is because if you execute it again teradata will hit the same BUG again and ever time you try it until you get the fix from Teradata.

Teradata should not have BUGs and we will fix them when they are discovered if we can.

 

[BillDHS]

I have seen this error with invalid SQL, for example an outer join statement problem. We are on V2R3, and in out version, we can't have a Select statement in the SELECT clause. Try removing the Select segment from your Coalesce-Sum-Case attribute, and make it a derived table.

 

[tdatgod]

Hi,
Sorry being a developer for Teradata a BUG is a BUG and needs to be fixed.

A query should not crash the box even if it uses Illegal syntax. It should return an informative message to the user telling them where the error in their SQL is, rather than giving them a cryptic message like



the SQL you wrote ( or generated )crashed the box....
Please Don't do that again.



In recent releases a lot of the 3610 have been turned into SNAPSHOT dumps and only abort the query rather than crashing the whole system, but again every 3610 needs to be fixed in the software rather than correcting the single SQL causing it.

If we fix the software it will help everyone in the Teradata community.

----