LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  LAE Error Code: brain.node.SqlSelect_ExprStmt.cpp.138

    Employee
    Posted 02-23-2017 17:04

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: lae_errors

    This post has been created for discussion of error code brain.node.SqlSelect_ExprStmt.cpp.138.

    Please reply to this thread with any description of error conditions, diagnostic information, and recommended resolutions.


  • 2.  RE: LAE Error Code: brain.node.SqlSelect_ExprStmt.cpp.138

    Employee
    Posted 02-23-2017 17:18

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rgvenkatesh

    Hi,

    I am trying to use sqlSelect function wherein I am supplying a dynamic SQL query with no bind parameters in every input iteration.

    The DB execute node receives 100 inputs having all the SQL queries being created dynamically and supplied to sqlSelect function as shown below.

    sqlSelect(1,dynamicSql)
    ##dynamicSql is a string field having a dynamically created SQL statement.

    When I run this node, I get the below error from the Exprstmt.cpp file:
    sql query changed: 'SELECT COUNT(......' WHERE ID=1234-> 'SELECT COUNT(....WHERE ID=1235.

    Not pretty sure why this error is thrown as the query is formed correctly and I have tried launching them separately on SQL developer and it works fine.

    Please help.


  • 3.  RE: LAE Error Code: brain.node.SqlSelect_ExprStmt.cpp.138

    Employee
    Posted 02-23-2017 22:11

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: stonysmith

    See the response posted here:
    http://community.lavastorm.com/threa...Select-Queries


  • 4.  RE: LAE Error Code: brain.node.SqlSelect_ExprStmt.cpp.138

    Employee
    Posted 02-24-2017 12:43

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rgvenkatesh

    Originally posted by: stonysmith
    					

    Hi,

    I did add a union in front of all the dynamic SQL queries and merged them all into a single query with the AGG node.

    Now, I have around 7K dynamic queries coming in into the AGG node and it even finishes off successfully but the output is not shown on the clipboard as it says the data is big for it to show on the clipboard.

    So I reduced the number of records coming in just for the test and it was able to merge them properly and even the DB execute node worked fine, but as soon as I let in all the 7K records come in, even though the AGG node says it finished OK, the DB execute node fails with an Oracle error of "SQL command not properly ended".

    Not sure if the huge merged data is causing this error?


  • 5.  RE: LAE Error Code: brain.node.SqlSelect_ExprStmt.cpp.138

    Employee
    Posted 02-24-2017 16:23

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rgvenkatesh

    Originally posted by: rgvenkatesh
    					

    Hi,

    I did add a union in front of all the dynamic SQL queries and merged them all into a single query with the AGG node.

    Now, I have around 7K dynamic queries coming in into the AGG node and it even finishes off successfully but the output is not shown on the clipboard as it says the data is big for it to show on the clipboard.

    So I reduced the number of records coming in just for the test and it was able to merge them properly and even the DB execute node worked fine, but as soon as I let in all the 7K records come in, even though the AGG node says it finished OK, the DB execute node fails with an Oracle error of "SQL command not properly ended".

    Not sure if the huge merged data is causing this error?

    Hi,

    This error is now resolved as it was due to a typo in the SQL query.

    Thanks a lot for the help.