Replication: Corrupt Dates in Logs

Post bug reports and the status of reported bugs
Post Reply
User avatar
Steve Vincent
Site Admin
Posts: 1054
Joined: Mon May 12, 2008 8:33 am
OLAP Product: TM1
Version: 10.2.2 FP1
Excel Version: 2010
Location: UK

Replication: Corrupt Dates in Logs

Post by Steve Vincent »

Long story cut short; has anyone who runs replication found issues where some log entries on the destination server for attribute value changes have a corrupt replication date where the year is stated as 0000?

I'm taking a long time to narrow it down and get a reproducable model for IBM to test, but i can be sure that;
  • logs on the source server are 100% OK in every case
  • logs on the destination appear to be 50/50 split of OK or corrupt (no obvious pattern)
  • only changes made in bulk (ie via TI) & on large-ish dims (5000+) seem to be affected
  • no data is affected in this way, only attribute values
The problem it causes is if you have a chain of servers (A to B to C) where changes are made in A. They will replicate to B OK but the corrupt date in B's logs means the replication to C will miss those transactions.

Much longer explaination, hopefully with an example, to come later once i finish swearing at my PC and IBM....
If this were a dictatorship, it would be a heck of a lot easier, just so long as I'm the dictator.
Production: Planning Analytics 64 bit 2.0.5, Windows 2016 Server. Excel 2016, IE11 for t'internet
User avatar
Steve Vincent
Site Admin
Posts: 1054
Joined: Mon May 12, 2008 8:33 am
OLAP Product: TM1
Version: 10.2.2 FP1
Excel Version: 2010
Location: UK

Re: Replication: Corrupt Dates in Logs

Post by Steve Vincent »

an example of said screwed up logs

Code: Select all

"","20110804155624","00000804133635","Admin","S","83ZF02 -","Q75","}ElementAttributes_Work Breakdown","83ZF02","AltName",""
"","20110804155624","00000804133635","Admin","S","83B800 -","Q78","}ElementAttributes_Work Breakdown","83B800","AltName",""
"","20110804155624","20110804133647","Admin","S","83A011 -","Q153","}ElementAttributes_Work Breakdown","83A011","AltName",""
"","20110804155624","00000804133647","Admin","S","83A016 -","Q154","}ElementAttributes_Work Breakdown","83A016","AltName",""
"","20110804155624","00000804133647","Admin","S","83A017 -","Q155","}ElementAttributes_Work Breakdown","83A017","AltName",""
"","20110804155624","20110804133648","Admin","S","83A019 -","Q156","}ElementAttributes_Work Breakdown","83A019","AltName",""
"","20110804155624","00000804133648","Admin","S","83A020 -","Q157","}ElementAttributes_Work Breakdown","83A020","AltName",""
"","20110804155624","20110804133649","Admin","S","83A021 -","Q158","}ElementAttributes_Work Breakdown","83A021","AltName",""
"","20110804155624","00000804133649","Admin","S","83A022 -","Q159","}ElementAttributes_Work Breakdown","83A022","AltName",""
"","20110804155624","00000804133649","Admin","S","83A023 -","Q160","}ElementAttributes_Work Breakdown","83A023","AltName",""
"","20110804155624","20110804133650","Admin","S","83N001 -","Q161","}ElementAttributes_Work Breakdown","83N001","AltName",""
If this were a dictatorship, it would be a heck of a lot easier, just so long as I'm the dictator.
Production: Planning Analytics 64 bit 2.0.5, Windows 2016 Server. Excel 2016, IE11 for t'internet
Post Reply