Actually it is not a bug , that is the expected behavior in version
10.1 after derby-390 fix. table name in the following should be
passed in upper case as TEST1 to the import procedure.
After the derby-390 fix with 208770 patch you mentioned, If you create
a schema, table, or column name as a non-delimited identifier, you
must pass the name to the import procedure using all upper-case
characters. If you created a schema, table, or column name as a
delimited identifier, you must pass the name to the import procedure
using the same case that was used when it was created.
Thanks
-suresht
Delaune, Todd I wrote:
I noticed a problem with the built-in system procedure,
SYSCS_UTIL.SYSCS_IMPORT_TABLE. Under 10.0.2.1 this procedure works fine,
however the new version consistently produces table not found errors. As
you can see below, the table test does exist, however the procedure
doesn't acknolwedge it:
ij> create table test (col integer);
0 rows inserted/updated/deleted
ij> select * from test;
COL
-----------
0 rows selected
ij> call syscs_util.syscs_import_table(null, 'test', 'somefile', null,
null, null, 1);
ERROR XIE0M: Table 'test' does not exist.
I've been unable to find any other reference to this problem. I've
tested it with the old and new versions, using brand new databases, and
consistently the procedure fails only in 10.1.1.0. Perhaps it's related
to the 208770 patch?
(http://www.mail-archive.com/[email protected]/msg06411.html)
Thanks in advance,
Todd Delaune
