DSXchange

The answer to my question is YES!

Will unique constraints also cause this error? I'm getting the same -100 error only with the row splitter. All the data is good from a sizing perspective, but there are a couple unique constraint violation. Should that have any impact on this error code as shown above? I wouldn't think that it would...

I found the problem and it comes down to the following:

If I try to use NVarChar in the OCI it fails saying the datatype isn't supported.

This prevents the proper Unicode conversion from taking place with the OCI stage. Changing the OCI stage to an ODBC stage allows this to happen.

I may have titled this correctly, but here is what I'm experiencing: I pull data from a SQL Server source that allows what I think are UTF-8 symbols. In this case the degree symbol. I pull that data and write it to a flat file and the degree symbol shows correctly in the file. I try to load that sam...

Thanks. so, I've captured the date in a file and use that file as input into ODBC stage. I can pass it to the proc as a parameter but I get data type conversion errors. But I can run that exact same proc from Query Analyzer with date in the same format as within DataStage and it runs just fine. Anyo...

How do you store it in the user status area?

Interesting. Thanks for the answer.

This issue with that for us is that each of the 70+ extract jobs can and will have different last load dates (even if only by minutes).

so one job per is going to get very cumbersome.

I'm trying to do the following with no luck: * I have a table on an Oracle database that will give me the last time a job ran and the last load date for the source table I'm extracting from on another system that happens to be MS SQL. * I read from that oracle table and get the last load date. * I w...

[quote="chulett"]There's typically more to these kinds of issues than just the array size. However, try dropping it to 1 and see if that helps.[/quote] Setting to 1 does resolve the issue. However, isn't having an array size of 1 and issue in itself!? 1 row at a time just doesn't make much...

[quote="soumik"]Hi, Can you give the job design? What are the other warnings shown in the log when you reset the aborted job? If you are using OCI stage, then what is the array size you are using?[/quote] I'm having the same problem with a job of mine. I am using an OCI stage that connects...

[quote="DSguru2B"]Try Array size 600. Try higher numbers. 10 wont bring you much. Also try transaction size with 0 then 10k or 20k. If you absolutely have to rollback if error occurs then specify transaction size as 0 else try with other numbers.[/quote] Ok. I'll give some of that a shot. ...

[quote="DSguru2B"]I am loading Oracle 10g with ~1.5KB record size with a throughput of 2.5Krows/sec. I am talking about 2 cpu server engine.All inserts. It also depends upon your record size, table indices etc. Out of curiosity. What transaction size/array size combo you tried ?[/quote] my...

[quote="kcbland"]You don't measure in ROWS/SEC. Performance is measured by CPU utilization. If your DS process thread can run at its maximum speed, which for a single-threaded process is a fully utilized CPU, then you have a tuned job. If the process is waiting on network traffic, as in a ...

[quote="kcbland"]1. What is your source database resource load when your process is running? 2. What is your target database resource load when your process is running? 3. What is your DataStage resource load when your process is running? 4. What is your DataStage job process CPU utilizati...

[quote="DSguru2B"]One reason is rejects. Try to get rid of your rejects. Correction: Try to get rid of rejects that create warnings in your log. Are you getting warnings? Also if your doing upserts, they are the worst. Try splitting your streams and doing inserts and updates seperately.[/q...