DSXchange

Hi I am using Oracle Stage in 7.5.1.A almost 130765 records are getting rejected from TARGET ORACLE Stage can any one help me on this. I am doing user defined upset (insert and load) method. bye Tried capturing the rejects through a reject link from the target stage? If so whats the error code tell?

Aakash, Quote from Parallel Job Developer's Guide - Sequential files, unlike most other data sources, do not have inherent column definitions, and so DataStage cannot always tell where there are extra columns that need propagating. You can only use RCP on sequential files if you have used the Schema...

I did that but still its not working On which stage is this error thrown?? Are you sure its in the Lookup stage. THis can also happen in the partitioning tab when you ask DS to do a case sensitive /insensitive sort on an incompatible data type. For Eg: a case sensitive sort for a numeric field. Do ...

Hi, I have a job with columm countryid . If the countryid =123 , I will load the respective records in to a table . If the countryid is not equal to 123 then I must raise an error in the log and stop the job (abort the job). Please can help , how to achieve this. You can also get this done inside a...

we are using lookup stage Inside the Look up stage - on the reference link tab you have a check box against each of the columns to define if you need a case sensitive look up or a case insensitive lookup against the keys. Check the datatype for your keys and also the case sensitive/insensitive chec...

You can find more details on the Difference stage in the Parallel Job Developer's Guide.

Drop Output for Copy = True Drops the record from the output if it is a copy record. Drop Output for Delete = False Keeps the record in the output if it is a Delete record (exists in Before Dataset but not in After Dataset) Drop Output for Edit = False Keeps the record in the output if it is an Upda...

You can use the sparse look up provided your main stream record count is very less compared to the Reference. In a Sparse look up, an SQL query is generated for each mainstream input row to find a match in the reference. So if you have 30 million records in the reference, but only 10 records coming ...

Change the column name in one of the links to the Join Stage and also switch off RCP on both the links to the Join Stage. This should take care of your warning.

The Bird.

Hi, You can do this by adding the warning (or the rule) to an existing or a new Message Handler, from the director. THere is an option called - "Add Rule to chosen Message Handler" - when selected you will get a drop down of existing named handlers. You can either chose one to add your war...

Note that if RCP is disabled at a Project level, then you wouldnt find this option at the output tab of any of the stages.

If this need to enabled at a project level, it would have to be done from the Administrator.

The Bird.

You can also do the same by using the Upsert Method and then putting the SQL Insert statement in the Update statement place holder - it will work...

Regards

The Bird.

Hi Raftsman,

I generally use -

@PARTITIONNUM + (@NUMPARTITIONS * (@INROWNUM - 1)) + 1 + SeedVal (where SeedVal si the MAX record from the last write from the prior run)

to generate counters/surrogate keys.

The Bird.

The Environment variables available to control the commit intervals are - APT_ORAUPSERT_COMMIT_ROW_INTERVAL APT_ORAUPSERT_COMMIT_TIME_INTERVAL These two environment variables work together to specify how often target rows are committed when using the Upsert method to write to Oracle. Commits are mad...

hi I added a sort stage and adjusted the partition type to same in the aggregator. Isn't that enough? Peter Thats not enough. You have to specify in the Aggregator stage that the data has already been sorted. Also set the Method property in the Aggregator stage to "Sort", by default it is...