Menu
▾
▴
#109 Raw Time Report broken w/ new MC change
Please roll back the Raw Time report ASAP.
Whatever Mike Cortez asked you to change on the
RawTime report, it broken the existing one. For
example, I can no longer query for RawTime for
ScanID='00362028'
You should have develop a separate report to look up
Old ID number -> new Banner ID number instead of
trying to have the same report do multiple things.
Logged In: YES
user_id=19972
It's not MC Change, it's the broken nightly cache update
with this error in step 5 (load RptRawLogCache) since 5am
10/30. Initial investigation lead to a cause external to
TKsystem, may be from web data entry.
Violation of PRIMARY KEY constraint 'PK_RptRawLogCache'.
Cannot insert duplicate key in object 'RptRawLogCache'.
[SQLSTATE 23000] (Error 2627) The statement has been
terminated. [SQLSTATE 01000] (Error 3621). The step failed.
Logged In: YES
user_id=19972
Found the problem: When we use the ID Utility to change
00363297 to 00363237 for the ID in site 150, we now have a
bunch of double entries which has the same SiteNo, ScanID,
RecID and ClockIn... This problem is going to take a while,
for now I will just remove the constraints (the system will
be slower) to make it work...
Logged In: YES
user_id=19972
Current status: Raw Time Reports for either 00363297 to
00363237 will produce the right number of minutes but
incorrect status fields.
Same thing for 00646284 or 00626484
Further investigation reveals that TKLogProcessor is not
adjusting new numbers entered via PIDMLookupCache... Major
fix is now required... Stay tune...
Logged In: YES
user_id=19972
It's broken again, this time since there is a real person
with 00363297 (Lucy Nguyen) was loaded into the database,
all previous wrong ID of 00363297 (Frances Watts) was no
longer converted correctly to the correct number of
00363237 (Frances Watts). This is getting frustrating! If
the AS card were printed correctly then we shouldn't have
this problem!
We have to putting a manual patch which will run every
night to replace WrongID to CorrectID.
Released on 11/6
Logged In: YES
user_id=19972
It's broken again, this time since there is a real person
with 00363297 (Lucy Nguyen) was loaded into the database,
all previous wrong ID of 00363297 (Frances Watts) was no
longer converted correctly to the correct number of
00363237 (Frances Watts). This is getting frustrating! If
the AS card were printed correctly then we shouldn't have
this problem!
We have to putting a manual patch which will run every
night to replace WrongID to CorrectID.
Released on 11/6
Logged In: YES
user_id=19972
The bug's coming back for BannerID #00371259 (Estrella,
Raymond) in site 6. He was enrolled in both CRN 012474 and
012498. For his Raw Time, he got 2047 minutes, way out of
wack with the Weekly Report of 523min. * 2.
Logged In: YES
user_id=19972
The latest bug appears to be in TKUsageProcessing code, for
TKUsage table containing old ID F%, C% and S%