Problem Note 70049: A floating point exception error occurs when using PROC METALIB
When you register a database library table in SAS® Management Console on SAS® 9.4M8 (TS1M8) using any SAS/ACCESS engine, a floating point exception error similar to the following occurs:
NOTE: The autoexec file, C:\SAS\Config\Lev1\SASApp\WorkspaceServer\autoexec.sas, was executed at server initialization.
1 LIBNAME myora ORACLE PATH=exadat USER=user-name PASSWORD=password ;
NOTE: Libref MYORA was successfully assigned as follows:
Engine: ORACLE
Physical Name: exadat
2
2 The SAS System 05:05 Tuesday, November 1, 2022
3 proc metalib
4 ;
4 ! omr (LIBURI="A5OPJM0F.B5000007"
5 user="sasadm@saspw" password=password
6 );
7 REPORT(type = summary out = "tab_info");
8 dbauth(dbuser="user-name"
9 dbpassword=password);
10 SELECT ("CASE_CONFIG"
11 );
12 FOLDERID = "A5OPJM0F.AA00001Y";
13 run;
ERROR: Invalid Operation.
ERROR: Termination due to Floating Point Exception
NOTE: The SAS System stopped processing this step because of errors.
NOTE: PROCEDURE METALIB used (Total process time)
Even though the error occurs in the registration log, the table is actually registered successfully.
Here are the steps to reproduce the issue on any SAS/ACCESS engine:
- Log on to SAS Management Console.
- Define a database server.
- Define a database library.
- Register a database table.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS/ACCESS Interface to Oracle | Microsoft® Windows® for x64 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows 8 Enterprise 32-bit | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows 8 Enterprise x64 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows 8 Pro 32-bit | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows 8 Pro x64 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows 8.1 Enterprise 32-bit | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows 8.1 Enterprise x64 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows 8.1 Pro 32-bit | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows 8.1 Pro x64 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows 10 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows 11 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows Server 2008 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows Server 2008 R2 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows Server 2008 for x64 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows Server 2012 Datacenter | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows Server 2012 R2 Datacenter | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows Server 2012 R2 Std | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows Server 2012 Std | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows Server 2016 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows Server 2019 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Microsoft Windows Server 2022 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Windows 7 Enterprise 32 bit | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Windows 7 Enterprise x64 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Windows 7 Home Premium 32 bit | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Windows 7 Home Premium x64 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Windows 7 Professional 32 bit | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Windows 7 Professional x64 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Windows 7 Ultimate 32 bit | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Windows 7 Ultimate x64 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
64-bit Enabled AIX | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
64-bit Enabled Solaris | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Linux for x64 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
Solaris for x64 | 9.45 | 9.45 | 9.4 TS1M8 | 9.4 TS1M8 |
*
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 register an library table in SAS Management Console, a floating point exception error occurs. Even though the error occurs in the registration log, the table is actually registered successfully.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2023-05-23 10:12:20 |
Date Created: | 2023-04-25 15:09:50 |