Troubleshooting
Problem
When saving a query definition in the Guardium GUI query builder the pop up error appears "invalid query".
Symptom
A popup like the example below will appear in the query builder when you click save.
Cause
The underlying SQL generated by the query builder does not have the correct syntax. This may be caused by defects in the functionality or by temporary problems in the query builder.
Resolving The Problem
1. Rebuild the query from scratch. This should eliminate any temporary problem saved in the previous definition.
2. If the problem is not resolved in step 1 remove one condition or field, save the query and see if error appears. Repeat this process for all the conditions and fields. You may find the query saves successfully when certain fields are removed. Note these down for future use by technical support.
3. There are some known defects that can cause this error in V9.1. To obtain Ad-Hoc patches listed below contact Guardium support.
- If you find from step 2 that fields or conditions from Full SQL entity cause the problem you should install Ad Hoc patch p308. GPU p300 is a prerequisite.
- If you find that queries built in a custom domain have the problem you should install Ad Hoc patches p308, p339 and p343. Re-save the custom domain after installing p343.
- Note: GPU 500 contains p308 and p339 but not p343. If you encounter this problem on GPU 500 please contact Guardium support with the information below.
4. If none of the above resolves the problem, contact Guardium support and provide:
- Export of query definition from GUI-> Administration Console-> Guardium Definitions-> Export
- File created when you run command in CLI:
- support must_gather system_db_info
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21695714