It makes a developer's life harder if one can't directly access a DB via a client. IF you've got the credentials the SAS library uses to access Oracle then the easiest way would be to get a client like DBeaver or SQL Developer. There are portable versions around so it's software you can just download and use even if you can't install software on your local machine.
If you're using a pre-assigned SAS library and though might not know the credentials then you can still query Oracle directly.
Let's assume the libref of your pre-assigned library a blah.
The following statement writes the library definition to your SAS log - one component of it is the Oracle schema name.
libname bla list;
You can also determine the schema name with below syntax.
%let ora_schema=;
proc sql noprint;
select sysvalue into :ora_schema trimmed
from dictionary.libnames
where
libname="BLAH"
and sysname='Schema/Owner'
;
quit;
%put &=ora_schema;
You can issue explicit Oracle SQL syntax out of SAS to query Oracle dictionary tables and so derive the DDL of a table.
proc sql;
connect using blah;
select * from connection to bla
(
<Oracle SQL syntax to be Googled>
);
disconnect from blah;
quit;
How the Oracle syntax needs to look like so it works for you (also dependent on the permissions your Oracle user has) is something you need to Google. A very quick try led me to this link.