Problem Note 62301: You receive "Encryption error 10011...Unable to load extension: (tkersa2)" when you use PROC PWENCODE with Oracle
When you use Oracle and PROC PWENCODE with method=sas003, an error similar to the following might occur:
ERROR: Encryption error 10011 (0x271b) occurred in R_CR_random_seed at line 749, the error message is "NOT_SUPPORTED"
{SAS002}123456789abcdefghijklmn
ERROR: Encryption error 10011 (0x271b) occurred in R_CR_random_seed at line 749, the error message is "NOT_SUPPORTED".
ERROR: Encryption run-time execution error
ERROR: Unable to load extension: (tkersa2)
Usually, the error "Unable to load extension: (tkersa2)" occurs because the LD_LIBRARY_PATH does not include the path to the SAS/SECURE® directory or adding a path before it, such as the Oracle path, causes a conflict with the Secure crypto modules. This problem occurs because SAS and Oracle use different versions of the RSA Crypto-C ME libraries.
To work around this problem, set TKERSA2_LIB_PATH to point to the SAS version of the libraries located in the SASHOME/Secure/sasexe: directory.
You can set the path in your equivalent of the SASHOME/SASFoundation/9.4/bin/sasenv_local file by adding the following:
export TKERSA2_LIB_PATH=SASHOME/Secure/sasexe
You can also set the path in a CONFIG file:
-set TKERSA2_LIB_PATH SASHOME/Secure/sasexe
Operating System and Release Information
| SAS System | SAS/SECURE | 64-bit Enabled AIX | | |
| 64-bit Enabled Solaris | | |
| HP-UX IPF | | |
| Linux for x64 | | |
| Solaris for x64 | | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
When you use an Oracle database and the PWENCODE procedure with method=sas003, you receive errors. This problem occurs because SAS® and Oracle use different versions of the RSA Crypto-C ME library.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2018-05-14 13:10:35 |
| Date Created: | 2018-05-09 15:54:04 |