Hi,
In our environment, this message "NO_NODES_TO_FORWARD_TO" occurs in two situations: dispatcher is not responding (may fall) or queue time limit has reached.
I told IBM that message is not clear.
Anyway, your cube is fetching data using CQM or DQM?
I have large cubes with large query results that fetches data using CQM.
When using CQM, data is fetched by Transformer engine and processed locally. When using DQM, query is fetched using Query Service of dispatcher configured in Cognos Configuration of Transformer install and is worst in terms of performance.
Maybe you're using DQM and your dispatcher is falling when retrieving results from database and sending to Transformer.
------------------------------
Jeam Coelho
Cognos Solution Architect
IBM Champion
LinkedIn:
https://www.linkedin.com/in/jeamcoelho/------------------------------
Original Message:
Sent: Tue April 28, 2026 10:03 AM
From: Penny Flower
Subject: After upgrade from 11.2.4 to 12.1.1 Transformer failing on large query - other cubes okay - see defect DT443193
The Transformer log shows: XQE-CON-0007 XQE error encountered: NO_NODES_TO_FORWARD_TO
There are a few more details after that line, requestId, sessionId, and the server name. The server name is the server running the content manager and the dispatcher. We have always run Transformer on a different server.
------------------------------
Penny Flower
------------------------------
Original Message:
Sent: Fri April 24, 2026 02:13 PM
From: John Cusack
Subject: After upgrade from 11.2.4 to 12.1.1 Transformer failing on large query - other cubes okay - see defect DT443193
Hi Penny,
Can you share the error message that you are receiving once it fails?
------------------------------
John Cusack
Analytica iQ