Exception when trying to use 1-char long table name (or bug in ojdbc?)

Question

Hello,
I`ve got exception while trying to prepare SQL statement using "prepareStatement(String sql, String columnNames[])"
Please have a look at the following test
        Connection con = null;
        String tblName = "k";
        try
            Class.forName("oracle.jdbc.driver.OracleDriver");
            con = DriverManager.getConnection("jdbc:oracle:thin:@oracle:1521:server", "usr", "passwd");
            con.prepareStatement("create table "+tblName+"(id number primary key)").execute();
            PreparedStatement stmt = con.prepareStatement("insert into "+tblName+"(id) VALUES (?)", new String[] {"id"});
            stmt.setInt(1, 1);
            stmt.executeUpdate();
        catch (Exception e)
            e.printStackTrace();
        finally
            try
                con.prepareStatement("drop table " + tblName).execute();
                con.close();
            catch (SQLException e)
                e.printStackTrace();
        }The result of the above is the following stacktrace:
java.sql.SQLException: Invalid argument(s) in call
     at oracle.jdbc.driver.AutoKeyInfo.getTableName(AutoKeyInfo.java:252)
     at oracle.jdbc.driver.T4CConnection.doDescribeTable(T4CConnection.java:3640)
     at oracle.jdbc.driver.PhysicalConnection.prepareStatement(PhysicalConnection.java:6427)
     at X.tst(X.java:22)
     at X.main(X.java:46)Now, if I change tblName to be kk (two characters long), it runs with no exceptions.
Has anyone ever faced the same problem?
Looks like a bug in JDBC driver... Or may be it is a known issue which I`m now aware of.
p.s. I`m using Oracle JDBC v. 11.2.0.1.0.

Answer 1

Well... this is definitelly not a requirement.
The code snippet came from the test (junit) for something which is much bigger. And of course the 1-char long table name has nothing to do with desing. At all.
We have a system where a user defines (named) xml structures, so to say. The structures are then "translated" into DB entities. So the result DB schema is fully auto-generated. The system supports 4 different SQL dialects. Oracle is just one of them.
Having restrictions like "name of a structure must be at least two characters" is no problem. But I still can`t believe Oracle has such a limitation. It does not sound logical (to me at least). And I had a hope may be someone has an explanation for that thing.
The code above works just fine if I do not request certain columns back after the statement is executed. (e.g. without the second parameter).
But anyway... I would post a bug for this, if I knew where to post it to :)
Thanks.