Problem Note 61266: Time zone offset values do not trigger the rollover of IOM server logs
The trigger that controls when the IOM server log files should be rolled over is not taking the time zone offset values into consideration when calculating the next trigger. This behavior causes log files to be rolled over very rapidly after the day changes, creating many unnecessary log files.
The behavior can occur with the metadata server, object spawner, stored process server, and pooled workspace server log files.
To circumvent this problem, edit the param name value in the logconfig.xml file located in the directory associated with the server from "true" to "false":
change: <param name="Unique" value="true"/>
to: <param name="Unique" value="false"/>
Note: This issue is fixed in Threaded Kernel Log for SAS® 9.4M5A . To find your Threaded Kernel Log for SAS release, view the deployment registry as documented in SAS KB0036131.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | N/A | Windows 7 Ultimate x64 | 9.4 TS1M5 | 9.4 TS1M5 |
Windows 7 Ultimate 32 bit | 9.4 TS1M5 | 9.4 TS1M5 |
Windows 7 Professional x64 | 9.4 TS1M5 | 9.4 TS1M5 |
Windows 7 Professional 32 bit | 9.4 TS1M5 | 9.4 TS1M5 |
Windows 7 Home Premium x64 | 9.4 TS1M5 | 9.4 TS1M5 |
Windows 7 Home Premium 32 bit | 9.4 TS1M5 | 9.4 TS1M5 |
Windows 7 Enterprise x64 | 9.4 TS1M5 | 9.4 TS1M5 |
Windows 7 Enterprise 32 bit | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows Server 2016 | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows Server 2012 Std | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows Server 2012 R2 Std | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows Server 2012 R2 Datacenter | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows Server 2012 Datacenter | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows Server 2008 for x64 | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows Server 2008 R2 | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows Server 2008 | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows 10 | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows 8.1 Pro x64 | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows 8.1 Pro 32-bit | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows 8.1 Enterprise x64 | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows 8.1 Enterprise 32-bit | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows 8 Pro x64 | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows 8 Pro 32-bit | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows 8 Enterprise x64 | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft Windows 8 Enterprise 32-bit | 9.4 TS1M5 | 9.4 TS1M5 |
Microsoft® Windows® for x64 | 9.4 TS1M5 | 9.4 TS1M5 |
z/OS 64-bit | 9.4 TS1M5 | 9.4 TS1M5 |
z/OS | 9.4 TS1M5 | 9.4 TS1M5 |
64-bit Enabled AIX | 9.4 TS1M5 | 9.4 TS1M5 |
64-bit Enabled Solaris | 9.4 TS1M5 | 9.4 TS1M5 |
HP-UX IPF | 9.4 TS1M5 | 9.4 TS1M5 |
Linux for x64 | 9.4 TS1M5 | 9.4 TS1M5 |
Solaris for x64 | 9.4 TS1M5 | 9.4 TS1M5 |
*
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.
The trigger that controls when the metadata log file should be rolled over is not taking the time zone offset values into consideration when calculating the next trigger.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2018-07-23 10:43:18 |
Date Created: | 2017-10-19 13:07:15 |