This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 185245 - [69cat] NullPointerException at oracle.jdbc.driver.T4C8Oall.getNumRows
Summary: [69cat] NullPointerException at oracle.jdbc.driver.T4C8Oall.getNumRows
Status: RESOLVED INCOMPLETE
Alias: None
Product: db
Classification: Unclassified
Component: Show Data (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-29 10:55 UTC by misterm
Modified: 2010-08-13 08:02 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 167629

Attachments
stacktrace (1.05 KB, text/plain)
2010-04-29 10:55 UTC, misterm 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description misterm 2010-04-29 10:55:20 UTC 
Build: NetBeans IDE Dev (Build 100426-6efae8300652)
VM: Java HotSpot(TM) Client VM, 16.2-b04, Java(TM) SE Runtime Environment, 1.6.0_19-b04
OS: Windows 7

Stacktrace: 
java.lang.NullPointerException
   at oracle.jdbc.driver.T4C8Oall.getNumRows(T4C8Oall.java:728)
   at oracle.jdbc.driver.T4CStatement.execute_for_rows(T4CStatement.java:477)
   at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1027)
   at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1515)
   at org.netbeans.modules.db.dataview.output.SQLExecutionHelper.executeSQLStatement(SQLExecutionHelper.java:601)
   at org.netbeans.modules.db.dataview.output.SQLExecutionHelper.initialDataLoad(SQLExecutionHelper.java:110)
Comment 1 misterm 2010-04-29 10:55:25 UTC 
Created attachment 98265 [details]
stacktrace
Comment 2 Jiri Rechtacek 2010-05-03 12:58:11 UTC 
Any steps to reproduce? No clear what caused the NPE. Thanks
Comment 3 misterm 2010-05-03 15:17:01 UTC 
As far as I remember, I was just running an ordinary query on Oracle 9i.
Comment 4 cayel 2010-08-13 08:02:37 UTC 
The stacktrace resembles a known fault in the JDBC driver which occur when a oracle function is call using upper case "CALL" in the statement.

Instead of 
"{ ? = CALL foo(?) }"

change to:
"{ ? = call foo(?) }"

or update JDBC driver.