Troubleshooting Guardium® Data Protection reports

These sections present troubleshooting and solutions for common problems with reports.

Cannot modify the receiver table for an Audit Process after it has been executed at least once
If you cannot modify the receiver table for an audit process, clone the audit process and replace the original.
Cannot see multi-byte characters
If you export a Guardium report to PDF and the characters are not correct, switch the PDF font configuration.
File system is almost full
If the Guardium file system is almost full, change the log rotation strategy.
Guardium audit reports viewed in Microsoft Excel have rows with unexpected characters
If you view an Audit report in .csv and see rows with unexpected characters, use another .csv viewer or view it as a .pdf file.
Reports show IP address as 0.0.0.0
Request was interrupted or quota exceeded error message
If you receive an error message that states the request was interrupted or the quota was exceeded when you run a report, divide the report into pieces of shorter reporting interval.
Scheduled Job Exceptions every 5 minutes
If you receive a Scheduled Job exception every 5 minutes, deactivate the alert from the Anomaly Detection page.
Scheduled jobs exception: merge required, delay executing process
If you receive an error message that states merge required, delay executing process, reschedule the Audit process.
The database user is not shown correctly in Guardium reports when you monitor Teradata
If Guardium reports do not show the database user correctly when you monitor Teradata, configure the Teradata Database.
Unexpected results in Guardium reports with embedded commands
If you receive unexpected results in Guardium reports, configure your policy rules to handle depth by using tuples.

Parent topic: Problems and solutions