You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (Commented) (JIRA)" <ji...@apache.org> on 2012/02/24 22:57:49 UTC
[jira] [Commented] (DERBY-5337) Encountering error when importing
to table using CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE
[ https://issues.apache.org/jira/browse/DERBY-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215970#comment-13215970 ]
Mamta A. Satoor commented on DERBY-5337:
----------------------------------------
With the given information, we have not been able to reproduce the bug. The problem may be with the import data file not having enough columns per row to match the table columns.
> Encountering error when importing to table using CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE
> -----------------------------------------------------------------------------------
>
> Key: DERBY-5337
> URL: https://issues.apache.org/jira/browse/DERBY-5337
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.8.1.2
> Environment: 3GB RAM, Windows XP SP3, Core i-5
> Reporter: Ranjit Aneesh
>
> I am encountering the following issue when trying to call CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE.
> I am passing the schema name as has been pointed out as a possible cause conflicting with multiple tables with the same name.
> The actual error is :
> CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE('DBA', 'TEST', 'C:/temp/unload/704.dat', ',', '"', 'UTF-8',0)
> The exception 'java.sql.SQLException: Column 'COLUMN2' is either not in any table in the FROM list or appears within a join specification and is outside the scope of the join specification or appears in a HAVING clause and is not in the GROUP BY list. If this is a CREATE or ALTER TABLE statement then 'COLUMN2' is not a column in the target table.' was thrown while evaluating an expression.
> This issue I am encountering in the 10.8.1.2 version of derby. I am using embedded driver
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira