problem with column with name "TIME_STAMP" or &quo
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 315
- Joined: Tue Oct 31, 2006 3:38 pm
problem with column with name "TIME_STAMP" or &quo
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!
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!
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?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
What database? Sometimes that's because it is a reserved word and you need to quote the field name in your sql.
Last edited by chulett on Tue Feb 27, 2007 11:22 am, edited 1 time in total.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Premium Member
- Posts: 315
- Joined: Tue Oct 31, 2006 3:38 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.
Thanks.
-
- Premium Member
- Posts: 315
- Joined: Tue Oct 31, 2006 3:38 pm
-
- Premium Member
- Posts: 315
- Joined: Tue Oct 31, 2006 3:38 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.
Make no assumptions about correctness, recheck everything about your sql - instance, schema, table name, everything.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers