Page 1 of 1

problem with column with name "TIME_STAMP" or &quo

Posted: Tue Feb 27, 2007 11:16 am
by kirankota79
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!

Posted: Tue Feb 27, 2007 11:19 am
by ArndW
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?

Posted: Tue Feb 27, 2007 11:20 am
by chulett
What database? Sometimes that's because it is a reserved word and you need to quote the field name in your sql.

Posted: Tue Feb 27, 2007 11:22 am
by chulett
Or you're not in the table you think you are. :wink: Double-check everything.

Posted: Tue Feb 27, 2007 12:31 pm
by kirankota79
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.

Posted: Tue Feb 27, 2007 12:32 pm
by kirankota79
one more thing........iam using ODBC stage

Posted: Tue Feb 27, 2007 1:01 pm
by chulett
What database?

Posted: Tue Feb 27, 2007 1:24 pm
by kirankota79
oracle

Posted: Tue Feb 27, 2007 1:37 pm
by kirankota79
anybody...........please give me reply

Posted: Tue Feb 27, 2007 2:23 pm
by narasimha
Switch to Ora OCI stage, you should be ok.

Posted: Tue Feb 27, 2007 2:31 pm
by chulett
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.