DSXchange

thanks,I'll try from the export. resetting is not enough, what's happening is that processes still hang, so a reset is not enough(next run will give unable to run on basic transformer stage, while status looks ok). Have a case open for this with datastage, who allready admitted it's a bug and are wo...

ArndW, indeed for getting the logentries I will use dsjob, compile is something I will only do after failures(we have a problem with basic-transformers that keep hanging, solution is unlock all + compile). Main question is however : How do i find all jobs within a workflow , I don't see this in dsjo...

Hi, For several reasons I would like to make a script that can get all jobnames that are run in a workflow. If we have this list we can do things like : -dump relevant loggings into one logfile -compile all these jobs -check if one of the jobs is running now, before starting the flow(maybe only for ...

When using the Sybase OC stage to read data there is the option to work parallel (stage-advanced tab, execution mode). In the oracle stage there is something likewise, but there you have some control about how it will run parallel because it askes for a partition table. In sybase we don't seem to ha...

ray, as far as I know in Oracle you always have to trigger a refresh, in a typical DWH this is not a real problem, you load all your dimensions/facts and then refresh the MV, which will then be valid untill the next run(in our case next nigth). Solution I'm now checking is: - Created a routine that ...

hi, we're using 2 types of materialized views in oracle(10g), for snapshot refresh from other oracle DB's and for standard MV to pre-calculate views. I would like to make some kind of datastage jobs to refresh these MV's. For now a unix script is run during the datastage flow to do this, but we woul...

by setting the compiler options in the project environment to values for gcc you can get your jobs compiled.

But as discussed here: is this worth the loss of support? compared to what you pay for DS the c-compiler is not that expensive.

You can always use a basic-transformer in a parallel job, then you can just use your old routine. watch out: on the one hand DS discourages the use of the Basic transformer in PX-jobs, on the other hand they give this same solution when you're experiencing problems in C-routines and development. (I'...

hi,

this wil be heap, data, stack, shared memory, this is your swap space and will be allocated even if it is not used

at install we had problems with the memory-settings that needed to be done in uvconfig (the values coming out of the shmemtest were invalid).
Could this then be related?

untill now we've been mostly using the basic-transformer in parallel jobs.(mostly because of use of old-routines). We are now trying to change all routines to C because the use of the basic-transformer is discouraged. I'm not a c-expert, but what I gather from the example c-routine on the install-cd...

the exact message the unix-admin gets is: Apr 8 01:06:02 tnet121 genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow stack for pid 13637 (osh) (in the /var/adm/messages file). How can we check the memory reserved for OS, we see 12GB available, so that seems a lot for the OS? We u...

Hi, I got a job that was running fine, but after increasing the number of nodes it fails. By setting the sort-stages in the job to sequential it runs fine. Unix admins tell me that the server is giving errors on full-swap space when this job fails. However there is still a lot of memory available. A...

probably you didn't mention the oracle 10 at install. In the directory : $DSHOME/../PXEngine/lib you will see a lot of files linked to files in the same dir. Example for us: ls -ltr *ora* -rwxr-xr-x 1 PDdtsadm PDdtsadm 1811572 Aug 9 2004 liborchoracle8isun4.so -rwxr-xr-x 1 PDdtsadm PDdtsadm 1811792 ...

We had the same issue. I think the number of warnings per field is dependant on the number of parallel processes you define.

So set this stage to sequential and hope you need less then 50 fields. The only real solution we found is actually upgrading and use the messagehandler.

This is not what the oracle change capture does. It actually looks at the log of what happened to select the changes. So this will never need to compare the 100mlj rows after with the 100mlj before. So for large tables this will be much more performant