problem with column with name "TIME_STAMP" or &quo

kirankota79 · Post by **kirankota79** » Tue Feb 27, 2007 11:16 am

Hi,

I have a problem with a column with name "TIME_STAMP" or "TIMESTAMP" in some tables. When i try to read or view from datastage, it says that this "filed does not exists". any hints.....pleaz!

ArndW · Post by **ArndW** » Tue Feb 27, 2007 11:19 am

What database and stage are you using? To rephrase your question, you have a column called "TIME_STAMP" in a table. You've loaded that table's metadata into DataStage and have used that in a database stage. When you do a "view data" on that table you get the error that the column "TIME_STAMP" doesn't exist. Did I understand taht correctly?

chulett · Post by **chulett** » Tue Feb 27, 2007 11:20 am

What database? Sometimes that's because it is a reserved word and you need to quote the field name in your sql.

chulett · Post by **chulett** » Tue Feb 27, 2007 11:22 am

Or you're not in the table you think you are.

Double-check everything.

kirankota79 · Post by **kirankota79** » Tue Feb 27, 2007 12:31 pm

I have two different tables, one has column name "Time_stamp" and the other one has "Timestamp" and when i import the data , the metadata for these columns is LongNBinary. Even i changed to datatype Timestamp.......it is not working. If it is a reserved type........what is the syntax i can use to over come this.

Thanks.

kirankota79 · Post by **kirankota79** » Tue Feb 27, 2007 12:32 pm

one more thing........iam using ODBC stage

chulett · Post by **chulett** » Tue Feb 27, 2007 1:01 pm

What database?

kirankota79 · Post by **kirankota79** » Tue Feb 27, 2007 1:24 pm

oracle

kirankota79 · Post by **kirankota79** » Tue Feb 27, 2007 1:37 pm

anybody...........please give me reply

narasimha · Post by **narasimha** » Tue Feb 27, 2007 2:23 pm

Switch to Ora OCI stage, you should be ok.

chulett · Post by **chulett** » Tue Feb 27, 2007 2:31 pm

Only because you'll probably fix your problem in the process. You really need to double-check everything in the stage - typical reason for a 'field does not exist' error is because (oddly enough) it doesn't exist. And it doesn't because you are not connecting to the table you think you are.

Make no assumptions about correctness, recheck everything about your sql - instance, schema, table name, everything.