After a successful purge, a Guardium administrator observes that the full percentage of the Guardium internal database is not decreasing. The administrator uses support show db-top- tables all and…

Question

Options

• AIncrease the retention period and rerun the purge.
• BRebuild the appliance and restore from the backup.
• CLogin to CLI and execute stop inspection-core.
• DOptimize the internal TURBINE database using diag CLI command.

• A
  2% (1)
• B
  7% (3)
• C
  17% (7)
• D
  73% (30)

Explanation

If you when using IBM InfoSphere Guardium product, you notice the database disk space is growing at a fast rate. This is caused by sniffer not able to handle some types of SQLs (usually a sniffer bug). This failure to handle the SQLs occurs frequently enough that GDM_ERROR table grows at a fast rate which then translates to database disk space usage growth. Use command support show db-status used % to show database used space. Run an Optimize to optimize the TURBINE database. This will reorganize the data in all tables, including GDM_ERROR, which will result in reflecting the current actual reduced size. Not C: The inspection-core is sniffer itself. You can stop inspection-core by "stop inspection-core" CLI command and start it by "start inspection-core" CLI command.

No community discussion yet for this question.