How to resolve "No Push Reason: Cannot push WITH clause because column alias cannot be pushed. Use an alias with appropriate length using just letters and digits"?
Article ID: KB0071593
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | - |
Description
During query execution, the FETCH node in the query execution plan may contain a column alias that incorporates a WITH clause. In such situations, an error message may arise, which reads as follows: "No Push Reason: Cannot push WITH clause because column alias cannot be pushed. Use an alias with appropriate length using just letters and digits."
Issue/Introduction
The purpose of this article is to elucidate how to resolve the error message "Cannot push WITH clause because column alias cannot be pushed. Use an alias with appropriate length using just letters and digits"
Environment
All Supported Environments
Resolution
The following instructions provide the essential steps to address the "No push reason" problem :
(1) Navigate to <TDV_install_dir>\conf\adapters\<system> or custom>\<datasource>_<version>\<datasource>_<version>_values.xml file.
(2) Open the aforementioned file in an editor
(3) Insert the following block of code after the commented block and before the </common:attributes> tag located at the end of the file:
--------------------------------------------------------------
<common:attribute xmlns:common="http://www.compositesw.com/services/system/util/common">
<common:name>/custom/jdbcds.max_sql_alias_length</common:name>
<common:type>STRING</common:type>
<common:value>128</common:value>
<common:configID>jdbcds.max_sql_alias_length</common:configID>
</common:attribute>
-------------------------------------------------------------
(4) Save the configuration file with the changes mentioned above.
(5) Restart the TDV server to apply the modifications.
(6) Verify your use case and inspect the query plan to determine if the "No Push" error is resolved.
(1) Navigate to <TDV_install_dir>\conf\adapters\<system> or custom>\<datasource>_<version>\<datasource>_<version>_values.xml file.
(2) Open the aforementioned file in an editor
(3) Insert the following block of code after the commented block and before the </common:attributes> tag located at the end of the file:
--------------------------------------------------------------
<common:attribute xmlns:common="http://www.compositesw.com/services/system/util/common">
<common:name>/custom/jdbcds.max_sql_alias_length</common:name>
<common:type>STRING</common:type>
<common:value>128</common:value>
<common:configID>jdbcds.max_sql_alias_length</common:configID>
</common:attribute>
-------------------------------------------------------------
(4) Save the configuration file with the changes mentioned above.
(5) Restart the TDV server to apply the modifications.
(6) Verify your use case and inspect the query plan to determine if the "No Push" error is resolved.
Feedback
Yes
No
Powered by
