SUPPORT / SAMPLES & SAS NOTES
Problem Note 33995: Error: "IOM call failed. Internal server exception: floating point divide by zero."
 |  |  |  |  |
A previously working metadata server might become unresponsive to requests when an index in memory has the wrong value. If this happens, the following error is written to the metadata server log file:
ERROR: IOM call failed. Internal server exception: floating point divide by zero.
Some logs might only contain the above message while others might include traceback information, such as the following:
NOTE: Address Frame (DBGHELP API Version 4.0 rev 5) 5DEE6495 0E2FCDB4 tkbplus:tkbplus+0x153E5 5DEE4333 0E2FCDE0 tkbplus:tkbplus+0x13283 6277D431 0E2FCE0C saseimdb:mcn_main+0xC431 6277CD96 0E2FCEF0 saseimdb:mcn_main+0xBD96 6277C60F 0E2FCF74 saseimdb:mcn_main+0xB60F 6277C4EB 0E2FCFF8 saseimdb:mcn_main+0xB4EB 6277B06E 0E2FD0A8 saseimdb:mcn_main+0xA06E 5D672ABE 0E2FD12C tkesasio:tkesasio+0x1ABE 5BC47DD6 0E2FD314 tkoms:tkoms+0x76DD6 5BC37A9D 0E2FD44C tkoms:tkoms+0x66A9D 5BC164AF 0E2FD4D8 tkoms:tkoms+0x454AF 5BC155BC 0E2FD674 tkoms:tkoms+0x445BC 5BC166B3 0E2FD70C tkoms:tkoms+0x456B3 5BC1642C 0E2FD738 tkoms:tkoms+0x4542C 5BC0C7BF 0E2FD764 tkoms:tkoms+0x3B7BF 5BC54A4C 0E2FD790 tkoms:tkoms+0x83A4C 5BBE31C9 0E2FDC50 tkoms:tkoms+0x121C9 5BBDD7D8 0E2FE3FC tkoms:tkoms+0xC7D8 5BC11820 0E2FE450 tkoms:tkoms+0x40820 5BC16364 0E2FE970 tkoms:tkoms+0x45364 5BC15091 0E2FE9A0 tkoms:tkoms+0x44091 5BC0C5FB 0E2FE9CC tkoms:tkoms+0x3B5FB 5BC0C5B0 0E2FE9F8 tkoms:tkoms+0x3B5B0 5C074CFF 0E2FEAC0 tkomi:tkomi+0x2DB1F 5C078E13 0E2FEB2C tkomi:tkomi+0x31C33 5C07BBF6 0E2FED8C tkomi:tkomi+0x34A16 5C07AFE2 0E2FEE08 tkomi:tkomi+0x33E02 5C071798 0E2FEE70 tkomi:tkomi+0x2A5B8 5C03517C 0E2FF06C 0001:0000417C tkomi.dll 5C0403E8 0E2FF15C 0001:0000F3E8 tkomi.dll 5D218C13 0E2FF758 tkiompeb:tkiompeb+0x7C13 5D217660 0E2FFC7C tkiompeb:tkiompeb+0x6660 5D1A9FD2 0E2FFF3C tkiomsvc:tkiomsvc+0x8FD2 5D6A1F53 0E2FFF88 tkepdl:tkepdl+0xF53 5C8B1AA3 0E2FFFAC tkmk:tkBoot+0xA7F 5C8B295B 0E2FFFB8 tkmk:tkBoot+0x1937 77E64829 0E2FFFEC kernel32:GetModuleHandleA+0xDF
To get the metadata server to respond again, you must either pause and then resume the metadata server or to restart the metadata server.
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | SAS Metadata Server | z/OS | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft® Windows® for x64 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows 2000 Server | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows 2000 Professional | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows NT Workstation | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows XP Professional | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Windows Vista | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| 64-bit Enabled AIX | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| 64-bit Enabled HP-UX | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| 64-bit Enabled Solaris | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| HP-UX IPF | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Linux | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Linux on Itanium | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||