Oracle (and any other DBMS I know of) does not have the concept of macro variables. If you use explicit pass-through, you have to convert the code to Oracle standards first, and have macro variables resolved to Oracle-compatible formats.
Are you sure that the Oracle side will understand a SAS MACRO variable of form '21JAN19'd?
I don't use Oracle but have seen a number of questions here about passing macro values to Oracle that make me believe this may not be appropriate.
It would likely help those who know more about Oracle than I do to include your connection info and the code using this macro variable. XXXX out anything like user or password in the connection.
Oracle (and any other DBMS I know of) does not have the concept of macro variables. If you use explicit pass-through, you have to convert the code to Oracle standards first, and have macro variables resolved to Oracle-compatible formats.
Don’t miss the livestream kicking off May 7. It’s free. It’s easy. And it’s the best seat in the house.
Join us virtually with our complimentary SAS Innovate Digital Pass. Watch live or on-demand in multiple languages, with translations available to help you get the most out of every session.
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.
Ready to level-up your skills? Choose your own adventure.