DSXchange

I think there is a problem with the EE aggregator stage when trying to pass char fields through. I think it has been raised with Ascential and they will fix it for the next release. We have used either Transformer stages with bespoke aggregation logic or you can also put a Server aggregator into a s...

Yes - just remember that the parameter is inserted into the SQL statement exactly as it is written and no quotes are put in there for you, so if the parameter contains a string value you will need single quotes around it.

e.g.

select * from my_table where my_varchar_col = '#pMY_PARM#'

I have now found what the problem was and will post solution below incase anyone else finds the same. It seems so obvious now that I know! The datatype in Oracle is "Date" and when this is imported into DataStage it is a "Timestamp". This works fine for the conventional load meth...

I have some more information to add to this post. It now appears that the dates are not being loaded as Nulls, there are actually dates in the fields and these can be seen when selecting from the table using SQLPLUS rather than a tool such as Toad or DBVisualiser. I still don't know what is happenin...

I am using the Oracle Load stage to load an Oracle 10g database. If I use the direct method all the date fields are null in the database. If I use non-direct method the dates are populated correctly. There are now warnings or errors from datastage. In database datatype = Date In Job datatype = Times...

From looking at your example I think you are doing the correct thing you just have the syntax wrong. If you have "where facility_id in ('#pFACILITY#')" and pass #pFACILITY# = 'FACILIY1', 'FACILITY2', 'FACILITY3' your sql will have too many quotes. i.e. it will look like "where facilit...

what are the column definitions? are the fields your testing chars? Are they nullable? if they are achars nd the the field you read is blank, i.e. not the correct length EE will pad the string with Ascii nulls (The default pad char, unless you have changed this) therefore when you are testing for nu...

It just seems to be a bug. If a sequential file stage is used in fixed width format with NLS set to UTF8, records read that contain special chars cause warnings. The internal function nls_readfixedwith (or whatever it is) seems to check the size in bytes not chars. If NLS tab had been available this...

IsNull() Will only return true if the value provided is null, it doesn't matter what data type the field is.

Hi, Has anyone else had problems with fixed width files and NLS? When I use the row merger or splitter it logs warnings when special characters are found because DS thinks the records are too long (or have an extra column). I think this is caused because the merger/splitter stage are using UTF8 and ...

have a look at page 115 of the servjdev.pdf doc in the datastage docs folder. There are some issues with using the euro sign.

Problem solved - something to do with having too many primary key fields on a low level segment.

I take it the records are in a sequential file. If so do the following: build a Routine that opens the file and tries to read the first record. if it can read the record return one value (NewRecords) else return (NoRecords). You can use this returned value in a simple job sequencer to determine whet...

I am having a problem loading an Idoc with multiple segments. Is it possible to have the streams populating the different segments coming from the separate transformers? It makes sense that you should be able to but when I run the job I get the following WARNING: Abnormal termination of stage SAP_iD...

I have tried your solution to this problem, using DSSetUserStatus(INPUT.FIELD) in the derivation of one of my columns in a transformer but it keeps showing an error. I am using DS v.7, AIX 5.2 in the derivation section of my output column I write: DSSetUserStatus (Source.Value) and it is always red....