GNOME Bugzilla – Bug 96810
Seg. Fault after Table Analysis On Oracle
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-db Severity: critical Version: 0.8.199 Synopsis: Seg. Fault after Table Analysis On Oracle Bugzilla-Product: gnome-db Bugzilla-Component: frontend BugBuddy-GnomeVersion: 2.0 (2.0.3) Description: Description of Problem: After connecting to a database with the Oracle provider, the table analysis takes quite a long time, and prints: ** (mergeant:14460): CRITICAL **: file gda-row.c: line 155 (gda_row_get_value): assertion `num >= 0 && num < row->nfields' failed A LOT, perhaps once per table, but probably more. Immediately after the table analysis completes, teh following messages are printed: ** (mergeant:14460): CRITICAL **: file gda-value.c: line 658 (gda_value_is_null): assertion `value != NULL' failed ** (mergeant:14460): CRITICAL **: file gda-value.c: line 1475 (gda_value_stringify): assertion `value != NULL' failed And the seg. fault message appears. Steps to reproduce the problem: 1. Create Oracle datasource 2. Connect to datasource Actual Results: Seg. fault. Expected Results: Successful analysis How often does this happen? Every time. Tried on a few different databases, same results. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/mergeant' (no debugging symbols found)...[New Thread 8192 (LWP 14460)] 0x420ae169 in wait4 () from /lib/i686/libc.so.6
+ Trace 29394
Thread 1 (Thread 8192 (LWP 14460))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-10-25 12:10 ------- The original reporter (dan@wellogic.com) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, rodrigo@gnome-db.org.
This should be fixed in CVS. Please test it as soon as you can, and re-open the bug if it's not fixed for you.
I'm now getting an error 923: ORA-00923: FROM keyword not found where expected while do aggregates analysis.
yes, missing commas in the SQL command, my fault. Now should be fixed. Reopen again if not.