- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I am trying to access Oracle database from SAS Server through ODBC Connectivity.
From Putty,I login to SAS Server and I created a ODBC Connection to connect to Oracle DB and I can able to view the tables.
But While registering the tables in SAS management console(after creating the library).I am getting the following error:
"No tables were retrieved from this query.Your connection information were incorrect"
When I opened the SAS log,
NOTE: SAS Initialization used (Total process time):
real time 0.00 seconds
cpu time 0.00 seconds
NOTE: The autoexec file, /SASINST/ediserver/Lev1/SASApp/WorkspaceServer/autoexec.sas, was executed at server initialization. No
server log was specified. Add the log option to the server startup command to see details of the autoexec execution (refer
to "Specifying Logging Options" under "Server Startup Command" in the Server Administrator's Guide).
LIBNAME prodlib ODBC DATASRC=PROD SCHEMA=PROD_STG USER=PROD_STG PASSWORD=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ;
NOTE: Libref PRODLIB was successfully assigned as follows:
Engine: ODBC
Physical Name:PROD
Library is successfully assigned,I dont know why I am getting the error.
Kindly help me on this.Thnks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
I am also experiencing the same for Oracle. This works for some oracle databases, but others are giving us the error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
We determined that reason for our error was because or DataDirect driver was not compatable with our Oracle version. Once we upgraded Oracle to a newer version our issue was resolved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Did you add schema='DBO' libname option ?
Xia Keshan
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
No. The schema was not DBO. We used the correct schema for our Database. The issue was resolved once we upgraded oracle to a version compatable with our version of data direct.