Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Shrinking the PostgreSQL database size in InterScan Web Security products

    • Updated:
    • 5 Oct 2015
    • Product/Version:
    • InterScan Web Security Suite 3.1 Linux
    • InterScan Web Security Virtual Appliance 5.6
    • InterScan Web Security Virtual Appliance 6.0
    • InterScan Web Security Virtual Appliance 6.5
    • Platform:
    • Linux - Red Hat RHEL 3 32-bit
    • Linux - Red Hat RHEL 4 32-bit
    • Linux - Red Hat RHEL 5 32-bit
    • Linux - SuSE version 10
    • Unix - Solaris (Sun) version 8 (SunOS 5.8)
    • Unix - Solaris (Sun) version 9 (SunOS 5.9)
Summary

When the size of the PostgreSQL database becomes too large, the cron jobs may not work efficiently.

Details
Public

To resolve this issue, delete the old entries to reduce the database size:

 
Generate the necessary reports before following these steps. This procedure will delete the contents of the specific tables in the database. TRUNCATE quickly removes all rows from a table in one run and VACUUM compresses the database.
  1. Log in to the InterScan Web Security Suite (IWSS) or InterScan Web Security Virtual Appliance (IWSVA) shell.
  2. Go to the applicable location:
    • For IWSS: .../etc/iscan/PostgreSQL/bin
    • For IWSVA: .../var/iwss/PostgreSQL/bin
  3. Execute the following command:

    ./psql –U sa –d iwss

     
    The "sa" password will be required. This is usually set by customer to "sa" or "trend". If this is not the case, the passowrd is stored in the /etc/iscan/.pgpass file or /etc/iscan/odbc.ini file, which you can see using the "# cat /etc/iscan/.pgpassu" command.

    Giving the correct password, the PostgreSQL interactive terminal displays the following:

    iwss => TRUNCATE TABLE [table name];

    Where the table names are:

    • tb_performance_value: This contains performance information when performance logging is enabled.
    • tb_url_usage: This contains access logs when access logging is enabled.
    • tb_violation: This contains caught viruses, blocked URLs, and other violations.
  4. After truncating each tables, execute this command:

    iwss => VACUUM;

    The vacuum task is done daily at 3:58 AM.

  5. Type "\q" to exit the interactive terminal.
  6. Chek if the database has been shrunk successfully by verifying the database size:

    # /usr/iwss/bin/admin_checksize.sh localhost 5432 sa iwss

Premium
Internal
Rating:
Category:
Configure
Solution Id:
1030715
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.