Usage Note 24544: Unable to import tables after creating an Oracle library in SAS Management Console, yet the library assigns successfully in Base SAS
 |  |  |  |
Receiving "ERROR: The SAS/ACCESS Interface to ORACLE cannot be loaded. The SASORA code appendage could not be loaded." after creating an Oracle library in SAS Management Console. If you copy the LIBNAME statement from SAS Management Console and submit it from a SAS session in Base SAS, it works.
The Oracle client installer for Microsoft Windows does not correctly set the permissions on the ORACLE_HOME directory. The value ”Everyone” is not included on the Security Tab, which means that only Administrators can access the executables. To resolve the permissions problem, make sure that users have 'Read and Execute' permissions on the ORACLE_HOME folder. You can set the permissions values by following these steps:
1. Right-click the ORACLE_HOME directory in Windows Explorer.
2. Select Properties from the drop-down list.
3. Click the Security tab in the Properties window.
4. Select Add. Type ”Everyone” and select Check Names. Click OK.
5. After you add the value ”Everyone” to the Group and user names, make sure that ”Everyone” has ‘Read and Execute’ permission.
6. Now, select “Everyone” again from the Group or user names, and click Advanced(for special Permission or for advanced setting).
7. Verify that the value “Everyone” is selected and it has full control.
8. Click the check box Replace permission entries on all child objects with entries shown here that apply to child objects.
2. Select Properties from the drop-down list.
3. Click the Security tab in the Properties window.
4. Select Add. Type ”Everyone” and select Check Names. Click OK.
5. After you add the value ”Everyone” to the Group and user names, make sure that ”Everyone” has ‘Read and Execute’ permission.
6. Now, select “Everyone” again from the Group or user names, and click Advanced(for special Permission or for advanced setting).
7. Verify that the value “Everyone” is selected and it has full control.
8. Click the check box Replace permission entries on all child objects with entries shown here that apply to child objects.
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | SAS/ACCESS Interface to Oracle | Microsoft® Windows® for 64-Bit Itanium-based Systems | 9 TS M0 | |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9 TS M0 | |||
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9 TS M0 | |||
| Microsoft Windows 2000 Advanced Server | 9 TS M0 | |||
| Microsoft Windows 2000 Datacenter Server | 9 TS M0 | |||
| Microsoft Windows 2000 Server | 9 TS M0 | |||
| Microsoft Windows 2000 Professional | 9 TS M0 | |||
| Microsoft Windows NT Workstation | 9 TS M0 | |||
| Microsoft Windows Server 2003 Datacenter Edition | 9 TS M0 | |||
| Microsoft Windows Server 2003 Enterprise Edition | 9 TS M0 | |||
| Microsoft Windows Server 2003 Standard Edition | 9 TS M0 | |||
| Microsoft Windows XP Professional | 9 TS M0 | |||
Receiving "ERROR: The SAS/ACCESS Interface to ORACLE cannot be loaded. The SASORA code appendage could not be loaded." after creating an Oracle library in SAS Management Console.
| Type: | Usage Note |
| Priority: | low |
| Date Modified: | 2008-02-19 14:51:14 |
| Date Created: | 2006-10-06 13:34:38 |