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 163822 - [67cat] java.sql.SQLException: OALL8 is in an inconsistent state.
Summary: [67cat] java.sql.SQLException: OALL8 is in an inconsistent state.
Status: RESOLVED WORKSFORME
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jiri Rechtacek
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-27 22:33 UTC by misterm
Modified: 2009-09-18 11:00 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 150177


Attachments
stacktrace (2.47 KB, text/plain)
2009-04-27 22:34 UTC, misterm
Details

Note You need to log in before you can comment on or make changes to this bug.
Description misterm 2009-04-27 22:33:56 UTC
Build: NetBeans IDE Dev (Build 090424)
VM: Java HotSpot(TM) Client VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_04-b12
OS: Windows XP, 5.1, x86

User Comments:
misterm: Just selecting a connection in a SQL Command view before running a few DML instructions



Stacktrace: 
org.netbeans.modules.db.metadata.model.api.MetadataModelException: org.netbeans.modules.db.metadata.model.api.MetadataException: java.sql.SQLException: OALL8 is in an inconsistent state.
        at org.netbeans.modules.db.metadata.model.JDBCConnMetadataModel.runReadAction(JDBCConnMetadataModel.java:99)
        at org.netbeans.modules.db.metadata.model.api.MetadataModel.runReadAction(MetadataModel.java:89)
        at org.netbeans.modules.db.explorer.node.SchemaNodeProvider.initialize(SchemaNodeProvider.java:97)
        at org.netbeans.api.db.explorer.node.NodeProvider.getNodes(NodeProvider.java:103)
        at org.netbeans.modules.db.explorer.node.NodeRegistry.getNodes(NodeRegistry.java:149)
        at org.netbeans.api.db.explorer.node.NodeProvider.getNodes(NodeProvider.java:113)
Comment 1 misterm 2009-04-27 22:34:03 UTC
Created attachment 81016 [details]
stacktrace
Comment 2 Jiri Rechtacek 2009-04-30 15:31:43 UTC
Caused by some problem on DB server side - OALL8 is in an inconsistent state.
Comment 3 Jiri Rechtacek 2009-09-18 11:00:19 UTC
Just once report, I supposed the problem disappeared itself.