CA Service Management

 View Only
  • 1.  Purge Active Tickets?

    Posted Dec 04, 2014 10:46 AM

    Windows 2012


    CA SDM 12.9



    Is there any way to purge all tickets? Currently they're active and fairly recent.

    We've been bringing up a new implementation and now just want to purge all tickets before the 'go-live' date. I know I could do it in the DB but that's not really the right way....


    Any help is appreciated.




  • 2.  Re: Purge Active Tickets?

    Posted Dec 04, 2014 11:13 AM

    You can close them, and temporary adjust server time or update the close date to older by using pdm_userlaod

  • 3.  Re: Purge Active Tickets?

    Posted Dec 04, 2014 11:29 AM

    pdm_extract -f "select close_date, status, id from Call_Req" >load.txt


    You will get output in file in such format

    { "" ,"OP" ,"400057" }

    { "" ,"RE" ,"400056" }

    change it to

    { "09/12/2002 16:00:00" ,"CL" ,"400057" }

    { "09/12/2002 16:00:00" ,"CL" ,"400056" }

    save and do

    pdm_userload -m -a -f load.txt

  • 4.  Re: Purge Active Tickets?

    Posted Dec 04, 2014 11:44 PM

    Hi Michael,


    You're right. Purging the data from the DB is not a right approach. We certainly ask you to go with the inactivating all the tickets and then perform purge only or archive purge. Here is the document in case if you haven't referred it:


    Archive and Purge Data.pdf




  • 5.  Re: Purge Active Tickets?
    Best Answer

    Posted Dec 08, 2014 11:40 AM

    All the above are on the right track. But here's is what I got from a consultant that worked perfectly. DISCLAIMER: This will delete ALL tickets, no matter status.


    Execute 2 commands on the Primary server cmd prompt.


    pdm_extract Call_Req > Call_Req_BKP.dat

    pdm_load –f  Call_Req_BKP.dat -r


    The first command, as you know does an extract of the records in the CR table to a file. The second command then reloads that data back in, but using the (-r) actually is removing that data from the table, therefore deleting the records. As a backup, just in case something goes wrong, you always have that .dat file it created. Do the above commands for the CR, Act_Log and Notify_Log_Header tables. I performed the above actions and it worked perfectly.