[JBoss JIRA] (TEIID-2930) SCROLL keyword for DECLARE CURSOR not being parsed correctly
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIID-2930?page=com.atlassian.jira.plugin... ]
Johnathon Lee reopened TEIID-2930:
----------------------------------
I have used isql and ODBC driver for RHEL5.
I am not able to force isql to generate "..scroll cursor for..", however when I type the query[1] directly into isql, it is processed by teiid correctly. So the fix seems to be ok.
However the query[2] fails and teiid throws an exception[3]
Syntax "cursor with hold for" works correctly for the unpatched version of EDS 5.3.1 so I consider it as a regression.
[1] declare "SQL_CUR0x11ad4120" scroll cursor for select intNum from bqt2.smalla;fetch 100 in "SQL_CUR0x11ad4120"
[2] declare "SQL_CUR0xe61c20" cursor with hold for select * from pg_proc
[3] org.teiid.jdbc.TeiidSQLException: Direct usage of XQuery is no longer supported, use XMLQUERY instead.
> SCROLL keyword for DECLARE CURSOR not being parsed correctly
> ------------------------------------------------------------
>
> Key: TEIID-2930
> URL: https://issues.jboss.org/browse/TEIID-2930
> Project: Teiid
> Issue Type: Bug
> Components: ODBC
> Affects Versions: 7.7.8
> Reporter: Johnathon Lee
> Assignee: Steven Hawkins
> Fix For: 7.7.9, 8.7.1, 8.8
>
>
> The DECLARE cursor is defined as [1]. However, in [2] line #155, the SCROLL keyword is not being matched. Correction would be to match the pattern fully as defined in [1]
> [1]
> http://www.postgresql.org/docs/8.4/static/sql-declare.html
> [2]
> https://github.com/teiid/teiid/blob/master/runtime/src/main/java/org/teii...
> Example of error:
> TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking server method: executeQuery [BEGIN;declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY>;fetch 100 in "SQL_CUR0x11ad4120"]
> DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: START TRANSACTION
> FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [START TRANSACTION] expecting: EITHER
> FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as transaction statement
> TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: sendUpdateCount [BEGIN, 0]
> FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [show client_encoding] expecting: RESULTSET
> FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as show statement
> FINER [org.teiid.jdbc] (New I/O server worker #3-1) Creating ResultSet requestID: -1 beginRow: 1 resultsColumns: 1 parameters: 0
> TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: setEncoding [UTF-8]
> FINE [org.teiid.jdbc] (New I/O server worker #3-1) Statement closed successfully.
> DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY>
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2971) wrong property name in max sessions message
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2971:
-------------------------------------
Summary: wrong property name in max sessions message
Key: TEIID-2971
URL: https://issues.jboss.org/browse/TEIID-2971
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7.1, 8.8
the error message references session-max-limit rather than max-session-allowed
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2481) common table (with) push down improvements
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2481?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2481:
---------------------------------------
I think the first improvement to tackle is actually just allowing views with common tables to be mergable into the parent plans. Currently we treat them as subplans - which means that further pushdown, dependent joins toward the side with a common table, etc. will not be done.
However this will require quite a few changes to the planning logic as it is currently geared solely to determining with pushdown on a single query/view layer at a time.
> common table (with) push down improvements
> ------------------------------------------
>
> Key: TEIID-2481
> URL: https://issues.jboss.org/browse/TEIID-2481
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> The general strategy for with pushdown should better handle:
> - a with clause that can be pushed against a source that does not support common table. If a single reference or some other sufficient condition is met then we should just inline the pushdown rather than inhibiting the whole query from pushing down.
> - even if a source supports with pushdown, it may be more performant in some circumstances to inline the common table reference (such as only a single reference). This is complicated slightly by subqueries.
> - alternatively in some situations even if a with clause can be pushed, it may be better to not perform the pushdown -e.g. two separate pushdown accesses to a common table that is expensive to compute (this may need to be hint driven).
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2969) timestamp parse format issues
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2969?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2969.
-----------------------------------
Resolution: Done
Removed support for pg pushdown of timestampdiff.
Corrected the format modifier to appropriately quote, and the pg format modifier will now account for differences with oracle.
> timestamp parse format issues
> -----------------------------
>
> Key: TEIID-2969
> URL: https://issues.jboss.org/browse/TEIID-2969
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.8
>
>
> Oracle and Postgresql pushdown of parse/format of timestamps is generally incorrect as the format string is left unquoted. Also Postgresql does not support the same syntax as oracle.
> Also pushdown of timestampdiff is not correct for pg for fields other than DAY and YEAR. Fractional seconds are not implemented and all of the other fields seem to return just the calendar field difference, not the number of intervals different - e.g. the difference in hours for timestamps that are years apart is just the 24 hour difference.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2969) timestamp parse format issues
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2969?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2969:
----------------------------------
Forum Reference: https://community.jboss.org/thread/241234
> timestamp parse format issues
> -----------------------------
>
> Key: TEIID-2969
> URL: https://issues.jboss.org/browse/TEIID-2969
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.8
>
>
> Oracle and Postgresql pushdown of parse/format of timestamps is generally incorrect as the format string is left unquoted. Also Postgresql does not support the same syntax as oracle.
> Also pushdown of timestampdiff is not correct for pg for fields other than DAY and YEAR. Fractional seconds are not implemented and all of the other fields seem to return just the calendar field difference, not the number of intervals different - e.g. the difference in hours for timestamps that are years apart is just the 24 hour difference.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2970) possible timing issue with transport services
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2970:
-------------------------------------
Summary: possible timing issue with transport services
Key: TEIID-2970
URL: https://issues.jboss.org/browse/TEIID-2970
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7.1, 8.8
Since the listener start is creating other threads we should ensure that services are added prior to starting the listener.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2969) timestamp parse format issues
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2969:
-------------------------------------
Summary: timestamp parse format issues
Key: TEIID-2969
URL: https://issues.jboss.org/browse/TEIID-2969
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 7.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7.1, 8.8
Oracle and Postgresql pushdown of parse/format of timestamps is generally incorrect as the format string is left unquoted. Also Postgresql does not support the same syntax as oracle.
Also pushdown of timestampdiff is not correct for pg for fields other than DAY and YEAR. Fractional seconds are not implemented and all of the other fields seem to return just the calendar field difference, not the number of intervals different - e.g. the difference in hours for timestamps that are years apart is just the 24 hour difference.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2913) Remove Logging Quickstart
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-2913?page=com.atlassian.jira.plugin... ]
Van Halbert resolved TEIID-2913.
--------------------------------
Resolution: Done
Removed the the custom-log4j-db-logger quick start
> Remove Logging Quickstart
> -------------------------
>
> Key: TEIID-2913
> URL: https://issues.jboss.org/browse/TEIID-2913
> Project: Teiid
> Issue Type: Task
> Components: Quick Starts
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> Add the following enhancements to the logging quick start:
> - add example for audit logging to a database (use h2)
> - add dynamic VDB's to expose the audit and command logging schemas
> - add a preconfigured dashboard to present the audit and command logs
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (TEIID-2967) ORA-01789: query block has incorrect number of result columns
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2967?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2967.
-----------------------------------
Resolution: Done
Corrected the RulePlanSorts logic and generalized the union limit/order by pushing.
> ORA-01789: query block has incorrect number of result columns
> -------------------------------------------------------------
>
> Key: TEIID-2967
> URL: https://issues.jboss.org/browse/TEIID-2967
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
> Labels: columns, group, oracle, union
> Fix For: 8.7.1, 8.8
>
>
> This case is similar to TEIID-2963. I can reproduce this in nightly build from master (0c7879a), which includes that fix.
> Two selects from the same table in Oracle, and then a dummy select.
> {code:sql}
> select
> "FOO"."SOURCE" "SOURCE",
> "FOO"."FOO_ID" "FOO_ID"
> from (
> (select 'X' "SOURCE", "ITEMS"."ITEM_ID" "FOO_ID" from "BLAH"."ITEMS" "ITEMS" group by "ITEMS"."ITEM_ID")
> union all
> (select 'Y' "SOURCE", "ITEMS"."ITEM_ID" "FOO_ID" from "BLAH"."ITEMS" "ITEMS")
> union all
> (select 'Z' "SOURCE", '123' "FOO_ID")
> ) "FOO"
> order by "FOO_ID" desc
> limit 50;
> {code}
> Running that in Squirrel fails with this.
> {code}
> ORA-01789: query block has incorrect number of result columns
> {code}
> Formatted Oracle SQL from stacktrace below. Notice 'Y' is being selected in the second branch.
> {code:sql}
> SELECT c_0
> FROM (
> (SELECT g_1."ITEM_ID" AS c_0 FROM "BLAH"."ITEMS" g_1 GROUP BY g_1."ITEM_ID")
> UNION ALL
> (SELECT 'Y' AS c_0, g_0."ITEM_ID" AS c_1 FROM "BLAH"."ITEMS" g_0 ORDER BY c_0 DESC)
> )
> WHERE ROWNUM <= 50
> {code}
> {code}
> 18:36:08,696 DEBUG [org.teiid.COMMAND_LOG] (New I/O worker #29) probZ0uIjf9B START USER COMMAND: startTime=2014-05-20 18:36:08.696 requestID=probZ0uIjf9B.0 txID=null sessionID=probZ0uIjf9B applicationName=JDBCprincipal=user@teiid-security vdbName=Blah vdbVersion=1 sql=select
> "FOO"."SOURCE" "SOURCE",
> "FOO"."FOO_ID" "FOO_ID"
> from (
> (select 'X' "SOURCE", "ITEMS"."ITEM_ID" "FOO_ID" from "BLAH"."ITEMS" "ITEMS" group by "ITEMS"."ITEM_ID")
> union all
> (select 'Y' "SOURCE", "ITEMS"."ITEM_ID" "FOO_ID" from "BLAH"."ITEMS" "ITEMS")
> union all
> (select 'Z' "SOURCE", '123' "FOO_ID")
> ) "FOO"
> order by "FOO_ID" desc
> limit 50
> 18:36:08,701 DEBUG [org.teiid.COMMAND_LOG] (Worker6_QueryProcessorQueue124) probZ0uIjf9B START DATA SRC COMMAND: startTime=2014-05-20 18:36:08.701 requestID=probZ0uIjf9B.0 sourceCommandID=5 executionID=102 txID=TransactionImple < ac, BasicAction: 0:ffff0a248478:-73f8bcbd:537bd3ec:49 status: ActionStatus.RUNNING > modelName=blah translatorName=oracle sessionID=probZ0uIjf9B principal=user@teiid-security sql=SELECT g_1.ITEM_ID AS c_0 FROM blah.ITEMS AS g_1 GROUP BY g_1.ITEM_ID UNION ALL SELECT 'Y' AS c_0, g_0.ITEM_ID AS c_1 FROM blah.ITEMS AS g_0 ORDER BY c_0 DESC LIMIT 50
> 18:36:08,731 DEBUG [org.teiid.COMMAND_LOG] (Worker6_QueryProcessorQueue124) probZ0uIjf9B ERROR SRC COMMAND: endTime=2014-05-20 18:36:08.731 requestID=probZ0uIjf9B.0 sourceCommandID=5 executionID=102 txID=TransactionImple < ac, BasicAction: 0:ffff0a248478:-73f8bcbd:537bd3ec:49 status: ActionStatus.RUNNING > modelName=blah translatorName=oracle sessionID=probZ0uIjf9B principal=user@teiid-security finalRowCount=null
> 18:36:08,732 WARN [org.teiid.CONNECTOR] (Worker6_QueryProcessorQueue124) probZ0uIjf9B Connector worker process failed for atomic-request=probZ0uIjf9B.0.5.102: org.teiid.translator.jdbc.JDBCExecutionException: 1789 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT c_0 FROM (SELECT g_1."ITEM_ID" AS c_0 FROM "BLAH"."ITEMS" g_1 GROUP BY g_1."ITEM_ID" UNION ALL SELECT 'Y' AS c_0, g_0."ITEM_ID" AS c_1 FROM "BLAH"."ITEMS" g_0 ORDER BY c_0 DESC) WHERE ROWNUM <= 50]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:326) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:135) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:369) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.relational.UnionAllNode.nextBatchDirect(UnionAllNode.java:151) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:69) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:70) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:84) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.common.buffer.AbstractTupleSource.nextTuple(AbstractTupleSource.java:48) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.relational.SortUtility.initialSort(SortUtility.java:272) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.relational.SortUtility.sort(SortUtility.java:202) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.relational.SortNode.sortPhase(SortNode.java:112) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.relational.SortNode.getBuffer(SortNode.java:205) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.relational.LimitNode.getBuffer(LimitNode.java:211) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.relational.RelationalPlan.getBuffer(RelationalPlan.java:250) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.QueryProcessor.getBuffer(QueryProcessor.java:289) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:154) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:444) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:326) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:254) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.8.0.Alpha2-SNAPSHOT.jar:8.8.0.Alpha2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_02]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_02]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02]
> Caused by: java.sql.SQLSyntaxErrorException: ORA-01789: query block has incorrect number of result columns
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
> at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1017)
> at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:655)
> at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:249)
> at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:566)
> at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:215)
> at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:58)
> at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:776)
> at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:897)
> at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1034)
> at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3820)
> at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3867)
> at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1502)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123)
> ... 32 more
> 18:36:08,751 DEBUG [org.teiid.COMMAND_LOG] (Worker6_QueryProcessorQueue124) probZ0uIjf9B ERROR USER COMMAND: endTime=2014-05-20 18:36:08.751 requestID=probZ0uIjf9B.0 txID=TransactionImple < ac, BasicAction: 0:ffff0a248478:-73f8bcbd:537bd3ec:49 status: ActionStatus.RUNNING > sessionID=probZ0uIjf9B principal=user@teiid-security vdbName=Blah vdbVersion=1 finalRowCount=null
> 18:36:08,752 WARN [org.teiid.PROCESSOR] (Worker6_QueryProcessorQueue124) probZ0uIjf9B TEIID30020 Processing exception for request probZ0uIjf9B.0 'TEIID30504 blah: 1789 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT c_0 FROM (SELECT g_1."ITEM_ID" AS c_0 FROM "BLAH"."ITEMS" g_1 GROUP BY g_1."ITEM_ID" UNION ALL SELECT 'Y' AS c_0, g_0."ITEM_ID" AS c_1 FROM "BLAH"."ITEMS" g_0 ORDER BY c_0 DESC) WHERE ROWNUM <= 50]'. Originally TeiidProcessingException 'ORA-01789: query block has incorrect number of result columns
> ' T4CTTIoer.java:450. Enable more detailed logging to see the entire stacktrace.
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month