Hi Jakarman,
I am running with similar issue.
I have set up SAS library(abc) in SAS SMC for oracle schema. This schema name called ‘ABC’ in Oracle server database(port opened and updated tnsnames.ora with path name details).
Created user group with ‘OraAuth_ABC’ domain added old schema user name and PW then added users.
Path name been defined in server connection and selected OraAuth_ABC domain for authentication field.
Library created : schema name added, selected the oracle connection and selected the username(OraAuth_ABC) for authentication.
Last week I have create another SAS library(xyz) for different schema called ‘XYZ’ (same tables for more data) which exist in same DB server same as above and domain:‘OraAuth_XYZ’ and different user id and PW for XYZ schema.
Users are able to access data from both abc and xyz libraries using SAS data and proc steps when users explicitly referred abc.table or xyz.table library names.
Issue: when users run pass through code to read from XYZ schema, the data is pulling from ABC schema.
If users access table from SAS Data step and Prod step by referring libref xyz.table then the data is coming for 201611 and 201612.
When user run pass through code for 201611, 201612 and 201701 data, as below code result is 0 records which means its pointing to old abc schema.
Pass through code for Last week set up library:
proc sql;
connect to oracle as edw(AuthDomain=OraAuth_XYZ path=Path);
create table test as Select * from connection to xyz
(select distinct(ID) from table
Where date=201611);
disconnect from xyz;
quit;
is this default behavior? why the above code is point to old schema table? am i mssing anything? shoudl i need to mention schema name?
... View more
