SAS/ACCESS to ORACLE ERROR: The ORACLE engine cannot be found.

[haibh]

NOTE: The autoexec file, /home/sas/SASConfig/Lev1/SASApp/WorkspaceServer/autoexec.sas, was executed at server initialization.
1 LIBNAME ORAREF ORACLE PATH=XEPDB1 SCHEMA=sasora USER=sas PASSWORD=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ;
ERROR: The ORACLE engine cannot be found.
ERROR: Error in the LIBNAME statement.

[carl_sommer]

Submit the following code and see if you see  the SAS/Access to Oracle engine listed

PROC SETINIT; RUN;

If your license includes SAS/Access for Oracle you should see a line like the following in the log, with a license expiration date:

---SAS/ACCESS Interface to Oracle 06FEB2024 

If you don't see the product listed, then it is not licensed and will need to your administrator or account team.

Carl Sommer

[haibh]

here is result after run:
28 PROC SETINIT; RUN;

NOTE: PROCEDURE SETINIT used (Total process time):
real time 0.00 seconds
cpu time 0.01 seconds

Original site validation data
Current version: 9.04.01M8P011823
Site name: '***'.
Site number: ***.
CPU A: Model name='' model number='' serial='+16'.
Expiration: 30JUN2023.
Grace Period: 15 days (ending 15JUL2023).
Warning Period: 17 days (ending 01AUG2023).
System birthday: 04APR2023.
Operating System: LIN X64 .
Product expiration dates:
---Base SAS Software 30JUN2023 (CPU A)
---SAS/STAT 30JUN2023 (CPU A)
---SAS/GRAPH 30JUN2023 (CPU A)
---SAS Integration Technologies 30JUN2023 (CPU A)
---SAS/Secure 168-bit 30JUN2023 (CPU A)
---SAS Enterprise Guide 30JUN2023 (CPU A)
---SAS/ACCESS Interface to PC Files 30JUN2023 (CPU A)
---SAS/ACCESS Interface to ODBC 30JUN2023 (CPU A)
---SAS Workspace Server for Local Access 30JUN2023 (CPU A)
---High Performance Suite 30JUN2023 (CPU A)
---SAS Add-in for Microsoft Excel 30JUN2023 (CPU A)
---SAS Add-in for Microsoft Outlook 30JUN2023 (CPU A)
---SAS Add-in for Microsoft PowerPoint 30JUN2023 (CPU A)
2 The SAS System 10:36 Sunday, May 28, 2023

---SAS Add-in for Microsoft Word

[AhmedAl_Attar]

Hi @haibh 

To access Oracle database tables from within SAS software, you require two components!

1. Oracle Client Software -----> Provides the required C libraries to enable third party software such as SAS to communicate with Oracle Database. This must be installed in order to enable communication with Oracle.

2. Licensed and installed/configured SAS/ACCESS Interface to Oracle -----> Establishes communication and translation between SAS & Oracle. This must be configured in order to enable connection to Oracle database.

For details, Your SAS System Administrator must checkout "System Requirements for SAS® 9.4 Foundation for Linux for x64"

Contrary to what @carl_sommer had mentioned about SAS Proc Setinit. Having the SAS/ACCESS product licensed is a must, but that does not guarantee it was installed!!

You'll need to run Proc Product_status; run;

"PROC PRODUCT_STATUS returns a list of the SAS Foundation products that are installed on your system, along with the version numbers of those products. It provides a quick method to determine whether a SAS product is available for your use. The results from PROC PRODUCT_STATUS are returned to the SAS log."

Hope this helps

[carl_sommer]

YES - what he said!

[haibh]

here is result after run :
28 proc product_status;
29 run;

For Base SAS Software ...
Custom version information: 9.4_M8
Image version information: 9.04.01M8P011823
For SAS/STAT ...
Custom version information: 15.3
For SAS/GRAPH ...
Custom version information: 9.4_M8
For SAS Integration Technologies ...
Custom version information: 9.4_M8
For SAS/Secure 168-bit ...
Custom version information: 9.41_M5
For High Performance Suite ...
Custom version information: 2.2_M9
For SAS/ACCESS Interface to PC Files ...
Custom version information: 9.4_M8
For SAS/ACCESS Interface to ODBC ...
Custom version information: 9.4_M8
NOTE: PROCEDURE PRODUCT_STATUS used (Total process time):
real time 0.20 seconds
cpu time 0.12 seconds

[AhmedAl_Attar · Accepted solution]

@haibh 

As your results shows, your company does not have SAS/ACCESS Interface to Oracle licensed! Therefore you can not use the ORACLE engine in your Libname statement(s).

You have SAS/ACCESS Interface to ODBC, which means you could connect to an Oracle Database via Oracle's or other Vendor ODBC Driver, as long as your SAS system Administrator sets-it-up/configure-it on the Linux/Unix Workspace Server

Note: The system requirements document I mentioned in my first response, has a section for SAS/ACCESS Interface to ODBC

Hope this helps