topic Re: waitfor after connect oracle in SAS Procedures

waitfor after connect oracle

GeorgeSAS — Thu, 07 Sep 2017 23:55:28 GMT

Hello all;

How to use waiting method wait for the oracle task finish?

*---start from PC SAS;

%put this is pc sas;


*----the oracle connection will create oraclelib.two

PROC SQL; CONNECT TO ORACLE AS ORA (USER="&user" PASSWORD="&pass" PATH = PA); EXECUTE (BEGIN CODE.CREATE_SASDATA.THREE('SASA',&sdate.,'Y'); END;); QUIT; 
*----------need to wait here until last step finish,then can run the next data step;

 data after_oracle; 
infile ORACLELIB.two; 
input a $100;
run;

Thanks!

Re: waitfor after connect oracle

SASKiwi — Fri, 08 Sep 2017 00:21:43 GMT

You don't need to do anything. SAS's default behaviour is to wait until the Oracle step has completed.

Also if you are reading an Oracle LIBNAME connection the correct syntax is:

 data after_oracle; 
  set ORACLELIB.two;
run;

Re: waitfor after connect oracle

GeorgeSAS — Fri, 08 Sep 2017 16:49:20 GMT

Thank you!

More to the topic, how to do if I want the last data step runing WITHOUT waiting for oracle finish?

Thanks!

Re: waitfor after connect oracle

SASKiwi — Fri, 08 Sep 2017 22:25:33 GMT

Run the Oracle update job separately from your Oracle read job. These could be two separate SAS batch jobs, or two separate EG sessions each running one of the jobs for example.

Re: waitfor after connect oracle

GeorgeSAS — Mon, 11 Sep 2017 18:51:37 GMT

Is that possible to run these in same session? just add some SAS option ?

Thanks!

Re: waitfor after connect oracle

SASKiwi — Tue, 12 Sep 2017 20:45:22 GMT

Yes it is possible to do this but not with a SAS option. Running SAS jobs in parallel rather than one after the other is not straightforward.

Personally I think the best way of doing this is to use a SAS product called SAS/CONNECT. This software allows you to start multiple SAS sessions from within the one SAS job so you can run any task in parallel.

If you don't have SAS/CONNECT you can start the parallel SAS sessions by using the X command: X 'SAS.EXE -sysin "Secondprog.sas" '; I wouldn't recommend this approach as it's pretty clunky and hard to get right. The SAS/CONNECT approach is way better.