Search found 258 matches
- Thu Sep 09, 2010 7:25 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Build a Complex XML document
- Replies: 15
- Views: 7340
Hi Ernie, The structure I want in the output is <Details> <Officecode> <DEP> </DEP> </Officecode> <Details> Now I will give you the actual data. 01,FIN 03,SLS 01,FIN 01,TEC 02,TEC 01,FEC 02,HUR 03,MRT One Office can have multiple DEP's and there are many offices.(as you can see in the sample data) T...
- Wed Sep 08, 2010 11:38 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Build a Complex XML document
- Replies: 15
- Views: 7340
Build a Complex XML document
Hi , I want to build a complex xml document using datastage. I also have gone through the XmlBestPractices.doc. My job design is like given below. file---->transformer------>xmlo/pDEP------------>join-----xmlo/pcombine ------->xmlo/pofficecode----> I am extracting data from a file which has officeco...
- Thu Apr 29, 2010 5:07 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: sting to time conversion
- Replies: 13
- Views: 4719
I have faced same issue while taking data from the teradata.Is the column you are picking form teradata table defined as time(8) in the table T1 and T2 . If not you need to cast this to proper time format as per datstge requirement while picking it . Hi, I casted the data from teh source to varchar...
- Fri Apr 16, 2010 2:20 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: sting to time conversion
- Replies: 13
- Views: 4719
Your transform stage input column HEUR_RELV_SOLD_PP is defined as Char(8), perhaps you inadvertantly redefined it in the sort or join stage. Without an explicit conversion, i.e. StringToTime(), DataSt ... hi ArndW, it is defined as time across all the stages. It is not defined as character in any s...
- Fri Apr 16, 2010 2:07 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: sting to time conversion
- Replies: 13
- Views: 4719
Hi Ray,ray.wurlod wrote:You have not specified either a default time format or an explicit time format. Do either or both of these things. ...
where do we specify either a default time format or an explicit time format
and how do we do it.
It would be great if you could give us a hint on this.
Thanks,
Samyam
- Fri Apr 16, 2010 1:04 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: sting to time conversion
- Replies: 13
- Views: 4719
sting to time conversion
Hi, I have job like described below. table1-->sort-->join(Left join T1-T2)-->transformer--table3 table2-->sort--> the tables are teradata tables. we have a column HEUR_RELV_SOLD_PP which is in time format 'hh:mi:ss' format in table1. this columns is mapped to table3 through sort,join,transformer. th...
- Tue Feb 16, 2010 3:57 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Phantom Aborting with @ABORT.CODE = 3
- Replies: 2
- Views: 7537
- Tue Feb 16, 2010 3:35 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Phantom Aborting with @ABORT.CODE = 3
- Replies: 2
- Views: 7537
Phantom Aborting with @ABORT.CODE = 3
the exact error message is given below.
From previous run
DataStage Job 57 Phantom 25321
Attempting to Cleanup after ABORT raised in stage JxXXXXXXXXX.
DataStage Phantom Aborting with @ABORT.CODE = 3
there is no clue on why it is aborting.
Thanks
Samyam
From previous run
DataStage Job 57 Phantom 25321
Attempting to Cleanup after ABORT raised in stage JxXXXXXXXXX.
DataStage Phantom Aborting with @ABORT.CODE = 3
there is no clue on why it is aborting.
Thanks
Samyam
- Wed Nov 04, 2009 5:23 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: When checking operator: Dropping component
- Replies: 17
- Views: 20088
- Wed Nov 04, 2009 4:47 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: When checking operator: Dropping component
- Replies: 17
- Views: 20088
- Wed Nov 04, 2009 4:39 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: When checking operator: Dropping component
- Replies: 17
- Views: 20088
- Wed Nov 04, 2009 3:42 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: When checking operator: Dropping component
- Replies: 17
- Views: 20088
- Wed Nov 04, 2009 2:04 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: When checking operator: Dropping component
- Replies: 17
- Views: 20088
- Mon Nov 02, 2009 4:12 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: U_ILLEGAL_ARGUMENT_ERROR encountered in Datastage PX 7.5.2
- Replies: 7
- Views: 3813
U_ILLEGAL_ARGUMENT_ERROR encountered in Datastage PX 7.5.2
Hi All, Has anyone encountered the following error while running a Datastage PX 7.5.2 Job before? U_ILLEGAL_ARGUMENT_ERROR encountered followed by Conversion problem in import method, trying to import:. followed by Operator terminated abnormally: received signal SIGSEGV. The source file format seems...
- Thu Oct 22, 2009 12:54 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: *DataStage*DSR_LOADSTRING
- Replies: 8
- Views: 3032
it worked for only one dsx file but now i am facing the same problem again. this time there is lot of space available. DS_AUDIT has permissions too. I am not able to run the UV command to check whats in the DS_AUDIT table. I am still getting the error on file DS_AUDIT cannot be written Program "...