Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
9 replies
Subscribers
7 subscribers
Views
2426 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
AI and Rules
Need help using a query rule with a DB2 database running on a Linux server.
mariod
over 9 years ago
Need help using a query rule with a DB2 database running on a Linux server.
we are using a DB2 database for the first time and while testing the query rule, the following error is displayed:
There was an error testing the rule:
Expression evaluation error in rule 'testsccdrule' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [SCCDDBHIERARCHYALLDT5651], query: [testSCCDRule], order by: [[Sort[hierarchyDescription asc]]], filters:[null])
I can query the view using the database node but I cannot get a CDT to work using a query rule.
The view only has one varchar field and we are on Appian v7.3
...
OriginalPostID-123789
OriginalPostID-123789
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 9 years ago
In order to troubleshoot issues where the message is very generic such as: "Unexpected error executing query" you need to reproduce and then find this error in the application-server.log, once you have identified it review each of the individual "Caused by" clauses. Usually the most bottom ones (that belong to that error) will be the most informative ones in the stack trace.
You won't know what the problem is if you only focus the troubleshooting on the generic "Unexpected error executing query" error message.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 9 years ago
In order to troubleshoot issues where the message is very generic such as: "Unexpected error executing query" you need to reproduce and then find this error in the application-server.log, once you have identified it review each of the individual "Caused by" clauses. Usually the most bottom ones (that belong to that error) will be the most informative ones in the stack trace.
You won't know what the problem is if you only focus the troubleshooting on the generic "Unexpected error executing query" error message.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data