Re: Possible variation on "Invalid name pattern" exception

I'll follow-up and close my own thread. It turns out that it was was programmer error, and the Oracle JDBC driver cheerfully assists me in hanging myself.

In my configuration file for the DataSource, I was accidentally supplying my username with an extra space at the end. Oddly enough, Oracle allows me to log in with this username without complaint, as though the driver is trimming the username before it uses it. However, it uses the "bad" version when setting up the namespace. Seems to me like it ought to quietly fix it in both areas or neither.

Rob

RobSeegel_at_aol.com (Rob Seegel) wrote in message
> I have a TYPE called NAME_LIST which is a VARRAY(20) OF VARCHAR2(25),
> which is created outside of any packages. I CAN successfully create an
> ArrayDescriptor when I qualify the NAME_LIST with the User name, like
> so:
>
> ArrayDescriptor ad =
> ArrayDescriptor.createDescriptor("RCSEEGE.NAME_LIST", connection);
>
> However, when I do the following:
>
> ArrayDescriptor ad =
> ArrayDescriptor.createDescriptor("NAME_LIST", connection);
>
> I get a SQLException with "Invalid name pattern: RCSEEGE .NAME_LIST"
>
> Note the space between RCSEEGE and .NAME_LIST - it's as though there's
> a configuration problem (with Oracle?) that's causing it to resolve
> the namespace incorrectly, when I connect to the database.
>
Received on Thu Oct 07 2004 - 08:33:07 CDT