SAS data set => Planned Outputs : How to disable 'Automatic Table Instance Creation' for 'Temporary Targets'.
Last updated on DECEMBER 05, 2016
Applies to:Oracle Life Sciences Data Hub - Version 2.2.1 and later
Information in this document applies to any platform.
a SAS program is maintained that includes a temporarily created SAS table.
this SAS table is neither meant to be visible in the workarea nor should a table descriptor be created.
It is solely used to do some sort of comparison during the complex SAS program run.
Unfortunately this target description leads to unwanted attempts
- to create a table instance to house the data
- to create a table descriptor to map to the program.
The behavior is documented in the chapter "Writing SAS Primary Source Code" of the manual :
Oracle® Life Sciences Data Hub Application Developer's Guide
Release 2.2/Oracle® Life Sciences Data Hub
Application Developer's Guide
under "Planned Outputs" i.e.
<-- START -->
If the required Output is a SAS data set, Oracle LSH can generate a Planned Output if the SAS Program's validation status is Development. You must define the new SAS
data set inside the library named "Target". Oracle LSH then treats the Output data set as the SAS Program's target Table. The system compares the SAS data set filenames
with those of the target Table Descriptors and if they match, loads data from the SAS
data set into the mapped Table instance.
If the system does not find a target Table Descriptor, it checks out the Program, adds a new target Table Descriptor to it, creates a new Table instance in the Work Area and
maps it to the newly created target Table Descriptor before installing the Program and the Table instance. Data is then loaded from the SAS data set into the mapped Table
instance. Oracle LSH triggers separate jobs for each of these processes. The system does not support Proc SQL and Insert commands in the generation of unplanned data set Outputs.
<-- END -->
Unfortunately there is no information in the documentation on how to Switch that off in case it is not wanted.
- Is there a way to switch this behavior of in case it is not wanted?
I think the behavior is different if the Validation Status is not "Development", but unfortunately we can't simply change that because of our study LifeCycle definitions.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms