Search found 51 matches
- Fri Jun 19, 2015 1:18 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Conversion of all fields in a job to Unicode
- Replies: 5
- Views: 2791
- Thu Jun 18, 2015 8:30 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Conversion of all fields in a job to Unicode
- Replies: 5
- Views: 2791
- Thu Jun 18, 2015 6:31 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Conversion of all fields in a job to Unicode
- Replies: 5
- Views: 2791
Conversion of all fields in a job to Unicode
Our team has noticed that all inserts to the tables which contain accented characters are failing to be mapped properly. We now need to go through hundreds of jobs and change the string fields to Unicode fields in the output of the transformer before the insert. The project default is set to UTF-8 I...
- Fri May 29, 2015 1:01 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Modify error converting Timestamp(Microseconds) to string
- Replies: 3
- Views: 3290
- Thu May 28, 2015 8:31 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Modify error converting Timestamp(Microseconds) to string
- Replies: 3
- Views: 3290
Modify error converting Timestamp(Microseconds) to string
Trying to convert a Timestamp(Microseconds) to string gives the following error modify(0),0: Un-handled conversion error on field "DT_DEB_SITUATION " from source type "timestamp[microseconds]" to destination type "string[20]": source value="2013-01-01 00:00:00.0000...
- Thu May 28, 2015 8:22 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Invalid Julian Day with Modify
- Replies: 3
- Views: 2608
- Thu May 28, 2015 3:02 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Invalid Julian Day with Modify
- Replies: 3
- Views: 2608
Invalid Julian Day with Modify
I am trying to create a generic job to remove duplicates based on a key column and a timestamp column. The key column can potentially be any numeric type, so I am creating another column in a string format and importing the key column as well as retaining the original key column The modify statement...
- Tue May 19, 2015 1:14 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Warnings when writing to an ODBC table with a schema
- Replies: 3
- Views: 3695
The updates are functioning with the custom SQL I am sorry Ray, I don't quite understand what you mean by that. Do you mean like this ? UPDATE TR_MODALITE SET DT_FIN_IMAGE = \'2015-05-18 17:48:03.000\', NUM_CHARGEMENT_UPD=20150506160002 WHERE NOM_MODALITE=? AND CODE=? AND TOP_LAST_IMAGE=1 I tried th...
- Tue Apr 28, 2015 1:36 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: using the COMMON across jobs
- Replies: 4
- Views: 5226
- Mon Apr 27, 2015 1:40 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: using the COMMON across jobs
- Replies: 4
- Views: 5226
using the COMMON across jobs
I have a job which reads a table into a routine. The routine contains a dynamic array in a common area which stores each column individually for each row. The common uses the following syntax COMMON /x/ a b This job is called from a job sequence. Once the job has run, I have another routine to read ...
- Mon Mar 09, 2015 7:19 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Object name not valid on inserting via ODBC
- Replies: 1
- Views: 2108
Re: Object name not valid on inserting via ODBC
Problem solved. The table script missed out the all important .DBO
- Mon Mar 09, 2015 5:02 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Object name not valid on inserting via ODBC
- Replies: 1
- Views: 2108
Object name not valid on inserting via ODBC
I have created an generic job to load a series of files into their counterpart tables on SQL Server. All of the tables load, except one. I get this error Odbc_Select_Schema: ODBC function "SQLExecDirect()" reported: SQLSTATE = 42S02: Native Error Code = 208: Msg = [IBM(DataDirect OEM)][ODB...
- Tue Feb 24, 2015 9:04 am
- Forum: General
- Topic: Improving Sequence Compilation times
- Replies: 18
- Views: 6829
The response from IBM was to reduce the number of objects in the Job Sequence. The only optimization that can be done is for compilation of PX jobs. Whilst I'm sure that Citrixing into the machine is a solution, its not one offered here. I'm closing this as a workaround as there seems to be no magic...
- Mon Feb 23, 2015 1:29 am
- Forum: General
- Topic: Improving Sequence Compilation times
- Replies: 18
- Views: 6829
- Thu Feb 19, 2015 8:52 am
- Forum: General
- Topic: Improving Sequence Compilation times
- Replies: 18
- Views: 6829