Re: Cache Exception for specific parameter values

[John Smith <ja...@gmail.com>]

Personally I think there is some sort of index corruption. I dropped the
table and recreated it and my problem went away.
I never restarted the application and it started to work again.

Maybe you can make a copy of your table, insert the data fresh and point
your app to the copied table. And see if that works. Before doing something
as drastic as I did.

On Fri, Jul 29, 2022 at 9:14 AM <do...@gmx.de> wrote:

> Hi Taras,
>
> attached the extract from the local node log (which is a Ignite client)
> and the remote node log (which is a Ignite server with persistance
> enabled).
>
> What's really strange is that previous value "IDX_STAGE_308" seems to be
> the root cause? This is a value in column UCID but it's not related to
> the current search, except that of course the H2 DB must search through
> this column. Maybe there is invalid characters in the index from data
> rows from a few days ago? Maybe the index is broken? Why would it only
> show when this specific query is executed?
>
> Please let me know your thoughts.
>
> Thanks,
> Thomas.
>
>
> Am 29.07.2022 um 12:48 schrieb Taras Ledkov:
> > Hi,
> >
> > Could you provide the original exception from the map node?
> > It must be available at the log files of the map node.
>

Re: Cache Exception for specific parameter values

[John Smith <ja...@gmail.com>]

The only other thing I can think of is that I did an upgrade to 2.12.0

On Thu, Aug 4, 2022 at 12:52 PM John Smith <ja...@gmail.com> wrote:

> Personally I think there is some sort of index corruption. I dropped the
> table and recreated it and my problem went away.
> I never restarted the application and it started to work again.
>
> Maybe you can make a copy of your table, insert the data fresh and point
> your app to the copied table. And see if that works. Before doing something
> as drastic as I did.
>
> On Fri, Jul 29, 2022 at 9:14 AM <do...@gmx.de> wrote:
>
>> Hi Taras,
>>
>> attached the extract from the local node log (which is a Ignite client)
>> and the remote node log (which is a Ignite server with persistance
>> enabled).
>>
>> What's really strange is that previous value "IDX_STAGE_308" seems to be
>> the root cause? This is a value in column UCID but it's not related to
>> the current search, except that of course the H2 DB must search through
>> this column. Maybe there is invalid characters in the index from data
>> rows from a few days ago? Maybe the index is broken? Why would it only
>> show when this specific query is executed?
>>
>> Please let me know your thoughts.
>>
>> Thanks,
>> Thomas.
>>
>>
>> Am 29.07.2022 um 12:48 schrieb Taras Ledkov:
>> > Hi,
>> >
>> > Could you provide the original exception from the map node?
>> > It must be available at the log files of the map node.
>>
>