E-IB: Publish Dttm Shows Unexpected Hours of Difference from Creation Dttm and Last Upd Dttm in a Receiving PeopleSoft System (Doc ID 2050362.1)

Last updated on SEPTEMBER 01, 2015

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.52 to 8.53 [Release 8.4]
Information in this document applies to any platform.

Symptoms

On PeopleTools release 8.52 or 8.53 Integration Broker messaging service operations work fine, but inbound service operations unexpectedly have Publish Dttm with hours of difference comparing to Creation Dttm and Last Upd Dttm, even though the servers have their time synchronized and are on in the same time zone, and the incoming data have the OrigTimeStamp parameter matching the transaction time and correctly indicating the timezone offset, for example for transaction logged at the Integration Gateway running in Eastern Time with time stamp "2013-02-25 10:45:06.031" have the OrigTimeStamp is "2013-02-25T10:45:05.000-0500".

The expectation is that the Publish time Creation time and Last Update times in such conditions should match (be close to each other, with difference no more than seconds or at most minute or two), but in practice they have hours of difference, which is raising concerns about the system's correct functioning.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms