ODBC stage problem

rajanikc · Post by **rajanikc** » Mon Jul 06, 2009 7:22 am

H;

I have a job which inserts records to an oracle table through ODBC statge. I wrote a custom sql. There was a syntax error in the sql while I ran the job. But the job just showed warning message for that error and showed finished status. It never showed Failed status with fatal error. Can you please tell me how to rectify this?

Thanks
Rajani

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Mon Jul 06, 2009 8:00 am

What is the custom SQL statement?

What is the warning / error?

Do not expect others to guess the issues you are facing. It is enough to guess the solution.

miwinter · Post by **miwinter** » Mon Jul 06, 2009 9:00 am

Exactly what I was going to ask... perhaps in ODBC a warning (Database side) will only generate a warning (Datastage side) as opposed to a fatal? We need to know the details involved to have any chance of assisting please.

rajanikc · Post by **rajanikc** » Mon Jul 06, 2009 9:31 am

Thanks for the replys guys

custom sql is

UPDATE
test_table
SET
col2 = ORCHESTRATE.col2
WHERE
col1 ORCHESTRATE.col1

and the warning the datastage is throwing is:

ODBC_Enterprise_5,0: [DataDirect][ODBC Oracle Wire Protocol driver][Oracle]ORA-00920: invalid relational operator

Thanks for the quick replies again

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Mon Jul 06, 2009 9:38 am

Your where clause does not have an '=' symbol in the last line (after col1).

rajanikc · Post by **rajanikc** » Mon Jul 06, 2009 10:10 am

yes thats right. My sql has an error. But this error is not shown as fatal warning in the director when I run the job. It just shows as message

miwinter · Post by **miwinter** » Mon Jul 06, 2009 10:19 am

When you say it shows as a 'message' is it an informational or warning in the Datastage log?

rajanikc · Post by **rajanikc** » Mon Jul 06, 2009 10:20 am

Warning

ray.wurlod · Post by **ray.wurlod** » Mon Jul 06, 2009 6:23 pm

That seems reasonable. There was no error in the stage per se.

I vaguely recall that there is a "treat warnings as fatal" check box available. Perhaps you could use that.

chulett · Post by **chulett** » Mon Jul 06, 2009 9:10 pm

Or perhaps run the job with a (very) low warning limit.

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Tue Jul 07, 2009 2:13 am

Or use a reject link from ODBC stage to capture anything not successful.