db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh" <drem...@gmail.com>
Subject Re: [jira] Created: (DERBY-1435) Conglomerate does not exist occurs in a specific case after dropping a table referenced by a trigger
Date Mon, 17 Jul 2006 15:28:46 GMT
On 7/17/06, Rob Scheepens <schr@oce.nl> wrote:
> Goodmorning all,
>
> I am also experiencing the conglomerate not found issue.
> I use Quartz to trigger a task that will perform some actions (See below
> for the stack trace).
>
> The thread that I have read is especially interested in reproducing these
> issues.
> But I also want to know if you all have a solution for this problem that I
> can try?
>
> Will derby.language.statementCacheSize=0 be sufficient?
>

On looking at the stack trace, this does not look like the scenario
described in DERBY-1435 which is a specific case where this error
(conglomerate does not exist) can occur. To see if it is a similar
case, can you please provide the details of the task you are trying to
execute using Quartz? It would be helpful to see the database schema,
sql/jdbc program being executed.

Thanks,
Deepa

Mime
View raw message