DSXchange

If you use search, you can see that every post stresses that if you reindex while users are logged in you will get exactly the error that you are seeing. Log everyone out and reindex again to make these jobs reappear.

The ODBC_Connector_108 stage has the string "
-XMLProperties '<?xml" which seems to trigger the error message at compilation. Is the "<" properly quoted so that it isn't interpreted as a redirection command?

The normal type will load the whole result to DataStage and use that for looking up each row. The sparse will do a singeton lookup for each data row. Unless you only have a few rows coming in your data stream, or you might be changing the lookup column values while the job is running and need the ne...

What happens when you try to open the jobs? Does it hang or do you get an error message? You can't open in the designer but can't see in the manager? Do you `see' any jobs at all in the manager? Has someone tried to re-index the project?

If they are independant in the job then you cannot control the execution order. If you need to do so, split the logic into 2 jobs and call them from a job sequence.

Put a constraint of "1=2" onto the transform stage output writing to your Oracle stage and run the job. Better yet, make a copy of your job and keep only your source stage and write the result to a sequential file at /dev/null to see how long your select takes to execute in the real job, not just th...

I wonder if it doesn't like the "age" column name - could you try using another label as a test?

I've been getting network timeouts all day here - but I don't remember trying to re-post this one. Too late to delete the duplicate now as well. I suppose that this is one way to rack up some serious points.

We have a number of files coming in (from the phone switches) with call information. Some files are just a couple of rows, others have hundreds of thousands. The PX job that processes these files uses a lot of lookup filesets and lookups to database tables - the startup time to load this information...

The format "ORCHESTRATE.age" is the correct one. What happens if you mark age as key and let DS auto-generate the SQL - does that compile and run correctly? Perhaps it is the BETWEEN statement and syntax and not the use of your token that is generating your error.

Remove the 'load' part, make the job write to /dev/null. If it still hangs, you know it is an issue on your extract, perhaps a very lenghty select. If it runs, then the issue is probably on your load stage. Some more details on the stage types involved in the source and target would make solving the...

Remove the 'load' part, make the job write to /dev/null. If it still hangs, you know it is an issue on your extract, perhaps a very lenghty select. If it runs, then the issue is probably on your load stage. Some more details on the stage types involved in the source and target would make solving the...

I have a PX job which has a named pipe as the input stream and which processes a lot of data during it's lengthy run. One of the columns in this file is "FILE_ID", which contains the reference to the actual source file. Due to the large amount of data (over a hundred million rows per day) I would li...

kcbland wrote:Just use CALL DSExecute(...)...

I guess I'm just too `olde skool' and used to using the direct call. You are correct, DSExecute is the correct routine to call.

Your approach is similar to what happens with database sequences - by changing the sequence 'cache size' you pre-allocate blocks of sequence numbers so that you don't need to get back to the database as often, with the downside that you might lose much of a cach block of sequence numbers if the job ...