Search found 68 matches
- Wed Oct 20, 2010 10:16 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Error in OCI stage
- Replies: 7
- Views: 2695
- Wed Oct 20, 2010 4:38 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Oracle Connector not running Before SQL
- Replies: 11
- Views: 12307
- Wed Oct 20, 2010 4:32 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Oracle Connector not running Before SQL
- Replies: 11
- Views: 12307
- Mon Oct 18, 2010 9:36 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Oracle Connector not running Before SQL
- Replies: 11
- Views: 12307
Oracle Connector not running Before SQL
I have a job that reads data from a source and does an initial load into an Oracle database via the Oracle Connector stage. Before the data can be loaded I need to disable the constraints, so I coded this into the Before SQL section of the page but when I run the job the Before SQL is not running so...
- Thu Mar 18, 2010 6:00 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: StringToDate Error
- Replies: 2
- Views: 1583
- Thu Mar 18, 2010 5:38 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: StringToDate Error
- Replies: 2
- Views: 1583
StringToDate Error
Hi Trying to convert a number of '19760109' to a date field in Oracle. When I use the StringToDate function with map of '%yyyy%mm%dd' I get the following error message - APT_CombinedOperatorController,0: Data string ' 1976010' does not match format '%yyyy%mm%dd': an integer was expected to match tag...
- Thu May 21, 2009 8:38 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Scheduled dsexport.exe will not end
- Replies: 10
- Views: 5273
If your running in Ver 8, have you tried the 'istools' command shell provided with the client install, it may work a little better. I know I have had problems with scheduled exports and imports, and it seemed to have something to do with the account attached to the scheduled task. This tools may wor...
- Sun Mar 29, 2009 6:59 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Problem cleaning up old projects
- Replies: 5
- Views: 3163
- Tue Feb 24, 2009 10:37 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Problem cleaning up old projects
- Replies: 5
- Views: 3163
- Tue Feb 24, 2009 6:20 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Problem cleaning up old projects
- Replies: 5
- Views: 3163
- Mon Feb 09, 2009 9:56 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Problem cleaning up old projects
- Replies: 5
- Views: 3163
Problem cleaning up old projects
Hi When trying to remove some old projects no longer needed I have run into two problems - 1) One of the projects does not appear in the list of projects within the Administrator, but the directory structure till exists on the server. I can 'LOGTO' the project on the TCL, but if I run the commands t...
- Wed Oct 15, 2008 10:58 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: non significant spaces,on the left must be replaced zeros
- Replies: 4
- Views: 1975
- Tue Aug 26, 2008 6:30 pm
- Forum: General
- Topic: Invocation Id not being always set
- Replies: 9
- Views: 5276
- Tue Aug 26, 2008 5:38 pm
- Forum: General
- Topic: Invocation Id not being always set
- Replies: 9
- Views: 5276
I have tried typing a new invocation id, as well as pasting one from my clipboard, we use a job number for the invocation id. I have to also check this from the command line as this is how we normally run our process end-to-end (Control-M calls DataStage from the unix command line). I will do some a...
- Tue Aug 26, 2008 12:00 am
- Forum: General
- Topic: Invocation Id not being always set
- Replies: 9
- Views: 5276
Hi Craig If I run from the primary job, it runs without an invocation id, whereas if I use an existing run of the job and try to change the invocation id it uses the existing one. I though it may have to do with the number already used, i.e. I had 10 previous invocation id's, so I cleared the status...