| Re: How bad is CU04
Ian,
We found many problems when we started CU4 testing as well.
One of the points that I remember specifcally was that we had some issues that were apparently caused by having a carriage return in our SQL statement. While this should not have caused any issue in the statement, OTM was unable to handle it, and it needed to be removed (This statement was working just fine in CU2)
We also had an issue about the number of rate records associated with a given lane. Because of how this had been coded, OTM was allocating resources exponentially for each additional carrier (We found this issue in CU2). This issue was supposed to be fixed in CU4, but the new coding actually caused the system to crash repeatedly (talk about it going wrong). It took us over 50 days with an active SR to get this issue resolved and Keith had to work directly with Development.
Since resolving these issues, we have been moving fairly smoothly through our testing. So while just a few weeks ago I would have suggested that you abandon all hope in CU4, I now am more willing to suggest working through the issues if possible.  |