Search found 19 matches
- Thu Sep 07, 2006 1:08 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: UserDefined Query Delete statement
- Replies: 11
- Views: 4619
Hi Ray, DELETE From postal_loc_pickdel_test1 WHERE pl_location_lk in (select pl_location_lk from postal_location where co_ctry_lk IN (select co_ctry_lk from country where co_ctry_cd=#CTRY_CD#)); INSERT INTO postal_loc_pickdel_test1 (plp_rec_key,plp_pos_pickdel_lk,pdc_pickdel_cap_lk,pl_location_lk,p...
- Thu Aug 24, 2006 12:25 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Inheriting a job: IPC Partition fed direct to IPC Collector
- Replies: 4
- Views: 1795
- Thu Aug 24, 2006 12:13 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Inheriting a job: IPC Partition fed direct to IPC Collector
- Replies: 4
- Views: 1795
Inheriting a job: IPC Partition fed direct to IPC Collector
I've inherited a legacy job and am having a tough time deciding why it was built the way it was. I'm hoping that the community can shed some light on what I'm thinking. Job design: SRC --> Transformer --> IPC-part --> IPC-collect --> flat file * note, that there is _nothing_ between the partitioner ...
- Tue May 23, 2006 3:30 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Error Trapping with the OLE DB Stage
- Replies: 3
- Views: 2137
- Tue May 23, 2006 3:02 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Error Trapping with the OLE DB Stage
- Replies: 3
- Views: 2137
Error Trapping with the OLE DB Stage
I'm using the MS OLEDB stage to insert records into SQL Server. I'm finding it lacking in it's abilities to trap errors and reject rows properly. If an error occurs, I'd like for the row and error messages to be sent to a log file. Instead, I see warning messages in the job log and a false completio...
- Fri May 19, 2006 9:53 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Routine to Call SQL Server Stored Proc?
- Replies: 4
- Views: 2648
Hehehe... good question. We're trying to re-use code that has already been built on our transactional database (SQL Server). The procedure inserts records into several tables with logic that would have to be rebuilt otherwise. After it's all said and done, we then have to synchronize a table (Oracle...
- Thu May 18, 2006 5:05 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Routine to Call SQL Server Stored Proc?
- Replies: 4
- Views: 2648
Routine to Call SQL Server Stored Proc?
Anyone done this? I saw a previous post from awhile ago of a user trying to call a stored procedure through a routine. He was doing this in order to support input/output arguments. I have a similar problem: I have a job that is similar in flow to: OCI --> StoredProc --> OCI The important things to n...
- Thu May 18, 2006 2:44 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: select substring with field function
- Replies: 3
- Views: 2262
If your job is defined as follows: seq file --> transformer --> seq file2 Why don't you just define the first sequential file stage with a '.' as a delimeter, pick the 1st and 4th columns in the transformer, then feed it to the second sequential file. Ofcourse, you can only do this if the source seq...
- Tue May 16, 2006 8:07 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Custom SQL to Update using ODBC or OLE/DB?
- Replies: 4
- Views: 1919
Custom SQL to Update using ODBC or OLE/DB?
Has anyone had any success in writing a custom SQL statement to update records using either a ODBC or a OLE/DB stage? I'm trying to update existing rows in SQL Server while including a subquery in my where clause. Here's a snippet of the SQL: UPDATE scorecard SET id=?, mo_date=?, region=?, employee=...
- Tue May 16, 2006 11:36 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Timestamps Oracle OCI to OLE/DB??
- Replies: 3
- Views: 1969
Just wanted to update the forum... So things seem to be working fine now. I was getting tripped up in the HRESULT error message when the job executed. I've since found out that the error was being caused by data issues in the source. For some reason, the error message reporting the data values was s...
- Tue May 16, 2006 10:02 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Timestamps Oracle OCI to OLE/DB??
- Replies: 3
- Views: 1969
Thanks Ray. I've resolved the issue #2, it was me javascript:emoticon(':roll:') Rolling Eyes concentrating on the HRESULT error versus looking at the data. That being said, however, the first issue is still around. Null Oracle date columns are still trying to be written as '0000/00/00 00:00:00'. I'm...
- Mon May 15, 2006 7:18 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Timestamps Oracle OCI to OLE/DB??
- Replies: 3
- Views: 1969
Timestamps Oracle OCI to OLE/DB??
Hi all. I'm finding some interesting behavior around timestamps. I've defined columns on both the Oracle and SQLServer side as 'Timestamp'. My job is as follows: OCI-->Trans-->OLE/DB What I'm seeing is as follows: 1. null dates in Oracle are trying to be written as '0000/00/00 00:00:00' in SQLServer...
- Wed Apr 19, 2006 3:55 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Datatypes and Length of Reject Codes (DBMSCODE,SQLSTATE,etc)
- Replies: 3
- Views: 1764
Datatypes and Length of Reject Codes (DBMSCODE,SQLSTATE,etc)
In defining the datatype and lengths of the reject columns, I'm at a loss as to what to define the values to. I'm capturing the following in my reject link: DBMSCODE LASTERR REJECT REJECTCODE SQLSTATE Does it matter what I define these to? All my searches have come up empty as to what the datatypes ...
- Fri Apr 14, 2006 12:57 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Dynamic build of Job Parameter for defining SQL source
- Replies: 4
- Views: 1773
2. Break your existing job into 2 parts. Job one is ODBC-->XFM-->SEQ where the SEQ file contains a fully crafted SQL query for each row with a UNION ALL between rows that will return a uniform set of columns. Job two is OCI-->XFM-->SEQ where the OCI stage executes the generated script (you can do t...
- Thu Apr 13, 2006 4:44 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Dynamic build of Job Parameter for defining SQL source
- Replies: 4
- Views: 1773
Dynamic build of Job Parameter for defining SQL source
Here's the design issue: I have a set of reference tables. In these reference tables there will be a where clause for a given rule. I want to take this where clause, set it to a job parameter, then use it to define a dynamic SQL. There are some key considerations: I have to process multiple rules Fo...