My Oracle Support Banner

E1: DB: "INVALID UTIME" in UTB or ActiveConsole.Exe / UTB.exe Crash with Error "Buffer overrun detected" When Fetching Any Record with UTIME Seconds Value =32 Seconds. (Doc ID 2284455.1)

Last updated on AUGUST 29, 2022

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.97 and Prior and later
IBM i on POWER Systems


When trying to view a record from a table in Universal Table Browser (UTB) that has UTIME type field , UTB  will either crash or display INVALID UTIME  while fetching a record whose UTIME column's time seconds value is "32" seconds. If using other windows  fat client processes such as a UBE running locally or an Interactive Application running on windows fat client, either the fetched value will be blank or NULL or Activconsole.exe will crash with error "Buffer Overrun Detected" for the same record. 

This issue is specific to Fat clients(Windows Development Clients) and occurs only for data stored in ISeries DB2 Database . 

In example below, the table has UTIME value ="2015-01-29-05:17:32.000000" as seen in database using client access or STRSQL commands 

When viewed in UTB , instead of correct Date and time we see INVALID UTIME. 

If the milliseconds value is greater than 0 and seconds value is 32 seconds , then a crash will be observed either in UTB or in ActivConsole.exe.

If the seconds value is not equal to 32 seconds then the correct value will be displayed .


As a result of this problem R9861101 report is not able to  successfully purge records from F9563110 Table . Jobs whose RJRPDSBTUT value contains "32" seconds will not be deleted from Tables. 

 Other symptoms may occur if time related fields are required, as these entries will exist.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.