Move to correct component.

Tried connecting to an Oracle Express database using the same steps and it
returned a list of a bunch of tables all of which were grayed out.  If I can
figure out how, I will post the screenshot.

Created attachment 30776 [details]
Screenshot trying to connected to an Oracle Express (XE) database

The grayed out tables issue is a result of the schema capture's failure to
retrieve the primary keys for the tables which I too am experiencing.  I use
both  MySQL datasources and Oracle 10g, and the problem only occurs with Oracle
(using the same driver as listed in gatep5's original post).  This seems to be a
seperate issue from the original issue posted and should IMO have its own issue
number.

Please try again with the latest daily build. More information will be displayed
in the "Retrieving the database schema" dialog -- the names of the tables and so
on. How many tables do you have in the database? How many of them are retrieved
when the exception occurs? What is your maximum heap size? Does increasing it help?

On the missing primary keys issue:  The problem is a permissions issue in a
round-a-bout fashion.  Even though you can get the primary keys from the JDBC
driver in Oracle via getPrimaryKeys, you must have the "ANALYZE ANY" permission
to call getIndexInfo on the DatabaseMetaData object.  Net beans uses the results
of getIndexInfo() to iterate through indexes looking for primary keys.  Because
it throws an exception listing the indexes without the "ANALYZE ANY" perm, it
never looks for the primary keys.  The work around is to ensure that the jdbc
connection account has the ANALYZE ANY permission.  IMO, this is an Oracle thin
JDBC bug as I cannot see any reason for escalating the user perms just to
enumerate the indices, but I'm no Oracle expert and that appears to be the way
it works.  Strangely granting the index permission on the table is insufficient.

Thank you for the info. The foreign keys problem is also filed as issue 78614. I
tried reproducing the problem with the script attached with that issue. I
created a new user specifically for this and granted it only the CONNECT and
RESOURCE roles (I believe none of them includes ANALYZE ANY). Still, I wasn't
able to reproduce the issue.

However, "ANALYZE ALL" reminds me of an issue in the Database Explorer caused by
the Oracle driver trying to execute the ANALYZE TABLE statement when calling
getIndexInfo(). The issue was caused by passing false as the approximate
parameter of this method. It was fixed in the Database Explorer, but dbschema
still passes false. I will change it to true, let's see if it helps.

Passing true instead of false for approximate.

Checking in src/org/netbeans/modules/dbschema/jdbcimpl/TableElementImpl.java;
/cvs/db/model/src/org/netbeans/modules/dbschema/jdbcimpl/TableElementImpl.java,v
 <--  TableElementImpl.java
new revision: 1.2.50.2; previous revision: 1.2.50.1
done

Created attachment 31684 [details]
dbschema module passing true for approximate

Since I don't know the date of the next daily build I attached the fixed
dbschema module. Please copy it to <netbeans>/enterprise3/modules and test.

perrych2: I took the liberty to add you to the CC so you can test it too if you
can. 

Thanks.

I gave the supplied jar a try and observed no change when the "ANALYZE ANY"
system privilege was removed.  The following code snippet comes from a test for
this issue (independant of netbeans):

boolean approximate = false;
boolean unique = false;
Connection conn = DriverManager.getConnection(connection, user, password);
DatabaseMetaData dmd = conn.getMetaData();
ResultSet indexrs =
dmd.getIndexInfo("","TESTSCHEMA","TESTTABLE",unique,approximate);

For any combination of values for approximate and unique where the user does not
have the "ANALYZE ANY" system privilege the following exception is thrown for
dmd.getIndexInfo:

java.sql.SQLException: ORA-01031: insufficient privileges

Interestingly though dmd.getPrimaryKeys, dmd.getImportedKeys, and
dmd.getExportedKeys do not throw an exception without the "ANALYZE ANY" system
privilege.  This is clearly a result of getIndexInfo() calling ANALYZE TABLE or
some such as you stated.  My guess is that it is because getIndexInfo includes
statistical information, where as the above 3 do not.  I am guessing from this
that there is no workaround for this that will result in a complete schema
implementation without granting "ANALYZE ANY" to the connection user.

The original problem that I described in this bug report seems to now be fixed
with the lastest daily build. I am able to see all the tables in my Oracle
database and successfully create the entity objects using the Netbeans wizard. 
Unfortunately, I do not know what really was changed inorder for this to be fixed.

gatep5: just to be sure: do you mean the OutOfMemoryError by "original problem"
or the tables being grayed out?

This problem must have been user error in setting up the Oracle database.  I
have since tried the daily build from June 29, 2006 as well as Netbeans Beta 1
and did not have any problems connecting and retreiving the database schema
(There were no OutOfMemory errors.)  I have tried builds with dates later than
that and they seem to work as well.  I realize that the grayed out tables that I
showed from the screen shot posted are grayed out because they don't have
primary keys set, so I don't consider that an issue that needs to be fixed.  My
apologies for wasting your time.

As far as the other person that is CCed on this bug report, I have not tried or
experienced the problems that he/she has and cannot provide any useful feedback
for that issue.  

The issue that I experienced with not finding primary keys was in fact due to
the missing analyze any privilege.  I later found in the Sun Java Application
Server documentation a footnote that the Analyze Any privilege is required for
exactly the same reason.  While I disagree that this privilege should be
required, it really doesn't have anything to do with Netbeans and I wouldn't
consider it an NB bug.  The issue is resolved from my perspective.

gatep5: good to hear, thanks. I take it there are no more problems from your
point of view (as far as this issue is concerned).

perrych2: I just (independently) also read in the docs of the Sun appserver that
the ANALYZE ANY privilege is needed for tables not in a schema owned by the user
connecting to the database. Is this your case? If yes then I can reproduce the
issue now. Actually, only when commenting out the fix of issue 56492, which
causes the missing indexes to be ignored, so the foreign keys are retrieved
correctly even if the "insufficient privileges" SQLException is thrown.

I guess this also fixes your use case. Note, however, that the fix of issue
56492 is not in beta 2.

Marking as fixed then.