|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Monitoring Timezone logging in TZ 0 |
« View previous topic :: View next topic » |
Author |
Message
|
GARNOLD5551212 |
Posted: Mon Nov 11, 2013 8:18 am Post subject: Monitoring Timezone logging in TZ 0 |
|
|
Novice
Joined: 23 Jul 2013 Posts: 13
|
We've setup Record/Replay for Monitoring on nodes and it is capturing all the Event Names correctly to our DB. The problem is that in the WMB_MSGS table in the Event_Timestamp (Type VarcChar2) the time is being logged in GMT TZ = 0. We would like it to be logged in the TZ of the system WMB is running on. Checked the system, the DB, the user WMB is running in and the locale is set correctly. Is there a setting in WMB that needs configured? I've looked 8.0 documentation and have not found any clues.
OS: AIX V6
WMB 8.0.0.2
Oracle 11
TZ=CST6CDT |
|
Back to top |
|
 |
kimbert |
Posted: Mon Nov 11, 2013 12:34 pm Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
I don't know of any such feature. The monitoring event messages themselves use GMT always - by design.
Quote: |
The problem is that in the WMB_MSGS table in the Event_Timestamp (Type VarcChar2) the time is being logged in GMT TZ = 0 |
That is not a 'problem'. It is good design to log timestamps in GMT, and only convert to the local time zone when displaying. Any other strategy is fragile.
Quote: |
We would like it to be logged in the TZ of the system WMB is running on |
I bet that the real requirement is to *view* the timestamps in the local time zone. _________________ Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
Back to top |
|
 |
GARNOLD5551212 |
Posted: Mon Nov 11, 2013 12:38 pm Post subject: Known bug IC90347 fixed in 8.0.0.3 |
|
|
Novice
Joined: 23 Jul 2013 Posts: 13
|
IC90347: Web user interface shows event time as GMT.
In my case I'll have to wait for 8.0.0.4 because of hot fixes we had added to 8.0.0.2 or get another hot fix built. Will work out with Crit Sit team. |
|
Back to top |
|
 |
GARNOLD5551212 |
Posted: Mon Nov 11, 2013 1:17 pm Post subject: |
|
|
Novice
Joined: 23 Jul 2013 Posts: 13
|
Kimbert,
You are correct that I need to view/select based on current TZ. The date is stored as time without TZ information, so I'll have to cast knowing it is in GMT.
Since I am using this table to write health monitors against I'll have to convert my current system time to GMT before I do my timestamp math with the stored values.
Convert WMB Time to local time.
cast(cast(to_timestamp(A.event_timeStamp,'YYYY-MM-DD HH24:MI:SS.FF') at time zone 'Etc/GMT-0' as timestamp) at time zone 'America/Chicago' as timestamp)
Get Last 15 minutes of started xtns
select local_transaction_id
from WMB_MSGS
where event_type = 'TransactionStart'
and MSGFLOW_NAME = 'MF_OMS_TO_OMNIA_ORD_RLS'
and to_timestamp(event_timeStamp,'YYYY-MM-DD HH24:MI:SS.FF') > systimestamp at time zone 'GMT' - 15/(24*60) )
Thanks for the clarity, just needed to think about it the right way. |
|
Back to top |
|
 |
GARNOLD5551212 |
Posted: Mon Nov 11, 2013 2:02 pm Post subject: |
|
|
Novice
Joined: 23 Jul 2013 Posts: 13
|
Wrong forum, but just wanted to correct this trail. My SQL was wrong. Timestamps are different than sysdates.
( select B.local_transaction_id
from WMB_MSGS B
where B.event_type = 'TransactionEnd'
and B.MSGFLOW_NAME = 'MF_OMS_TO_OMNIA_ORD_RLS'
and to_timestamp(B.event_timeStamp,'YYYY-MM-DD HH24:MI:SS.FF') > systimestamp at time zone 'GMT' - INTERVAL '0 00:15:00.0' DAY TO SECOND(1) ) |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|