DSXchange

Use the row generator stage, set to 1 row

The messages are from when you were writing to the hash file. They mean you wrote a row with a null primary key, which appropriately is rejected. To suppress this problem, use a constraint on that link to only write if the primary column value is not null. If null data shouldn't be happening, then f...

Sure, you answered your own question. Read the manuals under your Start button, they cover how to use the dscmdimport and dscmdexport programs on your client PC for doing just that. Search the forum, you'll see lots of .bat files and commentary on automating it.

You probably are passing a non-numeric value into a mathematical expression, or you are passing a NULL value to a function that is not prepared to handle it. You can alawys go to the job design logic for this job in the directory RT_BP751 (per the log message) and look at file JOB.1451978099.DT.1380...

The multiple instances jobs aren't the issue, the load on the node is the issue. I can have 100's of very resource-light jobs running simultaneously without issue, but 1 intensive job can use all resources. You neeeed to monitor server load. Every single DS developer needs to get into the habit of h...

You would be better served by gathering the distinct values for "mdm.mdm_benefit_fact" and issuing one delete statement. You do realize that for every row in your dataset you will issue that delete statement? Wouldn't you rather have a dedicated job that just takes that list of values and feeds an O...

You are: 1. Posting in the wrong forum 2. Hijacking someone elses message 3. Not giving enough information. How much data, for what purpose do you wish to stage. Upgrade from 6 to 7.5 is a non-issue. Change them from parallel to server, why? Is your licensing different and doesn't include parallel? ...

What do you mean, column name? Are you talking about during the actual SQL execution? It's too late. If you need the before-image of a row you need to update, use a reference lookup of some fashion and make the new data and the current data available in the transformer in order to do the logic you d...

You can't have two statements. The data streaming to this stage uses prepared SQL, so you're going to have to move the DELETE to another stage or job. You'll probably be able to move back to generated SQL then to handle your inserts.

You can always use the CONVERT statement , which is rather cool. It takes a string of characters and changes the each value to a correlated value in another string. Example: CONVERT "ABC" TO "123" IN yourstring This would change all occurrences of "A" to a "1", "B" to a "2", and ...

Your node that holds the DSEngine is probably slammed, your job control is timing out in its request to run a job. Think of it this way, the API sends a message to the engine process to please start the job, the engine doesn't acknowledge the message, the API times out. The only reason the engine pr...

See here

http://www.dsxchange.com/viewtopic.php?t=96215

sqlplus is not in the path for the DS engine process. Check the path in the dsenv file in the DSEngine directory. The DS engine was started without the path in the environment file that can find the Oracle binaries. Fix that and you fix your problems. The other method is to reference the binaries di...

The ONLY method you should use to stop a job in an emergency is the unix kill command. You are lucky you didn't corrupt your DS project with the things you did. NEVER attempt those things unless you absolutely understand the internals. You are lucky you didn't really screw things up. To stop a job, ...

Well, the OCI has TRUNCATE then INSERT load method, before/after SQL, and a few other Oracle specific options. It also handles DATE datatype the best of all stages, has the most comprehensive wizard if your SQL skills lack, and it is probably the stage that Ascential has spent the most time developi...