DSXchange

Has anyone experience this error?
Error 220(EM_DBC_CRASH_A) .....

It is a straightforward SQL query being executed in a Teradata enterprise stage. The data is being read by a join to 2 views in the TD database and can be written to anything - sequential file, dataset, another (SQL Server database).

As soon as the job starts, it crashes the entire database! I am not too familiar with Teradata, but really find it strange that a query can crash the database.

Anyway, running the same query through SQL assistant runs fine - but not through Datastage.

Any help will be greatly appreciated.

Welcome Aboard
Does this happen every time you run the query with datastage? I quick search in google on the error message revealed that error 220 is due to losing connection. For some reason you are losing connection.
Get your DBA invovled and then run your job. See what your DBA can detect on the monitor.

At first we thought that its just the connection. But, as mentioned in the original post, this job brings down entire Teradata database (and hence apparently the connection).

Wow, the entire database huh? What if you do a simple select from one view, no joins?

Its the next thing on our agenda - but currently we have almost been "blacklisted" - so have to get a separate time scheduled - so as to not interrupt other development efforts!

Please post this rogue query.

How large and complex are the views? How large and complex is the join between the two views? As an exercise in resource estimation, create the query without reference to the views - that is, with direct reference to the queries that define the views. That exercise may give you a gentle mental push in the right direction.