The truncate command removes all data from the staging tables. So any data that has not been migrated will be lost. Running the truncate ‘resets’ the tables and frees up disk space. Ideally Data Manager would do this on its own but only if the system reports all data are migrated and no staging/pull jobs are running. If a job gets ‘hung’, it can stop this process. Therefore it is advised to truncate the staging tables to resolve this state (again data not migrated will be lost). The SQL for the truncate commands are in the Data Manager admin guide. You can use CCR gap reports to find how far back you need to go for a catch-up pull after truncating.
>KIP
Kip Lamb
Sr Principal Consultant, Presales
CA Technologies | Bellevue, WA 98005
Office: +1 512 776 0235 | Mobile: +1 425 591 4358 | Kip.Lamb@ca.com
<mailto:Kip.Lamb@ca.com>[cid:image001.jpg@01D21EF5.6EBDF7D0][cid:image002.png@01D0928A.5E056B60]
<http://www.ca.com/us/default.aspx>
<http://www.ca.com/us/default.aspx>