Syntax Error or Access Rule Violation detected by database ((conn=1999638) Key 'qjozrwqi_for_table_cleaner' doesn't exist in table 'cmdb_par10')
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2022 07:11 PM
Hi All
When I open the reference list of cmdb_ci, I get the following error How should I handle this?
Syntax Error or Access Rule Violation detected by database ((conn=1999638) Key 'qjozrwqi_for_table_cleaner' doesn't exist in table 'cmdb_par10')
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2023 12:48 PM
I guess you didn't see my recommendation to create a Support Case. That is what I would do.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2023 12:19 AM
Hi,
Run the following code as a background script:
gs.invalidateCache();

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2023 01:43 PM
The message indicates the index is on the primary table partition (cmdb) but not the secondary (cmdb_par10). Open a support case and ask them to create the same index in the secondary partition.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2023 08:45 AM
I had this issue as well. I found an obscure reference about function fields being related to this issue. So, I de-activated all function fields on tables related to cmdb_ci and that fixed the issue. We didn't have that many and they were only used once for some validation reporting. 1. Open a report that uses the function field. 2. Configure function fields 3. Deactivate any that are related to cmdb_ci 4. test
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2023 05:32 AM
Hi All,
This issue is coming from the sorting (ASC or DESC) on one of the fields on your cmdb_ci list.
For my case, a user has this issue because he has sorted the status (install_status) on cmdb_ci. The sort performed on this field must be removed to resolve this issue (sort list with another field).
Regards,
Mansour NIANG