Purging Experience Portal report data from an external database

Last Updated : Dec 13, 2018 |
Prolog information
Metadata
Keywords:
The PurgeReportDataExtDB script purges the report data from the external database for any inactive Experience Portal system. 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
  • System information such as the unique identifier for each Media Server associated with the Experience Portal system
  1. Make sure that the Experience Portal system whose data you want to purge is inactive. To do so:
    1. Log on to the EPM web interface by using an account with the Administration, Operations, or Maintenance user role.
    2. From the EPM main menu, select Real-time MonitoringSystem Monitor and go to the Summary tab.
    3. Make sure the State column says Inactive. To change the system status to Inactive, disconnect the system from the shared external database. For more information, see Disconnecting the Experience Portal system from a shared external database
  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. 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.
  4. Enter the bash PurgeReportDataExtDB “Ext_DB_URL” JDBC_Driver Ext_DB_Username EP_System_Name command.
    ADDITIONAL INFORMATION:
    Where:
    ADDITIONAL INFORMATION:
    • “Ext_DB_URL” is the fully-qualified path to the external database.
      Note:
      The quotation marks are used around the first parameter when purging data from an external database. For example, the Ext_DB _URL parameter is surrounded with the quotation marks while running the script.
    • JDBC_Driver is the name of the Java class that implements the JDBC API to the external database.
    • Ext_DB_Username is the user name for the external database.
    • EP_System_Name is the name of an Inactive Experience Portal system.
    Note:
    Database URLs containing semi-colons need to be enclosed within quotes. For example, 'jdbc:sqlserver://<db ip address>:<port>;databaseName=<db name>'.
    The values specified for these parameters should match the values specified on the EPM Settings page in the EPM.
    ADDITIONAL INFORMATION:
    Important:
    The system may take some time to purge the data depending on the amount of data in the database tables.
  5. Enter the external database password.
  6. At the prompt, press Enter to continue.
    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. For example, the script will return an error message if you specify the name of an active system or if the system name you specify does not exactly match one of the systems in the external database.