Search found 13 matches
- Fri Mar 16, 2012 3:49 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Parameter Set values go missing
- Replies: 2
- Views: 3991
- Tue Nov 22, 2011 6:42 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Char (Teradata) to char/Nchar (Oracle) conversion
- Replies: 4
- Views: 4207
Re: Char (Teradata) to char/Nchar (Oracle) conversion
Thanks again, I did try out with Cast , but with the ODBC connector was having no luck. we used the Oracle connector to Load to Oracle , TD connector for Teradata (as earlier) and ran the job, ran absolutely fine. (The only reason we were not using it initially because we were not able to test conne...
- Tue Nov 22, 2011 5:51 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Char (Teradata) to char/Nchar (Oracle) conversion
- Replies: 4
- Views: 4207
Re: Char (Teradata) to char/Nchar (Oracle) conversion
Thank you for your response. The metadata was imported through designer , Import --Table Definitions --Start connector Import Wizard . Im not really sure how to do it otherwise, i'll look up that up, can you give me a headsup where I can read about it. I'll also definately read through on WCHAR , so...
- Tue Nov 22, 2011 5:29 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Char (Teradata) to char/Nchar (Oracle) conversion
- Replies: 4
- Views: 4207
Char (Teradata) to char/Nchar (Oracle) conversion
Hi. Some help needed for a test job on an NLS install. There is a column being imported from Teradata To Oracle. Currently all, we are doing is using a TD connector to extract from Teradata and an ODBC connector (Oracle connector isnt working, that's another issue though) to load to Oracle. The sour...
- Fri Nov 18, 2011 4:53 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Limitation to the number of columns?
- Replies: 2
- Views: 1639
- Fri Nov 18, 2011 10:52 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Limitation to the number of columns?
- Replies: 2
- Views: 1639
Limitation to the number of columns?
Is there a limitation to the number of columns (not rows) that a DataStage job can extract and consequently load? Some more info - There is a requirement that has come in from a new area of business. They want a table in the EDW that would have a very large number of cols, say 900. The ETL team has ...
- Tue Oct 04, 2011 10:57 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Logic for implementation of the req
- Replies: 4
- Views: 3215
- Tue Oct 04, 2011 3:49 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Logic for implementation of the req
- Replies: 4
- Views: 3215
Some more data
Sorry, here is more info. The First column is activity number , the second col is week number , the date cols are end.date and start.date.... This is how ideally the data should look like F.no||w.No||e.date||s.date|| 1 || 234||Oct 4th||0|| The current data looks like F.no||w.No||e.date||s.date|| 1 |...
- Tue Oct 04, 2011 12:27 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Logic for implementation of the req
- Replies: 4
- Views: 3215
Logic for implementation of the req
Gurus, here is something that I need your help on I have two cols - F.No and W.No (Both of Datatype Integer), and two date cols , s.date and e.date ||F.No||W.NO||e.date||s.date|| F.no - is supposed to have only one W.no associated with it, and only either of s.date or e.date associated with it. Curr...
- Fri Jan 28, 2011 7:44 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Record check after extract
- Replies: 6
- Views: 3861
some more details, which might paint a better picture of the scenario..... The jobs are scheduled through mainframe jobs which invoke a perl script wrapper which triggers the DataStage sequences. The above check should be done in the first sequence. If it registers positive then go through the seque...
- Thu Jan 27, 2011 9:43 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Record check after extract
- Replies: 6
- Views: 3861
Thank you Vincent And Craig.. Vincent, I'm going to try for the script or use the SQL plus commands and get back (with more questions I guess :) ). Though how does one make use of that o/p......... i.e once you have confirmed for zero records , how do you guide the flow? Craig, I've been trying to s...
- Thu Jan 27, 2011 4:35 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Record check after extract
- Replies: 6
- Views: 3861
Record check after extract
Hi, We need to extract records to a dataset from SQL server, on an everyday basis. There is a high possiblity that 0 records would be retrieved on a few days. If that is the case the job/seq shouldnt go ahead but exit gracefully. The check shouldnt be done when we are loading the data, it should be ...
- Thu Dec 23, 2010 1:14 pm
- Forum: General
- Topic: Estimation query
- Replies: 2
- Views: 2301
Estimation query
When you are asked to estimate a timeframe over how long a particular bit of DataStage job would take, it does depend on how complex the job is, what sort of transformations etc are required, are there any other dependencies like writting scripts etc etc But my question is there a document which exp...