|
PureBytes Links
Trading Reference Links
|
BMI users *Pay Attention* something caused the Midnight System Check to
occur about an hour early (23:01:21 EDT) - possibly a bad timestamp or other
undocumented TS4 feature and rather than a "10/27 Glitch" we got a "10/26
Glitch" so all servers are probably set to one day ahead.
You will need to Shutdown and Restart the TS4 server and then
Delete all data for 10/26/2001 by
1. Selecting Server | File | Delete
2. Checking only "intraday"
3. Setting "Start Date" and "End Date" to 10/26/2001
4. Select "Add all"
5. Select "OK"
Alternatively, you can replace the "full deletion" procedure by deleting
individual ticks. To find out which symbols are affected you can Copy Out
all of the 10/26/2001 tick symbols to a file and then Paste the file back in
using "Custom Paste". The Symbols shown are the only ones containing
10/26/2001 data. Cancel the Paste In procedure and delete the individual
ticks from the symbols that were shown. Delete from the first tick until
the recorded time starts and continues increasing. In my case there were a
lot of "23:59" times at the start of the tick file. Just select the first
tick to be deleted and delete it then just hold the keyboard ENTER key down.
The following is the a copy of my "Glitch Check Log" when the problem
occurred with the left side time being PDT and the right side being datafeed
time.
10/25/2001 20:01:21 - 10/25/2001 23:01>Midnight system check
10/25/2001 20:18:19 - 10/26/2001 23:18>Building schedule table...
~Bob
-----Original Message-----
From: multitrak@xxxxxxxxxxxxxxxx <multitrak@xxxxxxxxxxxxxxxx>
To: omega-list@xxxxxxxxxx <omega-list@xxxxxxxxxx>
Date: Thursday, October 25, 2001 9:35 PM
Subject: Re: Check your Server Dates - Something fishy going on here
>Nothing fishy other than another BMI bad date; check your server
>log. Apparently the 10/27 bug struck early this week :-)
>
>Just delete bad data and reboot.
>
>MT
>
>
|