Syntax Error or Access Rule Violation detected by database ((conn=5423583) exist in table cmdb_par10

[vasant Cool]

When I try to use a filter condition in the status(hardware_status) or Filter Out a field. I am getting the below error.

How to fix this error ?

Syntax Error or Access Rule Violation detected by database ((conn=5423583) Key 'bahstrry_sys_created_on' doesn't exist in table 'cmdb_par10')

[Manmohan K]

Hi @vasant Cool ,

The message indicates the index is on the primary table partition (cmdb) but not the secondary (cmdb_par10). Open a support case with servicenow and ask them to create the same index in the secondary partition.

[Greg46]

Hi @vasant Cool ,

I don't know if this will help, but I had the same issue pop up for me on a specific user.  When that user attempted to view a table with a specific filter, it would generate that error.  When other users tried the same filter, it worked without the error.  As I was attempting to debug the security of the table, (which didn't make sense since two people with the same groups and roles had different results), I tired to filter on something else in the same column.  

So for example in your image above, I see that you have 'Installed' as one of your values in the hardware_status field. Try

1. Show Matching on a different value, like 'Not Installed' (or whatever other values you have in there),

2. Try Show Matching or Filter Out on a different column. 

I don't know why this happens, but it may be something that is messed up just for your user or the user you are using to do the filter.  After the fact I even thought, perhaps if I had cleared the cache for that user, https://<yourinstance>.service-now.com/cache.do, that may have helped as well.

When I did this, and then had the user logout/on from their browser, it fixed the invalid cached info and they were able to few the table with the correct filter again. 

I don't know if this will help or not, but it did get my user back in business.

Good luck!

[Julie Gordon]

@Greg46  - Your solution worked for me temporarily, but the error kept coming back randomly.  Ultimately I had to open an support ticket to have them create the same index on the secondary partition. 

Per ServiceNow support: This is related to a known issue PRB1615879 where the listed index exists on cmdb but not on the additional partitions.

[Greg46]

Thank you for the information and the followup.  I can pass that info on to our platform team as well!

Greg