DSXchange

sure, they are just refreshing of materialized views in Oracle. CALL DBMS_SNAPSHOT.REFRESH ('DM_APSDM.MAT_View_1','C');; CALL DBMS_SNAPSHOT.REFRESH ('DM_APSDM.MAT_View_2','C');; CALL DBMS_SNAPSHOT.REFRESH ('DM_APSDM.MAT_View_3','C');; CALL DBMS_SNAPSHOT.REFRESH ('DM_APSDM.MAT_View_4','C');; COMMIT;;...

yes correct, it should be before, instead of after , though, ............ after the Multiple instance job been executed n time. How does the Multiinstance job been executed / Called? the multiinstance job is called in a job control datastage basic program, it is a daemon that runs and waits/sleeps a...

Hi Kumar, thank you very much for the quick reply, I think I wasn't very clear about the case, the thing is that I don't need to call the multi-instance job, I need to call my small job for one time only. i.e., lets say multi-instance job run for 5 different invocation IDs everyday but I still want ...

I need to call a few Oracle commands one time for a multi-instance job, I created a simple job which consist of an oracle stage and dummy file, and I put my commands in the oracle stage, now I need to call this job after a job which is multi-instance. there is no sequencer for this job and I should ...

There is a WaitForFile stage in sequence jpbs, you can create a master sequence and use a waitforfile activitiy stage and kick your main job/sequence

how about changing the password?

if you really want to use that stage variable in an SQL, you might be able to, (depending on the SQL you are trying to execute,) :

try to convert the sql into routine or function or implemet inside the transformer with the help of transformer functions, new stage variables.

My Target is an UDB table and I wanted to run a SQL using the stage variable from the transformer stage to update another control table. No, you cannot refer a stage variable outside of the current transformer. you can write the value of that stage variable in a flat file or an hash file and then u...

chulett wrote:Such as?

it will be a naive way but you can make the job aborted when he tries to run with his username. for other users the jobs can run without abort.

is there a limited number of jobs you don't want that operator to be able to run, or is it all the jobs? if it is the first case you can do some workaround.

...I'll have to figure out a way to easily compare the list of files. put both lists into two different sequential file, create a small datastage jobs and use one file as your input and the other as a look up and your unmatched rows will be the difference. or write a minus query if you can import t...

I think (not 100% sure), it will read the files one by one, not in parallel.

a naive workaround would be to try to use one basic and then a PX transformer or the other way around.

the files might have been deleted prior to the backup. what do you mean that when the DS working, does it mean you were able to connect to the DataStage server, because you won't be using those files when you just connect or compile a job.

There might be some space or other invisible characters before or after the actual value of the columns, for that reason you should use trim function for both the main input columns as well as the look up columns.