Troubleshooting
Problem
Some of Guardium predefined reports use SQL Exception Description field as a query condition. These reports will not return any record in Japanese/Chinese Edition of Guardium.
Symptom
Here are the reproduction steps:
- Prepare Japanese or Chinese edition of Guardium 8.
- Open "Returned SQL Error" report.
You won't see any result even though you actually have SQL error records.
Exceptions By Type
Failed User Login Attempts
New SQL Statements
SQL Errors
Exceptions By Server
Exceptions By Client
Exceptions By User
Exceptions Details
Dropped Requests
TCP Exceptions
Failed Login Attempts
Returned SQL Errors
EF - Exception
Cause
The language of SQL Error Description field depends on the edition of Guardium. For example, Japanese edition of Guardium records SQL Error Description field in Japanese.
On the other hand, the "Returned SQL Error" report uses SQL Error Description field as a query condition, and the report is common for all edition of Guardium. It means, these reports always try to match English text and will not return any result when you use non-English edition of Guardium.
Environment
Japanese/Chinese edition of Guardium
Resolving The Problem
This is a limitation of Guardium 8. Please apply the following workaround before using the reports in Japanese/Chinese edition of Guardium.
- Open "Returned SQL Error" report.
- Create a clone of this report, and open it with Query Builder.
- Edit the query condition. Add "Exception Type" entity - "Exception Type" attribute and set "SQL_ERROR" as the value.
- Delete "Exception Type" Entity - "Exception Description" attribute from the query condition.
Figure 1) an example of predefined report which uses an Exception Type - Exception Description in the where clause
Figure 2) an example of modification
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21501115