You could experiment with the NLS Code page at the job and stage levels. See if UTF-16 will help.
Mike
Search found 1015 matches
- Mon Sep 11, 2017 4:26 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Unicode with RCP?
- Replies: 11
- Views: 12369
- Mon Sep 11, 2017 11:27 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Unicode with RCP?
- Replies: 11
- Views: 12369
RCP isn't going to do any type conversion. If your source is a ustring then it will propagate as a ustring. If it is a string then it will propagate as a string. If you need to convert between ustring and string, you can use a modify stage with a parameterized specification. $OSH_PRINT_SCHEMAS will ...
- Mon Aug 07, 2017 6:26 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: waitForWriteSignal(): Premature EOF on node
- Replies: 9
- Views: 14628
- Fri Jun 30, 2017 2:33 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Update SK Files with last surrogate Key values
- Replies: 9
- Views: 6761
Can't really say what your issue might be without actually looking over your shoulder. But in your example, the originally updated 16 byte surrogate key file should show 2004 2004 when viewed with the stage in view mode (if I remember that correctly). Running on 4 nodes, I would expect you to end up...
- Fri Jun 30, 2017 9:30 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Update SK Files with last surrogate Key values
- Replies: 9
- Views: 6761
- Fri Jun 30, 2017 9:21 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Update SK Files with last surrogate Key values
- Replies: 9
- Views: 6761
Then you did not successfully start with an empty state file. It will have a length of 0 when it is empty. After your update it should have a length of 16. Use an ls -l mystatefile to check file size. The state file is a binary file. It will have no record or field delimiters. Each record will be ma...
- Fri Jun 30, 2017 7:41 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Update SK Files with last surrogate Key values
- Replies: 9
- Views: 6761
There are quite a few nuances to the surrogate key generator stage. It actually includes some interesting flexibility. You would have to spend some time experimenting to learn all of the nuances. I have a generic utility job that I use to sync a state file with the maximum key value for a table that...
- Wed Jun 21, 2017 7:08 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Generate sequence number using parallel job
- Replies: 6
- Views: 6647
- Tue Jun 20, 2017 6:45 pm
- Forum: General
- Topic: code version check
- Replies: 4
- Views: 3524
I've gone with a 2 step approach for identifying version change candidates. Step 1 is to compare the modification timestamps using XMETA. These are the same modification timestamps that you would see with an advanced find using the Designer client. This does require read access to the XMETA reposito...
- Fri Jun 16, 2017 7:28 am
- Forum: General
- Topic: Unable to find Java Technology Edition software
- Replies: 2
- Views: 2396
- Thu Jun 15, 2017 9:41 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Fatal Error: Attempt to setIsNull() on the accessor interfac
- Replies: 13
- Views: 10128
- Wed Jun 14, 2017 7:47 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Fatal Error: Attempt to setIsNull() on the accessor interfac
- Replies: 13
- Views: 10128
Unfortunately the report of schemas generally gets lost when the job aborts. 1) Verify that you have no column metadata defined in the ODBC connector. 2) Verify that the sql select statement doesn't have any function that might result in NULL. 3) Replace everything after the ODBC Connector with a co...
- Fri Jun 09, 2017 1:44 pm
- Forum: General
- Topic: Sequence x Job with ParameterSet
- Replies: 7
- Views: 4297
- Wed Jun 07, 2017 8:11 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Handling non English characters while using substring
- Replies: 5
- Views: 3966
As you see, bytes and characters have a variable ratio when you are dealing with UTF8. Characters will range in size from 1 to 4 bytes. Your 30 byte column in Oracle could potentially hold as few as 7 and as many as 30 complete characters. If you don't stick to character semantics, you run the risk ...
- Wed Jun 07, 2017 6:36 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Handling non English characters while using substring
- Replies: 5
- Views: 3966
UTF8 and bounded varchars come with the sort of baggage that you're seeing. That's due to UTF8 having a variable number of bytes per character. You should switch to nvarchar (or the equivalent of adding Unicode extended property to your varchar). Also if you look closely at the output that you think...