I can confirm that timestamp_from_string in a Modify stage in version 11.3 works exactly as expected with microseconds for me. Perhaps a version 8 bug?
Mike
Search found 1015 matches
- Wed Mar 15, 2017 5:00 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: timestamp_from_string with microseconds in Modify Stage
- Replies: 7
- Views: 5929
- Thu Mar 09, 2017 1:17 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: DB2 Connector Reject setting
- Replies: 3
- Views: 3706
- Wed Mar 01, 2017 3:21 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: XSD for the DataStage XML job report
- Replies: 4
- Views: 4292
- Wed Mar 01, 2017 8:04 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Look up is not happening while using Join stage
- Replies: 1
- Views: 2045
- Tue Feb 28, 2017 11:50 am
- Forum: General
- Topic: Editing built-in routines
- Replies: 4
- Views: 2834
As usual, Craig's memory is infallible. Do a quick find in the Designer client with your routine name and it'll jump right to it. Go to its properties and you can examine the source code on the Code tab. In my 11.3 version the routine is read-only by default, so you may have to remove the read-only ...
- Mon Feb 27, 2017 5:04 pm
- Forum: General
- Topic: Editing built-in routines
- Replies: 4
- Views: 2834
- Sat Feb 18, 2017 9:17 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: JDBC Connector Performance Tuning
- Replies: 9
- Views: 8051
Check with your support provider to determine if there are any known issues with partitioned read in the JDBC Connector. Add $CC_MSG_LVL to your job parameters and set it to 1, 2, or 3 to enable some connector tracing to be recorded in the job log. I usually start with a setting of 2. You may have t...
- Wed Feb 15, 2017 8:31 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Deadlock detected while updating table
- Replies: 9
- Views: 4684
In addition to answering the multiple questions about how you are partitioning the data (by primary key?), how many rows are in your target table? Updates are an expensive DML operation, so 6 million updates have a performance cost. If your table size is 10 million, then you might benefit (as an exa...
- Tue Feb 14, 2017 1:42 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Deadlock detected while updating table
- Replies: 9
- Views: 4684
I haven't touched an Oracle database in years, so don't know if my comments would apply. When I see a high-volume update statement (what percentage of the FACT table are you updating and what is the total volume?), I would also be concerned about how many indexes exist on the table. You normally wou...
- Wed Feb 08, 2017 7:53 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: RCP and Shared Containers
- Replies: 2
- Views: 3601
I use RCP within shared containers frequently. I have noticed an inconsistent bug in version 11.3 that results in an error like what you are seeing. When the bug occurs it has always been when the first stage inside the shared container was a transformer stage. But sometimes they work fine with the ...
- Wed Feb 08, 2017 7:42 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Identifying Basic transformer stage
- Replies: 4
- Views: 4113
- Wed Feb 01, 2017 11:37 am
- Forum: General
- Topic: (40521) Unable to retrieve the link details for the stage
- Replies: 1
- Views: 2592
This is a nasty one. I ran into it a couple of times on a single job. Seemed like a corruption of the job metadata somewhere in the repository. Like you, the only way I found to fix it was to manually rebuild the affected stages/links. I suspected that I triggered a bug when I copied a local contain...
- Thu Jan 26, 2017 12:41 pm
- Forum: General
- Topic: Looping on Value file name in Parameter Set
- Replies: 4
- Views: 21265
Not with the job activity stage unfortunately. It limits you to choosing a value file name from a drop down list. It's not possible to specify a parameter. As a workaround, you can use the execute command activity to run the dsjob command where you should be able to use $Counter in setting the value...
- Fri Jan 20, 2017 6:19 pm
- Forum: General
- Topic: Multi-instance job log cleanup
- Replies: 17
- Views: 10326
All of our invocation ids are normally reused. Even the small percentage where I've noticed an invocation in Director with no log entries would have been reused (or will be reused again). We've had our project-level auto purge on since day 1. I don't have any reason to believe that any of our develo...
- Fri Jan 20, 2017 7:56 am
- Forum: General
- Topic: Multi-instance job log cleanup
- Replies: 17
- Views: 10326
Just wanted to add a comment to the post by PaulVL... My current project is on 11.3 FP2 as well. Auto-purge of multi-instance jobs always clears our job log entries as expected. In the vast majority of cases, it also removes the instance so that it no longer appears in the Director client. The stran...