luciddb-users

Re: Lucid Indexes

5 messages

Tom Barber

Re: Lucid Indexes

Reply Threaded

Some javascript/style in this post has been disabled (why?)

Er yeah, my bad, I thought PDI was executing a analyze command, but I was wrong.

Anyway other indexing issues, I moved my lucid install from one place to another(I dunno if its relevant or not, this was a month or so ago), and it been running fine until I try to add some indexes but one on certain columns, anyway it returns this:

Error: Internal error: Assertion `isSingleton(inputTuple)' failed at line 944 in file /root/open/dev/fennel/lucidera/bitmap/LbmEntry.cpp

Did i break it? :)

Whats going on?

Cheers

Tom

On Mon 24/08/09 7:04 PM , Francisco Reyes [hidden email] sent:

[hidden email] writes:

> And this:
>
> explain plan for Select

One thing worth checking; were the tables analyzed?

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
luciddb-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/luciddb-users

John Sichi

Re: Lucid Indexes

Reply Threaded

Are you using v0.9.1? A bitmap index bug was introduced in there and
since fixed in the codebase but not released yet. Could you reply with
the SQL statement being executed when you hit the assertion below?

I'll start working on an 0.9.2 release now.

JVS

[hidden email] wrote:

> Anyway other indexing issues, I moved my lucid install from one place to
> another(I dunno if its relevant or not, this was a month or so ago), and
> it been running fine until I try to add some indexes but one on certain
> columns, anyway it returns this:
>
> Error: Internal error: Assertion `isSingleton(inputTuple)' failed at
> line 944 in file /root/open/dev/fennel/lucidera/bitmap/LbmEntry.cpp
>
> Did i break it? :)
>
> Whats going on?
>
> Cheers
>
> Tom

John Sichi

Re: Lucid Indexes

Reply Threaded

In reply to this post by Tom Barber

[hidden email] wrote:
>
> yeah it is 0.9.1, all I did was
> create index f_salesledger_stat_idx on OPEN_ACCOUNTS.F_SALESLEDGER(STAT);
>
> it happened on a couple of cols, and not on the rest, I thought maybe it
> was a certain data type but it happened both on varchar and int column
> types, so at that point I gave up :)

Since I'm not sure whether the fixes in 0.9.2 are relevant, here are the
recommended steps:

1) Take a cold backup of your database.

2) Execute ALTER TABLE OPEN_ACCOUNTS.F_SALESLEDGER REBUILD;

3) Assuming step 2 succeeds, retry your CREATE INDEX statement and see
if it works now.

Let me know what happens; even if that fixes it, the underlying problem
will still need to be tracked down so it doesn't keep happening.

JVS

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
luciddb-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/luciddb-users

Tom Barber

Re: Lucid Indexes

Reply Threaded

In reply to this post by Tom Barber

Some javascript/style in this post has been disabled (why?)

Still broken I'm afraid

Sep 7, 2009 9:35:56 AM net.sf.farrago.db.FarragoDbSession prepare
INFO: create index f_salesledger_stat_idx on OPEN_ACCOUNTS.F_SALESLEDGER(STAT)
Sep 7, 2009 9:35:56 AM net.sf.farrago.db.FarragoDbSession commitImpl
INFO: commit
Sep 7, 2009 9:35:57 AM net.sf.farrago.db.FarragoDbStmtContext cancel
INFO: cancel
Sep 7, 2009 9:35:58 AM org.eigenbase.util.EigenbaseException <init>
SEVERE: org.eigenbase.util.EigenbaseException: Internal error: Assertion `isSingleton(inputTuple)' failed at line 944 in file /root/open/dev/fennel/lucidera/bitmap/LbmEntry.cpp
Sep 7, 2009 9:35:58 AM net.sf.farrago.jdbc.FarragoJdbcUtil newSqlException
SEVERE: error while fetching from cursor
Sep 7, 2009 9:35:58 AM net.sf.farrago.jdbc.FarragoJdbcUtil newSqlException
SEVERE: Internal error: Assertion `isSingleton(inputTuple)' failed at line 944 in file /root/open/dev/fennel/lucidera/bitmap/LbmEntry.cpp
Sep 7, 2009 9:35:58 AM org.eigenbase.util.EigenbaseException <init>
SEVERE: org.eigenbase.util.EigenbaseException: DML statement execution failed.
Sep 7, 2009 9:35:58 AM org.eigenbase.util.EigenbaseException <init>
SEVERE: org.eigenbase.util.EigenbaseException: Failed while executing internal statement
Sep 7, 2009 9:35:58 AM net.sf.farrago.db.FarragoDbStmtContext cancel
INFO: cancel
Sep 7, 2009 9:35:58 AM net.sf.farrago.db.FarragoDbSession rollbackImpl
INFO: rollback
Sep 7, 2009 9:35:58 AM net.sf.farrago.jdbc.FarragoJdbcUtil newSqlException
SEVERE: Failed while executing internal statement
Sep 7, 2009 9:35:58 AM net.sf.farrago.jdbc.FarragoJdbcUtil newSqlException
SEVERE: DML statement execution failed.
Sep 7, 2009 9:35:58 AM net.sf.farrago.jdbc.FarragoJdbcUtil newSqlException
SEVERE: Internal error: Assertion `isSingleton(inputTuple)' failed at line 944 in file /root/open/dev/fennel/lucidera/bitmap/LbmEntry.cpp
Sep 7, 2009 9:35:58 AM net.sf.farrago.db.FarragoDbStmtContext cancel
INFO: cancel
Sep 7, 2009 9:35:58 AM net.sf.farrago.db.FarragoDbStmtContext cancel
INFO: cancel

Thats the log stack if its of any use.

Tom

On Fri 4/09/09 7:40 PM , "John V. Sichi" [hidden email] sent:

tom@... wrote:
>
> yeah it is 0.9.1, all I did was
> create index f_salesledger_stat_idx on OPEN_ACCOUNTS.F_SALESLEDGER(STAT);
>
> it happened on a couple of cols, and not on the rest, I thought maybe it
> was a certain data type but it happened both on varchar and int column
> types, so at that point I gave up :)

Since I'm not sure whether the fixes in 0.9.2 are relevant, here are the
recommended steps:

1) Take a cold backup of your database.

2) Execute ALTER TABLE OPEN_ACCOUNTS.F_SALESLEDGER REBUILD;

3) Assuming step 2 succeeds, retry your CREATE INDEX statement and see
if it works now.

Let me know what happens; even if that fixes it, the underlying problem
will still need to be tracked down so it doesn't keep happening.

JVS

John Sichi

Re: Lucid Indexes

Reply Threaded

Thanks Tom...I'll contact you privately to see if there's a way we can
get access to your data in order to reproduce the problem.

JVS

[hidden email] wrote:

> Still broken I'm afraid
>
>
> Sep 7, 2009 9:35:56 AM net.sf.farrago.db.FarragoDbSession prepare
> INFO: create index f_salesledger_stat_idx on
> OPEN_ACCOUNTS.F_SALESLEDGER(STAT)
> Sep 7, 2009 9:35:56 AM net.sf.farrago.db.FarragoDbSession commitImpl
> INFO: commit
> Sep 7, 2009 9:35:57 AM net.sf.farrago.db.FarragoDbStmtContext cancel
> INFO: cancel
> Sep 7, 2009 9:35:58 AM org.eigenbase.util.EigenbaseException <init>
> SEVERE: org.eigenbase.util.EigenbaseException: Internal error:
> Assertion `isSingleton(inputTuple)' failed at line 944 in file
> /root/open/dev/fennel/lucidera/bitmap/LbmEntry.cpp
> Sep 7, 2009 9:35:58 AM net.sf.farrago.jdbc.FarragoJdbcUtil newSqlException
> SEVERE: error while fetching from cursor
> Sep 7, 2009 9:35:58 AM net.sf.farrago.jdbc.FarragoJdbcUtil newSqlException
> SEVERE: Internal error: Assertion `isSingleton(inputTuple)' failed at
> line 944 in file /root/open/dev/fennel/lucidera/bitmap/LbmEntry.cpp
> Sep 7, 2009 9:35:58 AM org.eigenbase.util.EigenbaseException <init>
> SEVERE: org.eigenbase.util.EigenbaseException: DML statement execution
> failed.
> Sep 7, 2009 9:35:58 AM org.eigenbase.util.EigenbaseException <init>
> SEVERE: org.eigenbase.util.EigenbaseException: Failed while executing
> internal statement
> Sep 7, 2009 9:35:58 AM net.sf.farrago.db.FarragoDbStmtContext cancel
> INFO: cancel
> Sep 7, 2009 9:35:58 AM net.sf.farrago.db.FarragoDbSession rollbackImpl
> INFO: rollback
> Sep 7, 2009 9:35:58 AM net.sf.farrago.jdbc.FarragoJdbcUtil newSqlException
> SEVERE: Failed while executing internal statement
> Sep 7, 2009 9:35:58 AM net.sf.farrago.jdbc.FarragoJdbcUtil newSqlException
> SEVERE: DML statement execution failed.
> Sep 7, 2009 9:35:58 AM net.sf.farrago.jdbc.FarragoJdbcUtil newSqlException
> SEVERE: Internal error: Assertion `isSingleton(inputTuple)' failed at
> line 944 in file /root/open/dev/fennel/lucidera/bitmap/LbmEntry.cpp
> Sep 7, 2009 9:35:58 AM net.sf.farrago.db.FarragoDbStmtContext cancel
> INFO: cancel
> Sep 7, 2009 9:35:58 AM net.sf.farrago.db.FarragoDbStmtContext cancel
> INFO: cancel
>
>
> Thats the log stack if its of any use.
>
> Tom
>
>
> On Fri 4/09/09 7:40 PM , "John V. Sichi" [hidden email] sent:
>
> [hidden email]
> <javascript:top.opencompose('[hidden email]','','','')> wrote:
> >
> > yeah it is 0.9.1, all I did was
> > create index f_salesledger_stat_idx on
> OPEN_ACCOUNTS.F_SALESLEDGER(STAT);
> >
> > it happened on a couple of cols, and not on the rest, I thought
> maybe it
> > was a certain data type but it happened both on varchar and int
> column
> > types, so at that point I gave up :)
>
> Since I'm not sure whether the fixes in 0.9.2 are relevant, here are
> the
> recommended steps:
>
> 1) Take a cold backup of your database.
>
> 2) Execute ALTER TABLE OPEN_ACCOUNTS.F_SALESLEDGER REBUILD;
>
> 3) Assuming step 2 succeeds, retry your CREATE INDEX statement and see
> if it works now.
>
> Let me know what happens; even if that fixes it, the underlying problem
> will still need to be tracked down so it doesn't keep happening.
>
> JVS
>
>