Highlighted
Honored Contributor.
Honored Contributor.
613 views

Query result exceeded size limit SNOW integration failing with UD

Query result exceeded size limit.
Please refine your query.
Cause: Too many objects visited by DFS.
Size limit: Ignoring ucmdb_integ_ci_computer RTN tree because of invalid key.

 

Pls help

thanks
0 Likes
3 Replies
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: Query result exceeded size limit SNOW integration failing with UD

Go to JMX Console --> Setting Services --> Show Settings by Category --> Invoke.

Search for dal.object.condition.max.result.size. OTTB Value is 2M.

You could try to raise the fuse, but this will affect memory consumption. Keep an eye on jvm.statistics.log.log. Your HEAP FREE memory size shouldn't go lower 500M when the integration running. 

Otherwise, you need to rework the TQL.

Hope this helps.

Regards
-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Query result exceeded size limit SNOW integration failing with UD

This is not a fuse problem. I have seen the same with my usage of the ServiceNow adapter. As a start, change the SOAP to REST push method, enable the debugging as written in the documentation:

adapter.conf should state:

push.connector.class=com.hpe.ucmdb.adapters.snow.connector.ServiceNowRestConnector

 

Cheers,

Petko Popadiyski

Freelance Microfocus CMS UCMDB Consulting

Likes are appreciated!
0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: Query result exceeded size limit SNOW integration failing with UD

I am having this same issue. I have done both of the suggestions above and it is still not working. I can create a new computer record in SNOW but can't coalesce with the one that is already there. when i use u_correlation_id i receive the same error.

 

Query result exceeded size limit.
Please refine your query.
Cause: Too many objects visited by DFS.
Size limit: Ignoring u_ucmdb_integ_cmdb_ci_computer RTN tree because of invalid key.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.