SAS Job Fails with 'SAS may not be installed or configured correctly on the PSUB server' (Windows Backend)
(Doc ID 1535297.1)
Last updated on JULY 29, 2019
Applies to:Oracle Clinical - Version 4.6.4 to 4.6.6 [Release 4.6.4 to 4.6.6]
Information in this document applies to any platform.
QUESTION 1 :
OC 4.6.4+ / Windows Backend : run the Data Extract job which automatically kicks off the SAS job. This was not the case in the previous releases on Windows.
Why is this ?
QUESTION 2 :
Data Extract runs two batch jobs. The first job (Data Extract) finishes successfully while the second job (Sas) fails with the following error :
Connected to database.
Database state set to P
Starting 3GL command...
3GL/PLSQL Command started. PID saved.
'sas' is not recognized as an internal or external command,
operable program or batch file.
Error:Command exited with FAILURE status. Exit code=1
SAS may not be installed or configured correctly on the PSUB server
Completed with FAILURE status.
Can the second batch job be disabled in a similar way to what is documented in Note 1383638.1 - Can the Second Data Extract Job (SAS) Be Disabled ? (Unix specific note)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document