My Oracle Support Banner

Background Processor Jobs Created by System Task Server Complete Late when AppServer and Database are Configured with Different Time Zones (Doc ID 2982841.1)

Last updated on OCTOBER 27, 2023

Applies to:

Oracle Communications MetaSolv Solution - Version 6.3.1 and later
Information in this document applies to any platform.


Background Processor jobs created by the System Task Server are completing late - in this case 1 hour. The behavior occurs when the AppServer and database are configured with different Time Zones (not in same Time Zone).

The physical machine hosting AppServer is set to "Eastern Time Zone" and the MetaSolv Solution AppServer Runtime Information page shows "user.timezone = America/New_York" listed under "Java System Properties". However, the physical machine hosting the Oracle database is configured as "Central Time Zone" and the application's "System Information > Database Server Time Zone" system preference is configured with a KEY_VALUE TM_ZONE_ID that equates to "(UTC-06:00) Central Time (US & Canada)".

When the System Task Server creates a Background Processor "Task completion" job for the DD task, the job's JOB.JOB_QUEUE.JOB_POSTED_DATE and JOB.JOB_QUEUE.JOB_SCHEDULED_DATE values are future dated by 1 hour and based on the local time of the AppServer. Because of this, the jobs remain in a "Ready for Execution" status for 1 hour waiting for their scheduled time. This behavior only appears to impact Background Processor jobs created by the System Task Server (JOB.JOB_QUEUE.UID_REQUESTING_JOB = 'WM_TSKSV'). Task completion jobs submitted by application users have the correct date/timestamp values.



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.