Purging report data from a local Experience Portal database

Last Updated : Dec 13, 2018 |
Prolog information
Metadata
Keywords:
The PurgeReportDataLocalDB script purges all report data from the VoicePortal database. This data includes all:
  • Application Detail Records (ADRs) stored in the vpapplog table
  • Contact Detail Records (CDRs) stored in the cdr table
  • Performance records stored in the vpperformance table
  • Session Detail Records (SDRs) stored in the sdr table
Important:
After you run this script, users cannot generate reports through the EPM until the EPM has downloaded the current report data from the Media Servers.
  1. Make sure that the EPM is not currently downloading report data from the Media Servers.
    1. Log on to the EPM web interface by using an account with the Administration user role.
    2. From the Media Server Service Menu, select System Configuration > EPM Servers > Report Data.
    3. Go to the display text box in the Download and Maintenance Schedules group and make sure that no downloads are scheduled for the current time.
  2. Log in to Linux on the Primary or Auxiliary EPM server.
    ADDITIONAL INFORMATION:
    • If you are an Avaya Services representative, and use Avaya Enterprise Linux, or if the Avaya Service accounts are installed on this server, log on to the local Linux console as root.
    • Otherwise, log on remotely as a non-root user, and then change the user to root by entering the su - root command.
  3. Navigate to the Support/VP-Tools directory under the Experience Portal installation directory.
  4. Enter the cd $AVAYA_HOME/Support/VP-Tools command. $AVAYA_HOME is an environmental variable pointing to the name of the installation directory specified during the Experience Portal software installation.
    ADDITIONAL INFORMATION:
    The default value is /opt/Avaya/ExperiencePortal.
  5. Enter the bash PurgeReportDataLocalDB command.
    ADDITIONAL INFORMATION:
    Important:
    The system may take some time to purge the data depending on the amount of data in the database tables.
    STEP RESULT:
    If the script runs successfully, it returns a message stating that the data was purged from the database. Otherwise, it returns a message stating the problem that it encountered.