Hi All,
i am able to read the data using SAS code but the table doesn't appear under library.
also in SAS SMC while i try to register the table it doesn't appear there.
LIBNAME MX ODBC DSN="UAT01"
USER="uatxyz" PASSWORD="Uat@abc" SCHEMA="uat01";
proc sql;
connect to odbc(user=uatsuper password=Uat@abc dsn=UAT01);
create table work.job204 as
select * from connection to odbc
(select * from TANGOUAT.UAT01.JNL_ACQ);
quit;
what can be the reason behind this ?
Regards,
Ashish
>but table doesn't appear under library<
What library?
The MX library pointing to the external data base?
It cannot appear there since you are writing the data set to the SAS WORK library.
Change WORK.job204 to MX.job204, and you'll see it under MX - provided, of course, that you have a write access to the data base schema defined in your LIBNAME statement and your query actually runs.
If you expect to see it in the SAS WORK library, it should be there with your code as is, as long as your query runs error-free.
Kind regards
Paul D.
Yes, The MX library pointing to the external data base. Job204 is already exists in external DB schema. Once we execute Libname statement have external data sources references it executed successfully. But still data set in MX library is not visible. Ideally it should visible post assigning libref MX.
Secondly when we execute following command:
data work.abc;
set MX.job204;
run;
it also executed successfully.
Define "visible".
What kind of SAS user interface (UI) do you use to make it "visible"?
Native DMS? EGuide? SAS Studio?
In any case, if the data set in the library with the libref MX is visible to your SAS program (i.e. it can read it), as it appears to be the case, but not visible through the UI, it's an issue to be raised with your SAS admin or DBA or both.
Kind regards
Paul D.
Thanks Paul for your prompt response..
Yes data set appears as you mentioned, but through UI it doesn't appear.
I am raising a ticket for the same in SAS support.
Regards,
Ashish
I can't see anywhere in your LIBNAME where you are defining the database TANGOUAT. Is that defined in your DSN? If not then you might need to add a database = TANGOUAT parameter to your LIBNAME.
Have you got the solution for the issue ?
We are facing the same in our environment.
Hi folks,
You have the solution for this issue? We have the same problem on our new environment.
Regards,
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.