The SQL Data Translation of SYSTEM xxx.log may contain notes with the exact records that are having the problem (or at least the table to be viewed), such as:
SY_ZipCode......................... Records written: 961,934 of 961,931
SY_ZipCode......................... Key not found in PVX: ONTB3J3K1
SY_ZipCode......................... Key not found in PVX: ONTL7R 4L4
SY_ZipCode......................... Key not found in PVX: USA17135
In this example, the issue is the SY_Zipcode table in the MAS_SYSTEM database.
The zip code B3J3K1 in country ONT (this should be CAN, for Canada) is the first one. Someone entered record in older Premium install as Zip Code B3J3K1 but country code ONT instead of County CAN with State/Province of ONT.
For the 2nd entry, the Zip code was entered as L7R 4L4 instead of L7R4L4 and once again country of ONT instead of CAN.
Final entry is Country code of USA but with a zip code 17135 that does not exist, in checking further (State was PA) this should be Zip code 17535 which was mistyped in the older install.
These records would need to be corrected (or deleted) to resolve the error - it would also need to be confirmed if any customers, vendors, ShipTo addresses, are using these incorrect zip code entries.
Another example:
SY_ActivityLog..................... Records written: 68 of 66
SY_ActivityLog..................... Key not found in PVX: A~2022052012.048612
SY_ActivityLog..................... Key not found in PVX: A~2022052012.048616
This would indicate that bad records exist in the SY_activitylog table in the MAS_SYSTEM database.
|